managing-skills

<objective>
Manage Claude Code skills from multiple source types. This skill handles the full lifecycle of skill management: installation, updates, listing, and removal.
</objective>

<first_action>
When invoked for skill management:
1. Parse the user's request to identify operation type
2. If URL/reference provided, classify the source type
3. If install operation, ask which location (user vs project)
4. Only then proceed to execution
</first_action>

<classify_request>
Before any operation, classify what the user wants:

**Operation type:**
- INSTALL: User wants to add a new skill
- UPDATE: User wants to refresh an existing skill
- LIST: User wants to see installed skills
- REMOVE: User wants to delete a skill
- CHECK: User wants to verify skill source/status

**Source type (for INSTALL/UPDATE):**
- GITHUB_REPO: `user/repo` or `github.com/user/repo` without path after branch
- GITHUB_SUBDIR: URL contains `/tree/<branch>/` followed by a path
- SKILL_ZIP: URL ends with `.skill`

State both classifications before proceeding.
</classify_request>

<workflow>
## Phase 1: Understand Request
- Classify operation and source type
- Identify target skill name
- Determine install location (user vs project)

**Exit criteria:** Operation type, source type, skill name, and location all known.

## Phase 2: Validate
- Check if skill already exists (for install)
- Check if skill exists (for update/remove)
- Verify URL is accessible (for install/update)

**Exit criteria:** Preconditions verified, conflicts identified.

## Phase 3: Execute
- Run appropriate commands from reference sections
- Handle errors per `<error_handling>`

**Exit criteria:** Commands completed without error.

## Phase 4: Verify
- Confirm SKILL.md exists in target location
- Install dependencies if requirements.txt exists
- Report success per `<success_criteria>`

**Exit criteria:** Success criteria met, user reminded to restart.
</workflow>

<install_locations>
Skills can be installed in two locations:

- **Use