handbook-discover
This skill should be used when users want to discover, browse, or audit cc-handbook marketplace plugins. Shows all available plugins with installation status, versions, and component breakdown (skills, agents, commands, MCP/LSP servers, hooks). Trigger phrases include "discover plugins", "list handbook plugins", "what plugins are available", "browse marketplace".
git clone --depth 1 https://github.com/NikiforovAll/claude-code-rules /tmp/handbook-discover && cp -r /tmp/handbook-discover/plugins/handbook-discover/skills/handbook-discover ~/.claude/skills/handbook-discoverSKILL.md
# Handbook Plugin Discovery
Run the discovery script to inventory all plugins in a Claude Code marketplace.
## Usage
```bash
python ${CLAUDE_SKILL_DIR}/scripts/discover.py # default: cc-handbook
python ${CLAUDE_SKILL_DIR}/scripts/discover.py --detailed # show component names
python ${CLAUDE_SKILL_DIR}/scripts/discover.py --json # machine-readable
python ${CLAUDE_SKILL_DIR}/scripts/discover.py --filter dotnet # filter by keyword
python ${CLAUDE_SKILL_DIR}/scripts/discover.py --uninstalled # only uninstalled
python ${CLAUDE_SKILL_DIR}/scripts/discover.py -m <marketplace> # other marketplace
python ${CLAUDE_SKILL_DIR}/scripts/discover.py -r <path> # explicit repo path
```
## Interpreting Results
- `[+]` — installed and enabled
- `[o]` — installed but disabled
- `[ ]` — not installed
- Component counts: `S`=skills `A`=agents `C`=commands `M`=mcp `L`=lsp `H`=hooks
## Follow-up Actions
For uninstalled plugins, suggest:
```bash
claude plugin install <plugin-name>@cc-handbook
```This skill automates version bumping during the release process for the Claude Code Handbook monorepo. It should be used when the user requests to bump versions, prepare a release, or increment version numbers across the repository.
This skill should be used when the user wants to add components (commands, agents, skills, hooks, or MCP servers) to the Component Reference section of the website.
Guide spec-driven development workflow (Requirements → Design → Tasks → Implementation) with approval gates between phases. Use when user wants structured feature planning or says "use spec-driven" or "follow the spec process".
Review changed code for reuse, quality, and efficiency using three parallel disposable subagents. This skill should be used when the user says "review", "simplify", "code review", or wants a one-shot code review without persistent reviewers.
Review changed code for reuse, quality, and efficiency using a team of persistent named reviewers. This skill should be used when the user says "team review", "review with team", or wants parallel code review with persistent team members for follow-up questions. Similar to /subagent-review but reviewers persist after review.
Generate a .NET code coverage report scoped to files changed in the current branch. Runs tests with coverage collection and produces filtered HTML reports.
This skill should be used when investigating .NET project dependencies, understanding why packages are included, listing references, or auditing for outdated/vulnerable packages.
Run script-like CSharp programs using dotnet run file.cs. Use this skill when users want to execute CSharp code directly, write one-liner scripts via stdin, or learn about run file directives.