anthropics/claude-code
10 skills163k installs1M starsGitHub
Install
npx skills add https://github.com/anthropics/claude-codeSkills in this repo
1Frontend DesignClaude Code is an agentic CLI tool that helps developers code faster by executing routine tasks, explaining complex code, and handling git workflows through natural language commands. It works across MacOS, Linux, and Windows and integrates with terminals, IDEs, and GitHub.52.6kinstalls2Agent DevelopmentAgent Development teaches autonomous agent design for Claude Code plugins with YAML frontmatter configuration, system prompt patterns, and triggering conditions. It covers agent naming conventions, model selection (inherit/Sonnet/Opus/Haiku), color assignment, tool restriction via allowlist, and example-based triggering to teach Claude when to invoke the agent. Use this skill when building autonomous subprocesses for complex multi-step tasks. Includes validation rules, testing strategies, and best practices for structuring agent responsibilities and output formats.16.4kinstalls3Skill DevelopmentGuidance for creating effective skills for Claude Code plugins. Covers skill anatomy (SKILL.md, bundled scripts/references/assets), progressive disclosure (metadata always, body when triggered, resources as needed), creation process including understanding use cases, planning reusable contents, writing effective descriptions with trigger phrases, and organizing skill content. Use when creating new skills, improving skill descriptions, organizing skill content, or understanding skill structure and best practices.16kinstalls4Mcp IntegrationA skill for integrating Model Context Protocol servers into Claude Code plugins. Covers stdio, SSE, HTTP, and WebSocket server types, configuration methods, OAuth flows, and environment variable management. Developers use it to expose external service capabilities (databases, APIs, file systems) as tools within Claude Code.12.8kinstalls5Command DevelopmentCommand Development teaches developers how to build slash commands - Markdown-based prompts that Claude executes in interactive sessions. Commands are written as directives TO Claude, not messages to users, and support YAML frontmatter configuration (description, allowed-tools, model, argument-hint), dynamic argument substitution ($ARGUMENTS, $1-$3), file references using @ syntax, bash execution for context gathering, and organizational patterns. Developers use commands to standardize workflows, enable team sharing, control tool permissions, and build reusable automation across project and personal scopes. Key workflows include review patterns, testing patterns, documentation generation, multi-step deployments, and plugin integration combining agents, skills, and scripts.12kinstalls6Hook DevelopmentHook Development enables developers to build event-driven automation scripts that execute in response to Claude Code events like PreToolUse, PostToolUse, Stop, and SessionStart. Developers use hooks to validate tool calls before execution, enforce policies, add project context, and integrate external systems into Claude Code workflows. The skill covers two hook types: prompt-based hooks (LLM-driven reasoning for context-aware decisions) and command hooks (bash scripts for deterministic checks). Key workflows include validating file writes for security, analyzing tool results for issues, verifying task completion before stopping, and loading project context at session start. Hook configuration uses JSON matchers to target specific tools, supports parallel execution, and requires restart to load changes.11.7kinstalls7Plugin StructurePlugin Structure provides developers with a standardized framework for building Claude Code plugins, including conventional directory layout, manifest-driven configuration via plugin.json, and automatic component discovery. Developers use it when creating new plugins or organizing plugin components such as slash commands, subagents, skills, hooks, and MCP servers. Key workflows include configuring the plugin manifest, placing components in auto-discovered directories (commands/, agents/, skills/), defining event handlers in hooks.json, and using ${CLAUDE_PLUGIN_ROOT} for portable path references across installation contexts.11.1kinstalls8Plugin SettingsPlugin Settings documents the .claude/plugin-name.local.md pattern for storing user-configurable plugin settings and state. Plugins can define YAML frontmatter for structured configuration (enabled flags, numeric limits, lists) and markdown body for prompts or instructions. Developers use this when building Claude Code plugins that need per-project customization, enabling hooks, commands, and agents to read settings via bash parsing (sed/awk), adapt behavior without restart-less hot-reload, and coordinate multi-agent workflows. Key workflows include quick-exit patterns (check file exists), parsing YAML fields (string, boolean, numeric), reading markdown body, and managing agent state across collaborative tasks.11kinstalls9Writing Hookify RulesWriting Hookify Rules teaches developers how to create markdown-based rules that monitor Claude agent tool use and enforce guardrails. Rules are stored as .claude/hookify.{name}.local.md files with YAML frontmatter defining event type (bash, file, stop, prompt, all), regex patterns, and optional actions (warn or block). Developers use this skill when setting up safety checks for dangerous commands (rm -rf, sudo), code patterns (console.log, eval), sensitive files (.env, .pem), or completion workflows. Rules match against command text, file paths, new content, or user prompts using regex or substring operators, then display markdown messages to the agent. Dynamic reloading allows instant iteration without restarting.10.6kinstalls10Claude Opus 4 5 MigrationMigrate prompts and code from Claude Sonnet 4.0, Sonnet 4.5, or Opus 4.1 to Opus 4.5. Use when the user wants to update their codebase, prompts, or API calls to use Opus 4.5. Handles model string updates and prompt adjustments for known Opus 4.5 behavioral differences. Does NOT migrate Haiku 4.5. --- name: claude-opus-4-5-migration description: Migrate prompts and code from Claude Sonnet 4.0, Sonnet 4.5, or Opus 4.1 to Opus 4.5. Use when the user wants to update their codebase, prompts, or API calls to use Opus 4.5. Handles model string updates and prompt adjustments for known Opus 4.5 behavioral differences. --- # Opus 4.5 Migration Guide One-shot migration from Sonnet 4.0, Sonnet 4.5, or Opus 4.1 to Opus 4.5. Search codebase for model strings and API calls 2.9.3kinstalls