skills/agent-creator/SKILL.md
Meta-agent for creating new custom agents, skills, and MCP integrations. Expert in agent design, MCP development, skill architecture, and rapid prototyping. Activate on 'create agent', 'new skill', 'MCP server', 'custom tool', 'agent design'. NOT for using existing agents (invoke them directly), general coding (use language-specific skills), or infrastructure setup (use deployment-engineer).
npx skillsauth add curiositech/windags-skills agent-creatorInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Meta-agent specializing in creating new custom agents, skills, and MCP integrations. Transform requirements into fully-functional, well-documented agent systems.
User: "Create an agent for database optimization"
Agent Creator:
1. Analyze requirements (domain, users, problems, scope)
2. Design persona (Senior DBA, 20 years experience)
3. Map capabilities (EXPLAIN analysis, indexing, query rewriting)
4. Select template (Technical Expert)
5. Encode knowledge (anti-patterns, techniques, examples)
6. Add MCP tools (optional: SQL parser)
7. Document usage and limitations
Result: Production-ready agent in ~45 minutes
| Template | Best For | Key Elements | |----------|----------|--------------| | Technical Expert | Domain specialists | Problem-solving framework, code examples, best practices | | Creative/Design | Creative roles | Design philosophy, creative process, quality standards | | Orchestrator | Coordination | Delegation strategy, integration patterns, QA |
| Step | Time | Activity | |------|------|----------| | 1. Understand Need | 2 min | What capability is missing? | | 2. Design Persona | 3 min | What expert would solve this? | | 3. Map Knowledge | 10 min | What do they need to know? | | 4. Create Structure | 5 min | Organize into template | | 5. Add Examples | 10 min | Concrete, runnable code | | 6. Write Docs | 5 min | How to use it | | 7. Test & Refine | 10 min | Validate with queries |
Total: ~45 minutes for quality agent
Official Packages:
@modelcontextprotocol/sdk - Core TypeScript SDK@modelcontextprotocol/create-server - Scaffold new servers@modelcontextprotocol/inspector - Test and debugCreation Steps:
Use for:
Do NOT use for:
What it looks like: Pasting entire documentation into agent Why wrong: Overwhelming, poor retrieval, bloated context Instead: Curate essential knowledge, use progressive disclosure
What it looks like: "You are an expert assistant" Why wrong: No personality, generic outputs Instead: Specific role, years of experience, communication style
What it looks like: Agent that tries to do everything Why wrong: Jack of all trades, master of none Instead: Clear boundaries with redirect suggestions
What it looks like: Abstract descriptions without code Why wrong: Users can't see how to apply guidance Instead: Concrete, runnable examples for key patterns
references/agent-templates.md - Technical, Creative, Orchestrator templatesreferences/mcp-integration.md - MCP server creation patterns, SDK usagereferences/creation-process.md - End-to-end workflow, quality checklistCore insight: Great agents aren't knowledge dumps—they're thoughtfully designed expert systems with personality, practical guidance, and real-world applicability.
Use with: skill-coach (quality review) | skill-documentarian (documentation) | orchestrator (multi-agent design)
tools
Building resilient distributed systems with circuit breakers, retries with full-jitter exponential backoff, retry budgets (per-request 3-attempt + per-client 10% ratio per Google SRE), deadline propagation, and the cascading-failure math (4 layers × 3 retries = 64x amplification). Grounded in Resilience4j, Microsoft Cloud Patterns, AWS Architecture Blog (Marc Brooker), and Google SRE Book.
testing
Designing HTTP cache headers that work correctly across browsers, CDNs, and shared proxies — `Cache-Control` directives per RFC 9111, `stale-while-revalidate` and `stale-if-error` per RFC 5861, the Vary header for varying responses, and surrogate keys for tag-based purging. Grounded in IETF RFCs and Cloudflare/Fastly docs.
development
Use when designing or fixing a Content Security Policy on a real site, choosing between nonce-based and hash-based CSP, adding strict-dynamic, debugging "Refused to execute inline script" errors, deploying CSP in report-only mode first, configuring report-to / report-uri, or auditing an existing policy for unsafe-inline / unsafe-eval / wildcards. Triggers: "CSP blocks legitimate inline script", strict-dynamic, nonce-{RANDOM}, sha256-{HASH}, object-src none, base-uri none, frame-ancestors, Trusted Types, X-Content-Security-Policy obsolete, report-only vs enforced. NOT for general HTTP security headers (HSTS, COOP/COEP), Trusted Types deep dive, CORS configuration, or building a WAF.
tools
Choosing and operating an HTTP API versioning strategy that doesn't break clients — Stripe's date-based pinned versions, the Deprecation/Sunset header pair (RFC 9745 + RFC 8594), URI vs header vs media-type approaches, and the version-transformer pattern. Grounded in Stripe's published architecture and IETF RFCs.