Skills
100,928 packaged capabilities and playbooks for agents. Install any of them with one command.
All
This skill should be used when auditing Effect TypeScript compliance, or when users mention effect scan, effect audit, effect best-practices checks, or scan-effect-solutions. It provides a structured compliance checklist for TypeScript configuration, services/layers, data modeling, error handling, config, testing, runtime execution, and Option/Either anti-patterns.
Set up and run deterministic security scanners across a repo or a whole fleet of repos — gitleaks, trufflehog, semgrep, osv-scanner, trivy, checkov, Brakeman, govulncheck, Supabase advisors, and (guarded) nuclei/ZAP — then normalize their output to findings.json or SARIF, dedupe, suppress with expiry, schedule in CI, and hand findings to fix agents. Use when the user mentions 'run scanners,' 'security scanning pipeline,' 'set up gitleaks,' 'betterleaks in CI,' 'semgrep in CI,' 'osv-scanner,' 'trivy fs,' 'SARIF,' 'code scanning,' 'scan all my repos,' 'security-scan workflow,' 'weekly security scan,' 'Supabase RLS advisor,' 'dedupe scanner findings,' 'suppression file,' 'stop asking Claude to hack my app,' or wants tools, not an agent, to find the bugs.
Use when the user wants to iterate on a viral-article scoring system itself, calibrate or improve a scoring prompt against labeled samples, or run batch scoring experiments on a fixed article set. Best for prompt-only scoring research where the evaluator scripts stay fixed and only the scoring rubric/prompt is meant to evolve.
[Internal suite skill · Users usually don’t need to invoke this directly in the full workflow; state your needs to the coordinator short-drama-director, which routes them here automatically] [漫剧老李 V7.5.0-SLIM suite · subskill] Specialist engine for scriptwriting and adapting novels. Runs a six-stage writing pipeline (source registration → IP and character development → full-series development bible → episode planning → final script → five-seat roundtable review + refinement/rewriting with authorization), adapting novels, web fiction, outlines, or existing scripts into professional short-form or animated-drama scripts with traceable sources, complete episodes, and performable dialogue. **Also includes an “external script polishing layer”: external standard scripts (only “Character: Dialogue,” with no expression/action/state fields) → add performance and blocking layers → adapt to this package’s storyboard rules; polishing only adds, never changes (no changes to dialogue/events/characters), and the output must be returned for user confirmation.** Includes anti-flattery principles, creative notes, five-perspective reviews, a warning for excessively high consensus in consultations, seven-dimensional dialogue diagnosis (**checkup**) + **dialogue humanization engine (★ added 2026-10-13 · generation side: forms-of-address system + written-to-spoken comparison + four particle-sprinkling methods + mechanization symptom checklist + Stage ⑤ checkpoint)**, and a platform pacing matrix. Triggers: write a script, adapt a novel, novel to script, script adaptation, episodes, episode planning, development bible, story bible, IP development, script review, roundtable review, script refinement, dialogue diagnosis, edit dialogue, pacing diagnosis, external script polishing, adapt an external script, add expressions to a script, adapt a script to storyboards, make dialogue conversational, humanize dialogue, dialogue is too mechanical, dialogue isn’t conversational enough, unnatural forms of address, forms-of-address system. This skill is part of the suite; enter the complete workflow through coordinator short-drama-director. **The coordinator locks the source choice at 〇·1 (1 original / 2 adaptation / 3 hit-reference benchmarking / 4 rapid hot-topic development); ③④ must first go through sd-recon-engine to produce an “benchmark intelligence card” and receive user confirmation. This engine preserves the source and its tier (T1/T1.5/T2) in “① Source Registration.”**
Apply Semantic Versioning 2.0.0 (semver.org) to decide version bumps, validate version strings, and compare version precedence. Use whenever a task involves choosing the next version number, judging whether a change is a MAJOR/MINOR/PATCH bump, checking that a string is a well-formed version, ordering versions by precedence, or building a pre-release or build-metadata version. Often used as a building block by release, changelog, and publishing workflows — trigger whenever version numbers are being reasoned about, even if "semver" is never said.
When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," or "indexing issues." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema-markup. For AI search optimization, see ai-seo.
Write a publish-ready, search-optimized article for a target keyword: SERP-validated brief, full draft matched to search intent, on-page metadata (title tag, meta description, URL slug), and schema markup. Use when the user says 'write a blog post about X', 'write an article that ranks', 'create SEO content', 'I need content for this keyword', or hands over a keyword/content brief from an SEO plan — even if they never say 'SEO'. Also use to rewrite or upgrade an existing article that isn't ranking. Produces the complete article plus a metadata block and an on-page checklist result.
Break a tRPC backend into multiple services with custom routing links that split on the first path segment (op.path.split('.')) to route to different backend service URLs. Define a faux gateway router that merges service routers for the AppRouter type without running them in the same process. Share procedure and router definitions via a server-lib package with a single initTRPC instance. Each service runs its own standalone/Express/Fastify server.
Save session wrap-up documentation before clearing context by running the session-documenter workflow and writing `.agents/sessions/YYYY-MM-DD.md`. Use when ending a session, preparing to run `/clear`, or asked to document what changed before context is reset.
Connect an arbitrary REST API to the PostHog data warehouse as a Custom source by authoring a JSON manifest, with no per-source code. Use when the user points at an API that has no built-in PostHog connector — "import data from this REST API", "sync my internal API", "connect this API from its docs", "build a custom data warehouse source" — and gives a docs URL or a natural-language description of the endpoints. Walks through drafting the RESTAPIConfig manifest (auth — bearer, API key, HTTP basic, or OAuth2 client credentials / refresh token — pagination, record path, incremental cursor, parent/child fan-out), validating it, test-reading live rows to verify the field mappings, and creating the source. If the API already has a native PostHog connector, use setting-up-a-data-warehouse-source instead — this skill checks the connector registry first and only handles APIs with no native connector.
Set up, install, and configure CONFIDE local de-identification — installs Python deps (natasha, scrubadub, phonenumbers, pymorphy2), ensures Ollama + pulls the default qwen2.5:3b model, detects optional llama.cpp, and writes the optimal-default config so confide:anon and confide:red work with zero further config. Everything is local-first; raw text never leaves the machine. Use when the user says "set up confide", "install confide", "configure confide de-id", "confide setup", or "get confide ready".
Wire a Bolna voice agent to answer inbound calls on a specific phone number. Covers the `POST /inbound/setup` mapping, IVR menus and digit-collect steps (Plivo-only), caller identification via `ingest_source_config` (Internal API / CSV / Google Sheet), inbound spam controls (`inbound_limit`, `whitelist_phone_numbers`, `disallow_unknown_numbers`), and auto-switch multilingual system messages (hangup, user-online check, tool wait). Use when building a support line, front-desk agent, IVR router, or multi-agent department setup.
Publish a user-approved file or folder as a live website or shareable URL with sharenow. Also use when the user explicitly asks to keep or retrieve files in their private sharenow Drive, collaborate through a Channel, deploy an approved lightweight Fullstack app, or map a public GitHub repository in Codegraph. Trigger on requests such as "publish this", "put this online", "share this as a website", "give me a URL", or "save this to my sharenow Drive". Do not publish a repository, home directory, or current working directory unless the user explicitly identifies that exact target.
Shopify theme, Liquid, Hydrogen and app development reference, with live API lookups handed to Shopify's own tooling. Use when editing .liquid files, building OS 2.0 sections, blocks or JSON templates, wiring theme cart behaviour with the Ajax API, speeding up a slow Shopify storefront, debugging Liquid or theme editor errors, building or upgrading a Hydrogen storefront, scaffolding a Shopify app or extension, writing Shopify Functions, or picking a Shopify API version. Do NOT use for WooCommerce, Magento, BigCommerce or other platforms - answer from general knowledge; Do NOT use for exact GraphQL field or schema lookups - use the shopify-ai-toolkit plugin or @shopify/dev-mcp
Simulation and Parameter Estimation in Geophysics. Framework for geophysical forward modeling and inversion. Use when the agent needs to: (1) Run geophysical inversions (DC resistivity, magnetics, gravity, EM), (2) Create forward models for potential fields or electromagnetic methods, (3) Build survey geometries and receiver configurations, (4) Design mesh discretizations for simulations, (5) Apply regularization and optimization to inverse problems, (6) Model subsurface physical properties from geophysical data.
A complete guide to creating or updating skill packages. Useful when users want to distill methods, experience, and preferences from a conversation into reusable skills, or to structurally optimize existing skills (including scripts, workflows, resource organization, and packaging for release).
Audit the skill inventory for quality, coverage, and staleness. Detect overlapping, incomplete, or outdated skills and produce a health report. Activate when: skill audit, stocktake, skill inventory, check skills, which skills exist, audit skills, skill quality, skill coverage.
Create, update, and maintain skills in the canonical .skills/internal/ directory. Includes step-by-step directives for agents to work with users, validate skill structure, and sync changes across agent directories. Use when users want to create new skills, update existing ones, or need guidance on skill authoring.
Convert PDF presentations to HTML slide templates using a visual reproduction approach. Pipeline: PDF → slide screenshots → Claude writes HTML matching each screenshot. Use when the user wants to convert a PDF to HTML slide templates, reproduce a presentation as HTML, or create reusable templates from existing decks. Triggers: 'pdf to html', 'convert pdf to template', 'reproduce this deck as html', 'create template from pdf'.
Write algorithm-optimized captions/descriptions for social media posts and reels. Supports Instagram (Reels, Feed, Carousel), TikTok, Threads, Facebook, and YouTube Shorts. The user sends material (text, image, script, competitor post, screenshot) and gets ready-to-use captions for ALL platforms at once, in English. Use when asked to "write a caption", "write a description", "caption for instagram", "описание к посту", "подпись для рилса", "описание для тикток", "caption for reels", "social media post", or any caption/description writing task. Also triggers when user sends an image, screenshot, or text and says something like "сделай описание", "напиши подпись", "caption this", "описание для этого".
Best practices for integrating social media APIs (Instagram, TikTok, YouTube, Twitter/X, LinkedIn, Facebook, Threads, Pinterest, Bluesky, Snapchat, Google Business, Reddit, Telegram). Covers OAuth, AT Protocol, rate limiting, media uploads, encryption, and error handling. Use when building social media integrations, scheduling systems, or debugging platform API issues.
Social Media Matrix Tracker dashboard template. Use when users ask for a cinematic, data-dense social media analytics dashboard with multi-platform metrics, interactive charts, hover insights, range compare, and dark/light theme switching in a single HTML artifact.
Use when the user is deciding, reviewing, or second-guessing a software architecture or tech-stack choice — monolith vs microservices vs serverless vs event-driven, backend language, database type, caching, CQRS/event sourcing, polyglot, or a migration like Strangler Fig. Triggers on "should I use microservices", "which database", "tech stack for", "system design", or "architecture review". For how to deploy, operate, and scale that design (CI/CD, cloud, Kubernetes, IaC), use devops.
Use when creating, developing, building, publishing, migrating, or reasoning about SpacetimeDB database modules. Covers local development, module build/publish flow, transactions, automatic migrations, incremental migrations, and the database cheat sheet. Triggers on: database module, spacetime publish, build module, migration, transaction, atomicity, developing module.
Use when writing SpacetimeDB reducers, lifecycle reducers, scheduled reducers, reducer context code, table mutations, indexed lookups, reducer isolation logic, or reducer error handling. Triggers on: reducer, ReducerContext, ctx, sender, client_connected, client_disconnected, init, scheduled reducer, insert row, delete row, update row.
Rebuild a package's unit test suite around a behavior specification (SPEC.md) derived from the implementation, with every test citing a numbered rule ID. Use when asked to do a spec-driven test rebuild, write a SPEC.md for a package, repeat the state or store spec process (PRs #9158, #9172) for another package, or rebuild tests around a spec.
Reverse-engineer a functional specification (spec) from existing source code. Use when you need to write requirements documentation for legacy code, freeze existing behavior before a refactor or migration, or take over an undocumented codebase. The resulting spec structure follows GitHub Spec Kit conventions.
Split an implementation-ready spec into the fewest independently deliverable vertical tasks and select only risk-justified intermediate review checkpoints. Use when a spec has multiple outcomes needing separate delivery or dependency tracking; keep one coherent outcome as the spec itself.
Guided statistical analysis with test selection and reporting. Use when you need help choosing appropriate tests for your data, assumption checking, power analysis, and APA-formatted results. Best for academic research reporting, test selection guidance. For implementing specific models programmatically use statsmodels.
Task management CLI tool for command-line management of Super Productivity data. Supports task management, counter management, project management, viewing today's status and more. Triggered when the user mentions super-productivity, sp task management, or command-line task management.
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.