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)
data-ai
license: Apache-2.0 NOT for unrelated tasks outside this domain.
development
Use when designing caching strategies (cache-aside, write-through, write-behind), implementing distributed locks, building rate limiters, leaderboards, real-time streams (XADD/consumer groups), pub/sub, or tuning eviction policies. Triggers: thundering-herd on cache miss, dogpile on key expiry, Redlock vs SET-NX-PX choice, sliding-window rate limiter, hot-key on a single cluster slot, big-key blowup, MULTI/EXEC across slots, KEYS in production. NOT for Redis Cluster operations/admin (different domain), embedded KV (SQLite, leveldb), in-process LRU caches, or Memcached.
tools
Drawing the `'use client'` boundary correctly in React Server Components apps (Next.js App Router, RSC frameworks) — leaf-pushing, slot composition, serialization rules, and environment poisoning prevention. Grounded in react.dev and Next.js 16 docs.
development
Use when designing rate limiting for an API, choosing between token bucket / sliding window / leaky bucket / fixed window, implementing it in Redis, deciding edge (Cloudflare/Upstash) vs origin enforcement, sizing per-user vs per-IP vs per-endpoint quotas, returning the right 429 response with Retry-After, or fixing the boundary-burst bug in fixed-window limiters. Triggers: 429 too many requests, INCR + EXPIRE, ZADD + ZREMRANGEBYSCORE + ZCARD, X-RateLimit-Remaining header, Cloudflare WAF rate limiting rules, Upstash @upstash/ratelimit, leaky bucket shaping vs policing, distributed rate limiter consistency. NOT for DDoS mitigation specifically (different scale), CAPTCHA / bot management, full WAF design, or per-user quota billing.