Loading...
Loading...
Found 2,174 Skills
Decomposes complex, multi-day tasks into optimized milestones using parallel reviewer agents (ultraplan). Spawns 5 independent reviewers that analyze the problem from different angles, then synthesizes their findings into a milestone dependency DAG. Triggers when the user says "plan milestones", "break this into milestones", "ultraplan", or when long-run harness needs milestone generation.
Creates project constitution files (CLAUDE.md/AGENTS.md) that serve as always-loaded context for coding agents. Use when setting up a new project for spec-driven development, configuring agent instructions, writing CLAUDE.md or AGENTS.md, or establishing project-wide coding standards and constraints.
Nassim Taleb's Antifragility framework applied to a business idea, system, or portfolio position. Spawns a team of specialist agents — Fat-Tail Detector, Fragility Auditor, Optionality Scout, Iatrogenics Checker, Skin-in-the-Game Auditor — who each apply a distinct lens from Taleb's Incerto to evaluate whether the subject is fragile, robust, or antifragile. The lead synthesizes into a convexity assessment: what's the payoff structure under disorder, where are the hidden tail risks, and the honest Taleb verdict. Use when the user says "taleb this", "is this fragile", "antifragility analysis", "what would Taleb think", "tail risk check", or proposes a business/system and wants structural risk analysis. Works standalone or after /munger for complementary analysis.
Qualtrics XM platform help — CX surveys (NPS/CSAT/CES), Employee Experience (EX) pulse surveys, Strategy & Research, Experience Agents AI, XM Directory, dashboards, REST API v3, MCP servers. Use when surveys aren't getting responses, dashboards won't show the right data, API calls return errors, you're setting up Qualtrics for the first time, confused by XM Directory contact management, need to export response data, comparing Qualtrics vs Medallia, or Qualtrics is too complex and you need guidance. Do NOT use for general NPS/CSAT strategy across tools (use /sales-customer-feedback) or product review collection like Trustpilot or G2 (use /sales-customer-reviews).
Talkdesk platform help — cloud contact center (CCaaS) with AI virtual agents, omnichannel routing, workforce management, and quality management. Use when setting up Talkdesk ACD routing or Studio IVR, calls keep dropping or audio quality is bad, AI features like Autopilot and CoPilot are expensive add-ons, comparing Talkdesk pricing tiers (Digital $85 to Industry $225/agent/mo), integrating Talkdesk with Salesforce Service Cloud Voice, Talkdesk reporting is hard to customize, WFM forecasting or scheduling not working, or implementation taking too long. Do NOT use for building a general coaching program (use /sales-coaching) or reviewing a specific call transcript (use /sales-call-review).
Build command-line interfaces for AI agents. Covers arguments, flags, subcommands, help text, output formats, error messages, exit codes, config/env precedence, and safe/dry-run behavior. Use when building a new CLI or refactoring an existing one for agent use.
Authoritative reference for the neo4j-agent-memory Python package — a graph-native memory system for AI agents built on Neo4j — and for the hosted service (NAMS) at memory.neo4jlabs.com. Use this skill whenever the user mentions neo4j-agent-memory, agent memory with Neo4j, context graphs, the POLE+O model, MemoryClient/MemorySettings, the memory MCP server, or any of the framework integrations (LangChain, PydanticAI, CrewAI, AWS Strands, Google ADK, Microsoft Agent Framework, OpenAI Agents, LlamaIndex). Also use when the user mentions the hosted service at memory.neo4jlabs.com, NAMS, the Neo4j Agent Memory Service, the `nams_` API key prefix, or the hosted MCP endpoint. Also use when writing documentation, blog posts, tutorials, PRDs, or code samples for the project, when comparing agent memory approaches, or when positioning graph-native memory against vector-only approaches — even if the user doesn't explicitly name the package.
Scaffold a new Claude Code plugin with proper directory structure, plugin.json, skills, commands, and agents
Use when measuring or improving agent quality and performance — set up evaluators, online monitoring, CI/CD quality gates, observability, or cost optimization. Triggers on: "evaluate my agent", "add evaluator", "measure quality", "quality gate", "run evals", "agent too slow", "why is it slow", "reduce latency", "set up observability", "CloudWatch dashboard", "how much does my agent cost", "cost optimization", "logs not showing up", "logs missing", "spans not found", "eval failing", "eval error", "dev traces", "local traces", "agentcore dev traces", "traces to CloudWatch". Not for debugging errors or crashes — use agents-debug. Slow but correct routes here; broken routes to debug.
Creates or audits a Claude Code subagent file. Use when user says 'create an agent', 'build a subagent', 'review this agent', 'audit our agents', 'add a code-reviewer agent', or 'our agents are too broad'. Do NOT use for skills (use create-or-audit-skill), hooks (use create-or-audit-hook), or CLAUDE.md files (use create-or-audit-claude-md).
Agent-first OpenRouter introspection — terse output for cron and AI agents (--agent and --llm modes), local SQLite... Trigger phrases: `openrouter credits`, `check openrouter budget`, `openrouter cost by cron`, `shortlist openrouter models`, `openrouter providers degraded`, `use openrouter`, `run openrouter`.
Use when the user wants to author, refine, or audit a Product Requirements Document for AI coding agents. Walks through an 8-phase pipeline (Socratic discovery → PRD draft → acceptance criteria → adversarial review → task decomposition → AI-readiness gate → test generation → handoff). Triggers on "write a PRD", "spec this feature", "draft requirements", "prepare X for Claude/Cursor/Copilot/Windsurf/Aider to build", "audit my PRD", "is this PRD AI-ready", "score this spec".