wiki-narrate
Turn a wiki topic into a cited Markdown briefing, plain-language explanation, or progressive lecture. Use this skill for topic-based briefing, explanation, and lecture requests that must stay within the evidence compiled in an Obsidian vault.
Install / Use
npx skills add Ar9av/obsidian-wiki --skill wiki-narrateInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Content & MediaSupported Platforms
Our assessment of wiki-narrate
wiki-narrate scores 90/100 on our quality scale, 422nd of 1,153 Content & Media skills we index (top 37%).
Its SKILL.md is 8.6 KB long, well organised into 10 sections with 1 code example: a thorough specification that gives an agent plenty to work with.
With 3,485 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so wiki-narrate is actively maintained.
- Our last check on 2026-10-30 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
wiki-narrate compared with similar skills
All 4 of these similar skills score higher than wiki-narrate; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| wiki-narrate (this skill)by Ar9av | 90 | 3.5k | 54d ago | SKILL.md |
| LocalAIby mudler | 100 | 50.4k | today | MCP Server |
| siyuanby siyuan-note | 100 | 47.3k | today | MCP Server |
| x402by browser-use | 100 | 121.0k | 3d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
Frequently asked questions
- How do I install wiki-narrate?
- Run
npx skills add Ar9av/obsidian-wiki --skill wiki-narrate. The install tabs above show the steps for each supported agent. - Which AI agents does wiki-narrate work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is wiki-narrate safe to use?
- It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is wiki-narrate still maintained?
- The repository was last updated about 2 months ago, so wiki-narrate is actively maintained.
Skill content
View source on GitHubname: wiki-narrate description: > Turn a wiki topic into a cited Markdown briefing, plain-language explanation, or progressive lecture. Use this skill for topic-based briefing, explanation, and lecture requests that must stay within the evidence compiled in an Obsidian vault.
Wiki Narrate — Cited Narrative Readouts
Use this skill only for a topic-based Markdown readout. Do not add tag or page-list selection, prior-query input, voice aliases, HTML, PDF, slides, renderer handoffs, or new compiled knowledge pages.
Command Contract
/wiki-narrate <topic> [--voice briefing|plain-language|lecturer] [--save]
- Require a non-empty
<topic>. - The default voice is
briefing. - Voice names are canonical and case-sensitive. Unsupported values must return an
error listing
briefing,plain-language, andlecturerwithout searching or writing. --saveis the only persistence switch.- For a missing topic, malformed option, or unsupported voice, return a short usage
or validation error and do not search, write, append a log event, or change
hot.md.
Retrieval
Writing profile: Before drafting or rewriting natural-language Markdown, read and apply the Writing Profile Resolution section in llm-wiki/SKILL.md. Framework schema, provenance, safety, and operation-specific requirements take precedence.
WRITING.md preferences apply only to newly drafted or rewritten natural-language Markdown; preserve source content and structured records.
- Resolve configuration with the Config Resolution Protocol, including an inline
@namevault override, then read the target vault'sAGENTS.mdwhen it exists. LoadOBSIDIAN_LINK_FORMATbefore drafting citations. - Read
hot.mdandindex.mdfirst. Select candidates by frontmatter and summary before reading bodies. - When configured, use QMD before
rg; if QMD is absent, unconfigured, or fails, continue with the index andrgpath. Treat QMD output as candidate guidance, not evidence: establish each claim from the allowed vault page itself. - Honor filtered-mode phrases such as "public only", "user-facing", "no internal
content", "as a user would see it", and "exclude internal". Skip pages tagged
visibility/internalorvisibility/piiin that mode: never read, cite, or expose them. - Exclude
_readouts/,_raw/,_archives/,_meta/,index.md,log.md,hot.md, and_insights.mdfrom candidates. - Read matching sections before full pages, and read full pages only when a factual claim cannot otherwise be established. Preserve relevant lifecycle and freshness annotations; do not upgrade a page's trust.
Claim Ledger and Citation Audit
Draft a ledger before prose. Each item contains a claim, supporting [[vault page]]
links, and one status: supported fact, inferred connection, or ambiguous conflict.
When OBSIDIAN_LINK_FORMAT=markdown, render the same supporting page as a standard
Markdown link; otherwise use the vault's [[wikilink]] form.
Ensure every factual sentence has adjacent supporting citations. Mark inferred connections ^[inferred]; mark unresolved conflicts ^[ambiguous]. Never use web knowledge, model memory, or invented examples to close a gap. Omit unsupported claims and name the gap in Coverage. An inference or ambiguity marker supplements, rather than replaces, adjacent citations.
Approved Facts Gate
If $OBSIDIAN_VAULT_PATH/_meta/facts.md exists, read its approved rows before
drafting. They are the claims about the owner and their company that may be repeated
in public. Before returning the readout, pipe the draft through
obsidian-wiki facts check - --vault "$OBSIDIAN_VAULT_PATH" --json:
retired: the sentence uses a claim the owner has retired. Replace it with the current approved fact, or drop it. Never ship a retired claim.unsupported, about the owner or their company (their numbers, customers, rankings, certifications): keep it only if an adjacent vault citation supports it, and list it in## Coverageunder "Not in approved facts". In filtered mode ("public only", "user-facing"), drop it instead.unsupported, about anything else: no action. The check is a heuristic.
If the file is missing or the command is unavailable, skip this gate silently.
Drafting and Output
Read references/voices.md and use exactly the requested voice skeleton. The selected
voice may change prose and ordering, but cannot change the ledger's factual boundary.
Return Markdown only, structured as:
- A title naming the topic and selected voice.
- The selected voice's sections, in its documented order.
- Adjacent citations for each factual sentence, rendered with
OBSIDIAN_LINK_FORMAT. - A
## Coveragefooter listing cited pages, the count of inferred statements, and known evidence gaps.
If evidence is weak or contradictory, produce only the supported portion. Mark each
unresolved conflict ^[ambiguous] with citations to all conflicting pages, and list
the remaining gaps in ## Coverage.
Owner Voice
If $OBSIDIAN_VAULT_PATH/_meta/voice.md exists, read it with
obsidian-wiki voice show --json --vault "$OBSIDIAN_VAULT_PATH" before drafting.
Open a few of the love pages for rhythm and word choice, and skim the hate pages
for what to avoid. The voice file shapes prose only. It never adds a claim the
ledger lacks, and it never changes the selected voice's section skeleton.
Before returning, pipe the draft through obsidian-wiki voice check -. Rewrite every
flagged word or phrase, using the suggested replacement when one is given, and check
again. Quoted source text keeps its original words. If the file is missing or the
command is unavailable, skip this step silently.
Persistence
Present the result by default. For --save, create _readouts/ if necessary and write
_readouts/<slug>.md with title, topic, voice, sources, created, and
updated frontmatter. Use a deterministic, filesystem-safe <slug> derived from the
topic. Save the same completed Markdown readout that was returned in conversation.
A readout is derived output: exclude _readouts/ from retrieval and must not update index.md or .manifest.json. Do not create _readouts/ or a readout file without a successful --save result.
Logging and Hot Cache
After a narration attempt that reaches retrieval, append one WIKI_NARRATE event to
log.md:
obsidian-wiki memory log WIKI_NARRATE \
topic="<topic>" voice=<voice> result_pages=<N> \
mode=<normal|filtered> saved=<true|false> \
outcome=<success|no_match|write_failed>
This is the only write a narration without --save may perform. Do not touch index.md or hot.md by hand.
- Without
--save, append the event withsaved=falseafter returning the readout; do not create a readout or changehot.md. - After a successful
--savewrite, append the event withsaved=true, then refresh the hot cache with a one-line takeaway naming the topic, voice, cited-page count, and saved readout path:obsidian-wiki memory hot --takeaways "<line>".hot.mdchanges only after a successful save, and only through that command. - If the readout write fails after drafting, return the completed readout in
conversation, report that saving failed, append a
WIKI_NARRATEevent withsaved=false outcome=write_failedwhenlog.mdremains writable, and do not updatehot.md. - If appending
log.mdfails, preserve the readout result and report the logging failure separately. Never represent a failed log or save as successful.
Safe Failure Behavior
- No matching pages: explain that the vault lacks material for the topic. Create
no readout file even if
--savewas requested, do not changehot.md, and record aWIKI_NARRATEevent withoutcome=no_matchwhenlog.mdis writable. - Weak evidence or source conflict: do not resolve it with outside knowledge.
Return only supported claims, label ambiguity where applicable, and make the gap
explicit in
## Coverage; saving remains available for that successful partial readout. - QMD unavailable or unconfigured: state the fallback briefly in the working
update and continue safely through
index.mdandrg; do not fail the narration merely because QMD is unavailable. - Write failure: never leave a partial readout presented as saved, never update
hot.md, and never updateindex.mdor.manifest.json.
Before explicit takeaway replacement, read/reconcile the full current Key Takeaways and obtain TAKEAWAYS_REVISION from hot.takeaways_sha256 in memory status --json (llm-wiki/references/MEMORY.md). Preserve still-valid owner conclusions. Omit --takeaways for mechanical bookkeeping; stale revisions require review, not blind retry.
Related Skills
LocalAI
50.4kLocalAI is the open-source AI engine. Run any model - LLMs, vision, voice, image, video - on any hardware. No GPU required.
siyuan
47.3kAn open-source, privacy-first, self-hosted knowledge workspace where humans and AI agents work together 开源、隐私优先、自托管的知识工作空间,让人与智能体在此协作
x402
121.0kSet up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
