simple-skills-manager（简单技能经理）

Simple Skills Manager

Manage skill tips in ~/.claude/skills/ that point to skills from local paths or git repositories, enabling dynamic invocation via /{group}-{skill-name}.

Note: We use hyphen - as separator instead of colon : because Windows paths don't support colons in filenames.

Constants

• Repos directory: ~/.claude/simple-skills-manager-repos/
• Skills directory: ~/.claude/skills/
• Backup directory: ~/.claude/simple-skills-manager-backup-last-skills/

Workflow

Step 1: Ask Operation Type

First, ask the user what operation they want to perform:

{
  "questions": [{
    "question": "What operation would you like to perform?",
    "header": "Operation",
    "options": [
      {"label": "Add (Recommended)", "description": "Add skills from a local path or git repository"},
      {"label": "Update", "description": "Update an existing skill group (re-sync from source)"},
      {"label": "Remove", "description": "Remove an existing skill group"}
    ],
    "multiSelect": false
  }]
}

Step 2: Collect Information Based on Operation

For "Add" Operation

Ask user to directly input the source path or git URL:

{
  "questions": [{
    "question": "Please enter the local path or git URL for the skills:",
    "header": "Source",
    "options": [
      {"label": "Example: /path/to/skills", "description": "Local directory containing SKILL.md files"},
      {"label": "Example: https://github.com/user/repo.git", "description": "Git repository URL (will be cloned)"}
    ],
    "multiSelect": false
  }]
}

The user will select "Other" and type the actual path or URL. The system will auto-detect the source type:

• Git URL: starts with http://, https://, git@, or ends with .git
• Local path: everything else (treat as filesystem path)

After getting the source, ask for the group name:

{
  "questions": [{
    "question": "What group name should be used as prefix? (e.g., 'mygroup' creates '/mygroup-skill-name')",
    "header": "Group",
    "options": [
      {"label": "Use folder name", "description": "Use the source folder/repo name as group"},
      {"label": "Custom", "description": "Enter a custom group name"}
    ],
    "multiSelect": false
  }]
}

Group name validation: The group name must:

• Only contain lowercase letters, numbers, and hyphens (a-z, 0-9, -)
• Not start or end with a hyphen
• Not be empty
• Not contain spaces, slashes, asterisks, or other special characters

If the group name is invalid, ask the user to provide a valid name.

For "Update" or "Remove" Operation

First, list existing groups by checking subdirectories in repos directory:

