capture-learning
Skill0 starsChanged 2 months agoMITView on GitHub
Record a non-obvious insight discovered during work as a dated learning in knowledge/learnings/ so it compounds instead of being lost. Use at the end of any task that surfaced a constraint, failed approach, vendor quirk, corrected assumption, or hard-to-find fact, or when asked to "note that", "remember that", "write down what we learned".
14 other projects use a version of this.
Adopted by
Most recently taken up by
- callumflack/skillstheir own version, first seen Nov 8, 2026
- RoyoTech/royo-learntheir own version, first seen Nov 8, 2026
- netgrade-digital/shared-agentstheir own version, first seen Nov 1, 2026
- DentalEdge-Solutions/claude_codetheir own version, first seen Nov 1, 2026
- impactbrussels/AINativeOStheir own version, first seen Oct 20, 2026
- dsvid/claude-skillstheir own version, first seen Oct 8, 2026
Other versions14 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 14
- NVIDIA/multi-storage-client★ 91same name
- Kastalien-Research/thoughtbox★ 64same name
- PIXARTSeu/Synapse★ 9same name
- RoyoTech/royo-learn★ 7same name
- netgrade-digital/shared-agents★ 5same name
- hussainweb/skills★ 3same name
- impactbrussels/FounderOS★ 2same name
- subarnasaikia/kaggle-skills★ 2same name
- callumflack/skills★ 1same name
- DentalEdge-Solutions/claude_code★ 1same name
4 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 repository19 other files it gives its agents.
- agents/AGENTS.mdAGENTS.md
- AGENTS.mdAGENTS.md
- areas/AGENTS.mdAGENTS.md
- company/AGENTS.mdAGENTS.md
- knowledge/AGENTS.mdAGENTS.md
- scripts/AGENTS.mdAGENTS.md
- work/AGENTS.mdAGENTS.md
- agents/CLAUDE.mdCLAUDE.md
- areas/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- company/CLAUDE.mdCLAUDE.md
- knowledge/CLAUDE.mdCLAUDE.md
- scripts/CLAUDE.mdCLAUDE.md
- work/CLAUDE.mdCLAUDE.md
- answer-company-questionSkill
- import-knowledgeSkill
- record-decisionSkill
- research-questionSkill
- review-workspaceSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 14 edited versions we read keep these.
2
Distinctive
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
- Very specific: line 26
Check knowledge/learnings/ and the relevant area page for the same insight.
- Distinctive: line 30
Write the title as the statement of what is now known, for example "Learning: the payments provider settles weekly, not daily".
- Distinctive: line 37
If the learning contradicts an approved page, do not edit that page.
“Common” is measured: kept by at least 6 in 10 of the 14 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
Capture a learning
Insight that stays in a conversation is lost. This skill takes under five minutes and is part of finishing work.
Is it a learning?
Apply the counterfactual test: if this were never written down, would a future person repeat a mistake, rediscover a fact at real cost, or take on material risk? Yes means write it. It must also not already have a home. Examples: an API limit that shaped a design, a vendor process that differs from its documentation, a metric definition that turned out to be ambiguous, an approach that failed and why, a number that took an hour to find.
No, if it is task status (tracker), a record of what was done (Git history),
a choice with alternatives (record-decision), or something an existing page
already says (update that page).
Steps
- Check
knowledge/learnings/and the relevant area page for the same insight. If a page already covers it, update the page instead. - Create
knowledge/learnings/YYYY-MM-DD-short-name.mdfromtemplates/learning.md. Use today's date. - Write the title as the statement of what is now known, for example "Learning: the payments provider settles weekly, not daily".
- Fill every section briefly. "Evidence" must contain at least one source, observation, or reproduction step. "Prevention" says what to do differently. "Promote to" names the page this should eventually live in.
- Set
ownerto the person who can verify it,status: draft, andreview_by60 days out. - If the learning contradicts an approved page, do not edit that page. Mention the conflict in the learning and tell the owner.
- Run
python3 scripts/lint.py. - Include the learning in the same branch or pull request as the work that produced it. A learning filed later is usually never filed.
Report
One line in your final message: "Captured learning: knowledge/learnings/...
(promote to areas/...)".
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.

