agentleFS
kimgoetzkekimgoetzke/coding-agent-configs/skills/update-skills/SKILL.md

update-skills

Skill2 starsChanged 7 months agoMITView on GitHub

Check for and apply updates to locally installed skills from the kimgoetzke/coding-agent-configs GitHub repo. Use when user asks to update skills, sync skills, check for skill updates, or mentions updating their skills.

18 other projects use a version of this.

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

We split this skill into the rules it gives an agent

6 rules. 0 are common, 4 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 18 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Check for updates to locally installed skills by fetching the latest from kimgoetzke/coding-agent-configs on GitHub and comparing against …

    line 9
  2. Distinctive:

    If you cannot determine which tool you are, ask the user.

    line 24
  3. Distinctive:

    Run the check script:

    line 40
  4. Very specific:

    If ALL_UP_TO_DATE: tell the user all skills are up to date and stop

    line 61
  5. Distinctive:

    Ask the user if they want to apply this update

    line 65
  6. Distinctive:

    After processing all skills, print a summary:

    line 79

“Common” is measured: kept by at least 6 in 10 of the 18 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

Update Skills

Check for updates to locally installed skills by fetching the latest from kimgoetzke/coding-agent-configs on GitHub and comparing against the local skills directory.

Configuration

  • Remote repo: https://github.com/kimgoetzke/coding-agent-configs.git
  • Scripts location: Bundled in this skill's scripts/ directory

Target directory by tool

ToolDefault target directory
Claude Code~/.claude/skills
Copilot~/.copilot/skills
Pi~/.pi/agent/skills

If you cannot determine which tool you are, ask the user.

Workflow

1. Determine target directory

Set the target directory based on the table above. Use the variable TARGET_DIR in subsequent steps.

Also resolve SKILL_DIR to the absolute path of this locally installed skill directory. Typical values:

  • Claude Code: ~/.claude/skills/update-skills
  • Copilot: ~/.copilot/skills/update-skills
  • Pi: ~/.pi/agent/skills/update-skills

2. Check for updates

Run the check script:

bash "$SKILL_DIR/scripts/check-updates.sh" "$TARGET_DIR"

3. Parse the output

The script outputs one line per skill with a status prefix:

PrefixMeaning
UP_TO_DATE:<name>No changes
CHANGED:<name>Files differ — diff follows until END_DIFF line
MISSING_LOCALLY:<name>Exists in repo but missing locally
ALL_UP_TO_DATENo updates available at all

Skills that exist locally but not in the remote repo are ignored.

4. Present results to the user

  • If ALL_UP_TO_DATE: tell the user all skills are up to date and stop
  • Otherwise, FOR EACH CHANGED or MISSING_LOCALLY skill:
    • List the skill name and summarise what changed (files added/removed/modified)
    • Show the diff in a code block
    • Ask the user if they want to apply this update

5. Apply updates

For each skill the user approves, run:

bash "$SKILL_DIR/scripts/apply-update.sh" "$TARGET_DIR" <skill-name>

Report success or failure for each.

6. Summary

After processing all skills, print a summary:

  • How many skills were updated
  • How many were skipped
  • How many were already up to date

Finally, ask the user if they wish to use the /update-agents skill to sync any agents from the remote repo.

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.