update-agents
Skill2 starsChanged 7 months agoMITView on GitHub
Check for and apply updates to locally installed agents from the kimgoetzke/coding-agent-configs GitHub repo. Use when user asks to update agents, sync agents, check for agent updates, or mentions updating their agents.
In this repository23 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- .copilot/copilot-instructions.mdCopilot instructions
- ahaSkill
- explain-prSkill
- fetch-planSkill
- generate-pr-descriptionSkill
- grill-meSkill
- improve-a-planSkill
- improve-codebaseSkill
- persistSkill
- planning-modeSkill
- planningSkill
- research-modeSkill
- review-prSkill
- rust-bevy-standardsSkill
- rust-bevy-test-conventionsSkill
- rust-standardsSkill
- tddSkill
- unslopSkill
- update-planSkill
- update-skillsSkill
- write-a-skillSkill
- wtfSkill
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 9 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
Distinctive · estimate
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
- Very specific: line 9
Check for updates to locally installed agents by fetching the latest from kimgoetzke/coding-agent-configs on GitHub and comparing against …
- Distinctive: line 24
If you cannot determine which tool you are, ask the user.
- Distinctive: line 32
If you are Claude Code, set:
- Distinctive: line 35
If you are Copilot, set:
- Distinctive: line 38
If you are Pi, set:
- Distinctive: line 42
If you cannot determine which tool you are, ask the user before proceeding.
- Distinctive: line 44
Only use the directory for the currently running tool.
- Distinctive: line 48
Run the check script using the current tool's skill directory:
- Very specific: line 69
If ALL_UP_TO_DATE: tell the user all agents are up to date and stop
- Distinctive: line 73
Ask the user if they want to apply this update
- Distinctive: line 87
After processing all agents, print a summary:
≈ “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 Agents
Check for updates to locally installed agents by fetching the latest from kimgoetzke/coding-agent-configs on GitHub and comparing against the local agents directory for the current coding agent product.
Configuration
- Remote repo:
https://github.com/kimgoetzke/coding-agent-configs.git - Scripts location: Bundled in this skill's
scripts/directory
Target directory by tool
| Tool | Default target directory |
| Claude Code | ~/.claude/agents |
| Copilot | ~/.copilot/agents |
| Pi | ~/.pi/agent/agents |
If you cannot determine which tool you are, ask the user.
Workflow
1. Determine the current tool and target directory
First determine which tool is currently running this skill:
- If you are Claude Code, set:
TARGET_DIR=~/.claude/agentsSKILL_DIR=~/.claude/skills/update-agents
- If you are Copilot, set:
TARGET_DIR=~/.copilot/agentsSKILL_DIR=~/.copilot/skills/update-agents
- If you are Pi, set:
TARGET_DIR=~/.pi/agent/agentsSKILL_DIR=~/.pi/agent/skills/update-agents
If you cannot determine which tool you are, ask the user before proceeding.
Only use the directory for the currently running tool. Do not check or update the other tool's agents directory.
2. Check for updates
Run the check script using the current tool's skill directory:
bash "$SKILL_DIR/scripts/check-updates.sh" "$TARGET_DIR"3. Parse the output
The script outputs one line per agent file with a status prefix:
| Prefix | Meaning |
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_DATE | No updates available at all |
Agent files 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 agents are up to date and stop - Otherwise, FOR EACH
CHANGEDorMISSING_LOCALLYagent file:- List the file name and summarise what changed
- Show the diff in a code block
- Ask the user if they want to apply this update
5. Apply updates
For each agent file the user approves, run:
bash "$SKILL_DIR/scripts/apply-update.sh" "$TARGET_DIR" <agent-file>Report success or failure for each.
6. Summary
After processing all agents, print a summary:
- How many agents were updated
- How many were skipped
- How many were already up to date
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.