How do I install the Update Skills skill?

Run npx skillmds@latest add beargrass/update-skills in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Update Skills safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Update Skills?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Update Skills free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under Apache-2.

Who published Update Skills?

beargrass (@beargrass) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Update Skills by beargrass — Agent Skill

Name: Update Skills
Author: beargrass

Update Skills

Regenerate project workflow skills (.claude/skills/) without touching any documentation. TRIGGER when: user says "update skills", "regenerate skills", "refresh skills", "update project skills", "只更新skill", "重新生成技能", or wants to update skills after ai-dev-setup without redoing docs. DO NOT TRIGGER when: user wants full setup (use /ai-dev-setup instead).

beargrass 9587056 2.6 KB Updated Sep 17, 2026

File contents

Update Project Skills

Regenerate .claude/skills/ workflow files for the current project. Docs are untouched.

Usage

/update-skills [doc-directory-name]

If $ARGUMENTS is provided, use it as DOC_DIR. Otherwise detect from CLAUDE.md.

Step 1: Read Project Config

Read CLAUDE.md — extract:
- DOC_DIR: look for documentation links like (./.docs/ or (./docs/ — use that directory name
- BUILD_CMD, TEST_CMD, LINT_CMD, TEST_COVER_CMD from Build & Run / Testing sections
- If $ARGUMENTS is provided, override DOC_DIR with it
If CLAUDE.md not found: ask user for DOC_DIR and commands before proceeding

Set variables: DOC_DIR, TEST_CMD, LINT_CMD, TEST_COVER_CMD, RACE_FLAG (Go projects only, -race)

Report extracted values. Wait for confirmation.

Step 2: Check Existing Skills

List .claude/skills/ contents. Report which of these already exist:

plan, dev, dev-resume, test, test-resume, sync-docs

If any exist: warn they will be overwritten. Wait for confirmation.

Step 3: Generate Skills

Load: ../ai-dev-setup/references/skill-templates.md

Generate all 6 skills into .claude/skills/, replacing placeholders:

{DOC_DIR} → detected DOC_DIR
{TEST_CMD} → detected TEST_CMD
{LINT_CMD} → detected LINT_CMD
{TEST_COVER_CMD} → detected TEST_COVER_CMD
{RACE_FLAG} → detected RACE_FLAG

Skills to generate: plan, dev, dev-resume, test, test-resume, sync-docs

Step 4: Report

## Skills Updated

DOC_DIR: {DOC_DIR}
TEST_CMD: {TEST_CMD}

Updated:
- .claude/skills/plan/SKILL.md
- .claude/skills/dev/SKILL.md
- .claude/skills/dev-resume/SKILL.md
- .claude/skills/test/SKILL.md
- .claude/skills/test-resume/SKILL.md
- .claude/skills/sync-docs/SKILL.md

Docs untouched. Run /plan to start planning, /dev to develop, /test to improve coverage.

Error Handling

Situation	Action
CLAUDE.md missing	Ask user for DOC_DIR and commands
DOC_DIR not found in CLAUDE.md	Ask user which directory to use
skill-templates.md not found	Report path tried, ask user to provide commands manually
`.claude/skills/` missing	Create it

---name: update-skillsdescription: Regenerate project workflow skills (.claude/skills/) without touching any documentation. TRIGGER when: user says "update skills", "regenerate skills", "refresh skills", "update project skills", "只更新skill", "重新生成技能", or wants to update skills after ai-dev-setup without redoing docs. DO NOT TRIGGER when: user wants full setup (use /ai-dev-setup instead).license: Apache-2.0---# Update Project SkillsRegenerate `.claude/skills/` workflow files for the current project. Docs are untouched.## Usage```/update-skills [doc-directory-name]```If `$ARGUMENTS` is provided, use it as `DOC_DIR`. Otherwise detect from CLAUDE.md.---## Step 1: Read Project Config1. Read `CLAUDE.md` — extract: - `DOC_DIR`: look for documentation links like `(./.docs/` or `(./docs/` — use that directory name - `BUILD_CMD`, `TEST_CMD`, `LINT_CMD`, `TEST_COVER_CMD` from Build & Run / Testing sections - If `$ARGUMENTS` is provided, override `DOC_DIR` with it2. If CLAUDE.md not found: ask user for `DOC_DIR` and commands before proceedingSet variables: `DOC_DIR`, `TEST_CMD`, `LINT_CMD`, `TEST_COVER_CMD`, `RACE_FLAG` (Go projects only, `-race`)**Report extracted values. Wait for confirmation.**---## Step 2: Check Existing SkillsList `.claude/skills/` contents. Report which of these already exist:- plan, dev, dev-resume, test, test-resume, sync-docsIf any exist: warn they will be overwritten. Wait for confirmation.---## Step 3: Generate Skills> **Load:** [../ai-dev-setup/references/skill-templates.md](../ai-dev-setup/references/skill-templates.md)Generate all 6 skills into `.claude/skills/`, replacing placeholders:- `{DOC_DIR}` → detected DOC_DIR- `{TEST_CMD}` → detected TEST_CMD- `{LINT_CMD}` → detected LINT_CMD- `{TEST_COVER_CMD}` → detected TEST_COVER_CMD- `{RACE_FLAG}` → detected RACE_FLAGSkills to generate: plan, dev, dev-resume, test, test-resume, sync-docs---## Step 4: Report```## Skills UpdatedDOC_DIR: {DOC_DIR}TEST_CMD: {TEST_CMD}Updated:- .claude/skills/plan/SKILL.md- .claude/skills/dev/SKILL.md- .claude/skills/dev-resume/SKILL.md- .claude/skills/test/SKILL.md- .claude/skills/test-resume/SKILL.md- .claude/skills/sync-docs/SKILL.mdDocs untouched. Run /plan to start planning, /dev to develop, /test to improve coverage.```---## Error Handling| Situation | Action ||-----------|--------|| CLAUDE.md missing | Ask user for DOC_DIR and commands || DOC_DIR not found in CLAUDE.md | Ask user which directory to use || skill-templates.md not found | Report path tried, ask user to provide commands manually || `.claude/skills/` missing | Create it |

Frequently asked questions