---
name: skills
description: Browse and search all available skills, grouped by workflow stage or activity type
type: ops
version: v0.5
argument-hint: "[list | types | search <keyword>]"
---

# Skills

Discover and search installed global skills plus enabled project-local pack skills, grouped by workflow stage or activity type.

## Process

1. **Parse arguments:**
   - If `$ARGUMENTS` is empty or `list` → **list mode** (show all skills grouped by workflow stage).
   - If `$ARGUMENTS` is `types` → **type mode** (show all skills grouped by activity type).
   - If `$ARGUMENTS` starts with `search ` → **search mode** (filter by keyword after `search`).

2. **Discover skills:**
   - Always scan global Claude skills in `global/claude/*/SKILL.md`.
   - If `.agents/project.json` exists, read `enabled_packs` and scan `packs/<pack>/claude/*/SKILL.md` for each enabled pack. Also scan sub-directories like `packs/<pack>/claude/<skill>/frameworks/*/SKILL.md` for sub-skills.
   - Also scan all packs in `packs/*/claude/*/SKILL.md` (and `frameworks/*/SKILL.md` children) to discover available-but-not-installed skills.
   - If `.claude/skills/*/SKILL.md` exists in the current project, include those local skills too.
   - Read the first 10 lines of each file to extract YAML frontmatter fields: `name`, `description`, `type`, `invocation`, `parent`.
   - Track which pack each skill belongs to (if any).
   - Default `invocation` to `primary` when the field is absent.

3. **Group skills by workflow stage** using this static mapping:

   The mapping includes global skills and pack-provided skills. Only skills
   discovered in step 2 should be printed, so domain and kanban entries appear
   only when the corresponding project-local pack is enabled or linked.
   PoketoWork kanban skills are intentionally absent while the kanban packs are hibernated.

   | Stage | Skills (pack in parentheses; no label = global) |
   |-------|--------|
   | Pack Management | `pack`, `pack list`, `pack status`, `pack recommend`, `pack install <pack-or-skill>`, `pack remove <pack-or-skill>`, `pack which <skill>` |
   | Discovery & Market Fit | `customer-discovery` (business-discovery), `enterprise-icp` (business-discovery) |
   | Game Development | `game-workflow` (game), `game-audience` (game), `game-fantasy` (game), `game-genre-map` (game), `game-comparables` (game), `game-core-loop` (game), `game-prototype-test` (game), `game-store-page-test` (game), `game-playtest-metrics` (game), `game-roadmap` (game), `game-launch` (game) |
   | Devtool Development | `devtool-workflow` (devtool), `devtool-user-map` (devtool), `devtool-integration-map` (devtool), `devtool-dx-journey` (devtool), `devtool-adoption` (devtool), `devtool-positioning` (devtool), `devtool-monetization` (devtool), `devtool-docs-audit` (devtool) |
   | Planning | `idea-scope-brief`, `brainstorm` (product-design), `feature-interview` (product-design), `user-flow-map` (product-design), `spec-interview` (product-design), `spec-interview --ideas` (product-design), `ui-interview` (product-design), `ux-variations` (product-design), `consolidate-variations` (product-design), `experiment` (business-growth) |
   | Mapping | `journey-map` (customer-lifecycle), `metrics` (business-ops) |
   | Strategize | `roadmap` (agent-work-admin), `competitive-analysis` (business-discovery), `platform-strategy` (business-growth), `gtm` (business-growth), `landing-copy` (business-growth), `monetization` (business-growth), `positioning` (business-discovery), `runway-model` (business-ops) |
   | Evaluate | `dogfood` (product-testing), `mvp-gap` (business-discovery), `scale-audit` (business-ops), `customer-feedback` (customer-lifecycle), `assumption-tracker` (business-discovery), `cohort-review` (customer-lifecycle), `retro` (business-ops) |
   | Research Health | `research-roadmap` (research-admin), `reconcile-research` (business-discovery), `reconcile-dev-docs` (docs-health) |
   | Detail | `plan-phase` (agent-work-admin) |
   | Execution | `exec` (exec-loop), `guide` (guided-walkthrough) |
   | Shipping | `ship` (exec-loop), `ship-end` (exec-loop) |
   | Code Quality | `expert-review` (code-review), `regression-check` (code-review), `dead-code` (code-review), `slim-audit` (code-review) |
   | Debugging | `investigate` (code-debug), `debug` (code-debug), `trace` (code-debug), `session-triage` (session-analytics) |
   | Refactoring & Migration | `migrate` (code-maintenance), `decommission` (teardown), `scaffold` (monorepo) |
   | Monorepo | `affected` (monorepo), `mono-plan` (monorepo), `mono-guard` (monorepo) |
   | Release & Deploy | `release` (release-ops), `deploy` (release-ops), `branch-lifecycle` (release-ops) |
   | Context & Session | `afps-status`, `codebase-status`, `analyze-sessions` (session-analytics), `handoff` (context-transfer), `sync` (gitops), `investor-update` (business-ops) |
   | Skill Development | `targeted-skill-builder` (skill-dev), `skill-interview` (skill-dev), `create-agentic-skill` (skill-dev), `create-local-skill` (skill-dev) |
   | Testing | `uat` (product-testing), `uat-guide` (guided-walkthrough), `quiz-me` (knowledge-check) |
   | Utility | `commit-and-push-by-feature` (gitops), `init-agentic-skills`, `provision-agentic-config`, `skills`, `bootstrap-repo` (repo-maintenance), `desk-flip` (teardown), `compile-central-alignment` (alignment-page-admin), `patch-exec-profile` (exec-profile), `delegate` (agent-bridge), `report-website` (report-gen), `icon-handler` (website-polish), `design-system` (product-design), `prototype` (product-design), `spec-drift` (agent-work-admin), `hygiene` (docs-health), `update-packages` (code-maintenance) |

   Skills not found in the mapping go into an **Other** group at the end.

