working-with-claude-code
Use when working with Claude Code CLI, plugins, hooks, MCP servers, skills, configuration, or any Claude Code feature - provides comprehensive official documentation for all aspects of Claude Code
- Installs
- 200
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/obra/superpowers-developing-for-claude-code --skill working-with-claude-code- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads working-with-claude-code automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Working with Claude Code
Overview
This skill provides complete, authoritative documentation for Claude Code directly from docs.claude.com. Instead of guessing about configuration paths, API structures, or feature capabilities, read the official docs stored in this skill's references directory.
When to Use
Use this skill when:
- Creating or configuring Claude Code plugins
- Setting up MCP servers
- Working with hooks (pre-commit, session-start, etc.)
- Writing or testing skills
- Configuring Claude Code settings
- Troubleshooting Claude Code issues
- Understanding CLI commands
- Setting up integrations (VS Code, JetBrains, etc.)
- Configuring networking, security, or enterprise features
Quick Reference
| Task | Read This File |
|---|---|
| Create a plugin | plugins.md then plugins-reference.md |
| Set up MCP server | mcp.md |
| Configure hooks | hooks.md then hooks-guide.md |
| Write a skill | skills.md |
| CLI commands | cli-reference.md |
| Troubleshoot issues | troubleshooting.md |
| General setup | setup.md or quickstart.md |
| Configuration options | settings.md |
Documentation Organization
All documentation is stored as individual markdown files in references/. Use the Read tool to access specific documentation:
references/
├── overview.md # Claude Code introduction
├── quickstart.md # Getting started guide
├── setup.md # Installation and setup
├── plugins.md # Plugin development
├── plugins-reference.md # Plugin API reference
├── plugin-marketplaces.md # Plugin marketplaces
├── skills.md # Skill creation
├── mcp.md # MCP server integration
├── hooks.md # Hooks overview
├── hooks-guide.md # Hooks implementation guide
├── slash-commands.md # Slash command reference
├── sub-agents.md # Subagent usage
├── settings.md # Configuration reference
├── cli-reference.md # CLI command reference
├── common-workflows.md # Common usage patterns
├── interactive-mode.md # Interactive mode guide
├── headless.md # Headless mode guide
├── output-styles.md # Output customization
├── statusline.md # Status line configuration
├── memory.md # Memory and context management
├── checkpointing.md # Checkpointing feature
├── analytics.md # Usage analytics
├── costs.md # Cost tracking
├── monitoring-usage.md # Usage monitoring
├── data-usage.md # Data usage policies
├── security.md # Security features
├── iam.md # IAM integration
├── network-config.md # Network configuration
├── terminal-config.md # Terminal configuration
├── model-config.md # Model configuration
├── llm-gateway.md # LLM gateway setup
├── amazon-bedrock.md # AWS Bedrock integration
├── google-vertex-ai.md # Google Vertex AI integration
├── vs-code.md # VS Code integration
├── jetbrains.md # JetBrains integration
├── devcontainer.md # Dev container support
├── github-actions.md # GitHub Actions integration
├── gitlab-ci-cd.md # GitLab CI/CD integration
├── third-party-integrations.md # Other integrations
├── legal-and-compliance.md # Legal information
├── troubleshooting.md # Troubleshooting guide
└── migration-guide.md # Migration guide
Workflow
For Specific Questions
- Identify the relevant documentation file from the list above
- Use Read tool to load:
@references/filename.md - Find the answer in the official documentation
- Apply the solution
Example:
User: "How do I create a Claude Code plugin?"
→ Read @references/plugins.md
→ Follow the official plugin creation steps
For Broad Topics
When exploring a topic, start with the overview document, then drill into specific files:
- Extending Claude Code: Start with
plugins.md,skills.md, ormcp.md - Configuration: Start with
settings.mdorsetup.md - Integrations: Check relevant integration file (vs-code.md, github-actions.md, etc.)
- Troubleshooting: Start with
troubleshooting.md
For Uncertain Topics
Use Grep tool to search across all documentation:
pattern: "search term"
path: ~/.claude/skills/working-with-claude-code/references/
Updating Documentation
The skill includes scripts/update_docs.js to fetch the latest documentation from docs.claude.com.
Run when:
- Documentation seems outdated
- New Claude Code features are released
- Official docs have been updated
node ~/.claude/skills/working-with-claude-code/scripts/update_docs.js
The script:
- Fetches llms.txt from docs.claude.com
- Extracts all Claude Code documentation URLs
- Downloads each page to
references/ - Reports success/failures
Common Patterns
Plugin Development
Read plugins.md for overview, then plugins-reference.md for API details.
MCP Server Setup
Read mcp.md for configuration format and examples.
Hook Configuration
Read hooks.md for overview, then hooks-guide.md for implementation details.
Skill Creation
Read skills.md for the complete skill authoring guide.
What This Skill Does NOT Do
- This skill provides documentation access, not procedural guidance
- For workflows on how to build plugins/skills, use the
extending-claude-codeskill (when available) - This skill is a reference library, not a tutorial
Red Flags
If you find yourself:
- Guessing about configuration file locations → Read
settings.md - Speculating about API structures → Read relevant reference doc
- Unsure about hook names → Read
hooks.md - Making assumptions about features → Search the docs first
Always consult the official documentation before guessing.
FAQ
What does the working-with-claude-code skill do?
Use when working with Claude Code CLI, plugins, hooks, MCP servers, skills, configuration, or any Claude Code feature - provides comprehensive official documentation for all aspects of Claude Code
How do I install working-with-claude-code?
Run npx skills add https://github.com/obra/superpowers-developing-for-claude-code --skill working-with-claude-code in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/working-with-claude-code/ (personal) or .claude/skills/working-with-claude-code/ (project).
Which AI agents can use working-with-claude-code?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is working-with-claude-code safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains working-with-claude-code?
It is published by obra in obra/superpowers-developing-for-claude-code. It has 200 recorded installs.
More from obra/superpowers-developing-for-claude-code
developing-claude-code-plugins
obra/superpowers-developing-for-claude-code
Use when working on Claude Code plugins (creating, modifying, testing, releasing, or maintaining) - provides streamlined workflows, patterns, and examples for the complete plugin lifecycle
Popular ai & agents skills
google-agents-cli-publish
google/agents-cli
This skill should be used when the user wants to "publish an agent", "publish my ADK agent", "register an agent with Gemini", "publish to Gemini" (formerly Gemini Enterprise), or needs guidance on the agents-cli publish gemini command. Also use when the user wants to "manage agents in Agent Registry", "list/update/delete registered agents", or "register an MCP server". Covers ADK vs A2A registration modes, programmatic and interactive usage, flag reference, auto-detection from deployment metadata, Agent Registry fleet management, and troubleshooting. Part of the agents-cli skills suite. Do NOT use for deployment (use google-agents-cli-deploy).
google-agents-cli-eval
google/agents-cli
This skill should be used when the user wants to "run an evaluation", "evaluate my agent", "evaluate my ADK agent", "write an eval dataset", "analyze eval failures", "compare eval results", "optimize agent", or needs guidance on the Gemini platform eval methodology and the Quality Flywheel. Covers eval metrics, dataset schema, LLM-as-judge scoring, and common failure causes. Applies to any agents-cli project, whatever framework the agent is written in. Do NOT use for agent API code patterns (ADK: use google-agents-cli-adk-code), deployment (use google-agents-cli-deploy), or project scaffolding (use google-agents-cli-scaffold).
skill-creator
anthropics/skills
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
codex-pet
prime-skills/runcomfy-agent-skills
Codex Pet generator on RunComfy. Build a Codex-compatible Codex Pet spritesheet.webp + pet.json from a single reference image, drop it into ${CODEXHOME:-$HOME/.codex}/pets/ / and Codex picks it up as a custom Codex Pet next to the 8 built-ins. This skill produces the exact Codex Pet atlas Codex expects (1536x1872 PNG/WebP, 8 cols x 9 rows, 192x208 cells, 9 animation states — idle, running-right, running-left, waving, jumping, failed, waiting, running, review). Calls OpenAI GPT Image 2 edit ONCE via the local RunComfy CLI as runcomfy run openai/gpt-image-2/edit to produce a canonical Codex Pet pose, then assembles all 9 animation rows programmatically with ImageMagick micro-transforms — no Codex Pro, no $imagegen, no OPENAIAPIKEY required, only RUNCOMFYTOKEN. Triggers on "codex pet", "create codex pet", "make codex pet", "hatch codex pet", "/hatch image", "desktop pet codex", "codex pets", "spritesheet.webp", or any explicit ask to build a custom pet for OpenAI Codex.
full-output-enforcement
leonxlnx/taste-skill
Overrides default LLM truncation behavior. Enforces complete code generation, bans placeholder patterns, and handles token-limit splits cleanly. Apply to any task requiring exhaustive, unabridged output.
executing-plans
obra/superpowers
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available