Curate
Curate improves the existing knowledge surface. The agent reads the notes, identifies their
distinct contributions and edits the smallest useful scope. A cleaner note does not establish
learner understanding or stronger evidence for a claim.
Resolve scope
Use the obsidian skill to resolve the vault and load its contract before any mutation.
Read Resources/Vault Layout.json when present; its paths own placement. In local vault mode,
use file tools. Otherwise use the governed Obsidian tools and their contract gate.
Use direct read, edit and write operations for routine note work. Machine policy can
automatically grant Markdown edits inside the configured vault. This is not a grant for compound
shell commands, arbitrary scripts or changes outside that root. Keep a read of the original
content for comparison; do not introduce temporary shell backups or mandatory prose-linter
commands for ordinary curation. Use an existing diff when available. If a genuine operation
needs permission, respect the gate and explain it; never retry a denied or deferred operation
through another tool. Technical permission prompts and content decisions are separate.
Start from the selected note and its directly linked active notes, including backlinks. A
topic request first resolves to one existing anchor note. If no unambiguous anchor exists,
ask for the note to curate. Do not create a topic just to obtain an anchor. Read related notes
only as needed to understand ownership and overlap. Do not traverse their links recursively
or turn the request into whole-vault cleanup. A source summary or exercise is a valid anchor.
Vault rules, session logs and .archive/ are outside the editable scope.
Use the supplied desired outcome and time budget. Without a budget, perform one bounded pass
on the anchor and the directly related notes needed for it; ask only when scope is ambiguous.
Structural findings supplied by Learn are leads to re-check against current files, not authority
to move or rewrite notes.
Inspect, propose, apply
- Read the full anchor, relevant neighbors and sources already available in scope. Search
titles, aliases and paraphrases across the active folders before creating an extracted note
or selecting a canonical owner. Distinguish repetition from a different premise, use case,
disagreement, example or uncertainty.
- State the concrete improvement and affected notes. Apply clear wording reductions, metadata
repairs and explanatory links within the requested scope directly. Starting Curate authorizes
these routine edits; do not turn the sitting into an inspection-only proposal. Correcting stale
framing, separating note quality from mastery, clarifying archived-source labels and linking
an existing pending request are routine when the underlying facts and curriculum stay unchanged.
A substantial rewrite changes the note's argument, coverage or ownership, not merely several
sentences. For a merge, deletion,
move, split or substantial rewrite, show the proposed owner, destination, preserved material
and affected links before asking for approval. Existing approval applies only to its named
changes; do not repeatedly ask for it. Prepare the full proposal before asking.
In the Learn sidebar, ask necessary approval questions as plain text in this chat and wait
for the reply. Do not call
ask, queue a decision or send the owner to /decisions: RPC
ask currently defers to the terminal queue. Show the exact proposal followed by one direct
approval question. Continue independently authorized edits while approval is pending. A pending
proposal must not block routine corrections elsewhere in the requested scope.
- Edit only the approved scope. Re-read each file immediately before changing it and preserve
concurrent edits. Remove repetition and stale scaffolding, while retaining every distinct
idea, caveat, counterexample, attribution and source. A shorter note is useful only if the
reasoning remains reconstructable. Leave useful material alone when there is no improvement.
- Link where the relationship helps reasoning: prerequisite, explanation, implication,
application or disagreement. Prefer a sentence explaining the relationship over an unrelated
links list. Do not pursue a link count. Several learning paths share one canonical concept.
- Extract source-independent explanations into Knowledge and keep source-specific summaries
in Resources. Keep provenance attached to the statements it supports. Split only when the
ideas can stand on their own; preserve discoverability from the original note. Use existing
topic maps before making another and follow the contract's folder threshold.
Do not silently resolve factual conflicts. Preserve the competing statements and their sources,
or verify the disputed point before changing it. Do not upgrade status: verified or maturity
just because prose improved. Do not create taught claims, rewrite ## Because arguments in a
way that changes their meaning, or change learning-path node states. Preserve existing progress
when repairing links or restructuring a path. Do not manufacture a learning session log entry.
For approved moves, use Obsidian's link-aware file manager when available. If only local file
tools are available, map incoming links, relative links and figure paths first, update them
together, and verify the result. Never overwrite an existing destination. Merges preserve all
distinct content in the canonical owner and retain an alias or redirect when needed. Use a
recoverable removal mechanism; otherwise leave the superseded note and report pending removal.
Close
An explicit stop ends editing without another approval round. Save only already-authorized work.
- Re-read the edited files. Compare before and after for lost qualifications, source mappings,
changed arguments and accidental progress changes. Check required metadata, valid frontmatter
at the beginning of each note, placement, resolved links, headings and figure paths.
- Re-run the scoped structural checks against current files. The Learn command Check vault
structure checks placement, metadata and unresolved wikilinks; it does not assess meaning.
Without the command, perform those checks with the available file or Obsidian tools.
- Report the changed files and why, unresolved conflicts or proposals, and checks that actually
ran. Mark UI rendering as unverified when it was not inspected. Store a durable pending issue
beside its relevant content only when it is useful; do not create an administration note or
duplicate session transcript. Never report an unapproved proposal as applied.
- A failed required write or integrity check prevents a successful close. Report the exact
remaining problem. A deliberate no-op can close successfully when nothing needed changing.
1---2name: curate3description: Improve existing Obsidian knowledge notes by slimming repetition, connecting ideas, extracting reusable explanations and consolidating overlap. Use for a curation sitting on a note, topic cluster or learning path. Do not use to teach or assess understanding, run practice, bulk-rewrite the vault or automatically restore archived notes.4metadata:5 source: https://skillmd.com/skills/larsboes/curate6---78# Curate910Curate improves the existing knowledge surface. The agent reads the notes, identifies their11distinct contributions and edits the smallest useful scope. A cleaner note does not establish12learner understanding or stronger evidence for a claim.1314## Resolve scope1516Use the `obsidian` skill to resolve the vault and load its contract before any mutation.17Read `Resources/Vault Layout.json` when present; its paths own placement. In local vault mode,18use file tools. Otherwise use the governed Obsidian tools and their contract gate.19Use direct `read`, `edit` and `write` operations for routine note work. Machine policy can20automatically grant Markdown edits inside the configured vault. This is not a grant for compound21shell commands, arbitrary scripts or changes outside that root. Keep a read of the original22content for comparison; do not introduce temporary shell backups or mandatory prose-linter23commands for ordinary curation. Use an existing diff when available. If a genuine operation24needs permission, respect the gate and explain it; never retry a denied or deferred operation25through another tool. Technical permission prompts and content decisions are separate.2627Start from the selected note and its directly linked active notes, including backlinks. A28topic request first resolves to one existing anchor note. If no unambiguous anchor exists,29ask for the note to curate. Do not create a topic just to obtain an anchor. Read related notes30only as needed to understand ownership and overlap. Do not traverse their links recursively31or turn the request into whole-vault cleanup. A source summary or exercise is a valid anchor.32Vault rules, session logs and `.archive/` are outside the editable scope.3334Use the supplied desired outcome and time budget. Without a budget, perform one bounded pass35on the anchor and the directly related notes needed for it; ask only when scope is ambiguous.36Structural findings supplied by Learn are leads to re-check against current files, not authority37to move or rewrite notes.3839## Inspect, propose, apply40411. Read the full anchor, relevant neighbors and sources already available in scope. Search42 titles, aliases and paraphrases across the active folders before creating an extracted note43 or selecting a canonical owner. Distinguish repetition from a different premise, use case,44 disagreement, example or uncertainty.452. State the concrete improvement and affected notes. Apply clear wording reductions, metadata46 repairs and explanatory links within the requested scope directly. Starting Curate authorizes47 these routine edits; do not turn the sitting into an inspection-only proposal. Correcting stale48 framing, separating note quality from mastery, clarifying archived-source labels and linking49 an existing pending request are routine when the underlying facts and curriculum stay unchanged.50 A substantial rewrite changes the note's argument, coverage or ownership, not merely several51 sentences. For a merge, deletion,52 move, split or substantial rewrite, show the proposed owner, destination, preserved material53 and affected links before asking for approval. Existing approval applies only to its named54 changes; do not repeatedly ask for it. Prepare the full proposal before asking.55 In the Learn sidebar, ask necessary approval questions as plain text in this chat and wait56 for the reply. Do not call `ask`, queue a decision or send the owner to `/decisions`: RPC57 `ask` currently defers to the terminal queue. Show the exact proposal followed by one direct58 approval question. Continue independently authorized edits while approval is pending. A pending59 proposal must not block routine corrections elsewhere in the requested scope.603. Edit only the approved scope. Re-read each file immediately before changing it and preserve61 concurrent edits. Remove repetition and stale scaffolding, while retaining every distinct62 idea, caveat, counterexample, attribution and source. A shorter note is useful only if the63 reasoning remains reconstructable. Leave useful material alone when there is no improvement.644. Link where the relationship helps reasoning: prerequisite, explanation, implication,65 application or disagreement. Prefer a sentence explaining the relationship over an unrelated66 links list. Do not pursue a link count. Several learning paths share one canonical concept.675. Extract source-independent explanations into Knowledge and keep source-specific summaries68 in Resources. Keep provenance attached to the statements it supports. Split only when the69 ideas can stand on their own; preserve discoverability from the original note. Use existing70 topic maps before making another and follow the contract's folder threshold.7172Do not silently resolve factual conflicts. Preserve the competing statements and their sources,73or verify the disputed point before changing it. Do not upgrade `status: verified` or `maturity`74just because prose improved. Do not create taught claims, rewrite `## Because` arguments in a75way that changes their meaning, or change learning-path node states. Preserve existing progress76when repairing links or restructuring a path. Do not manufacture a learning session log entry.7778For approved moves, use Obsidian's link-aware file manager when available. If only local file79tools are available, map incoming links, relative links and figure paths first, update them80together, and verify the result. Never overwrite an existing destination. Merges preserve all81distinct content in the canonical owner and retain an alias or redirect when needed. Use a82recoverable removal mechanism; otherwise leave the superseded note and report pending removal.8384## Close8586An explicit stop ends editing without another approval round. Save only already-authorized work.8788- Re-read the edited files. Compare before and after for lost qualifications, source mappings,89 changed arguments and accidental progress changes. Check required metadata, valid frontmatter90 at the beginning of each note, placement, resolved links, headings and figure paths.91- Re-run the scoped structural checks against current files. The Learn command **Check vault92 structure** checks placement, metadata and unresolved wikilinks; it does not assess meaning.93 Without the command, perform those checks with the available file or Obsidian tools.94- Report the changed files and why, unresolved conflicts or proposals, and checks that actually95 ran. Mark UI rendering as unverified when it was not inspected. Store a durable pending issue96 beside its relevant content only when it is useful; do not create an administration note or97 duplicate session transcript. Never report an unapproved proposal as applied.98- A failed required write or integrity check prevents a successful close. Report the exact99 remaining problem. A deliberate no-op can close successfully when nothing needed changing.