Topic: claude-code-plugin
1,213 skills in this topic.
-
claude-gladiator
Continuous learning — hooks observe failures and prompt reflection, sibling synergy deepens analysis with history and tool discovery
Vvkmnn/claude-emporium 113
-
claude-historian
Automatic history search — checks past sessions before web research, planning, and debugging, siblings deepen coverage
Vvkmnn/claude-emporium 113
-
claude-oracle
Automatic tool discovery across 17 sources — hooks search before planning and after errors, siblings avoid redundant searches
Vvkmnn/claude-emporium 113
-
claude-orator
Prompt rhetoric coach — deterministic scoring and restructuring using Anthropic best practices
Vvkmnn/claude-emporium 113
-
claude-praetorian
Context preservation with cross-session memory — hooks prompt compaction at high-impact moments, siblings enrich what gets saved
Vvkmnn/claude-emporium 113
-
claude-vigil
File checkpoint and recovery — auto-quicksaves before destructive commands, manual checkpoints for safe rollback
Vvkmnn/claude-emporium 113
-
memory-engine
Memory management system for Claude Code — Student Loop, Smart Context, Auto Learn, Session Handoff, Correction Cycle. Triggered by memory commands (/save, /reflect, /handoff, /check) or memory-related questions. Not for general programming tasks.
HelloRuru/claude-memory-engine 114
-
subagent-review
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.
NikiforovAll/claude-code-rules 114
-
team-review
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.
NikiforovAll/claude-code-rules 114
-
skill-creator
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
NikiforovAll/claude-code-rules 114
-
update-component-reference
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.
NikiforovAll/claude-code-rules 114
-
version-bump
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.
NikiforovAll/claude-code-rules 114
-
spec-driven
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".
NikiforovAll/claude-code-rules 114
-
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".
NikiforovAll/claude-code-rules 114
-
dotnet-dependency
This skill should be used when investigating .NET project dependencies, understanding why packages are included, listing references, or auditing for outdated/vulnerable packages.
NikiforovAll/claude-code-rules 114
-
dotnet-run-file
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.
NikiforovAll/claude-code-rules 114
-
dotnet-test
This skill should be used when running .NET tests selectively with a build-first, test-targeted workflow. Use it for running tests with xUnit focus.
NikiforovAll/claude-code-rules 114
-
dotnet-verify
This skill should be used when working with Verify snapshot tests in .NET projects. Use when updating verified snapshots after intentional code changes, accepting new snapshots, discovering verify tests, or troubleshooting snapshot mismatches. Trigger phrases include "verify tests", "update snapshots", "accept snapshots", "verified files", ".verified.txt".
NikiforovAll/claude-code-rules 114
-
ilspy-decompile
Understand implementation details of .NET code by decompiling assemblies. Use when you want to see how a .NET API works internally, inspect NuGet package source, view framework implementation, or understand compiled .NET binaries.
NikiforovAll/claude-code-rules 114
-
elasticsearch
Interact with Elasticsearch and Kibana via REST API using curl. Use when querying, indexing, managing indices, checking cluster health, writing aggregations, deploying dashboards, or troubleshooting Elasticsearch. Requires cluster URL and API key. Covers: search (Query DSL), CRUD operations, index management, mappings, aggregations, cluster health, ILM, ES|QL, Kibana API (dashboards, data views, saved objects), OpenTelemetry data patterns, and common troubleshooting patterns.
NikiforovAll/claude-code-rules 114
-
nano-banana
This skill should be used for Python scripting and Gemini image generation. Use when users ask to generate images, create AI art, edit images with AI, or run Python scripts with uv. Trigger phrases include "generate an image", "create a picture", "draw", "make an image of", "nano banana", or any image generation request.
NikiforovAll/claude-code-rules 114
-
nano-banana-prompting
This skill should be used when crafting prompts for Nano Banana Pro (Gemini image generation). Use when users want help writing image generation prompts, need guidance on prompt structure, or want to optimize their prompts for better results.
NikiforovAll/claude-code-rules 114
-
structured-plan-mode
This skill should be used when planning and tracking complex feature implementations that require systematic task decomposition. Use this skill to break down large features into manageable, well-documented tasks with clear dependencies, action items, and success criteria. The skill provides a structured template and methodology for iterative planning and tracking throughout implementation.
NikiforovAll/claude-code-rules 114
-
adr-plan
Analyze a task and produce an Architecture Decision Record with implementation steps.
NikiforovAll/claude-code-rules 114