Promote
Promote a durable insight from a raw capture into the curated notes/ layer. Trigger when the user approves keeping an insight ("promote that", "save that as a note", "add that to the wiki") or accepts your offer after an answer.From its SKILL.md
npx -y skills add jdiazromeral/tars --skill promoteAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 29 days oldThe repository was created 29 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.3 KB, 266 tokens by cl100k_base, as published. Nobody here has run it
Promote an insight
Vault house rules. Before acting, read
$TARS_HOME/AGENTS.mdif it exists and honor it — per-vault rules there (source allowlists, tone, privacy, output layout) override this skill's defaults on conflict.
Promotion is deliberate and rare — notes/ stays small and high-signal (decisions, rationale, concepts). Never bulk-promote.
- Confirm the exact insight wording with the user if you haven't already.
tars promote <doc_id> --title "<title>"— creates the note skeleton with provenance frontmatter and prints its path.- Edit the created file: replace the placeholder with the distilled insight
(a few sentences to a few paragraphs, not a dump of the source). Link the
concepts it belongs to (
[[<concept-slug>]]) and related notes — checkwiki/concepts/andwiki/notes/for candidates. Keep the generatedSource: [[…]]line — it's the Obsidian backlink to the raw capture. - Add the note under
## Noteson each linked concept's hub page. - Show the user the final note content.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.