mir-skills-update
Skill2 starsChanged 44 days agoMITView on GitHub
Update globally installed skills using the Skills CLI command documented in README.md
In this repository22 other files it gives its agents.
- AGENTS.mdAGENTS.md
- changelog-bump-verSkill
- gh-copilot-review-readSkill
- gh-copilot-review-resolveSkill
- gh-copilot-reviewSkill
- gh-cr-submitSkill
- gh-issue-fixSkill
- gh-issueSkill
- gh-pr-mergeSkill
- gh-protect-default-branchSkill
- gh-pr-reviewSkill
- gh-prSkill
- gh-releaseSkill
- git-branchSkill
- git-commitSkill
- git-pushSkill
- make-changelogSkill
- mir-skills-installSkill
- python-venvSkill
- save-planSkill
- session-noteSkill
- work-reportSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
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
- Very specific: line 13
Check that npx is available
- Distinctive: line 14
Run the documented command to update globally installed skills
- Distinctive: line 19
Use when the user wants to update globally installed skills.
- Very specific: line 23
Run the exact README command after checking for npx:
- Very specific: line 38
If npx is missing, report the prerequisite error and stop.
≈ “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
What I do
- Check that
npxis available - Run the documented command to update globally installed skills
- Report the update result or the command's error
When to use me
Use when the user wants to update globally installed skills. Invocation authorizes the update without another confirmation prompt.
Workflow
Run the exact README command after checking for npx:
(
set -e
if ! command -v npx >/dev/null 2>&1; then
echo 'Error: npx not found. Install Node.js and npm, then retry.' >&2
exit 1
fi
npx skills@latest update -g
)- On exit code
0, report success and summarize the command's output, including whether skills were updated or already up to date. - If
npxis missing, report the prerequisite error and stop. - On any other failure, report the exit code and command error without claiming success or silently retrying with different flags.
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.

