update-skills
Skill0 starsChanged 57 days agoMITView on GitHub
Create or update repository skills and instructions when major learnings are discovered during a session. Use when the user says "learn!", when a significant pattern or pitfall is identified, or when reusable domain knowledge should be captured for future sessions.
20 other projects use a version of this.
Adopted by
Most recently taken up by
- antick/skillstheir own version, first seen Nov 16, 2026
- Trixx4191/asrartheir own version, first seen Nov 15, 2026
- nanocoai/nanoclawtheir own version, first seen Nov 15, 2026
- IndusCore-AI/connect-anythingtheir own version, first seen Nov 8, 2026
- tandregbg/core-claude-skillstheir own version, first seen Nov 4, 2026
- ss2code/nanoclaw-opstheir own version, first seen Oct 15, 2026
Used with
Projects with it also use add-anydoc, add-clidash and 8 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.
TomGranotSkilladd-anydoc
Add local office-document-to-Markdown conversion to NanoClaw agent containers with the pinned Firecrawl AnyDoc CLI. Use when agents need to read attached Word, PowerPoint, Excel, OpenDocument, RTF, EPUB, CSV, or text-based PDF files without uploading them to a hosted parser.
Also in 5 projects that use this
TomGranotSkilladd-clidash
Add clidash — a zero-dependency, read-only web dashboard that derives its tabs and tables at runtime from any CLI that lists resources as JSON. Ships pre-wired for NanoClaw's ncl CLI (agent groups, sessions, channels, users, roles), plus message-activity charts, a log tail, and a read-only file viewer for group skills/CLAUDE.md/profiles.
Also in 5 projects that use this
qwibitaiSkilladd-iron-proxy
Install or refresh Iron Proxy and its official Iron Control web console for NanoClaw. Use when selecting the Iron gateway, adding its management UI, configuring credentials and grants, or restoring the proxy, approval bridge, and agent guidance.
Also in 4 projects that use this
qwibitaiSkilladd-mattermost
Add a self-hosted or cloud Mattermost bot channel through the Chat SDK bridge, reusing a healthy server when available and linking to official server setup guidance when needed.
Also in 4 projects that use this
b1rdmaniaSkillmigrate-memory
Migrate from monolith CLAUDE.md to the three-file memory system (identity + state + log). Non-destructive — backs up the original first.
Also in 6 projects that use this
- +5 more from TomGranot
Other versions20 projects use a version of this.
Word for word · 2
- microsoft/vscode★ 195k100% same
- patterson-agents/skills★ 0100% same
Edited · 0
None found.
Wrote their own version · 18
- gavrielc/nanoclaw★ 31ksame name
- nanocoai/nanoclaw★ 31ksame name
- qwibitai/nanoclaw★ 31ksame name
- L-X-T/ng-agentic-skills★ 13same name
- Orderful/orderful-netsuite-skills★ 7same name
- microsoft/amplifier-app-nanoclaw★ 5same name
- tandregbg/core-claude-skills★ 4same name
- TomGranot/groupguard★ 3same name
- kimgoetzke/coding-agent-configs★ 2same name
- prathish-ks/isthmus★ 2same name
8 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 repository32 other files it gives its agents.
- .github/copilot-instructions.mdCopilot instructions
- act-on-feedbackSkill
- algorithmic-artSkill
- animateSkill
- canvas-designSkill
- coderSkill
- code-reviewSkill
- coderSkill
- commitSkill
- create-draft-prSkill
- create-prSkill
- criticSkill
- designerSkill
- design-taste-frontendSkill
- fix-ciSkill
- frontend-designSkill
- generalistSkill
- generate-run-commandsSkill
- mergeSkill
- ponytailSkill
- researcherSkill
- researcherSkill
- securitySkill
- shadcnSkill
- syncSkill
- sync-upstreamSkill
- theme-factorySkill
- toolsSkill
- troubleshootSkill
- ui-ux-pro-maxSkill
- update-prSkill
- web-design-engineerSkill
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 6 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 17 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
When a major repository learning is discovered — a recurring pattern, a non-obvious pitfall, a crucial architectural constraint, or domain …
- Distinctive: line 20
Add a learning to an existing instruction: when:
- Very specific: line 23
Follow the pattern in .github/instructions/learnings.instructions.md
- Distinctive: line 47
Before creating new files, search for existing skills and instructions that might be the right home:
- Very specific: line 62
If an appropriate file exists, add the learning to its ## Learnings section (create the section if it doesn't exist).
- Distinctive: line 66
If the knowledge warrants a standalone skill:
- Very specific: line 71
Create the directory and SKILL.md with frontmatter:
- Distinctive: line 89
If the knowledge should apply automatically:
- Distinctive: line 111
After creating or updating the file:
“Common” is measured: kept by at least 6 in 10 of the 17 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
<!-- Customize this skill and select save to override its behavior. Delete that copy to restore the built-in behavior. -->Update Skills & Instructions
When a major repository learning is discovered — a recurring pattern, a non-obvious pitfall, a crucial architectural constraint, or domain knowledge that would save future sessions significant time — capture it as a skill or instruction so it persists across sessions.
When to Use
- The user explicitly says "learn!" or asks to capture a learning
- You discover a significant pattern or constraint that cost meaningful debugging time
- You identify reusable domain knowledge that isn't documented anywhere in the repo
- A correction from the user reveals a general principle worth preserving
Decision: Skill vs Instruction vs Learning
Add a learning to an existing instruction when:
- The insight is small (1-4 sentences) and fits naturally into an existing instruction file
- It refines or extends an existing guideline
- Follow the pattern in
.github/instructions/learnings.instructions.md
Create or update a skill (.github/skills/{name}/SKILL.md or .agents/skills/{name}/SKILL.md) when:
- The knowledge is substantial (multi-step procedure, detailed guidelines, or rich examples)
- It covers a distinct domain area (e.g., "how to debug X", "patterns for Y")
- Future sessions should be able to invoke it by name
Create or update an instruction (.github/instructions/{name}.instructions.md) when:
- The rule should apply automatically based on file patterns (
applyTo) or globally - It's a coding convention, architectural constraint, or process rule
- It doesn't need to be invoked on demand
Procedure
1. Identify the Learning
Reflect on what went wrong or what was discovered:
- What was the problem or unexpected behavior?
- Why was it a problem? (root cause, not symptoms)
- How was it fixed or what's the correct approach?
- Can it be generalized beyond this specific instance?
2. Check for Existing Files
Before creating new files, search for existing skills and instructions that might be the right home:
# Check existing skills
ls .github/skills/ .agents/skills/ 2>/dev/null
# Check existing instructions
ls .github/instructions/ 2>/dev/null
# Search for related content
grep -r "related-keyword" .github/skills/ .github/instructions/ .agents/skills/3a. Add to Existing File
If an appropriate file exists, add the learning to its ## Learnings section (create the section if it doesn't exist). Each learning should be 1-4 sentences.
3b. Create a New Skill
If the knowledge warrants a standalone skill:
- Choose the location:
.github/skills/{name}/SKILL.mdfor project-level skills (committed to repo).agents/skills/{name}/SKILL.mdfor agent-specific skills
- Create the directory and SKILL.md with frontmatter:
---
name: {skill-name}
description: {One-line description of when and why to use this skill.}
---
# {Skill Title}
{Body with guidelines, procedures, examples, and learnings.}- The
namefield must match the parent folder name exactly. - Include concrete examples — skills with examples are far more useful than abstract rules.
3c. Create a New Instruction
If the knowledge should apply automatically:
---
description: {When these instructions should be loaded}
applyTo: '{glob pattern}' # optional — auto-load when matching files are attached
---
{Content of the instruction.}4. Quality Checks
Before saving:
- Is the learning general enough to help future sessions, not just this one?
- Is it specific enough to be actionable, not just a vague principle?
- Does it include a concrete example of right vs wrong?
- Does it avoid duplicating knowledge already captured elsewhere?
- Is the description clear enough that the agent will know when to invoke/apply it?
5. Inform the User
After creating or updating the file:
- Summarize what was captured and where
- Explain why this location was chosen
- Note if any existing content was updated vs new content created
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.

