masterdeck-notes
Skill4 starsChanged 25 days agoMITView on GitHub
Write to the user's MasterDeck notes (the Notes panel in MasterDeck) — a new note, more text on a note you made, or the note of a ticket. Use when the user asks to "write it to a note", "save this in notes", "add to the ticket's note", "make a note of …", or wants something kept in MasterDeck's notes.
In this repository8 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- babysit-prSkill
- babysit-ticketSkill
- babysit-worktreeSkill
- kill-worktreeSkill
- masterSkill
- queueSkill
- worktree-janitorSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are 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.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 50
Only write what the user asked to keep, or what they agreed to.
- Distinctive: line 52
If the script says MasterDeck is not running, or reports an error, tell the user.
≈ “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
masterdeck-notes — write to MasterDeck's notes
MasterDeck keeps the user's notes: global notes (a title and text) and one note per ticket. You can
add to them; you cannot read them or change what the user wrote. Write the note in Markdown
(headings, lists, - [ ] task lists, links, code): MasterDeck shows it rendered. HTML is shown as
plain text, so do not use it.
The script is next to this file: ~/.claude/skills/masterdeck-notes/scripts/note.sh. The text goes
on stdin; use a quoted heredoc so nothing in it is expanded.
A new note
~/.claude/skills/masterdeck-notes/scripts/note.sh new "Release checklist" <<'EOF'
- [ ] Tag v1.2
- [ ] Write the release notes
EOFIt prints the new note's id (n-…). Each new makes another note: write several when the user
asks for separate notes. Keep the id if you will add to the same note later.
More text on a note you made
~/.claude/skills/masterdeck-notes/scripts/note.sh append n-0123456789abcdef0123456789abcdef <<'EOF'
Done: tagged v1.2.
EOFA ticket's note
~/.claude/skills/masterdeck-notes/scripts/note.sh ticket acme/widgets#12 <<'EOF'
Waiting on the API review before the migration.
EOFThe text is added at the end of the ticket's note (the note is made when there is none). Name the
ticket in full (owner/name#12); #12 alone means MasterDeck's primary repository. When this
session was started for a ticket, that is usually the one to use.
Rules
- Only write what the user asked to keep, or what they agreed to. Never put secrets or tokens in a note.
- Text is only ever added. To change or remove a note, ask the user to do it in Notes.
- If the script says MasterDeck is not running, or reports an error, tell the user; do not retry in a loop.
- A note is 50,000 characters at most.
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.