Automated summary
Checks and pulls updates for shared skills, handling both project submodules and the global standalone repository at ~/.claude/skills/.
Strengths
- Manages both project submodules and global repositories
- Provides a clear table showing the status of each skill (current, stale, unreachable)
- Allows updating all skills or a specific one by name
- Verifies versions after update to confirm success
Limitations
- Requires each skill to be a git repository
- Does not handle merge conflicts (uses --ff-only)
- Depends on remote repository availability
When you need to check or apply updates to the skills installed in your environment.
If you do not use the git-based skill system or prefer manual updates per repository.
Security analysis
CautionThe skill uses Bash to perform git operations for updating skills. It does not sanitize the provided skill name, leading to potential path traversal. No destructive commands (rm, curl, etc.) or data exfiltration, but the ability to inadvertently update directories outside the intended skill tree warrants caution.
- •Path traversal vulnerability in skill name argument: the script directly interpolates the user-supplied skill name into a directory path without sanitization, allowing an attacker to cd into arbitrary directories if a path like '../../etc' is provided.
- •Executes git pull and submodule update, which modify local files; while legitimate, it could overwrite files if the remote repository is compromised.
Examples
/update-skills/update-skills all/update-skills context7name: update-skills description: Check for and pull updates to shared skills. Handles both project submodules and global standalone clones in ~/.claude/skills/. Use when checking for skill updates, pulling latest versions, or verifying skill health. argument-hint: "[all | skill-name]" allowed-tools:
- Bash
- Read
Update Skills
Check for and pull updates to shared skills. Two sources:
- Project submodules (
.claude/skills/in$CLAUDE_PROJECT_DIR): Agent-specific skills tracked as git submodules. - Global clones (
~/.claude/skills/): Skills shared by all agents, cloned as standalone git repos.
Usage
/update-skills Check all skills for available updates (both sources)
/update-skills all Pull all available updates
/update-skills context7 Pull updates for a specific skill (checks both locations)
Step 0: Create Task List
Use TaskCreate to create these tasks:
- Check global skills for updates
- Check project submodules for updates
- Report status
- Pull updates (if requested)
- Verify updated versions
Mark each task in_progress when you start it and completed when done.
Procedure
Step 1: Check global skills
for dir in ~/.claude/skills/*/; do
[ -d "$dir/.git" ] || continue
name=$(basename "$dir")
cd "$dir"
LOCAL=$(git rev-parse HEAD 2>/dev/null)
git fetch origin --quiet 2>/dev/null
REMOTE=$(git rev-parse origin/main 2>/dev/null || git rev-parse origin/HEAD 2>/dev/null)
if [ -z "$REMOTE" ]; then
echo "UNREACHABLE [global] $name (cannot reach remote)"
elif [ "$LOCAL" != "$REMOTE" ]; then
BEHIND=$(git rev-list HEAD..origin/main --count 2>/dev/null || echo "?")
echo "STALE [global] $name behind=$BEHIND"
else
echo "CURRENT [global] $name"
fi
cd - > /dev/null
done
Step 2: Check project submodules
cd "$CLAUDE_PROJECT_DIR"
git submodule foreach --quiet '
LOCAL=$(git rev-parse HEAD)
REMOTE=$(git ls-remote origin HEAD 2>/dev/null | cut -f1)
if [ -z "$REMOTE" ]; then
echo "UNREACHABLE [project] $name (cannot reach remote)"
elif [ "$LOCAL" != "$REMOTE" ]; then
BEHIND=$(git rev-list HEAD..origin/main --count 2>/dev/null || echo "?")
echo "STALE [project] $name behind=$BEHIND"
else
echo "CURRENT [project] $name"
fi
'
Step 3: Report results
Format the output as a table:
| Source | Skill | Status | Behind | |--------|-------|--------|--------|
- CURRENT: Up to date, no action needed
- STALE: Updates available, show how many commits behind
- UNREACHABLE: Cannot contact remote (network issue or repo moved)
If no argument was provided, stop here (check-only mode). Show the table and ask if the user wants to pull updates.
Step 4: Pull updates (if argument is "all" or a specific skill name)
Global skills:
for dir in ~/.claude/skills/*/; do
[ -d "$dir/.git" ] || continue
name=$(basename "$dir")
cd "$dir"
git pull --ff-only origin main 2>&1 | grep -v "Already up to date" && echo "Updated [global] $name"
cd - > /dev/null
done
Project submodules:
cd "$CLAUDE_PROJECT_DIR"
git submodule update --remote --merge
For a specific skill, check global first, then project:
# Global
if [ -d "$HOME/.claude/skills/SKILL_NAME/.git" ]; then
cd "$HOME/.claude/skills/SKILL_NAME" && git pull --ff-only origin main
fi
# Project submodule
cd "$CLAUDE_PROJECT_DIR"
git submodule update --remote --merge .claude/skills/SKILL_NAME 2>/dev/null
Step 5: Verify
After updating, confirm versions:
echo "=== Global Skills ==="
for dir in ~/.claude/skills/*/; do
[ -d "$dir/.git" ] || continue
echo "$(basename "$dir"): $(cd "$dir" && git rev-parse --short HEAD)"
done
echo "=== Project Submodules ==="
cd "$CLAUDE_PROJECT_DIR"
git submodule foreach --quiet 'echo "$name: $(git rev-parse --short HEAD)"'
Report what was updated and the new commit hashes.
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/update-skills-mrwakasq/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/update-skills-mrwakasq' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/update-skills-mrwakasq/download' --output '.skill-downloads/update-skills-mrwakasq/SKILL.md.part' && mv '.skill-downloads/update-skills-mrwakasq/SKILL.md.part' '.skill-downloads/update-skills-mrwakasq/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/update-skills-mrwakasq/SKILL.md' && test -s '.skill-downloads/update-skills-mrwakasq/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/update-skills' && cp -R '.skill-downloads/update-skills-mrwakasq' '.claude/skills/update-skills'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/update-skills-mrwakasq'openskills read 'update-skills-mrwakasq'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/update-skills-mrwakasq/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.