update-knowhow
Skill25 starsChanged 2 months agoMITView on GitHub
Use when the user explicitly asks to archive environment, toolchain, debugging, or operational knowledge. Triggers on "记下来", "归档", "save this".
In this repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- project-skillSkill
- project-skillSkill
- analyze-experimentSkill
- commit-changelogSkill
- init-projectSkill
- monitorSkill
- new-experimentSkill
- read-paperSkill
- survey-literatureSkill
- todoSkill
- update-docsSkill
- update-project-skillSkill
- visualizeSkill
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 9
Use the archival contract with an existing knowhow destination.
- Distinctive: line 18
Update an existing entry when it covers the same problem.
≈ “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
Update Knowhow
Use the archival contract with an existing knowhow destination. This alias can complete the task directly; it does not depend on being able to invoke another skill.
Preserve exact observed commands/configuration, relevant versions, provenance and verification. Separate symptoms, candidate causes, attempted fixes and verified resolution. An unresolved investigation may be saved as unresolved; a failed command does not prove a fix or justify changing the environment.
Update an existing entry when it covers the same problem. Carry forward the task's archival authorization, check the changed slice, and report paths and remaining uncertainty. Do not duplicate the record into a personal wiki or commit/publish it unless that destination/action was also requested.
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.