The Best Claude Code Agents, Skills & Commands to Install First
A curated starter kit from the AgentsCamp library — the subagents, skills, and slash commands that pay off immediately, by workflow.
Start with five: the code-reviewer and debugger agents (delegate review and diagnosis), the conventional-commits skill and create-pr command (polish the git loop), and one domain specialist for your stack. Add the test-runner pattern, security-auditor, and workflow skills as friction appears. Everything here is a Markdown file — copy it in, restart, done.
Key takeaways
- Install for friction you actually have: each artifact is one Markdown file in ~/.claude/, so the cost of trying is near zero — but a curated five beats a hoarded fifty.
- Agents to start with: code-reviewer (fresh-eyes review on every diff), debugger (delegated diagnosis), then one specialist matching your stack (react, python, sql, terraform…).
- Skills/commands that pay daily: conventional-commits, create-pr, write-tests, explain-error — the git-and-verify loop, automated.
- The Claude Code power tools are in the library too: hook-writer turns 'always do X' into enforcement, claude-settings-auditor hardens a new repo's config.
- Installation is copy-paste: agents → ~/.claude/agents/, skills → ~/.claude/skills/<name>/SKILL.md, commands → ~/.claude/commands/ — project-level .claude/ shares them with your team.
The fastest upgrade to a stock Claude Code setup isn't a prompt trick — it's installing a few well-built extensions. Everything below comes from this site's library, is a plain Markdown file, and installs by copy-paste. Here's the starter kit we'd give a new teammate, by workflow.
The first five
- code-reviewer (agent) — fresh-eyes review of every diff for correctness, security, and maintainability, in its own context. The single highest-value delegate: it reads what you've stopped seeing.
- debugger (agent) — hand it the failing test or stack trace; it reproduces, traces the root cause, and reports — noise stays in its window.
- conventional-commits (skill) — staged changes become clean Conventional Commits messages, every time.
- create-pr (command) —
/create-prpushes the branch and opens a PR with a real title and description drafted from the diff. - One stack specialist — match your daily language: react-specialist, python-pro, typescript-pro, sql-pro, or terraform-specialist.
The second wave, by friction
- Tests feel like a chore → write-tests command + test-scaffolder skill, and fix-failing-test for the red ones.
- Security review keeps slipping → security-auditor agent + security-scan on diffs; secret-scanner before pushes.
- Errors eat your mornings → explain-error — paste the trace, get the diagnosis and fix.
- Branches drift → sync-branch and the branch-rebaser skill for conflict-walking rebases.
- Docs rot → readme-generator and update-readme, grounded in the actual repo.
The Claude Code power tools
The library also extends Claude Code itself: hook-writer turns "always run prettier after edits" into an enforced hook; claude-settings-auditor reviews a repo's checked-in config before you trust it; plugin-scaffolder packages your setup for the team; setup-claude-ci wires the GitHub Action.
Install once, then make them yours
Mechanics in one breath: agents are files in ~/.claude/agents/, skills are ~/.claude/skills/<name>/SKILL.md, commands are ~/.claude/commands/ — use a repo's .claude/ instead to share with the team, and start a new session to load. (Full walkthrough.) Then treat every install as a draft: tighten the description so delegation fires when you'd want it, restrict tools to the job, and rewrite house rules into the body. The library's real product isn't the files — it's working examples of the craft, pre-installed.
Frequently asked questions
- How do I install a Claude Code agent or skill from AgentsCamp?
- Copy the file. Agents are single Markdown files for ~/.claude/agents/ (or .claude/agents/ in a repo to share with the team); skills are folders with a SKILL.md under ~/.claude/skills/<name>/; commands go in ~/.claude/commands/. Every item page has the install path and a copy button; start a new session and it's live.
- How many should I install?
- Fewer than you think. Subagent descriptions are read during delegation routing, so dozens of overlapping agents blur each other. A working set of five to eight focused items — review, debugging, your stack's specialist, your git loop — outperforms a hoard. Add when you feel friction, prune what never fires.
- Can I customize them?
- That's the point — they're plain Markdown with a frontmatter header and a system prompt. Edit the description to tune when Claude delegates, restrict tools, pin a model tier, and rewrite the body for house rules. The library entries are starting points engineered to be edited.
Related
- Getting Started with Claude Code AgentsWhat Claude Code subagents are, why they help, and how to add your first one.
- Writing Your First Custom AgentA step-by-step guide to authoring a focused, effective custom subagent.
- Skills vs Agents vs CommandsHow Claude Code's two extension mechanisms — subagents and skills — differ across three invocation patterns, with a decision table for choosing the right one.
- Code ReviewerUse this agent to review code changes for correctness, security, and maintainability before merging. Examples — reviewing a PR diff, auditing a new module, checking a refactor for regressions.
- DebuggerUse this agent to diagnose failing tests, runtime errors, or unexpected behavior by forming and testing hypotheses. Examples — a stack trace to root-cause, a flaky test, a "works locally but not in CI" bug.
- Conventional CommitsGenerate clear Conventional Commits messages from staged changes. Use when committing code and you want a well-structured, consistent commit message.
- Create PRPush the current branch and open a GitHub pull request with a generated title and body.
- 25 Claude Code Tips, Shortcuts, and Power FeaturesThe 25 highest-leverage Claude Code tips — keyboard shortcuts, bash and memory shortcuts, session commands, model tricks, and the power features most people miss.
- AI Coding Statistics 2026: The Numbers That Are Actually SourcedHow much code AI writes, who uses the tools, and what it does to quality — every statistic dated and traced to its primary source, updated on a cadence.
- The AI Engineer Roadmap for 2026A staged path from API calls to production agents — the skills that matter in 2026, what to skip, and the guides and tools for each stage, in order.