update-skills
Skill1 starsChanged 6 months agoMITView on GitHub
Check for and apply updates to installed skill branches from upstream.
20 other projects use a version of this, 2 of them edited.
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-opsedited, first seen Oct 15, 2026
Used with
Projects with it also use add-anydoc, add-clidash and 10 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
MicrosoftSkillact-on-feedback
Act on user feedback attached to the current session. Use when the user submits feedback on the session's changes via the Submit Feedback button.
Also in 3 projects that use this
- +5 more from TomGranot
Other versions20 projects use a version of this.
Word for word · 0
None found.
Edited · 2
- microsoft/amplifier-app-nanoclaw★ 599% same
- ss2code/nanoclaw-ops★ 116% same
Wrote their own version · 18
- microsoft/vscode★ 195ksame name
- 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
- 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 repository42 other files it gives its agents.
- AGENTS.mdAGENTS.md
- container/AGENTS.mdAGENTS.md
- add-atomic-chat-toolSkill
- add-dashboardSkill
- add-discordSkill
- add-emacsSkill
- add-gcal-toolSkill
- add-gchatSkill
- add-githubSkill
- add-gmail-toolSkill
- add-imessageSkill
- add-karpathy-llm-wikiSkill
- add-linearSkill
- add-macos-statusbarSkill
- add-matrixSkill
- add-ollama-providerSkill
- add-ollama-toolSkill
- add-parallelSkill
- add-resendSkill
- add-signalSkill
- add-slackSkill
- add-teamsSkill
- add-telegramSkill
- add-vercelSkill
- add-webexSkill
- add-wechatSkill
- add-whatsapp-cloudSkill
- add-whatsappSkill
- clawSkill
- convert-to-apple-containerSkill
- customizeSkill
- debugSkill
- get-qodo-rulesSkill
- init-first-agentSkill
- manage-channelsSkill
- manage-mountsSkill
- migrate-from-openclawSkill
- migrate-clawbridgeSkill
- qodo-pr-resolverSkill
- setupSkill
- update-clawbridgeSkill
- x-integrationSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
25 rules. 0 are common, 21 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 19 edited versions we read keep these.
21
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Run /update-skills in Claude Code.
- Distinctive: line 28
Never proceed with a dirty working tree.
- Distinctive: line 29
Only offer updates for skills the user has already merged (installed).
- Distinctive: line 30
Use git-native operations.
- Distinctive: line 31
Keep token usage low: rely on git commands, only open files with actual conflicts.
- Distinctive: line 38
If output is non-empty:
- Very specific: line 44
If upstream is missing:
- Very specific: line 45
Ask the user for the upstream repo URL (default: https://github.com/other2368-byte/clawbridge-agent.git).
- Distinctive: line 57
Check if the user has merged this skill branch before:
- Distinctive: line 61
Check if there are new commits on the skill branch not yet in HEAD:
- Distinctive: line 63
If this produces output, there are updates available.
- Distinctive: line 72
If no skills have updates available:
- Distinctive: line 74
If there are uninstalled skills, mention them briefly (e.g., "3 other skills available in upstream that you haven't installed").
- Distinctive: line 77
If updates are available:
- Very specific: line 84
Use AskUserQuestion with multiSelect: true to let the user pick which skills to update.
- Distinctive: line 86
Add an option: "Skip — don't update any skills now"
- Distinctive: line 87
If user selects Skip, stop here.
- Distinctive: line 95
If the merge is clean, move to the next skill.
- Distinctive: line 97
Run git status to identify conflicted files.
- Distinctive: line 105
If a merge fails badly (e.g., cannot resolve conflicts):
- Distinctive: line 112
After all selected skills are merged:
- Distinctive: line 118
Only fix issues clearly caused by the merge (missing imports, type mismatches).
- Distinctive: line 119
Do not refactor unrelated code.
- Distinctive: line 120
If unclear, ask the user.
- Distinctive: line 130
If the service is running, remind the user to restart it to pick up changes.
“Common” is measured: kept by at least 6 in 10 of the 19 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
About
Skills are distributed as git branches (skill/*). When you install a skill, you merge its branch into your repo. This skill checks upstream for newer commits on those skill branches and helps you update.
Run /update-skills in Claude Code.
How it works
Preflight: checks for clean working tree and upstream remote.
Detection: fetches upstream, lists all upstream/skill/* branches, determines which ones you've previously merged (via merge-base), and checks if any have new commits.
Selection: presents a list of skills with available updates. You pick which to update.
Update: merges each selected skill branch, resolves conflicts if any, then validates with build + test.
Goal
Help users update their installed skill branches from upstream without losing local customizations.
Operating principles
- Never proceed with a dirty working tree.
- Only offer updates for skills the user has already merged (installed).
- Use git-native operations. Do not manually rewrite files except conflict markers.
- Keep token usage low: rely on
gitcommands, only open files with actual conflicts.
Step 0: Preflight
Run:
git status --porcelain
If output is non-empty:
- Tell the user to commit or stash first, then stop.
Check remotes:
git remote -v
If upstream is missing:
- Ask the user for the upstream repo URL (default:
https://github.com/other2368-byte/clawbridge-agent.git). git remote add upstream <url>
Fetch:
git fetch upstream --prune
Step 1: Detect installed skills with available updates
List all upstream skill branches:
git branch -r --list 'upstream/skill/*'
For each upstream/skill/<name>:
- Check if the user has merged this skill branch before:
git merge-base --is-ancestor upstream/skill/<name>~1 HEAD— if this succeeds (exit 0) for any ancestor commit of the skill branch, the user has merged it at some point. A simpler check:git log --oneline --merges --grep="skill/<name>" HEADto see if there's a merge commit referencing this branch.- Alternative:
MERGE_BASE=$(git merge-base HEAD upstream/skill/<name>)— if the merge base is NOT the initial commit and the merge base includes commits unique to the skill branch, it has been merged. - Simplest reliable check: compare
git merge-base HEAD upstream/skill/<name>withgit merge-base HEAD upstream/main. If the skill merge-base is strictly ahead of (or different from) the main merge-base, the user has merged this skill.
- Check if there are new commits on the skill branch not yet in HEAD:
git log --oneline HEAD..upstream/skill/<name>- If this produces output, there are updates available.
Build three lists:
- Updates available: skills that are merged AND have new commits
- Up to date: skills that are merged and have no new commits
- Not installed: skills that have never been merged
Step 2: Present results
If no skills have updates available:
- Tell the user all installed skills are up to date. List them.
- If there are uninstalled skills, mention them briefly (e.g., "3 other skills available in upstream that you haven't installed").
- Stop here.
If updates are available:
- Show the list of skills with updates, including the number of new commits for each:
skill/<name>: 3 new commits skill/<other>: 1 new commit - Also show skills that are up to date (for context).
- Use AskUserQuestion with
multiSelect: trueto let the user pick which skills to update.- One option per skill with updates, labeled with the skill name and commit count.
- Add an option: "Skip — don't update any skills now"
- If user selects Skip, stop here.
Step 3: Apply updates
For each selected skill (process one at a time):
- Tell the user which skill is being updated.
- Run:
git merge upstream/skill/<name> --no-edit - If the merge is clean, move to the next skill.
- If conflicts occur:
- Run
git statusto identify conflicted files. - For each conflicted file:
- Open the file.
- Resolve only conflict markers.
- Preserve intentional local customizations.
git add <file>
- Complete the merge:
git commit --no-edit
- Run
If a merge fails badly (e.g., cannot resolve conflicts):
git merge --abort- Tell the user this skill could not be auto-updated and they should resolve it manually.
- Continue with the remaining skills.
Step 4: Validation
After all selected skills are merged:
pnpm run buildpnpm test(do not fail the flow if tests are not configured)
If build fails:
- Show the error.
- Only fix issues clearly caused by the merge (missing imports, type mismatches).
- Do not refactor unrelated code.
- If unclear, ask the user.
Step 5: Summary
Show:
- Skills updated (list)
- Skills skipped or failed (if any)
- New HEAD:
git rev-parse --short HEAD - Any conflicts that were resolved (list files)
If the service is running, remind the user to restart it to pick up changes.
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.

