update-skills-via-skills-sh
Skill1 starsChanged 14 days agoMITView on GitHub
Use when installing or updating agent skills with skills.sh, avoiding repo-local .agents installs, or enabling OMP discovery. Not for skill authoring.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- vladcheck/skillsword for word, first seen Nov 1, 2026
Other versions1 project uses a version of this.
Word for word · 1
- vladcheck/skills★ 1100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
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 repository19 other files it gives its agents.
- analyze-session-pingpong-logsSkill
- create-glossarySkill
- deepseek-reasoning-tier-clarifierSkill
- defineSkill
- find-alternativesSkill
- get-note-links-from-textSkill
- gitlab-eas-tickets-publishSkill
- gitlab-mr-roundtripSkill
- git-rebuild-branchSkill
- git-sequentialSkill
- gost-report-rebuildSkill
- mattpocock-skills-researchSkill
- mirea-moodle-downloadSkill
- obsidian-add-links-to-noteSkill
- opsx-spec-validateSkill
- paretto-principleSkill
- publish-spec-gitlab-milestoneSkill
- publish-tickets-gitlabSkill
- solidSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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
- Distinctive: line 21
Use the same command for both operations.
- Very specific: line 23
Verify each expected skill at the global Claude Code location.
- Very specific: line 37
If project-local installation was not requested, distinguish new output from pre-existing content.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
Install or update skills via skills.sh
Record the original directory, then set the command working directory to the user's home directory. The current working directory determines where the CLI can create
./.agents/skills/; running from a repository can pollute that repository instead of producing the intended global installation.project_dir=$PWD cd "$HOME"Install or update from a source identified as
<owner>/<repo>:DISABLE_TELEMETRY=1 npx -y skills add <owner>/<repo>Use the same command for both operations. Rerun it to overwrite previously installed skills with the source's current versions.
Verify each expected skill at the global Claude Code location; do not treat CLI success or an
.agentsdirectory alone as proof of installation:test -f "$HOME/.claude/skills/<skill-name>/SKILL.md"Inspect the original directory for an unintended repository-local installation:
if [ -d "$project_dir/.agents" ]; then printf 'Inspect installation output: %s\n' "$project_dir/.agents" fiIf project-local installation was not requested, distinguish new output from pre-existing content. Move only confirmed unwanted output to a trash or backup location; if
.agentspre-existed, move only the newly added skill entries. Do not recursively delete the directory.Inspect the OMP configuration actually loaded in the target environment, following includes or symlinks when present rather than assuming a personal dotfiles path. Ensure
skills.customDirectoriesincludes~/.claude/skills, preserving the active configuration's existing style:skills: customDirectories: - ~/.claude/skillsConfirm that the configured directory exists:
test -d "$HOME/.claude/skills"
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.