4. **Group skills by activity type** (type mode only) using the `type` field from frontmatter:

   | Type | Description |
   |------|-------------|
   | `research` | Web search + analysis → produces documents |
   | `analysis` | Reads codebase/docs → produces assessments |
   | `planning` | Interactive → produces specs/plans |
   | `execution` | Writes/modifies code |
   | `review` | Reads code → reports issues (no changes) |
   | `debugging` | Investigates + fixes problems |
   | `shipping` | Commits, deploys, session management |
   | `ops` | Manages boards, branches, meta-tooling |

   Display order: research → analysis → planning → execution → review → debugging → shipping → ops.
   Skills with no `type` field go into an **Other** group at the end.

5. **Apply filter (search mode only):**
   - Match the keyword case-insensitively against each skill's `name`, `description`, and `type`.
   - Keep only matching skills. Remove empty groups.

6. **Output results:**
   - Print each non-empty group as a `## Group Name` heading.
   - Under each heading, list installed/global primary and chained skills as `/<name> — <description>  [type]`.
   - Show orchestrator skills with an `⚙` prefix: `⚙ /<name> — <description>  [type]`.
   - Show sub-skills indented under their parent skill (identified by the `parent:` frontmatter field or by living under a `frameworks/` directory). Format: `  ↳ /<name> — <description>  [sub-skill]`. If the parent is not in the same group, place sub-skills in a "Sub-skills" subsection at the end of the parent's group.
   - For available-but-not-installed pack skills, list as `/<name> — <description>  [type]  ⚠ requires \`/pack install <skill>\` or \`/pack install <pack>\``.
   - Omit groups that have no skills (after filtering in search mode).
   - At the bottom, print a total count: `**N skills** installed (M sub-skills), **P skills** available via packs` (or `**N skills** matching "<keyword>"`).

## Output

### List mode (default — grouped by workflow stage)
```
## Discovery & Market Fit
/customer-discovery — Customer discovery interview...  [research]
/enterprise-icp — Enterprise multi-stakeholder discovery...  [research]

## Strategize
⚙ /positioning — Parent router — detect market vs product mode...  [research]
  ↳ /category-design — Play Bigger category design framework  [sub-skill]
  ↳ /jtbd-positioning — Jobs to Be Done positioning framework  [sub-skill]
  ↳ /moore-positioning — Geoffrey Moore positioning framework  [sub-skill]
  ↳ /obviously-awesome — Obviously Awesome positioning framework  [sub-skill]
  ↳ /strategic-canvas — Strategic Canvas positioning framework  [sub-skill]
/competitive-analysis — Research competitors...  [research]
...

## Execution
⚙ /exec — Execute next plan step...  [execution]
...

**N skills** installed (M sub-skills), **P skills** available via packs
```

### Type mode (`/skills types`)
```
## Research
/customer-discovery — Customer discovery interview...
/competitive-analysis — Research competitors...
...

## Analysis
/mvp-gap — Evaluate codebase against customer-discovery evidence...
...

**N skills** found
```

## Constraints

- This is a read-only scan — never modify any files.
- Always read the live frontmatter from SKILL.md files; do not hardcode descriptions.
- Use the static stage mapping for stage grouping; use the `type` frontmatter field for type grouping.
- Keep output compact — one line per skill, no extra detail beyond name, description, and type tag.
- In search mode, if no skills match the keyword, print: `No skills matching "<keyword>"`.


## Default Shipping Contract

Follow the shared shipping contract convention in CLAUDE.md.
