create-note
Skill15 starsChanged 15 days agoMITView on GitHub
Create an Obsidian Inbox capture, a human-owned Atomic Note draft, or approved reusable knowledge from a conversation. Use for "capture this", "create a note", "write this in my own words", "save this explanation", or promoting material from existing notes. Use ingest for external sources and save-session for a session recap.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- atomicinnovation/acceleratortheir own version, first seen Sep 22, 2026
- braincandy-parallel/tamarindos-workflow-kittheir own version, first seen Sep 18, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- atomicinnovation/accelerator★ 34same name
- braincandy-parallel/tamarindos-workflow-kit★ 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 repository53 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- analyze-repoSkill
- architectSkill
- codebase-designSkill
- code-reviewSkill
- commitSkill
- create-prSkill
- create-verification-skillSkill
- debugSkill
- frontendSkill
- implementSkill
- mswSkill
- playwrightSkill
- react-hook-form-auditSkill
- react-hook-formSkill
- reactSkill
- refactorSkill
- researchSkill
- resolving-merge-conflictsSkill
- specSkill
- tailwindSkill
- tanstack-querySkill
- testSkill
- typescriptSkill
- zodSkill
- auditSkill
- neovimSkill
- shell-envSkill
- teachSkill
- tilSkill
- atomic-note-to-mocSkill
- close-daySkill
- goalsSkill
- import-goodreadsSkill
- import-meetingsSkill
- ingestSkill
- memory-recallSkill
- process-inboxSkill
- projectSkill
- save-sessionSkill
- todays-focusSkill
- vault-auditSkill
- vaultSkill
- weekly-reviewSkill
- careerSkill
- check-communicationSkill
- deslopifySkill
- standupSkill
- blogSkill
- broSkill
- docsSkill
- talkSkill
- tweet-todaySkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
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 18
Read ../vault/SKILL.md and the live AGENTS.md.
- Distinctive: line 27
Use the request to choose the mode.
- Very specific: line 30
When promoting material from daily notes or other existing notes, read references/promote-mode.md.
- Distinctive: line 45
Capture: keep the supplied material short and preserve its meaning and source context.
- Distinctive: line 46
Human draft: use the live template, resolve title/date fields, and add only approved tags and relevant source links.
- Distinctive: line 49
Agent synthesis: write a standalone explanation supported by the conversation and sources.
≈ “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
Create Note
Choose the purpose before the template. An Atomic Note can explain a technique, preserve a principle, or explore a question; it is not limited to ideas.
1. Choose the note and owner
Read ../vault/SKILL.md and the live AGENTS.md. Resolve the destination and active template:
| Intent | Note |
| Save an observation, question, thought, or snippet before losing it | Inbox capture using General Notes |
| Leave space for the user to develop their own explanation | Human-owned draft using Atomic Note |
| Preserve a reusable explanation developed in the conversation | Approved agent-written Knowledge note using Atomic Note |
| Explain connections across several notes | MOC using its live template and existing Bases |
Use the request to choose the mode; ask when authorship or destination is unclear. A quick capture needs no classification interview. An unfinished question can already deserve an Atomic Note.
When promoting material from daily notes or other existing notes, read references/promote-mode.md.
Completion: purpose, owner, destination, and active template are known.
2. Check for an existing note
For Knowledge or MOCs, read root index.md, search when needed, and inspect plausible matches.
Choose to create, link, or enrich based on scope and ownership. An existing human-owned page is not
an automatic enrichment target. For Inbox captures, check for a filename collision without turning
capture into a vault-wide research task.
Completion: the proposed write does not overwrite an existing note or duplicate known coverage.
3. Draft the right amount
- Capture: keep the supplied material short and preserve its meaning and source context.
- Human draft: use the live template, resolve title/date fields, and add only approved tags and relevant source links. Leave the user's explanation and questions for them to write. User-supplied prose may be included exactly as approved. Omit agent ownership metadata.
- Agent synthesis: write a standalone explanation supported by the conversation and sources. Distinguish facts from open questions; use the schema's wiki metadata. Do not invent the user's beliefs, experiences, or learning.
- MOC: explain the connections, preserve existing Base embeds, and select an existing Base when useful. A new or changed Base needs separate approval.
Completion: the draft fits its purpose and represents its owner honestly.
4. Preview, write, and verify
Show the exact path and content or section edit, plus any required index/log changes. After approval, use the vault safe-write flow and account for automatic template insertion. Reread the result and verify one frontmatter block, resolved fields, and working links.
Register Knowledge writes as the live schema requires. Human drafts belong under the human-note catalog section, not agent-written concepts. Ordinary Inbox captures need no wiki registration. Preserve source daily notes and unrelated content.
Completion: every approved change is verified, required registration is complete, and the report states the path, owner, create/enrich mode, and any incomplete step.
References
| Priority | Load when | Reference |
| 1 | Promoting observations, questions, or explanations from existing notes | references/promote-mode.md |
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.