toolkit

Plugin toolkit from marketplace claude-toolkit in dwmkerr/claude-toolkit. Commands read from the repo's manifest — 5 days ago.

Skills (16)

• agent-development

  This skill should be used when the user asks to "create an agent", "write an agent", "build an agent", or wants to add new agent capabilities to Claude Code.

• anthropic-evaluations

  This skill should be used when the user asks to "create evals", "evaluate an agent", "build evaluation suite", or mentions agent testing, graders, or benchmarks. Also suggest when building coding agents, conversational agents, or research agents that need quality assurance.

• claude-code-agent-teams

  This skill should be used when the user asks to "create an agent team", "run a multi-agent team", "coordinate multiple Claude sessions", "use agent teams", or wants to parallelize work across multiple Claude Code instances.

• claude-code-hook-development

  This skill should be used when the user asks to "create a hook", "add a hook", "write a hook", or mentions Claude Code hooks. Also suggest this skill when the user asks to "automatically do X" or "run X before/after Y" as these are good candidates for hooks.

• claude-code-memory-and-rules

  This skill should be used when the user asks to "set up memory", "configure CLAUDE.md", "add rules", "create project rules", "organize instructions", or mentions Claude Code memory, CLAUDE.md files, .claude/rules, rules, or project instructions. Also use when the user wants to persist preferences, a

• claude-code-plugin-development

  This skill should be used when the user asks to "create a plugin", "build a plugin", "write a plugin", or wants to bundle agents, hooks, commands, skills, or MCP servers into a distributable Claude Code plugin.

• claude-code-slash-commands

  This skill should be used when the user asks to "create a command", "write a slash command", "build a plugin command", or wants to add custom commands to Claude Code.

• claude-code-statusline-development

  This skill should be used when the user asks to "create a statusline", "customize the status line", "add a custom prompt", or mentions Claude Code statusline. Also suggest when the user wants to display git branch, context usage, model name, or session costs at the bottom of Claude Code.

• editable-html

  Let the user edit the copy of an HTML page or web app in the browser while an agent applies each change to the source in real time. Use when the user asks to "make the html editable", "let me edit the text", "live edit", "edit copy in the browser", "watch my edits", or wants to tweak wording on a pa

• learn-and-improve

  This skill should be used when the user asks to "improve my setup", "learn from this session", "fix my config", "stop asking for permissions", or reports friction with skills, agents, hooks, or permissions. Analyzes conversation history and proposes configuration improvements.

• makefile-development

  This skill should be used when the user asks to "create a Makefile", "write a Makefile", "add a make target", or mentions Makefile conventions.

• release-please-development

  This skill should be used when the user asks to "set up release please", "configure automated releases", "manage version numbers", "add changelog automation", or mentions release-please, semantic versioning, or monorepo versioning.

• research

  Deep research into technical solutions by searching the web, examining GitHub repos, and gathering evidence. Use when the user explicitly says "use the research skill", "use a research agent", or asks for deep/thorough research into implementation options or technologies.

• shell-script-development

  This skill should be used when the user asks to "create a bash script", "write a shell script", or mentions shell scripting conventions.

• claude-code-skill-development

  This skill should be used when the user asks to "create a skill", "write a skill", "build a skill", or wants to add new capabilities to Claude Code. Use when developing SKILL.md files, organizing skill content, or improving existing skills. Do NOT use for plugin development, hook creation, agent cre

• solve-problem

  This skill should be used when the user says "solve problem", "solve this problem", or invokes /solve-problem. Applies a methodical, evidence-first approach to diagnosing a problem - understand intent, observe the problem first-hand, form multiple hypotheses, gather discriminating evidence to elimin

Slash commands (5)

• /toolkit:agent-history

  Show which agents were invoked during this session

• /toolkit:ghpr

  Open or create GitHub pull request for current branch

• /toolkit:skill-history

  Show which skills were invoked during this session

• /toolkit:vfast

  Run a request on Sonnet, faster and cheaper than Opus, e.g. /toolkit:vfast check open bugs

• /toolkit:vvfast

  Run a request on Haiku, the fastest and cheapest model, e.g. /toolkit:vvfast check open bugs

Subagents (1)

• researcher

  Research technical solutions by searching the web, examining GitHub repos, and gathering evidence. Use when exploring implementation options, evaluating technologies, or investigating how to solve a technical problem.