Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →human-agent-society/create-notes
Write a note to {shared_dir}/notes/ that future agents can actually act on. Use after every coral eval, when a heartbeat (reflect / consolidate / pivot) asks for a note, or when you discover a grader / build / runtime issue that future agents will hit. Covers 4 note variants (experiment / infra / focus / synthesis), the required frontmatter with the team-level `creator:` filter, the structured-trace schema (`type` / `claim` / `status` / `confidence` / `based_on` / `evidence` / `supersedes` / `re
Passed 9 of 14 test cases with the skill, and 4 of 14 without it.
and 12 more in the full report
9 fixed5 passed either way7 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
I want to save my experiment reflection note under notes/experiments/Eval_12_SIMD_widening.MD using agent ID 'agent-1' in the filename. Is this filename acceptable?
| Checked | Without skill | With skill |
|---|---|---|
| Rejects uppercase characters and spaces in filename | Missed | Passed |
| Rejects agent ID in experiment note filename | Missed | Passed |
The instructions your model reads when the skill loads.
A good note answers three questions a future agent will actually ask:
A bad note is a wall of headings with empty bodies, or a final-design pitch with no record of the alternatives you rejected. The bad pattern shows up enough that this skill exists to prevent it.
Each heartbeat that produces a note corresponds to one variant. The skill is one document, but you only need the variant your current trigger asks for.
| Triggered by | Variant | File location |
|---|---|---|
reflect heartbeat after each eval | Experiment note (Variant A) | notes/experiments/eval-<N>-<slug>.md |
pivot plateau detection | Focus note (Variant C) | notes/focus/focus-<topic>.md |
consolidate synthesis / connections / open-questions | Synthesis + map + gaps (Variant D) | notes/_synthesis/<topic>.md, notes/_connections.md, notes/_open-questions.md |
| First time a grader / build / runtime issue is hit | Infra note (Variant B) | notes/infra/<slug>.md (or notes/<slug>.md) |
deep-research warm-start phase | Research note | Per deep-research/SKILL.md (not duplicated here) |
If you are about to Write any file under notes/, stop and use this skill first — even if the prompt did not say "write a note."
The directory structure is owned by organize-files. Do not invent new top-level subdirectories; place new content in the right existing one:
notes/
├── index.md ← table of contents; you update this for any new note
├── raw/ ← immutable sources (do not write here directly)
├── research/ ← deep-research findings (link back to raw/)
├── experiments/ ← per-eval reflections, written by the reflect heartbeat
├── infra/ ← grader / build / runtime issues + workarounds (recommended)
├── focus/ ← per-agent focus declarations (owned by the pivot heartbeat)
├── migrations/ ← island-arrival notes (written by the framework)
├── _synthesis/ ← owned by consolidate; do not write here unless consolidating
├── _connections.md ← owned by consolidate
├── _open-questions.md ← owned by consolidate
test cases passed, vs 4 / 14 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.