AgentStack
Sign in Publish
MCP servers Skills Toolkits Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Agent Development

skill-dwmkerr-claude-toolkit-agent-development · by dwmkerr

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.

↗ Website ↗ Repository
— No reviews yet
0 installs
7 views
0.0% view→install

Install

$ agentstack add skill-dwmkerr-claude-toolkit-agent-development

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Agent Development? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Agent Development

Create effective Claude Code agents.

Agent Colors

Agents support color assignments for visual distinction. Set in YAML frontmatter:

---
name: explore
description: Explores codebases
color: purple
---

Color Conventions

| Color | Agent Type | Purpose | |-------|------------|---------| | Purple | Explore | Codebase exploration, documentation | | Blue | Plan | Analysis, planning, architecture | | Green | Create | Testing, creation, validation | | Orange | Debug | Debugging, refactoring | | Yellow | Clean | Optimization, cleanup | | Red | Reflect | Security, critical review | | Pink | - | Available | | Cyan | - | Orchestration, coordination |

Agent Behavior

Permission Denial Resilience

Subagents continue after permission denial rather than stopping entirely. When a subagent hits a permissions wall, it tries alternative approaches automatically. This makes autonomous workflows more resilient and reduces the need for human intervention.

Important

After creating or modifying agents, inform the user:

> No restart needed. Agent changes take effect immediately - agents are hot-reloaded.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Agent Skills