riff
Skill4 starsChanged 49 days agoMITView on GitHub
Turn a rambly spoken or stream-of-consciousness transcript into a clean, faithful first-person knowledge-base note under kb/riffs/. Use when the user pastes a dictated voice dump, says “riff” or “add a riff,” or asks to clean up a journal-style transcription. Preserve every useful idea, aside, hedge, attribution, and coined term; execute embedded transcriber research requests; use attachments as context without embedding the raw files.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- NasonZ/rifftheir own version, first seen Nov 8, 2026
- develop212/rifftheir own version, first seen Oct 20, 2026
- AZ-1224/rifftheir own version, first seen Jun 17, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- NasonZ/riff★ 2same name
- develop212/riff★ 1same name
- AZ-1224/riff★ 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 repository48 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .agents/skills/AGENTS.mdAGENTS.md
- .agents/skills/assumption-audit/AGENTS.mdAGENTS.md
- .agents/skills/decision-matrix/AGENTS.mdAGENTS.md
- .agents/skills/direct-setup/AGENTS.mdAGENTS.md
- .agents/skills/direct-verify/AGENTS.mdAGENTS.md
- .agents/skills/first-principles-thinking/AGENTS.mdAGENTS.md
- .agents/skills/percolate-kb/AGENTS.mdAGENTS.md
- .agents/skills/percolate-reading/AGENTS.mdAGENTS.md
- .agents/skills/phase-final-reviewer/AGENTS.mdAGENTS.md
- .agents/skills/phase-implementer/AGENTS.mdAGENTS.md
- .agents/skills/phase-orchestrator/AGENTS.mdAGENTS.md
- .agents/skills/phase-reviewer/AGENTS.mdAGENTS.md
- .agents/skills/plan-kb/AGENTS.mdAGENTS.md
- .agents/skills/pr-cleanup/AGENTS.mdAGENTS.md
- .agents/skills/query-kb/AGENTS.mdAGENTS.md
- .agents/skills/question-forge/AGENTS.mdAGENTS.md
- .agents/skills/reclaim-disk-space/AGENTS.mdAGENTS.md
- .agents/skills/refresh-kb/AGENTS.mdAGENTS.md
- .agents/skills/riff/AGENTS.mdAGENTS.md
- .agents/skills/save-pdf-kb/AGENTS.mdAGENTS.md
- .agents/skills/save-url-kb/AGENTS.mdAGENTS.md
- .agents/skills/write-phase-plan/AGENTS.mdAGENTS.md
- docs/AGENTS.mdAGENTS.md
- kb/AGENTS.mdAGENTS.md
- personal-website/AGENTS.mdAGENTS.md
- scripts/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- assumption-auditSkill
- decision-matrixSkill
- direct-setupSkill
- direct-verifySkill
- first-principles-thinkingSkill
- percolate-kbSkill
- percolate-readingSkill
- phase-final-reviewerSkill
- phase-implementerSkill
- phase-orchestratorSkill
- phase-reviewerSkill
- plan-kbSkill
- pr-cleanupSkill
- query-kbSkill
- question-forgeSkill
- reclaim-disk-spaceSkill
- refresh-kbSkill
- save-pdf-kbSkill
- save-url-kbSkill
- write-phase-planSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 6 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
6
Distinctive
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
- Distinctive: line 14
Write the result to:
- Very specific: line 20
Create a finished, self-contained note that reads as if the speaker wrote it deliberately.
- Distinctive: line 25
Keep every useful idea, aside, uncertainty, hedge, attribution, and coined term.
- Distinctive: line 26
Keep the note in first person and preserve the speaker's vocabulary.
- Distinctive: line 32
Treat “sidebar for the transcriber,” “look this up,” “flesh this out,” and similar phrases as instructions, not prose to preserve.
- Very specific: line 35
Put substantial companion research in an appropriately named kb/ note and link it once from the riff.
- Distinctive: line 41
Use attached screenshots, whiteboards, or documents to verify names and recover meaning.
- Distinctive: line 43
Read the entire transcript before writing, complete embedded follow-ups, write the note and any companion files, then report the paths …
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Clean up a riff
Write the result to:
kb/riffs/<YYYY-MM-DD>-<descriptive-slug>.mdCreate a finished, self-contained note that reads as if the speaker wrote it deliberately. Follow WRITING.md: lead with the point, prefer active voice, name concrete details, and cut filler.
Preserve the person
- Repair run-ons, punctuation, dropped words, and obvious transcription mistakes.
- Keep every useful idea, aside, uncertainty, hedge, attribution, and coined term.
- Keep the note in first person and preserve the speaker's vocabulary.
- Reorder scattered threads into a coherent arc when needed. Use headings only when the note genuinely spans multiple topics.
- End on the strongest natural beat. Do not manufacture a conclusion or add a recap.
Resolve transcriber instructions
Treat “sidebar for the transcriber,” “look this up,” “flesh this out,” and similar phrases as instructions, not prose to preserve.
- Perform the requested lookup or research and integrate the result into the finished note.
- Put substantial companion research in an appropriately named
kb/note and link it once from the riff. - State what remains open only when the follow-up cannot be completed.
- Attribute additions only when a reader could otherwise mistake them for the speaker's claim.
An optional editorial note must be brief, clearly labeled, and genuinely additive. Omit it when it only restates the riff.
Use attached screenshots, whiteboards, or documents to verify names and recover meaning. Describe relevant content in prose; do not copy or embed the raw attachment in the riff.
Read the entire transcript before writing, complete embedded follow-ups, write the note and any companion files, then report the paths created and any material inference that remains uncertain.
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.

