Skills
100,928 packaged capabilities and playbooks for agents. Install any of them with one command.
All
Design ObjectStack automation — Flows (visual logic), Triggers, Approvals, state machines, and the `jobs` (`defineJob`) / `webhooks` (`defineWebhook`) stack collections. Use when the user is adding `*.flow.ts`, wiring an event-driven rule, modelling an approval chain, or building an interactive screen flow / wizard (objectstack-ui routes those here). Do not use for data lifecycle hooks at the object layer (see objectstack-data) or for kernel / plugin events (see objectstack-platform). CEL expressions in flow conditions / edge guards: load objectstack-formula alongside.
Author ObjectStack translation bundles — object/field labels, view text, app navigation strings, automation messages — and configure locale fallback, coverage reporting, and the source layout. Use when the user is adding `*.translation.ts` files, authoring a `translation` metadata item in the Studio or through the metadata API, shipping a generated bundle from a package or plugin, wiring a new locale, or resolving missing-translation warnings. Do not use for general i18n library questions unrelated to ObjectStack bundles.
Construct ObjectQL queries — filters, sorting, pagination, aggregation, relation expansion, and full-text search. Use when the user is writing a query DSL expression or picking a pagination strategy. Do not use for defining objects / fields / relationships (see objectstack-data), for designing the API endpoint that exposes a query (see objectstack-api), or for a list view's filter rules / dashboard datasets (see objectstack-ui).
Shellcode development reference for offensive security engagements. Use when writing custom x86/x64 shellcode, implementing position-independent code (PIC), building shellcode loaders, evading AV/EDR detection, or converting PE files to shellcode. Covers null byte avoidance, API hashing, encoder/decoder patterns, staged vs stageless payloads, Windows PEB traversal, and cross-platform shellcode techniques.
Generate AI music with Producer via AceDataCloud API. Use when creating songs, generating lyrics, extending tracks, creating covers, swapping vocals/instrumentals, replacing song sections, or uploading reference audio. Supports custom lyrics, instrumental-only mode, and multiple creative actions.
Write, render and edit diagrams in reladraw, a text diagram language where you say where things go, so the arrangement can be read back out of the source without looking at the picture. Use when asked to draw, diagram, sketch or visualize an architecture, a system, a data flow, a pipeline, a deployment, a directory layout, or the shape of a change or pull request; when reading or editing a .reladraw file; or when the user says "reladraw", "diagram this", "draw the architecture", "show me how these pieces fit". Use it in place of Mermaid, Graphviz, D2 or hand-drawn ASCII boxes whenever a node-and-line diagram is wanted and reladraw is installed. NOT for charts of data — bar, line, pie, scatter — and NOT for pictures that are not nodes and lines.
Turns an approved topic or copy into a video plan ready for filming, screen recording, or production with video tools. Also supports digital-human videos after the user confirms portrait and voice rights and manually uploads to the platform, as well as animated explainer videos without on-camera presenters, using synthetic narration and AI-generated visuals (educational, historical, or brand stories). For scripts, opening 3-second hooks, storyboards, subtitles, screen-recording checklists, covers, topics, music and licensing, digital-human or animation production packs, multi-platform horizontal and vertical versions, and publishing copy for WeChat Channels, Douyin, Xiaohongshu video, YouTube landscape videos, and Shorts.
Rebuild an approved source HTML application as a real, high-fidelity UI in the target repository. Use for source-to-app design tasks requiring interactive source discovery, authored routes and components, local UI behavior, responsive/theme adaptation, and paired Playwright evidence.
From an idea to a sellable series design: series engine/franchise, story pattern, character webs that keep generating conflict, pilot types, and the documents that sell them (series engine/franchise/story pattern/character web/pilot types/series bible/springboard/pitch). Merged from Rabkin's four-element franchise and story landmines, Landau's tacit contract and pitch recipe, Oberg's series types and bible specs, Douglas's franchise-plus-springboard and bible tiers, Goldberg & Rabkin's 100-episode test, Blum's concept/presentation/bible ladder, Miller's ten-component treatment, Calvisi's Compelling Crisis, Smith's series format, plus engines read off Sopranos, Fleabag, and Succession. Use when turning an idea into a series, testing whether a premise has legs, choosing premise vs. typical-episode pilot, designing a sustainable character web, writing a logline, pitch document, bible, or treatment, picking a series type, adapting IP into a series, or diagnosing a project that feels “more like a movie than a series.”
Re-inject Synapse A2A initial instructions after context has been cleared. Use this skill when the agent has lost its identity, A2A communication protocol, or configuration after /clear or context reset, when synapse send/reply commands stop working, or when the agent no longer recognizes its SYNAPSE_AGENT_ID. Triggered by /synapse-reinst command.
Build, review, and audit technical docs and agent instruction files. Applies Simplified Technical English (ASD-STE100) to prose, scales to huge docs trees with sharded audits and ledgers, and runs as Claude Workflows or sub-agents when available.
Automate TikTok + Instagram slideshow marketing for any app or product. Researches competitors, generates AI images, adds text overlays, posts via Upload-Post (multi-platform in one API call), tracks analytics, and iterates on what works. Use when setting up TikTok marketing automation, creating slideshow posts, analyzing post performance, optimizing app marketing funnels, or when a user mentions TikTok growth, slideshow ads, or social media marketing for their app. Covers competitor research (browser-based), image generation, text overlays, multi-platform posting (Upload-Post API — TikTok + Instagram + more simultaneously), analytics tracking, hook testing, CTA optimization, conversion tracking with RevenueCat, and a full feedback loop that adjusts hooks and CTAs based on views vs conversions.
Translate free-text tumor descriptions to OncoTree codes and resolve cancer subtypes/tissue hierarchy. Cross-references UMLS/NCI vocabularies. Use for standardizing cancer-type nomenclature in EHR free-text, building cohorts in OncoKB or GDC, mapping tumor-board notes to ontology codes, and ensuring consistent terminology across cancer-genomics pipelines.
HLA gene-family analysis and MHC-peptide binding for transplant compatibility, vaccine epitope coverage, and cancer immunotherapy. Uses IMGT (HLA polymorphism), IEDB (epitope-MHC binding), UniProt (annotation), DGIdb (druggability). Use for HLA typing/imputation review, vaccine HLA coverage, and immunotherapy prediction biomarkers (HLA-LOH, neoantigen presentation).
Use this skill when writing, designing, or optimizing Trigger.dev background tasks and workflows. This includes creating reliable async tasks, implementing AI workflows, setting up scheduled jobs, structuring complex task hierarchies with subtasks, configuring build extensions for tools like ffmpeg or Puppeteer/Playwright, and handling task schemas with Zod validation.
Turn wiki golden pages into a CI-blocking eval suite with a cheap→expensive assertion cascade plus a committed regression baseline. Goldens are md files under llmwiki/wiki/sources/evals/ with YAML frontmatter (input, expected, optional rubric, asserts). The engine runs deterministic tier-1 asserts (equals/contains/regex/is-json/is-sql-ish) in pure code, an optional tier-2 similarity, and reports tier-3 (LLM-rubric judge) as the quarantined adapter — never calling a model. Candidate outputs come from --outputs outputs.json so the suite is fully runnable without any model. Trigger when the user says "wikieval", "eval suite for the wiki", "regression gate for goldens", "assertion cascade", "block CI on eval drop", or invokes /wikieval.
Expert iOS App Store submission and approval system. 9 specialized agents provide senior App Review Team-level expertise across compliance, design, privacy, monetization, metadata, technical requirements, timing, rejection recovery, and learning. Triggers on keywords like app store, iOS submission, apple review, app rejection, aso, privacy manifest, privacy labels, ATT, iap, in-app purchase, subscription, storekit, review guidelines, HIG, testflight, app store connect.
Use when implementing Liquid Glass effects, reviewing UI for Liquid Glass adoption, debugging visual artifacts, optimizing performance, or requesting expert review of Liquid Glass implementation - provides comprehensive design principles, API patterns, and troubleshooting guidance from WWDC 2025. Includes design review pressure handling and professional push-back frameworks
Expert knowledge for Azure AI Search 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 indexes, vector/semantic search, indexers and skillsets, RBAC/ACL security, or deployment automation, and other Azure AI Search-related development tasks. Not for Azure Cosmos DB (use azure-cosmos-db), Azure Data Explorer (use azure-data-explorer), Azure SQL Database (use azure-sql-database), or Azure Synapse Analytics (use azure-synapse-analytics).
Use when writing, reviewing, or refactoring TypeScript or React code with a focus on craftsmanship—naming, function and component shape, error handling, data modeling, tests, and abstraction. Translates Robert C. Martin's Clean Code principles into modern TS+React idioms (TS 5.x, React 19), with first-class “When NOT to apply” guidance and a Meta category for principle conflicts (DRY vs. SRP, small functions vs. deep modules, type safety vs. ergonomics). Triggers on code review, refactoring for clarity, naming, function/component design, “is this clean?”, “make this more readable,” “right abstraction?”—even when the user doesn't say “clean code.” Does NOT cover React-specific APIs (RSC, hooks API surface)—use the `react` skill. Does NOT cover TS compiler performance or tsconfig—use the `typescript` skill.
Troubleshoot and resolve common issues with the ClickHouse Node.js client (@clickhouse/client). Use this skill whenever a user reports errors, unexpected behavior, or configuration questions involving the Node.js client specifically — including socket hang-up errors, Keep-Alive problems, stream handling issues, data type mismatches, read-only user restrictions, proxy/TLS setup problems, or long-running query timeouts. Trigger even when the user hasn't precisely named the issue; vague symptoms like "my inserts keep failing" or "connection drops randomly" in a Node.js context are strong signals to use this skill. Do NOT use for browser/Web client issues.
End-to-end Proteina-Complexa design pipeline driver. Reach for this skill whenever the user wants to "design a binder", "design binders for X", "run complexa design", "de novo binder", "PDL1 binder", "TrkA binder", "design proteins for target", "protein binder design", "ligand binder", "design a small-molecule binder", "ATP-binding protein", "AME motif scaffolding", "scaffold a motif near a ligand", "motif + ligand design", "enzyme scaffolding", "flow matching protein design", "beam-search binder", "FK steering", "MCTS protein design", "refold with AF2", "refold with RF3", or wants success rates, interface pAE, scRMSD, or FoldSeek diversity from a single command. This is the scientific anchor of the skill set: it drives `complexa design <pipeline>` from target picking to manifest emission and tells the user how many designs passed
Comprehensive customer success and retention expertise combining onboarding, health scoring, churn prevention, retention strategies, and LTV maximization. Use when designing customer onboarding flows, reducing churn, building health scores, creating retention systems, designing upsells, or improving customer lifetime value. Covers proactive engagement, cancel flows, dunning, re-engagement, and the full customer lifecycle.
Root-causes AI agent failures from MLflow traces without requiring a code change, regression suite, scorer, or evaluation run. Use when the user asks to debug, investigate, explain, or determine why an agent produced an output. Prefer an existing matching trace; reproduce only when no usable trace exists.
Structure a Flutter design system as tokens→theme→modifiers→shapes with two-tier tokens (primitives named by measured value and semantic slots named by role) exposed through a ThemeExtension read via an asserting of(context); hand-author both light and dark ColorScheme instead of ColorScheme.fromSeed; keep every raw color/hex/Colors./Curves./Duration/BorderRadius/fontSize inside lib/theme/ behind a no-raw-values gate; collapse animation to zero under reduced motion, restore the persisted theme before first paint, bundle fonts (never google_fonts/dynamic_color), and derive each stateful meaning’s supporting color last so color is never its sole signal. Use when creating or editing ThemeData/ThemeExtension/ColorScheme, adding or renaming a design token, wiring theme injection or theme-mode persistence, reaching for fromSeed/dynamic_color/google_fonts/FontVariation, structuring a theme/ or DesignSystem/ folder, or reviewing any widget that renders a color, radius, duration, or font.
Help users debug PostHog Error Tracking stack-trace symbolication for any supported platform — JavaScript/TypeScript web, React Native (Hermes), Android (Proguard / R8), or iOS / macOS (dSYM). The PostHog symbol-set lookup flow is universal across platforms; build-tool and artifact details live in per-platform references (JavaScript is fleshed out, others come as we encounter them). Use when stack frames stay minified or obfuscated after symbols are uploaded, PostHog symbol sets show last_used but frames are not readable, chunk IDs or dSYM UUIDs do not match, "Token not found" appears, uploaded source maps / dSYMs / Proguard mappings look empty, or bundler / symbol-upload configuration needs troubleshooting.
Trigger when the user provides dream-related text, a diary excerpt, or a spoken account of a dream and wants to generate a video. Trigger phrases include “dreamed of,” “dreamt about,” “I had a dream,” “dream material,” “generate a video for me,” “turn it into a video,” and “dream to video.” Also applies when the user pastes a dream description and expects a video file. This skill converts the text into video prompts, submits them to the 即梦 platform for generation, and downloads the video file.
Register AI agents on Ethereum mainnet using ERC-8004 (Trustless Agents). Use when the user wants to register their agent identity on-chain, create an agent profile, claim an agent NFT, set up agent reputation, or make their agent discoverable. Handles bridging ETH to mainnet, IPFS upload, and on-chain registration.
Identify and analyze A-share company events that may create pricing disparities, including mergers and restructurings, asset injections, buybacks and share purchases, management changes, and index adjustments. Use this skill when users ask about merger and restructuring opportunities, asset injections, share buyback analysis, state-owned enterprise reform, index-adjustment trading, special-situation investing, or event-driven strategies.
Explainer video production guide: scripting, voiceover, visuals, and assembly. Covers script formulas, pacing rules, scene planning, and multi-tool pipelines. Use for: product demos, how-it-works videos, onboarding videos, social explainers. Triggers: explainer video, how to make explainer, product video, demo video, video production, video script, animated explainer, product demo video, tutorial video, onboarding video, walkthrough video, video pipeline
Use this skill alongside figma-use when the task involves translating an application page, view, or multi-section layout into Figma. Triggers: 'write to Figma', 'create in Figma from code', 'push page to Figma', 'take this app/page and build it in Figma', 'create a screen', 'build a landing page in Figma', 'update the Figma screen to match code', 'convert this modal/dialog/drawer/panel to Figma'. This is the preferred workflow skill whenever the user wants to build or update a full page, modal, dialog, drawer, sidebar, panel, or any composed multi-section view in Figma from code or a description. Discovers design system components, variables, and styles from Code Connect files, existing screens, and library search, then imports them and assembles views incrementally section-by-section using design system tokens instead of hardcoded values.
Transcribe audio or video files into timestamped Markdown files using the local FunASR service. Supports common formats such as mp4, mov, mp3, wav, and m4a. Use this skill when the user needs speech-to-text, meeting notes, video subtitles, or podcast transcription.
Use when executing an engineering plan produced by gitnexus-plan (or a small, bounded task directly): implement step by step with GitNexus impact checks before every symbol edit, run tests from the plan’s scenarios, and gate every commit with detect_changes. Examples: “/gitnexus-work docs/plans/2026-07-11-gitnexus-plan-ingestion-retry.md”, “/gitnexus-work” (latest plan), “execute the plan”
Expert blueprint for sports games (FIFA, NBA 2K, Rocket League, Tony Hawk) covering physics-based ball interaction, team AI formations, contextual input, and match umpire/score authority. Broadcast framing routes to godot-camera-systems. Use when building soccer, basketball, hockey, racing sports, or arcade sports games. Keywords ball physics, magnus effect, formation AI, team tactics, contextual controls, steering behaviors.
Google Ads account audit and business context setup. Use for account-health audits and business-context setup. Trigger on "audit my ads", "ads audit", "set up my ads", "onboard", "account overview", "how's my account", "ads health check", "what should I fix in my ads", or when the user is new to NotFair and hasn't run an audit before
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.