Skip to content
SkillModel-led1,333 tokens in use

save

Saves only the answer, decision or insight you select from a conversation into an Obsidian vault, as one reviewed transaction.

16,653 stars on the repository MIT LicenseAgriciDaniel/claude-obsidian · skills/save
claude plugin marketplace add AgriciDaniel/claude-obsidian claude plugin install claude-obsidian@agricidaniel-claude-obsidian
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing save costs

79tokens idle
1,333tokens in use

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

shelldetected

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Good
  • Frontmatter12/15
  • Structure17/25
  • Examples9/15
  • Output15/15
  • Size10/15
  • Resources10/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent
  • Runs shell commands−5

    does this on the machine, and the frontmatter does not say so

    SKILL.md, line 27

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Good
  • Development activity84
  • Maintenance100
  • Community56
  • Maturity28
  • Momentum40

save files the part of a conversation you choose as a note in your Obsidian vault. It never runs on its own and never archives a whole transcript. It looks for an existing note first, drafts the smallest useful note type, and shows the title, destination and changed paths before applying.

One transaction writes the note together with the index entry, a new log entry and a refreshed hot cache, so the vault stays navigable.

What You Get

  • A new or updated note in the vault limited to the scope you selected
  • An index entry, a top-of-file log entry and a hot cache under 500 words
  • Source and claim ledger updates only when evidence changed
  • A preview of title, destination and create or replace modes
  • An operation ID and exact changed paths after apply

Common Use Cases

  • Keeping a good answer from a research chat as a question note
  • Recording a decision and its reasoning in the vault
  • Saving a session summary you approved

What Makes It Unique

It saves on request only, in the scope selected, and uses the transaction engine so the note, index, log and hot cache land together or not at all. It asks before replacing an existing canonical note, supports a no-op when the content is already represented, and refuses to invent quotes or sources.

Under The Hood

The skill is instructions that point to the plugin’s transaction and provenance references. It needs no network access. It runs the plugin’s Python core script through the shell to inspect a workflow bundle and apply it with the approved plan hash, and that step is the only thing that writes to the vault. A Git checkpoint is a separate command run only when you ask. Host file write tools are not used for vault changes.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers