qna
Skill0 starsChanged 19 days agoMITView on GitHub
Answer a question from the vault's own notes, citing each note used with a wikilink. Use when the user asks something their notes can answer, or asks to check the vault.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- POSTTTT/SKILLstheir own version, first seen Jun 9, 2026
- yushman/claude-skillstheir own version, first seen Mar 30, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- POSTTTT/SKILLs★ 1same name
- yushman/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository6 other files it gives its agents.
- template/AGENTS.mdAGENTS.md
- template/CLAUDE.mdCLAUDE.md
- digestSkill
- explainSkill
- lintSkill
- wikiSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Read Index.md to find the relevant notes.
- Distinctive: line 9
Read those notes (at most five).
- Very specific: line 13
If the answer is new (not a restatement of one note), offer to save it as a fleeting note.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/qna
- Read
Index.mdto find the relevant notes. - Read those notes (at most five). The index is a catalog, not a source.
- Answer directly and cite every note with a
[[wikilink]]. If notes disagree or the vault is silent on part of the question, say so instead of filling the gap with outside knowledge presented as vault content. - If the answer is new (not a restatement of one note), offer to save it as a
fleeting note. Write nothing until the user says yes; then follow /digest
steps 2, 4, 7, and 8 with the cited notes as
sources:.
Answering without saving needs no lock and no log line.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.