Organize the shared notes directory when it becomes hard to navigate. Restructure within research/ and experiments/, deduplicate, update index.md.
SkillScore82Maintained
Automatic
◆Knowledge Management pack
Last verified 8/15/2026
What it changes
Passed 15 of 18 test cases with the skill, and 3 of 18 without it.
Without skill18%
With skill82%
Checks it passed that the model alone missed
Declines to edit notes/research/_coverage.md
Specifies a similarity threshold value of 0.5
Directs logging the contradiction in _open-questions.md
and 13 more in the full report
14 fixed4 passed either way4 still failing0 broke
Pass-rate lift
+64 pp
Tokens
+46%
Agent turns
0%
Response time
-61%
Model gemini-3.6-flashMeasured 8/15/2026v118 of 22 cases passed with skill · 18 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 14 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 14
Prompt
Which file serves as the append-only record for documenting structural changes, merges, and moves performed during note maintenance?
What was checked, without and with the skill
Checked
Without skill
With skill
Identifies _organization-log.md as the destination file
Missed
Passed
case-18 · gemini-3.6-flash · 8/15/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md139 lines8 filesincludes scripts
Organize Files
Restructure the shared notes directory so every agent can find what they need quickly.
For a complete before/after walkthrough on a realistic messy notes/ tree — including the dedup pass, naming fixes, subdirectory creation, link repair, and audit-log entry — see references/worked-example.md. Read it once before your first reorganization; it makes the abstract steps below concrete.
For recovery procedures and judgment calls (move script aborted partway, false-positive duplicates, files that look misplaced in _synthesis/, contradicting _open-questions.md, races between agents…), see references/edge-cases.md.
When to Use
Too many flat files in research/ or experiments/
Duplicate or near-duplicate notes
Inconsistent naming (spaces, uppercase, agent IDs in filenames)
After a deep-research or consolidate phase that created many files
You can't find a note you know exists
Notes Directory Structure
notes/
├── index.md ← table of contents (research + experiments only)
├── raw/ ← immutable sources (DON'T touch)
├── research/ ← deep-research findings (organize within)
│ ├── <topic>/ ← group by topic or theme
│ └── ...
├── experiments/ ← eval reflections and results (organize within)
│ ├── <approach>/ ← group by approach or technique
│ └── ...
├── _synthesis/ ← consolidate owns this (DON'T touch)
├── _connections.md ← consolidate owns this
├── _open-questions.md
└── _organization-log.md ← append-only log of what you changed