note
Skill293 starsChanged 10 days agoMITView on GitHub
Use when the user says 'jot this down', 'note to self', 'just thinking out loud', or 'park this thought' — saves an actor-owned private draft locally and promotes it to organizational knowledge only on an explicit request.
24 other projects use a version of this.
Adopted by
Most recently taken up by
- Renozoic-Foundry/forge-publictheir own version, first seen Nov 15, 2026
- WALKERKILLER/Look-Tongji-Notestheir own version, first seen Nov 8, 2026
- buildomator/buildomatortheir own version, first seen Nov 4, 2026
- lza6/claw-code-tingfengtheir own version, first seen Nov 1, 2026
- Srltas/claude-skillstheir own version, first seen Oct 31, 2026
- chris-peterson/tacktheir own version, first seen Oct 26, 2026
Used with
Projects with it also use add, resume and 3 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
tim-mccrimmonSkilladd
Process a document (PRD, architecture doc, security requirements, etc.) into structured context. Extracts relevant information and generates appropriate SCDs.
Also in 3 projects that use this
genomewalkerSkillresume
Resume a thread by loading its ~800-token context capsule
Also in 3 projects that use this
BlockSkillplan
Draft a TDD, PRD, or lightweight plan in the conversation without committing it.
Also in 4 projects that use this
GoogleSkilltdd
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
Also in 3 projects that use this
SentrySkillskill-creator
Create new agent skills following the Agent Skills specification. Use when asked to "create a skill", "add a new skill", "write a skill", "make a skill", "build a skill", or scaffold a new skill with SKILL.md. Guides through requirements, writing, registration, and verification.
Also in 3 projects that use this
Other versions24 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 24
- buildomator/buildomator★ 102same name
- yha9806/academic-writing-toolkit★ 54same name
- WALKERKILLER/Look-Tongji-Notes★ 53same name
- owenliang60-ship-it/knowledge-mgmt★ 37same name
- microsoft/DocAtlas-Harness★ 21same name
- maxwellsdm1867/wheeler★ 12same name
- flowing-abyss/obsidian-vault-skills★ 9same name
- lza6/claw-code-tingfeng★ 5same name
- tansuasici/claude-research-kit★ 4same name
- TashanGKD/cc_plugins★ 4same name
14 more not listed
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 repository50 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- activitySkill
- announceSkill
- archiveSkill
- branchSkill
- checkupSkill
- commitSkill
- contributeSkill
- create-skillSkill
- dark-modeSkill
- dashboardSkill
- deep-reflectSkill
- delete-userSkill
- emissarySkill
- envSkill
- handoffSkill
- harvestSkill
- ingest-corpusSkill
- ingest-notionSkill
- ingestSkill
- ingest-user-interviewSkill
- inviteSkill
- issueSkill
- meetingSkill
- meSkill
- notion-connectSkill
- onboardingSkill
- prSkill
- pullSkill
- pushSkill
- questSkill
- recordsSkill
- reflectSkill
- review-prSkill
- saveSkill
- slack-connectSkill
- summonSkill
- sync-reposSkill
- telegram-connectSkill
- telemetrySkill
- testSkill
- the-spiralSkill
- tui-designSkill
- tutorialSkill
- updateSkill
- viewSkill
- visual-explainSkill
- wrapSkill
- preview-designSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 18 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Use when the user says 'jot this down', 'note to self', 'just thinking out loud', or 'park this thought' — saves an actor-owned private …
- Distinctive: line 18
No arguments: ask what to capture.
- Distinctive: line 47
After the user explicitly approves organizational promotion, call:
- Distinctive: line 65
Do not access another actor's note or treat policy hints as authorization.
- Distinctive: line 66
Do not call Git, QMD, graph, telemetry, publishing, sharing, notification, or control-plane mechanics directly.
“Common” is measured: kept by at least 6 in 10 of the 18 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
Note
Capture a half-baked thought for the active actor. Private notes are local draft state, not canonical organizational truth, and are never committed, indexed, published, shared, or notified automatically.
When to invoke
Use when the user says 'jot this down', 'note to self', 'just thinking out loud', or 'park this thought' — saves an actor-owned private draft locally and promotes it to organizational knowledge only on an explicit request.
Commands
- No arguments: ask what to capture.
- Content: infer a short title and one of
thought,session,retrospective, orjournal; write the user's meaning without polishing it into a decision. list: callbash bin/knowledge.sh note-listand format the returned notes.share <title>orpromote <title>: select the actor's note, preview it, choosedecision,finding, orpattern, and explicitly confirm promotion.
Capture
Render only the note body to a temporary file under tmp/, then call with {note-file}
for that file, {title} for the title inferred from the user's words, and {note-type}
for the inferred thought, session, retrospective, or journal type:
bash bin/knowledge.sh note-create \
--title '{title}' \
--type '{note-type}' \
--input '{note-file}'The Runtime adapter resolves ActorContext and authorizes the actor before local private persistence. The resulting envelope carries stable actor identity and a private policy hint. The hint describes posture; authorization remains the Runtime policy decision.
Promotion
Open the selected note through bash bin/knowledge.sh note-open "{path}".
After the user explicitly approves organizational promotion, call:
bash bin/knowledge.sh note-promote \
--path "{path}" \
--type "{decision|finding|pattern}" \
--title "{title}" \
--topic "{topic}" \
--workstream "{workstream}"Promotion uses CanonicalArtifactWriteback: authorize, assign stable typed identity and source provenance, persist Markdown, record Git provenance, update retrieval, start background embedding, then emit content-free telemetry. The private copy remains and records the canonical target.
Boundaries
- Do not access another actor's note or treat policy hints as authorization.
- Do not call Git, QMD, graph, telemetry, publishing, sharing, notification, or control-plane mechanics directly.
sharemeans promotion into authorized organizational Markdown, not external publication. External sharing and notification require separate permission and exact consent.
Confirm private capture with its local path. Confirm promotion with the new canonical path and writeback status.
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.

