agentleFS
mcarmona1064-cellmcarmona1064-cell/clawbridge-codex/.claude/skills/update-skills/SKILL.md

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

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.
  • TomGranotSkill

    add-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

  • TomGranotSkill

    add-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

  • qwibitaiSkill

    add-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

  • qwibitaiSkill

    add-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

  • b1rdmaniaSkill

    migrate-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

  • MicrosoftSkill

    act-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

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
  1. Very specific:

    Run /update-skills in Claude Code.

    line 10
  2. Distinctive:

    Never proceed with a dirty working tree.

    line 28
  3. Distinctive:

    Only offer updates for skills the user has already merged (installed).

    line 29
  4. Distinctive:

    Use git-native operations.

    line 30
  5. Distinctive:

    Keep token usage low: rely on git commands, only open files with actual conflicts.

    line 31
  6. Distinctive:

    If output is non-empty:

    line 38
  7. Very specific:

    If upstream is missing:

    line 44
  8. Very specific:

    Ask the user for the upstream repo URL (default: https://github.com/other2368-byte/clawbridge-agent.git).

    line 45
  9. Distinctive:

    Check if the user has merged this skill branch before:

    line 57
  10. Distinctive:

    Check if there are new commits on the skill branch not yet in HEAD:

    line 61
  11. Distinctive:

    If this produces output, there are updates available.

    line 63
  12. Distinctive:

    If no skills have updates available:

    line 72
  13. Distinctive:

    If there are uninstalled skills, mention them briefly (e.g., "3 other skills available in upstream that you haven't installed").

    line 74
  14. Distinctive:

    If updates are available:

    line 77
  15. Very specific:

    Use AskUserQuestion with multiSelect: true to let the user pick which skills to update.

    line 84
  16. Distinctive:

    Add an option: "Skip — don't update any skills now"

    line 86
  17. Distinctive:

    If user selects Skip, stop here.

    line 87
  18. Distinctive:

    If the merge is clean, move to the next skill.

    line 95
  19. Distinctive:

    Run git status to identify conflicted files.

    line 97
  20. Distinctive:

    If a merge fails badly (e.g., cannot resolve conflicts):

    line 105
  21. Distinctive:

    After all selected skills are merged:

    line 112
  22. Distinctive:

    Only fix issues clearly caused by the merge (missing imports, type mismatches).

    line 118
  23. Distinctive:

    Do not refactor unrelated code.

    line 119
  24. Distinctive:

    If unclear, ask the user.

    line 120
  25. Distinctive:

    If the service is running, remind the user to restart it to pick up changes.

    line 130

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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 git commands, 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>:

  1. 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>" HEAD to 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> with git 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.
  2. 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: true to 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):

  1. Tell the user which skill is being updated.
  2. Run: git merge upstream/skill/<name> --no-edit
  3. If the merge is clean, move to the next skill.
  4. If conflicts occur:
    • Run git status to 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

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 build
  • pnpm 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.