create-brain-note
Skill2 starsChanged 53 days agoMITView on GitHub
Saves a conversation recap or an idea as a dated note in a chosen GitHub repository. Use when asked to note, save, remember, jot down, or recap something for later.
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
When an idea follows the repository, summarize that idea.
- Distinctive: line 19
Use only known facts and leave out secrets.
- Very specific: line 31
Write with an authenticated GitHub tool or gh.
≈ “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 a brain note
Append a dated entry to a notes repository on GitHub.
1. Pick the repository
The destination is the owner/repo the request names as the place to save. A repository the
note is about is not the destination. When none is named, ask for owner/repo as free text with
the ask skill. Never infer it from the working directory or offer a guessed name as an option.
2. Pick the content
When an idea follows the repository, summarize that idea. Otherwise recap today's conversation. Use only known facts and leave out secrets. When there is nothing useful to save, ask what to save.
3. Write the entry
On the default branch, open daily/YYYY-MM-DD.md for the local date, creating it with
# YYYY-MM-DD when absent. Add a short ## entry with the idea or recap, plus decisions and
next steps when there are any. Update an existing entry for the same idea, and keep everything
else in the file.
4. Save
Write with an authenticated GitHub tool or gh. An API update needs the file's current SHA, so
fetch it again and retry after a conflict.
Output
One line: the note URL, or why the write failed. When the run stops before writing: the question, the target path, and the prepared entry.
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.