Skills
101,323 packaged capabilities and playbooks for agents. Install any of them with one command.
All
Build and optimize SOQL queries including relationship queries, aggregate functions, polymorphic TYPEOF, and selective filters. Use when asked to write queries, debug slow queries, optimize existing SOQL, or enforce query security. Activate on mentions of "SOQL", "query", "SELECT", "WHERE", "aggregate", "relationship query", or "query optimization".
Install, update, remove, create, improve or audit skills for Claude Code and Codex, on this computer, in one folder or on their server. Use when the user says "installe ce skill", gives a skill link, "supprime ce skill", "mets à jour mes skills", "fais-en un skill", or a skill misbehaves
Use when you need to turn a supplied set of comments, DMs, reviews, community posts, or call notes into an evidence-backed picture of what people ask, resist, and repeat. Trigger phrases include "what are people saying about this?", "mine these comments", "what language should we use?", "find recurring objections", and "summarise this community feedback". Do not use this to scrape platforms, infer demographics, or write positioning from a handful of anecdotes; use agent-reach to collect public evidence first, audience-personas to group people, and positioning-audit to decide the message.
SolidJS 2.0 implementation and API explanations, including React comparisons, async patterns, stores, DOM, and server functions. Use for code or questions targeting solid-js major 2. For a requested 1.x conversion use solidjs-v2-migration; for a diff review use solidjs-v2-reviewer.
Use when you need to locate the current spec pack (FEATURE_DIR) in the sdlc-dev Spec workflow, avoid reading or writing requirements/*.md in the wrong directory, or when issues arise such as "wrong context / wrong file written / branch not following the convention".
Compress the boring, repetitive stretches of a video - long form fills, waiting, repeated steps - by cutting the middle out and adding a brief "sped up" cue so the pacing stays honest. Use when the user says "speed up the boring parts", "time-lapse the form filling", "fast-forward through the waiting", "the repetitive section drags", or shares a video with long stretches of the same action repeating.
Use this skill when driving the `stackbone` CLI to scaffold, run, ship or operate a Stackbone workspace: signing in with the device flow (login / logout / whoami), scaffolding a workspace and linking it to the organization (init, with an optional first agent / workflow / workflow-agent), adding pieces offline (add agent / add workflow / add workflow-agent), running the local emulator with Studio (dev), compiling the deployable bundle (build) or writing a deploy folder (package), registering a deployed box (link --installation --url --secret --tag), switching the active organization (organization use), reading workspace state as JSON (metadata), managing Drizzle migrations (db migrate create / up / status), and operating a running installation from the shell: discovering targets (agents), listing / inspecting / starting durable workflows (workflows), inspecting and controlling runs (runs), tailing logs (logs), browsing the agent DB read-only (db query / schemas / table), moving objects (storage), operating the RAG index (rag), setting secrets (secrets), versioning the config document (config), deciding approvals (hitl), managing the prompt catalog (prompts), inspecting the protocol contract (contract), running eval suites (eval), and printing how to reach the docs MCP server (docs). Trigger on requests like: scaffold a workspace, add an agent, add a workflow, start the dev stack, log in, list my agents, start a workflow by name, retry a failed run, tail the logs, run a SELECT against the agent, set a secret, roll the config back, approve an approval, generate a migration, build the bundle, package for deploy, register the deployed agent, switch org. For writing the code inside the workspace with @stackbone/sdk use the stackbone skill; to triage an error or a stuck run use stackbone-debug; to start a new piece from a description use stackbone-coder.
Use this skill when triaging an error, a failure or unexpected behavior in a Stackbone workspace: a deep agent or a durable workflow running locally under `stackbone dev`, or an installation deployed in the customer's cloud. Covers SDK errors (the { data, error } envelope and its `<prefix>_<reason>` codes), thrown errors from stackbone.database, callDeepAgent and stackbone.connection(id), HTTP 4xx/5xx from the control plane or the box, CLI error codes (dev_not_running, runtime_not_configured, …), a `stackbone dev` boot that stops or fails, durable run failures and timeouts, a workflow start rejected on its input schema (workflow_input_invalid), HITL stuck at either level (a workflow parked on requestApproval(), an agent turn interrupted on a gated tool), durable-session issues (memory not surviving), database slow queries / pgvector mismatches, secrets decryption errors, connector call failures (no installation, a bad credential), build failures (native dep, a second SDK copy), and tier / billing 402 responses. Trigger on requests like: my agent isn't working, why is this 500, this run hung, the inbox is empty but the run is paused, the agent forgot the conversation, the workflow rejected my input, dev won't boot, why am I getting 402, my connector call is rejected, the model returns nothing. This skill locates the cause and does not propose fixes: once found, switch to the stackbone skill (code) or the stackbone-cli skill (commands) for the fix.
Continuously improve Remotion Studio by making a video, reproducing real UX and performance issues, fixing them, and verifying the result. Use for ongoing Studio dogfooding and maintenance, including checkpoints that hand one PR over for review while work continues in a stacked PR.
Session management and project status dashboard. Owns the full session lifecycle (start/work/close/resume), focus lane, bookmarks, worktree detection, and tab naming. Also serves as the project status dashboard — shows active epics, progress, actionable next steps, blocked items, tasks, GitHub issues, and recommendations. Worktree creation is deferred to swain-do task dispatch (SPEC-195). Triggers on: 'session', 'status', 'what's next', 'dashboard', 'overview', 'where are we', 'what should I work on', 'show me priorities', 'bookmark', 'focus on', 'session info'.
Orchestrate multi-agent swarms with agentic-flow for parallel task execution, dynamic topology, and intelligent coordination. Use when scaling beyond single agents, implementing complex workflows, or building distributed AI systems.
Use this skill whenever the user mentions Microsoft Teams in a development context — whether they're building, integrating, configuring, debugging, porting a Slack bot to Teams, or just asking questions. Covers bots, message extensions, embedded web apps, Adaptive Cards, dialogs, SSO, infrastructure, the Teams Developer CLI/SDK, Slack Bolt migration, and general Teams platform queries. If the word "Teams" appears, err on the side of invoking this skill.
Create, edit, push, or version a Coder template. Use for requests like "scaffold a Docker template", "build a Kubernetes template", "add a coder_parameter for the Git repo URL", "push my template to this Coder deployment", "update the existing aws-linux template to add JetBrains", or "deprecate this template version". Do not use for installing or upgrading Coder itself (use the setup skill), adding a single module to a template that already builds (use the modules skill), or authoring custom Terraform providers unrelated to Coder.
Testing expert with comprehensive knowledge of test structure, mocking strategies, async testing, coverage analysis, and cross-framework debugging. Use PROACTIVELY for test reliability, flaky test debugging, framework migration, and testing architecture decisions. Covers Jest, Vitest, Playwright, and Testing Library.
Run and manage long-lived background commands using tmux sessions instead of background processes. Use when starting backend/API servers, Expo/React Native dev servers, job workers, watchers, or any task that should keep running while other commands are executed.
Use when the user wants to view AI conversation token usage as a receipt, invoice, checkout slip, token bill, usage receipt, cost snapshot, or creative monospace thermal-paper artifact. Always consider this skill for Chinese prompts like 查看本次对话 Token 消耗, 生成 token 小票, 对话发票, AI 用量账单, 把这次对话打成小票, 看看这轮 token 消耗, or any request to make token/context usage visually shareable.
Operate Trau (display name Cobble) — the autonomous, ticket-driven development loop (trau.sh) — from a shell or MCP client: file, search and queue tickets, arm or pause the queue drain, watch and steer live runs, switch a run's provider, answer a PR or QA hold, settle an ADR conflict, read evidence, spend and conformance results, diagnose, resume or discard failed or quarantined runs, hand a run a secret, work a ticket's operator checklist, set config, manage QA sign-in accounts, tracker and forge connections, hosted collaborators and the local web hub. Use whenever the user mentions trau or Cobble, the trau hub, queue, drain, babysitting a drain, steering a run, a quarantined, parked, awaiting-qa or needs-human ticket, `trau doctor`, `trau forensics`, `trau update`, `trau connect`, QA accounts or proofs — or asks to start, stop, monitor, or debug autonomous ticket runs in a repo trau manages, even phrased as "queue this ticket", "what is the loop doing", "why won't the drain arm", or "why didn't COD-123 merge". Do not use for writing trau's own source code, or for general git/PR workflow questions unrelated to trau runs.
Use whenever writing, editing, refactoring, or reviewing TypeScript or TSX code. This skill defines how TypeScript should be modeled, how boundaries and shared helpers should be handled, how intent should be expressed without code comments, and how to keep code clear, DRY, and free of defensive AI slop. For review workflows, read references/review-and-fix-changes.md.
Implement semantic vector search for construction data. Build AI-powered search using embeddings and vector databases (Qdrant, ChromaDB) for intelligent querying of specifications, standards, and project documents.
Calculate a complete Vedic/Jyotish natal chart directly from birth date, exact time, and place, producing the canonical structured_data.md for downstream analysis. Use for requests such as 'calculate my Vedic chart', 'cast my birth chart', 'generate a chart from my birth details'; Chinese triggers including '直接排盘', '计算星盘', '快速排盘', and '算一下'; or Japanese triggers including '出生図を作って', 'ホロスコープを計算して', and 'ヴェーダ占星術で出生図を出して'. Also use when vedic-reader has birth details but no chart file. / 吠陀占星排盘计算引擎。
Produces a dubbed, re-synced version of an existing Clueso video in one or more target languages, using a confirmed glossary to keep product and feature names consistent across every language, a register check (tu/vous, du/Sie, keigo), and a duration-inflation budget per clip before any voice is generated. Translation is done by the assistant itself; Clueso handles voice selection, narration generation, and re-sync. Use when the user says "translate this video into Spanish", "dub this demo in French and German", "localize my onboarding video for the Japanese market", "add a Spanish voiceover", or "make a French version of this project".
Help users write professional-grade AI video prompts and generate an MP4 video straight from them. Supports multiple creative scenarios and problem diagnosis to ensure prompts are accurate and executable. Trigger words: video prompt, video generation prompt, AI video creation, write video prompt, director instruction, text-to-video prompt, video script, generate video
Complete platform upload specifications for viral video creation across TikTok, YouTube Shorts, Instagram Reels, Facebook Reels, Snapchat Spotlight, and Twitter/X. PROACTIVELY activate for: (1) Platform-specific video encoding, (2) Upload requirements lookup, (3) Multi-platform export, (4) File size optimization, (5) Aspect ratio conversion, (6) Duration limits, (7) Audio requirements, (8) Caption/subtitle specs, (9) Thumbnail requirements, (10) Quality vs compatibility trade-offs. Provides: Comprehensive spec tables, FFmpeg presets per platform, optimal encoding settings, file size calculators, batch export workflows, and 2025-2026 platform-specific algorithm insights.
Aggregate customer feedback from multiple sources — support tickets, NPS comments, Slack messages, G2 reviews, call transcripts, survey responses — into a unified VoC report with theme clustering, sentiment analysis, trend detection, and actionable recommendations for product, marketing, and CS teams. Chains review-scraper for public review data.
Use to diagnose and fix incorrect gradients in differentiable Warp programs. Anything trained, optimized, calibrated, or fit through Warp kernels depends on wp.Tape gradients, so treat any misbehavior of such a workflow as a gradient problem until proven otherwise — use this when training diverges or NaNs, won't train at all, stalls or plateaus above the expected loss, converges to a wrong or biased answer, is worse than a reference implementation, works at small scale but fails at production scale, or fails a QA/validation recheck. Also for explicit symptoms — exploding, NaN/inf, zero, or subtly wrong gradients, suspected wp.Tape/backward issues, gradcheck failures — but users usually describe only the surface symptom ("the sim explodes", "the fit gets dragged toward outliers") without mentioning gradients: make that leap. Not for forward-only Warp work, build/install problems, or autograd issues in other frameworks without Warp.
Visual inspection and code review for compliance with the Web Interface Guidelines. Triggers on "review my UI", "check accessibility", "audit design", "review UX", "fix the layout", "find design problems". Supports static code analysis and visual inspection in the browser with automatic fixes.
Discover your actual workflow through conversation or observation, then generate a tailored skills bundle that encodes it as loadable agent skills with trigger conditions. Use when you want to understand your own process, formalize it, or share it with collaborators. Also use when a session feels aimless — this skill gives it structure. Do not use this skill for unrelated requests; route to the nearest named specialist.
Create a WeChat Mini Program project with AI capabilities from scratch. Triggered when the user wants to create a brand-new WeChat Mini Program (not adding features to an existing project). Integrates cloud development, database, login, payment, and other capabilities. Requires Node.js 18+ and the mp-skills CLI.
When the user wants to build a developer following on Twitter/X, write technical threads, or understand what works for dev audiences on X. Trigger phrases include "Twitter," "X," "developer Twitter," "tech Twitter," "technical threads," "building dev following," or "Twitter for developers."
A focused development workflow engine for AI coding agents, invoked as `/absolute <command> [target]`. One skill, eleven commands. One sets it up: `init` (interview how you want absolute to behave + detect the stack once, then write JSON config — `.absolute.config.json` per project and `~/.absolute/config.json` for user defaults and per-project overrides — that every other command reads instead of re-detecting; non-blocking, the others soft-recommend it). Five cover the build loop you run every day — think → spec → plan → build → polish → document: `work` (end-to-end, phase-gated SDLC: relentless design interview → reviewed spec → dependency-graphed task board → safe-wave TDD execution → verification), `spec` (lightweight standalone design spec: codebase scan → bounded clarify pass → write a reviewed design doc to docs/plans → scored reviewer subagent → stop, no build), `ui` (polished, intentional interface design with concrete CSS/Tailwind values — typography, color, layout, dark mode, accessibility, animations), `simplify` (autonomously simplify your working git changes — reduce complexity, remove redundancy, keep tests green), and `docs` (Diátaxis-driven documentation — tutorials, how-tos, reference, explanation, READMEs, ADRs, with stack detection and code-verified accuracy). Five more keep the codebase healthy — standing maintenance on green main, each a risk-ranked, gated, safe-wave scan-and-fix: `upgrade` (dependency upgrades — outdated/vulnerable deps bumped in semver waves, majors gated and changelog-read, tests green after each), `audit` (vulnerability & security scan — dependency CVEs plus risky code patterns, severity-triaged and remediated; defensive, on your own repo), `prune` (dead code & dependency cleanup — unused deps, exports, files removed with evidence, repo-wide), `debt` (lint & typecheck debt paydown — clear pre-existing warnings/errors and suppressions by rule, no cheating the checker), and `deflake` (flaky test fixes — diagnose and fix the root nondeterminism, never retry/skip/sleep). Triggers on "absolute init|work|spec|ui|simplify|docs|upgrade|audit|prune|debt|deflake", "set up absolute", "initialize absolute", "configure absolute", "build this end-to-end", "plan and build", "grill me on this", "write a spec", "draft a design doc", "design this UI", "make this less like AI slop", "simplify this", "clean up my changes", "write docs", "audit our docs", "upgrade our dependencies", "are we vulnerable", "security audit", "remove dead code", "fix our lint/type errors", "fix flaky tests", or any multi-step development, design, cleanup, documentation, or maintenance task.
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.