note
Skill4 starsChanged 6 months agoMITView on GitHub
Append a timestamped tagged line (finding / decision / summary) to the session journal at .hook-state/session-journal.md, so a discovered fact, a settled choice, or a transient breadcrumb survives context compaction in a long writing session. Delegates to scripts/note.sh.
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
- egregore-labs/egregoretheir own version, first seen Nov 6, 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
Used with
Projects with it also use add, update and 7 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.
VercelSkilladd
Add Turborepo to an existing repository in any toolchain Turborepo supports. Use when asked to add, introduce, or set up Turborepo or turbo in a repository that does not use it yet.
Also in 3 projects that use this
AnthropicSkillupdate
Sync tasks and refresh memory from your current activity. Use when pulling new assignments from your project tracker into TASKS.md, triaging stale or overdue tasks, filling memory gaps for unknown people or projects, or running a comprehensive scan to catch todos buried in chat and email.
Also in 4 projects that use this
genomewalkerSkillexplore
RLM-style recursive memory exploration - dynamically navigate the memory graph
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
Microsoft AzureSkilltest
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
- egregore-labs/egregore★ 293same name
- 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
- 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 repository24 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- abstractSkill
- citation-auditSkill
- claim-checkSkill
- cover-letterSkill
- gap-finderSkill
- journal-fitSkill
- lit-briefingSkill
- literature-reviewSkill
- lit-ingestSkill
- lit-lintSkill
- manuscript-cycleSkill
- methods-reviewSkill
- outlineSkill
- peer-reviewSkill
- plain-language-summarySkill
- reference-formatSkill
- response-to-reviewersSkill
- retroSkill
- review-resurfaceSkill
- scorecardSkill
- stats-checkSkill
- submission-pipelineSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 18 edited versions we read keep these.
2
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
- Very specific: line 24
Do not use /note for things with a permanent home: a settled framing/scope/methods decision belongs in tasks/decisions.md.
- Distinctive: line 39
Run the backing script (the skill does nothing else):
- Very specific: line 43
Keep <text> to one self-contained line — it must make sense with zero surrounding context, because post-compaction that is exactly the …
- Distinctive: line 94
Write the note as if the reader has no memory of this session — because after compaction, they don't.
“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
Core Rule
A long writing session will compact. When it does, the conversation summary keeps the gist and drops the detail — the gotcha you found three hours ago, the reason you picked one framing over another, the exact key you decided not to cite. /note is the kit's defense: it writes one timestamped line to a durable-within-the-session journal before the detail is at risk, so CLAUDE.md → After Compaction can re-read it and restore what the summary lost.
This is deterministic memory, not judgment (CLAUDE.md → Model vs Code). Do not paraphrase a finding back into the chat and hope it survives — append it. The skill never reasons about the text; it timestamps and stores it. One line, one fact.
When to Use
Invoke with /note <tag> <text> the moment something is worth not re-deriving:
- You discovered a fact or gotcha that cost you effort — a source's real scope, a notation collision, a compile quirk. Tag it
finding. - You made a choice with a reason — picked one term for a concept, settled a framing, decided a claim is the author's own and not citeable. Tag it
decision. - You want a transient breadcrumb for this working block — "left off mid-paragraph in Results §3.2, the CI still needs checking." Tag it
summary. - Proactively, when you sense a session is getting long and dense, before compaction takes the detail.
Do not use /note for things with a permanent home: a settled framing/scope/methods decision belongs in tasks/decisions.md; a recurring reviewer critique belongs in tasks/reviews/; an open task belongs in tasks/todo.md. The journal is short-term working memory, not the archive.
The Three Tags
| Tag | Means | Survives to handoff? | Example |
finding | A discovered fact or gotcha — something true you had to work out and don't want to re-derive | Yes — folded | finding tooluse2023 is single-turn QA only; do NOT cite it for multi-turn agent claims |
decision | A choice made and why — the reasoning, so future-you doesn't reopen it | Yes — folded | decision standardize on "tool-call accuracy" (not "success rate") across the draft — one term per concept |
summary | A transient breadcrumb for the current block — pure "where am I" state | No — discarded | summary mid-rewrite of Discussion ¶2, softening the causal verbs flagged by /claim-check |
The split is intentional: findings and decisions are knowledge worth carrying into the next session; a summary is scaffolding that is stale the moment the block is done. journal-fold.sh (below) folds the first two and discards summary-only journals — so over-tagging as summary silently loses the note. If it would matter tomorrow, it is a finding or a decision.
Process
- Pick the tag honestly against the table above. The tag is the only thing that decides whether the note survives — get it right.
- Run the backing script (the skill does nothing else):
Keep./scripts/note.sh <finding|decision|summary> "<text>"<text>to one self-contained line — it must make sense with zero surrounding context, because post-compaction that is exactly the context it gets. Name the artifact it concerns (a.bibkey, a.texsection, a quantity). - The script appends
<ISO-timestamp> [<tag>] <text>to.hook-state/session-journal.md(creating the dir + its.gitignoreon first use) and echoes back the line plus the running entry count. - Carry on writing. Do not stop to summarize the journal — it accumulates silently and is read only on demand (after compaction) or folded at session end.
An invalid tag or empty text exits non-zero with usage — fix the tag, do not invent a fourth.
After compaction — reading the journal back
When you detect a compaction (a conversation summary appears; earlier detail is gone), CLAUDE.md → After Compaction step 5 has you re-read .hook-state/session-journal.md if it exists. That is the payoff for every /note you logged this session: the findings and decisions you journaled are still there verbatim, even though the chat summarized them away. Read it before resuming — do not draft on a half-restored context.
Choosing the tag — worked examples
Tag choice is the load-bearing decision; these settle the common ambiguities:
- "I just realized
halluc2022reports a 23% rate, not 32% — I had it backwards." →finding. A corrected fact you must not re-confuse; it has to survive to the next session. - "We're going with IEEE style, not APA — the target journal requires it." →
decision(the why is the venue requirement). Then promote it totasks/decisions.mdif it is a settled manuscript-level choice — the/noteis the short-term capture,decisions.mdis the durable home. - "Currently rewriting Discussion ¶3 to soften the causal verbs; will re-run
/claim-checkafter." →summary. Pure where-am-I state; stale once ¶3 is done. Folding it to handoff would be noise. - "latexmk needs
-shell-escapefor themintedblocks or the compile-gate fails." →finding. A non-obvious build gotcha worth not rediscovering — exactly what a folded handoff should carry. - "Decided the horizon-scaling sentence is the author's own observation, not a citeable claim — Results §3.2 supports it." →
decision. A sourcing judgment with a reason; future-you should not reopen it.
The test in every case: would this matter to a session that starts tomorrow with none of today's chat? Yes → finding/decision. Only-right-now → summary.
Output Format
The script reports the appended line and the journal's new size:
Noted: 2026-06-03T14:22:05Z [finding] tooluse2023 is single-turn QA only; do NOT cite it for multi-turn agent claims
→ .hook-state/session-journal.md (4 entries)There is no manuscript output and nothing to commit — the journal is gitignored (same lifetime as the rest of .hook-state/). Its only durable trace is what journal-fold.sh carries into the handoff.
Lifecycle — where notes go
- Within the session: the journal lives at
.hook-state/session-journal.md, gitignored, accumulating one line per/note. It is the across-compaction memory described above. - At session end:
.claude/hooks/journal-fold.sh(a SessionEnd hook) reads the journal and folds[finding]and[decision]lines intotasks/handoff-<session-id>.md— appending them under a## Journalblock with per-tag counts, so the next session's Tier-2 boot (CLAUDE.md → Session Boot, "read the latesttasks/handoff-*.md") inherits them.[summary]-only journals are discarded — a journal with no findings or decisions is deleted unfolded. Then the journal is cleared so the next session starts clean.
So a finding is a promise that survives twice — across compaction (re-read) and across sessions (folded to handoff). A summary survives neither; it is honestly transient.
Pairs With
.claude/hooks/journal-fold.sh(SessionEnd) — the consumer: folds findings + decisions into the handoff, discards summary-only. Runs alongsidesession-end.sh(the/scorecardaudit hook).CLAUDE.md → After Compaction— the reader: step 5 re-reads the journal to recover pre-compaction findings./noteexists so that step has something to recover.tasks/handoff-*.md— the destination for folded findings/decisions; read at session boot when continuing work.tasks/decisions.md— for a durable, manuscript-level decision (framing, scope, methods, an approved Protected Claim). A/note decisionis its short-term cousin; promote it here if it will outlive the session./retro— reads the folded journal findings out of the handoffs when assembling the "what was learned" section of a windowed retrospective.
Notes
- One fact per note. Two findings in one line means one of them gets lost when you skim the journal post-compaction.
- Write the note as if the reader has no memory of this session — because after compaction, they don't.
- This is a
headless-friendly operation (mode:headless): in an unattended pass, journaling each non-obvious finding/decision as you go is how an autonomous run leaves a trail the next session can pick up — there is no human watching the chat to remember it for you. - The journal is append-only through this skill; there is no
/noteedit or delete. A superseded note is corrected by adding a newer one, not by rewriting history — the timestamps are the record. - Tagging discipline is the whole game: the difference between "carried to the next session" and "silently dropped" is one word. When unsure whether something is durable, tag it
findingordecision— folding a slightly-too-trivial note costs nothing; losing a load-bearing one costs a re-derivation.
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.

