Skills
98,639 packaged capabilities and playbooks for agents. Install any of them with one command.
Development
Structures and organizes Storybook files for scalability using battle-tested patterns from Cassondra Roberts' "A Storybook format that scales with you". Covers story definitions, template composition, controls/args, visual regression with Chromatic, component documentation, and CSF conventions. Activates on any Storybook question — file structure, controls, args, or component documentation.
Run a git merge, PR merge, conflict resolution, or rollback safely — readiness-checked and BACKED UP before anything touches shared history. Assesses branch/CI/review state and conflict risk, tags a backup point before non-trivial merges, resolves conflicts without dropping either side (regenerating lockfiles, not hand-editing), validates the result, then cleans up or rolls back — routing to the worktree specialist when isolated execution is safer. Never claims success with unresolved conflicts or failing validation, prefers `git revert` over `reset` on shared branches, and requires explicit confirmation before destructive rollback, force-push, or branch deletion. Use only when the user explicitly asks to merge, resolve conflicts, or roll back.
Expert-level toolkit for modular Godot 4.7+ CLI automation and headless build orchestration. Use when you need to: (1) Build complex scene trees or UI layouts programmatically, (2) Automate expert 3D asset pipelines (glTF -> Collision), (3) Optimize procedural geometry headlessly (CSG -> Static Mesh), or (4) Engineer production-grade CI/CD pipelines. Set GODOT_PATH env var for custom engine location. Keywords: Godot CLI, headless, CI, export, builder, 4.7.
Inspects, filters, and maps z-schema validation errors for application use. Use when the user needs to handle validation errors, walk nested inner errors from anyOf/oneOf/not combinators, map error codes to user-friendly messages, filter errors with includeErrors or excludeErrors, build form-field error mappers, use reportPathAsArray, interpret SchemaErrorDetail fields like code/path/keyword/inner, or debug why validation failed.
Expert knowledge for Microsoft Foundry Classic (aka Azure AI Foundry classic) development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when configuring Foundry agents, model routing, Azure OpenAI/RAG, multi-agent apps, or secure on-your-data tools, and other Microsoft Foundry Classic related development tasks. Not for Microsoft Foundry (use microsoft-foundry), Microsoft Foundry Local (use microsoft-foundry-local), Content Safety in Foundry Control Plane (use azure-content-safety), Azure Speech in Foundry Tools (use azure-speech).
Guide for migrating Dagster projects to Apache Airflow 3 on Astro. Use when the user mentions migrating, converting, or porting Dagster (or Dagster+) code to Airflow or Astro, wants to plan or assess such a migration, or asks what a Dagster construct maps to in Airflow. Covers assets, partitions, schedules, sensors, declarative automation, resources, IO managers, ops/jobs, dbt, Pipes, Components, and Dagster+ platform config. Always load this skill as the first step for any Dagster-to-Airflow request
Apply these opinionated rules whenever CSS is written, refactored, or reviewed, so agents and people write it consistently. They complement the Modern Web Guidance skill and resolve choices it leaves open across architecture, layout, typography, colors, and motion. Use this skill when the user asks things like “set up the base styles for this project,” “style this component,” “make this responsive,” “add dark mode,” “scope these styles,” “fluid type scale,” or “refactor my styles to modern CSS”; when they ask to build a page or component; and for any other CSS task, even if they don't say “CSS”
Enforces one app-wide GoRouter in lib/routing/ wired via MaterialApp.router, deep-linkable identity in path params never state.extra, context.go-vs-context.push discipline, redirect guards as pure functions driven by a Riverpod refreshListenable, StatefulShellRoute.indexedStack for branch-state-preserving BottomNavigationBar/NavigationRail shells, CustomTransitionPage transitions that respect reduced motion, PopScope (canPop/onPopInvokedWithResult) for unsaved-changes interception, and an errorBuilder 404 route. Use when adding routes, GoRoute, redirect, auth/onboarding gates, deep links, ShellRoute or nested navigation, bottom-nav/rail tab shells, page transitions, back-button/unsaved-changes handling, notification-payload-to-location mapping, typed routes, go_router_builder, or wiring go_router into app.dart.
Build or review a Next.js App Router surface against the project's installed framework version and established architecture. Covers pages, layouts, async request APIs, server and browser API clients, authentication, client concurrency, Route Handlers, metadata, i18n, accessibility, machine-readable content, and layered testing. Use when a task touches Next.js and must preserve project-specific decisions such as the resolved framework version, backend session protocol, canonical domain, and locked visual theme.
Multi-agent workflow examples for working together on the OpenServ Platform. Covers agent discovery, multi-agent workspaces, task dependencies, and workflow orchestration using the Platform Client. Read reference.md for the full API reference. Read openserv-agent-sdk and openserv-client for building and running agents.
Use the public `orca` CLI to operate Supervibe-managed worktrees, folder contexts, terminals, repos, automations, artifacts, worktree comments, and the browser embedded inside the Supervibe app. Use when the user says "$orca-cli", "use orca cli", "Supervibe worktree", "child worktree", "cardStatus", "spawn codex/claude in a worktree", "read/wait/send Supervibe terminal", "terminal send", "full handoff", "handover", "give this to another agent", "another worktree", "Supervibe browser", "orca artifacts", "share HTML/Markdown", "public artifact link", or "control the browser inside Supervibe". Prefer this over raw `git worktree`, ad hoc PTYs, Playwright, or Computer Use when the task touches Supervibe-managed state. Use Computer Use for browser windows, webviews, or desktop UI outside Supervibe's embedded browser.
Commit and push agent-skill changes to the user's private skills GitHub repo (<private-skills-repo>, rooted at ~/.agents). Use after creating or updating any skill, when the user says "push the skill", "push skills to github", "save the skill to my repo", or "update the skills repo". Handles staging, committing, and pushing directly in the current shell — works in any agent, no cmux needed.
Run the Build phase of an SDD/AgentSpec workflow from the Brainstorm, Define, and Design Markdown files and user interactions. Use when the user wants to implement an already specified feature: read the three artifacts, extract and order the File Manifest, recommend and confirm the execution mode, change only the planned code, verify incrementally, handle drift and LLM prompts, apply the migration from the manifest to the database (with project name and ref confirmation and read-back proof), run the blocking Verify Gate from Define, and generate BUILD_REPORT_{FEATURE}.md with evidence. Requires write access to the project/code and must finish with the SDD workflow completed and the BUILD_REPORT validated.
Run the Define phase of an SDD/AgentSpec flow based on the Markdown file generated by Brainstorm and clarification interactions with the user. Extract and structure the problem, users, goals, metrics, scope, constraints, and technical context; write acceptance tests in EARS, resolve ambiguities, calculate a Clarity Score, and define an objective Verify Gate. Use after SDD Brainstorm by RDD to generate a DEFINE_{FEATURE_NAME}.md ready for the next gate.
Produce the Design phase of an SDD/AgentSpec flow from the Brainstorm Markdown file, the DEFINE file, and technical clarification interactions with the user. Turn validated requirements into architecture, components, inline ADRs, file manifest, code standards, data flow, integrations, testing strategy, error handling, configuration, security, and observability. Use after SDD Define by RDD, especially when the user provides BRAINSTORM_*.md and DEFINE_*.md and wants to generate a DESIGN_*.md ready for SDD Build by RDD.
Generate a detailed product specification document from a vague idea, rough description, or supporting materials (UI sketches, screenshots, notes, existing docs). Use this skill whenever the user wants to turn a rough concept into a structured spec — even if they say things like "write up a spec for...", "turn this idea into a requirements doc", "I have this rough idea for a product", "help me spec this out", "create a PRD for...", or uploads images/files and wants a spec written from them. Covers all product types including internal tools. Trigger this skill even if the request seems simple — a vague one-liner idea deserves a proper spec just as much as a detailed brief.
Test-Commit-Revert + TDD (TCRDD): red/green/refactor with per-phase auto-commit on success and auto-revert on failure, gated by user approval before code and before committing. TRIGGER when: user says TCRDD, TCR, TDD, red-green-refactor, "test-first", "write the test first", "let's TDD this", "baby steps", "commit on green", "revert on failure", or "go step by step with tests"; user wants approval-gated pair programming or test-then-code cadence. DO NOT USE for: retrofitting tests onto existing code (use `testing`); one-off bug fixes; no runnable test command; trivial code, GUI layout, throwaway scripts, or trusted third-party wrappers. Prefer over `testing` for commit cadence.
Planning skill for transactional notifications, alerts, and reminders. Assesses developer needs across urgency, channel selection, delivery confirmation, and fallback patterns to recommend the right Twilio notification architecture. Handles both “send shipping updates to customers” and “build a multi-channel alert system with delivery confirmation and fallback”
Build AI-powered voice agents using Twilio ConversationRelay. Handles real-time speech recognition (ASR), text-to-speech (TTS), and bidirectional audio streaming via WebSocket. Covers TwiML setup, WebSocket message types, LLM integration, streaming responses, and voice provider configuration. Use this skill to build voice bots, IVR replacements, or real-time AI voice assistants on Twilio calls.
TypeGPU and raw WebGPU adapter patterns for FrameVideo. Use when creating GPU-rendered compositions with TypeGPU, raw WebGPU, WGSL fragment shaders, compute pipelines, liquid glass effects, particle systems, or any canvas layer driven by navigator.gpu that responds to FrameVideo fv-seek events
Web Animations API adapter patterns for FrameVideo. Use when authoring element.animate() motion, Animation currentTime seeking, document.getAnimations(), KeyframeEffect timing, fill modes, or native browser animations that must render deterministically in FrameVideo
Expert skill for designing, building, and deploying modern premium websites with advanced animations and 3D interactive experiences using Three.js, React Three Fiber, GSAP, and Framer Motion. Use this skill whenever the user wants to build a website with 3D elements, create an immersive web experience, add interactive 3D graphics to a page, build a premium landing page with cinematic visuals, design a modern startup website with animations, create WebGL or Three.js scenes, build a product showcase with 3D models, or produce any kind of visually impressive, award-winning web interface. Also trigger when the user says things like "make it look like Awwwards", "add 3D to my site", "build an interactive landing page", "create an immersive experience", "premium website with animations", "modern startup page", "hero with particles or globe", "floating 3D elements", or mentions anything related to Three.js, React Three Fiber, WebGL, GSAP timelines, scroll-driven animations, particle systems, 3D product visualization, or cinematic web design — even if they don't explicitly say "3D" or "animation"
Audit and prioritize performance work through bounded-work and forward-progress checks. Use when asked to find performance issues, investigate freezes/500s/OOMs, review retries or polling for no-progress loops, rank a performance backlog, or implement the next simple performance fixes
Expert knowledge for Azure SignalR Service development, including troubleshooting, best practices, decision-making, architecture and design patterns, limits and quotas, security, configuration, integrations and coding patterns, and deployment. Use when configuring SignalR modes, upstream endpoints, Entra auth, multi-region topologies, or Event Grid/API Management integrations, and for other Azure SignalR Service-related development tasks. Not for Azure Web PubSub (use azure-web-pubsub), Azure Service Bus (use azure-service-bus), or Azure Event Hubs (use azure-event-hubs).
Edit the scene currently open in Creator Hub through its MCP server: entities, components, Smart Items, scene settings, and preview. Use when `creator-hub` MCP tools are in the session, a scene is or may be open in Creator Hub (including before editing its main.composite, main.crdt, or scene.json), when connecting an external agent to the Hub, or when the user mentions the Creator Hub AI assistant or its MCP server.
TOP PRIORITY skill — find and immediately fix or remove every piece of wrong, outdated, or redundant information in ToolUniverse docs. Wrong code, broken links, incorrect counts, and overlapping instructions must be fixed or removed — never left in place. Runs five phases: (D) static method scan, (C) static tool-call check, (A) automated validation, (B) ToolUniverse audit, (E) less-is-more simplification. Core philosophy: each concept appears exactly once; remove don't add; no emojis; single setup entry point. Use when reviewing docs, before releases, after API changes, or when asked to audit, fix, or simplify documentation.
Build functional prototypes and MVPs at maximum speed to validate ideas through working software. Use for proof-of-concept development, rapid iteration on user feedback, no-code or low-code solutions, backend-as-a-service integration, A/B testing scaffolding, quick feature validation, or modular architectures designed for fast experimentation and learning.
End-to-end orchestration for non-trivial software feature development. Use this skill whenever the user asks to implement a PR-sized feature, break down a plan, have subagents review a plan, run a plan-review-development-acceptance loop, coordinate multiple review perspectives, produce an acceptance report, or generate an HTML PR summary. Prefer this skill for multi-step code changes even if the user only says "build this feature" and the task is not a tiny one-file edit.
Initialize a Harness Engineering framework in the current project. Use when user says 'harness', 'init harness', 'initialize framework', 'setup harness engineering', '/harness', or wants to set up a Plan-Build-Verify development workflow with specialized agents (planner, generator, evaluator). Creates CLAUDE.md, agent definitions, command templates, hooks, and documentation structure for autonomous AI-driven development
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.