Skills
99,448 packaged capabilities and playbooks for agents. Install any of them with one command.
All
Troubleshoot Electric sync issues. Covers fast-loop detection from CDN/proxy cache key misconfiguration, stale cache diagnosis (StaleCacheError), MissingHeadersError from CORS misconfiguration, 409 shape expired handling, SSE proxy buffering (nginx proxy_buffering off, Caddy flush_interval -1), HTTP/1.1 6-connection limit in local dev (Caddy HTTP/2 proxy), WAL growth from replication slots (max_slot_wal_keep_size), Vercel CDN cache issues, and onError/backoff behavior. Load when shapes are not receiving updates, sync is slow, or errors appear in the console.
Build, scaffold, debug, and ship desktop applications with Electrobun — an ultra-fast TypeScript desktop app framework using Bun as the runtime and native OS webviews. This skill provides comprehensive guidance for building cross-platform desktop applications with TypeScript, covering project scaffolding, window management, main↔webview RPC communication, native UI integration, auto-updates, and distribution. Use this skill when the user mentions Electrobun, wants to build a desktop app with TypeScript or Bun, asks about BrowserWindow, BrowserView, RPC between main and webview processes, app bundling, cross-platform desktop development, or needs help with menus, tray icons, updater setup, or packaging for distribution. Also trigger when they say "desktop app" and are using or considering Bun. Common triggers include: "create Electrobun app", "desktop application TypeScript", "Bun desktop app", "BrowserWindow", "webview RPC", "Electrobun tutorial", "desktop app updater", "cross-platform desktop", "macOS app with Bun", "Windows desktop app TypeScript", or any discussion about building native desktop applications with web technologies and Bun runtime.
Build, review, debug, test, migrate, secure, or deploy Elysia and ElysiaJS applications with current documentation. Use for Bun or Node Elysia servers, routes, schemas and validation, lifecycle hooks, plugins and scope, guards, macros, context extension, error handling, Eden Treaty, OpenAPI, WebSocket, SSE, runtime adapters, security advisories, production readiness, and Elysia 1.4 to Elysia 2 beta (elysia@next, @elysia/codemod) migration. Reject route factories that pass db, Effect runtime, or other app singletons as arguments or via decorate; import those modules directly. Endpoint tests must use @elysia/eden treaty(app) — ban app.handle(new Request(...)) helpers.
Use when the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," or "lifecycle emails." For in-app onboarding, see onboarding-cro.
Use when the user needs to write, review, or migrate SQL queries in ADVPL/TLPP using BeginSQL/EndSQL blocks and macro expressions (%table%, %xfilial%, %notDel%, %exp%, %Order%) instead of raw TCQuery string concatenation -- covering INNER/LEFT JOIN patterns, aggregations (SUM/COUNT/GROUP BY/HAVING), subqueries, column type declarations, DML via TCSqlExec, and SQL-injection prevention. Also triggers on Portuguese phrasing like "consulta SQL", "query embutida", "migrar TCQuery para BeginSQL", "escrever SELECT com filial e notDel", or "montar JOIN em ADVPL".
Writing, reviewing, refactoring, or running end-to-end tests, or verifying a change through the e2e suite — whole-system checks that drive a running build the way a real user or client does. Triggers on snapshots, test IDs, selectors or locators, polling and waiting, flaky tests, scenario coverage, a runner (Playwright, Cypress, Maestro, Detox, WebdriverIO, Vitest), or a failing e2e run. For a test that mocks its dependencies to isolate one unit, use a unit-testing capability; for the runner's own config and reporters, that runner's own. Covers the test-id then role then copy locator hierarchy, poll-not-sleep waiting, and server lifecycle.
Proofread and improve English text written by the user before answering their actual question. Use this skill whenever the user's message contains English sentences or paragraphs — even mixed with Korean — and a substantive answer is expected. Trigger on any message where English prose is present: questions, requests, opinions, descriptions, or explanations written (fully or partly) in English. Do NOT skip proofreading just because the English looks mostly correct; always run the correction block first. Skip only for: single English words, proper nouns, code snippets, or messages written entirely in Korean with no English prose.
Chinese enterprise registration info lookup — queries the 接口盒子 API for company registration details (工商信息) by company name or Unified Social Credit Code (统一社会信用代码). Triggered whenever the user asks about a Chinese company: "查公司", "查企业", "企业信息", "工商信息", "查一下XX公司", "查XX的统一信用代码", "这家公司信息", "营业执照查询", "企业工商查询", "查一下这家公司", "看看这家企业", "this company info", or pastes a company name or credit code and asks to look it up. Supports both full company name and 18-digit Unified Social Credit Code.
Generate the `СведенияОВнешнейОбработке` function in the object module of a processing — the description for connecting via the БСП «Additional reports and processings» subsystem. Use when you need to make a processing compatible with БСП and connectable via «Additional reports and processings»
Add Sentry v8 error tracking and performance monitoring to your services. Use this skill when adding error handling, creating new controllers, instrumenting cron jobs, or tracking database performance. ALL ERRORS MUST BE CAPTURED TO SENTRY - no exceptions.
Cria e mantém o TRD (Technical Requirements Document) em `docs/trd.md` — stack, arquitetura, requisitos não-funcionais, dependências externas, padrões e decisões globais do projeto. Também cria ADRs (Architecture Decision Records) no Modo Decision: registra uma decisão técnica em `docs/adrs/` e atualiza a seção Decisões Globais. O TRD é o contexto técnico consultado pelas skills do fluxo sdd (`sdd-especificar` em diante). Use ao criar um TRD, documentar a stack, registrar padrões de arquitetura, começar projeto novo sem TRD, quando a stack mudou, ou quando o `sdd-especificar` pedir contexto técnico por falta de `docs/trd.md` — mesmo sem usar o termo "TRD". Use o Modo Decision quando o usuário quiser "registrar uma decisão", "criar um ADR", ou disser "decidimos usar/trocar X por Y" — é decisão técnica/arquitetural, distinta de decisão de produto (que fica no PRD).
Improve AI application with evaluation-driven development. Define eval criteria, instrument the application, build golden datasets, observe and evaluate application runs, analyze results, and produce a concrete action plan for improvements. ALWAYS USE THIS SKILL when the user asks to set up QA, add tests, add evals, evaluate, benchmark, fix wrong behaviors, improve quality, or do quality assurance for any Python project that calls an LLM model.
GitHub security research methodology: search GitHub for evasion/Loader/C2 technique repositories, analyze code patterns, extract new techniques into the knowledge base. Use when the knowledge base lacks evasion techniques for the current detection environment - first search high-star GitHub repositories, analyze the code, then write to evasion-techniques-db.json or loader-components-db.json.
This skill should be used when the user asks to "execute this blueprint", "run the plan", "execute the plan", "start building from the plan", "implement the blueprint", "implement the plan", "continue the plan", "resume execution", "execute 01_milestone_name.md", "execute step 3", "run steps 3-5", or "skip to step 4".
Transform detailed product updates into concise executive briefings. Use when asked to write an executive update, leadership update, product update for the exec team, or a C-suite product briefing. Produces a structured 250-word briefing with headline, key metrics, progress, risks, decisions needed, and next steps.
Analyze an existing website before improve, redesign, rebuild, or migration decisions. Use when a project has a current URL, local HTML/codebase, screenshots, sitemap, robots, analytics export, asset folder, or legacy site materials and needs a local-first audit with approval-gated crawling or authenticated access.
Develop working exploits from memory-corruption bugs in native binaries — turning a stack/heap overflow, use-after-free, or type confusion into control flow, an arbitrary read/write, and a shell, and defeating ASLR, NX, stack canaries, PIE, and RELRO along the way. Use when you have a crashing input or a known bug class in an ELF/PE and need a primitive, when building a ROP chain with pwntools and ROPgadget, or when working a CTF pwn challenge or authorized binary exploitation.
Feishu cloud document content optimization and formatting. Use this skill when the user needs to optimize the layout, structure, formatting, or visual appeal of Feishu documents. Supports: (1) reading Feishu document content (2) optimizing document structure and hierarchy (3) clearing and replacing document content (4) editing documents via browser automation. Trigger words: optimize Feishu document, beautify document, organize document format, document layout.
Traditional Feng Shui and Kanyu advisor. Skilled in San Yuan Xuan Kong flying stars, Eight Mansions (Ba Zhai), and landform analysis, with additional training in date selection and BaZi destiny analysis. Trigger words: feng shui, kanyu, house viewing, residence viewing, date selection, eight mansions, flying stars, auspicious positions, sha qi, remedies, orientation, placement, layout, life gua, yearly fortune, landscape, dragon lair and sand-water. Applies to: analysis of yang dwellings and yin dwellings, home and office layout, date and time selection, feng shui combined with BaZi, and Q&A on feng shui theory.
Draw an animated figure—boxes, arrows, and moving data—as a self-contained SVG for a GitHub README, PR, issue, or blog post. Use when a change or explanation needs a diagram, such as showing request flow, what a background job does, or what a feature changed; also use when the user asks for a diagram, figure, animation, or to “show it visually.” For pages on the docs site itself, use the interactive player instead (see step 4).
Orchestrate the full FinalRun loop — use finalrun-generate-test to explore a feature and author tests, run them via finalrun-use-cli, then triage failures from CLI artifacts and fix app code or tests until the run is green. Trigger for requests like "debug this failing FinalRun test", "verify and fix the feature with FinalRun", or as the Definition-of-Done loop after a UI change.
When the user wants to review their business finances, understand their P&L, check cash position, plan spending, review unit economics, or says things like 'financial review,' 'look at my numbers,' 'P&L review,' 'cash flow,' 'can I afford to hire,' 'pricing review,' 'unit economics,' 'how's my business doing financially.' Works with whatever level of financial detail they have.
When the user is making capital allocation decisions: buybacks, dividends, acquisitions, reinvestment. The key judgment is "is this action smart or foolish at the current price". Language signals: "the company is going to buy back stock" / "should we pay dividends or reinvest" / "is this acquisition price reasonable" / "can retained earnings create value". Not applicable to: pure operating decisions that do not involve price.
Full FlagRelease pipeline orchestrator. Runs the complete LLM deployment, verification, and benchmarking pipeline for multi-chip GPU backends. Executes: install-stack → env-verify → model-verify → perf-test in sequence, passing state between steps and producing a final structured report. Assumes gpu-container-setup (Step 1) is already done — a running container with PyTorch + GPU access must exist.
Diagnose intermittent VS Code Electron smoke-test failures from the Azure DevOps Flaky Smoke Tests pipeline (definition 700). Covers finding failed iterations, downloading task logs and platform artifacts with Azure CLI, correlating cumulative runner logs, tracing the introducing commit, and queueing focused validation runs.
Generate images with FLUX models (Black Forest Labs) via inference.sh CLI. Models: FLUX Dev LoRA, FLUX.2 Klein LoRA with custom style adaptation. Capabilities: text-to-image, image-to-image, LoRA fine-tuning, custom styles. Triggers: flux, flux.2, flux dev, flux schnell, flux pro, black forest labs, flux image, flux ai, flux model, flux lora
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.