# List groups from repos directory (source of truth for groups)
ls -d ~/.claude/simple-skills-manager-repos/*/ 2>/dev/null | xargs -I {} basename {}

Important: Groups are determined by subdirectories in ~/.claude/simple-skills-manager-repos/, NOT by folder names in skills directory.

Display the found groups as reference information, then ask the user to input the group name they want to manage:

{
  "questions": [{
    "question": "Which group do you want to update/remove? (Enter the group name)",
    "header": "Group",
    "options": [
      {"label": "Example: mygroup", "description": "Enter the group name you want to manage"},
      {"label": "Example: arcblock", "description": "The group prefix used in skill names like /arcblock-commit"}
    ],
    "multiSelect": false
  }]
}

The user will select "Other" and type the actual group name. Validate that the group exists by checking if ~/.claude/simple-skills-manager-repos/{group}/ directory exists before proceeding.

Step 3: Backup Before Operation (Required)

Before executing any Add, Update, or Remove operation, you MUST backup the current skills directory:

# Remove old backup if exists, then create new backup
rm -rf ~/.claude/simple-skills-manager-backup-last-skills
cp -r ~/.claude/skills ~/.claude/simple-skills-manager-backup-last-skills

This ensures the user can recover their skills if something goes wrong.

Step 4: Execute Operation

Add Operation

1. Verify and prepare source:

- If local path: Verify the path exists first, then create group directory mkdir -p ~/.claude/simple-skills-manager-repos/{group} echo "{absolute-working-path}" > ~/.claude/simple-skills-manager-repos/{group}/path.txt - If git URL: - If group directory already exists and has .git, run git pull instead: git -C ~/.claude/simple-skills-manager-repos/{group} pull - Otherwise, clone to ~/.claude/simple-skills-manager-repos/{group}/: git clone {git-url} ~/.claude/simple-skills-manager-repos/{group} - If clone/pull fails, stop and report error - do not proceed

1. Determine working path:

- Local path: use the path from user input - Git URL: use ~/.claude/simple-skills-manager-repos/{group}/

1. Scan for skills in the working path: find "{working-path}" -name "SKILL.md" -type f 2>/dev/null

- If no SKILL.md found, stop and report error - do not proceed

1. Clean existing tips for this group (if group already exists):

- Read ~/.claude/simple-skills-manager-repos/{group}/skill-names.txt if it exists - Delete each skill listed in the file: # For each skill-name in skill-names.txt rm -rf ~/.claude/skills/{skill-name}

1. Create skill tips for each SKILL.md found (see "Creating Skill Tips" section)
2. Save skill manifest - write all created skill names to skill-names.txt: # Write skill names (one per line) to skill-names.txt echo "{group}-{skill-name-1}" > ~/.claude/simple-skills-manager-repos/{group}/skill-names.txt echo "{group}-{skill-name-2}" >> ~/.claude/simple-skills-manager-repos/{group}/skill-names.txt #... for each skill Example skill-names.txt content: my-commit my-deploy my-test
3. Report results

Update Operation

1. Verify group exists:

- Check if ~/.claude/simple-skills-manager-repos/{group}/ directory exists - If not exists, stop and report error - group not found

1. Determine source type and pull latest:

- Git source: Check if it's a git repo (has .git directory) test -d ~/.claude/simple-skills-manager-repos/{group}/.git && echo "git" || echo "local" - If git repo, run git pull first: git -C ~/.claude/simple-skills-manager-repos/{group} pull - Working path: ~/.claude/simple-skills-manager-repos/{group}/ - Local path source: Check if path.txt exists in the group directory cat ~/.claude/simple-skills-manager-repos/{group}/path.txt - If exists, read the original path from it - If path.txt not found, ask user to provide the source path - Working path: the path from path.txt or user input

1. Scan for skills in the working path: find "{working-path}" -name "SKILL.md" -type f 2>/dev/null

- If no SKILL.md found, stop and report error - do not proceed

1. Clean existing tips using skill manifest (if exists):

- Read ~/.claude/simple-skills-manager-repos/{group}/skill-names.txt if it exists - Delete each skill listed in the file: # For each skill-name in skill-names.txt rm -rf ~/.claude/skills/{skill-name}

1. Recreate skill tips for each SKILL.md found (see "Creating Skill Tips" section)
2. Update skill manifest - overwrite skill-names.txt with new skill names
3. Report results (include git pull output if applicable)

Remove Operation

1. Verify group exists:

- Check if ~/.claude/simple-skills-manager-repos/{group}/ directory exists - If not exists, stop and report error - group not found

1. Remove skill tips using skill manifest (if exists):

- Read ~/.claude/simple-skills-manager-repos/{group}/skill-names.txt if it exists - Delete each skill listed in the file: # For each skill-name in skill-names.txt rm -rf ~/.claude/skills/{skill-name}

1. Remove group directory from repos: rm -rf ~/.claude/simple-skills-manager-repos/{group}
2. Report results

Creating Skill Tips

For each SKILL.md found, extract:

1. Skill name: From name: field in frontmatter, or from parent directory name
2. Description: From description: field in frontmatter
3. Allowed tools: From allowed-tools: field in frontmatter

Create directory and SKILL.md in ~/.claude/skills/{group}-{skill-name}/SKILL.md:

mkdir -p ~/.claude/skills/{group}-{skill-name}

Generated SKILL.md format:

---
name: {group}-{skill-name}
description: {original-description}
allowed-tools:
  - Read
  - Glob
  - Grep
  {... copy remaining allowed-tools from original skill, excluding duplicates}
---

# {group}-{skill-name}

This is a tip pointing to a skill from external source.

## Instructions

**IMPORTANT**: Read and execute the skill from the following path:

{absolute-path-to-original-SKILL.md}

Use the Read tool to load the actual skill content, then follow all instructions in that file.

Note: When copying allowed-tools, always include Read, Glob, Grep first (required for tip to work), then add any additional tools from the original skill that are not already listed.

Example Workflows

Adding from Git

1. User runs /simple-skills-manager
2. Agent asks: "What operation?" -> User selects "Add"
3. Agent asks: "Please enter the local path or git URL" -> User types: https://github.com/example/my-skills.git
4. Agent auto-detects it's a git URL
5. Agent asks: "Group name?" -> User selects "Use folder name" (becomes my-skills)
6. Agent validates group name format
7. Agent backs up ~/.claude/skills/ to ~/.claude/simple-skills-manager-backup-last-skills/
8. Agent clones repo to ~/.claude/simple-skills-manager-repos/my-skills/, scans skills, verifies SKILL.md files found
9. Agent cleans old tips (if skill-names.txt exists), creates new tips
10. Agent writes skill-names.txt with: my-skills-setup, my-skills-deploy, my-skills-test
11. Agent reports: "Created 3 skill tips: /my-skills-setup, /my-skills-deploy, /my-skills-test"

Adding from Local Path

1. User runs /simple-skills-manager
2. Agent asks: "What operation?" -> User selects "Add"
3. Agent asks: "Please enter the local path or git URL" -> User types: /home/user/projects/my-plugin
4. Agent auto-detects it's a local path, verifies path exists
5. Agent asks: "Group name?" -> User types custom name: myteam
6. Agent validates group name format
7. Agent backs up ~/.claude/skills/ to ~/.claude/simple-skills-manager-backup-last-skills/
8. Agent creates ~/.claude/simple-skills-manager-repos/myteam/ and writes path.txt with the local path
9. Agent scans skills, verifies SKILL.md files found
10. Agent cleans old tips (if skill-names.txt exists), creates new tips
11. Agent writes skill-names.txt with: myteam-build, myteam-release
12. Agent reports: "Created 2 skill tips: /myteam-build, /myteam-release"

Updating a Group

1. User runs /simple-skills-manager
2. Agent asks: "What operation?" -> User selects "Update"
3. Agent lists existing groups by checking subdirectories in ~/.claude/simple-skills-manager-repos/
4. User types: my-skills
5. Agent validates group exists (subdirectory exists in repos)
6. Agent backs up ~/.claude/skills/ to ~/.claude/simple-skills-manager-backup-last-skills/
7. Agent checks if it's a git repo (has .git) or local (has path.txt)
8. If git: runs git pull; if local: reads path from path.txt
9. Agent scans skills, verifies SKILL.md files found
10. Agent reads skill-names.txt and deletes listed skills
11. Agent recreates tips and updates skill-names.txt
12. Agent reports: "Updated 3 skill tips for group 'my-skills'"

Removing a Group

1. User runs /simple-skills-manager
2. Agent asks: "What operation?" -> User selects "Remove"
3. Agent lists existing groups by checking subdirectories in ~/.claude/simple-skills-manager-repos/
4. User types: my-skills
5. Agent validates group exists (subdirectory exists in repos)
6. Agent backs up ~/.claude/skills/ to ~/.claude/simple-skills-manager-backup-last-skills/
7. Agent reads skill-names.txt and deletes listed skills
8. Agent removes group directory from repos
9. Agent reports: "Removed group 'my-skills' and its repository/metadata"

Notes

• Backup directory: ~/.claude/simple-skills-manager-backup-last-skills/ - created before each operation
• Repos directory structure:

- Git sources: ~/.claude/simple-skills-manager-repos/{group}/ (contains .git + skill-names.txt) - Local sources: ~/.claude/simple-skills-manager-repos/{group}/ (contains path.txt + skill-names.txt)

• Skill manifest: skill-names.txt stores exact skill folder names (one per line), used for precise deletion/update
• Group detection: Groups are identified by subdirectories in ~/.claude/simple-skills-manager-repos/, NOT by skill folder names
• Naming convention: Skills use hyphen - as separator (e.g., {group}-{skill-name}) for Windows compatibility
• Local path sources are referenced directly, not copied
• Tips dynamically load content, so changes to original skills are reflected immediately
• Each group's tips are managed independently
• The original skill files are never modified
• Skills are loaded at startup - restart Claude Code after adding/updating skills