Skills
98,639 packaged capabilities and playbooks for agents. Install any of them with one command.
Development
Corrects the wrong defaults a model has when designing a relational schema — the DDL decisions an experienced engineer makes differently. Use when creating or reviewing tables, migrations, ER models, or ORM schema definitions. Covers identity and keys (surrogate vs natural, identity vs serial, uuidv7, composite keys that make cross-tenant references impossible), relationships (polymorphic foreign keys the database cannot enforce, referential actions, unindexed FK columns, disjoint subtypes), invariants the engine can prove instead of application code (EXCLUDE, partial unique indexes, CHECK limits, deferrable cycles, NOT VALID), types (timestamptz, exact money, range types, enum vs lookup table), derived and encoded data (generated columns, JSONB as an escape hatch), and time (events vs in-place updates, soft-delete flags that silently disable constraints, temporal keys). NOT for query tuning, index selection for read paths, or connection pooling.
Evaluate a public GitHub repository's momentum and maintenance health. Use when asked whether a repository is healthy, growing, declining, abandoned, or well maintained, or when vetting dependencies and OSS projects. Do NOT use for code or architecture review.
Use when developing, editing, or testing a Roblox (Luau) game — the disk + Rojo + selene + Studio-MCP dev loop, the sync cycle, how to test with execute_luau/screenshots, and the engine gotchas that waste hours (200-local ceiling, stale-code syncs, duplicate-instance drift). Load at the start of any Roblox coding/testing task.
Use when adding, changing, testing, or reviewing Postgres persistence in Rust services that use sqlx, especially when designing migrations, query! or query_as! calls, PgPool injection, transactions, compile-time checked SQL, SQLx offline mode, repository boundaries, or database-backed integration tests.
Sa-Token advanced security features skill. Covers secondary authentication (safe-auth second verification), account bans (full ban / categorized ban / graduated ban), impersonating others and identity switching, multi-account authentication (StpUserUtil/StpKit), global listeners (login/logout/kick-out/ban/renewal events), global filters (SaServletFilter/SaReactorFilter), password encryption (MD5/SHA1/SHA256/AES/RSA/BCrypt/TOTP), session queries (terminal list / global Token search), Http Basic/Digest authentication, firewall (IP allow/deny lists / rate limiting), custom authorization annotations, dynamic route authorization, reverse-proxy URI repair, async Mock context, and data architecture Redis key-value design. Use when the user needs to implement second verification for sensitive operations, graduated account bans, simulated user operations, multiple account systems (separate User/Admin), global event listeners, or password encryption tools. For basic login authentication, use the sa-token skill.
Sa-Token API security defense skill. Covers API parameter signing (sa-token-sign) for tamper and replay protection (the four-step evolution of timestamp+nonce+sign), API Key (sa-token-apikey) partial authorization and Scope control (revocable / rights-restrictable), and temporary Token (SaTempUtil, embedded in the core package) for short-lived link invitations. API signing supports multi-application (multi secret-key) mode and multiple digest algorithms (md5/sha256/sha512). API Key supports multi-account systems and a database persistence mode. Temporary Token supports prefix trimming, reverse lookup, and JWT integration. For basic login authentication, use the sa-token skill first.
Specialized skill for Sa-Token SSO single sign-on. Covers complete solutions for three SSO modes: mode one (same domain + shared Redis/Cookie), mode two (cross-domain + shared Redis/URL redirect), mode three (cross-domain + separate Redis/Http ticket). Setting up the SSO-Server authentication center, SSO-Client integration, single sign-out, custom login pages, frontend-backend separated SSO (H5 approach), message push, anonymous clients, domain validation, NoSdk non-Java integration, custom API routes, platform center redirects. Use when the user needs unified login/logout across multiple systems, to set up a single sign-on authentication center, or cross-domain SSO integration. For basic login authentication, use the sa-token skill first.
Search and read the decompiled C# code of the Space Engineers 1 Dedicated Server to learn how the server works inside and to get exact signatures, method bodies, IL and content files. If the se-dev-server-book handbook is installed, read it first for how a system works overall and come here for the exact code.
Seata distributed transaction skill. Covers the decision tree for choosing among the four modes AT/TCC/SAGA/XA, the mandatory undo_log table in AT mode, useTCCFence in TCC mode to solve idempotency/hanging/empty rollback, SAGA state machine for long processes, global transaction timeout configuration (@GlobalTransactional timeoutMills), and read isolation enhancement (@GlobalLock + FOR UPDATE). Corrects LLM mistakes: not knowing which of AT/TCC/SAGA to choose, not creating the undo_log table, non-idempotent TCC Confirm, and not handling the watch dog.
Use when user wants to develop on the SecondMe platform (second-me.cn, develop.second-me.cn). Triggers: building SecondMe third-party apps, SecondMe OAuth login integration (Client ID/Secret, token exchange), MCP integration for SecondMe, Agent Memory API, Act stream API, app scaffolding, review submission, or hackathon projects targeting SecondMe. Covers the full developer lifecycle from app creation and credentials to release. NOT for casual SecondMe usage like browsing profiles, adding friends, or social features — only for building and integrating with SecondMe as a developer platform.
Settle a session by saving its work, recording what remains, and freeing proven-merged, unoccupied worktrees while leaving the caller and terminal layout open. Use when the user says "settle" or "end the session" about this session, or when another skill says to settle. When the user says to settle an effort, use /settle-effort instead.
Installs prerequisite CLI tools (gh, glab, jq), guides GitHub/GitLab authentication, installs uvx, and configures the existing mcp-atlassian MCP server for Jira in OpenCode. Idempotent: safe to rerun the skill. Triggered when the user says “setup,” “install prerequisites,” or “configurer jira.” To build a new MCP server (rather than configure an existing one), use mcp-builder instead.
Set up Ralph RLM in an existing OpenCode project by installing the package, running the opencode-ralph-rlm setup command, checking generated .opencode config, and verifying the provider/worker loop wiring. Use when a user asks to install, configure, initialize, troubleshoot setup for, or add opencode-ralph-rlm / Ralph RLM to a repository.
credit_transactions audit trail invariants and daily reconciliation patterns. PROACTIVELY activate for: (1) Designing a credit / balance / entitlement ledger, (2) credit_transactions row shape (delta, balanceAfter, reason, referenceType, referenceId, idempotencyKey), (3) Canonical idempotency key formats (refund:/debit:/stripe_checkout:/stripe_invoice:/stripe_refund:/stripe_signup_bonus:/dispute_hold:/dispute_restore:), (4) Daily reconciliation cron design (snapshot comparison, not full-sum), (5) Alert-only policy (never auto-correct drift), (6) Canonical refund helper pattern (single source of truth across pg-raw and Drizzle call sites), (7) Past_due block + credit balance shared preflight, (8) creditsDeducted boolean return pattern for pre- vs post-deduction error differentiation, (9) Money-safe email description based on resolvedVia flag, (10) Skip-users-without-baseline-snapshot reconciliation logic. Provides: table schema, canonical helper skeleton, reconciliation SQL, email gating pattern.
Structural validation and damage systems for Three.js building games. Use when implementing building stability (Fortnite/Rust/Valheim style), damage propagation, cascading collapse, or realistic physics simulation. Supports arcade, heuristic, and realistic physics modes.
Implement, harden, or review defensive security controls for REST APIs, including authentication and authorization boundaries, validation, rate limiting, abuse prevention, resource limits, SSRF defenses, safe errors, logging, and security tests. Use when API security, endpoint hardening, threat review, rate limiting, token handling, or sensitive business-flow protection is an explicit concern. Do not use for ordinary endpoint logic without meaningful security scope or for offensive exploitation
Diagnose and repair reproducible, intermittent, environment-specific, or production-observed software failures by tracing evidence to a root cause. Use when a symptom exists but its cause is uncertain or when a proposed fix needs causal validation. Do not use for feature implementation, speculative cleanup, or a general review without a concrete failure.
Svelte 5 special elements skill. Use when the user needs svelte:boundary, svelte:window, svelte:head, svelte:element, svelte:options and other special elements, or when configuring compiler options, custom elements, catching render errors or async pending states.
SvelteKit configuration/build/deployment/performance skill. Use when the user configures adapters (node/static/cloudflare/netlify/vercel), uses advanced routing/layouts, optimizes performance (code splitting/asset/hydration), handles images (@sveltejs/enhanced-img), implements accessibility/SEO, debugs a SvelteKit app, or migrates from SvelteKit v1/Sapper.
SvelteKit data loading, forms, and page options skill. Use when the user loads data with +page.js/+page.server.js, uses +server.js API routes, handles form actions (default/named/GET), uses use:enhance for progressive enhancement, or configures prerender/ssr/csr/trailingSlash page options in SvelteKit.
Comprehensive guide for implementing Syncfusion EJ2 JavaScript input components including CheckBox, ColorPicker, MaskedTextBox, NumericTextBox, OTP Input, RangeSlider, Rating, Signature, TextArea, TextBox, and Uploader. Use this when adding checkboxes, color selection, masked formatting, numeric inputs, OTP entry, range sliders, star ratings, signature capture, text inputs, or file upload to TypeScript/JavaScript applications.
Expert SystemVerilog guidance for RTL, interfaces, and verification-adjacent code with EDA-friendly design patterns. Use when designing, reviewing, or refactoring hardware-oriented SystemVerilog and when spotting HDL antipatterns that cause timing, lint, CDC, or tool-flow pain.
Set up and use Tailwind CSS v4 only with Next.js (App Router), Vite, or CLI; no tailwind.config.js—theme via @theme in CSS. Use when styling with Tailwind, configuring Tailwind, installing Tailwind, utility classes, @theme, @layer, @utility, or when the user mentions Tailwind CSS or Tailwind v4.
Provider-agnostic AI guidance for chat, tools, structured output, persistence, memory, runtime skills, MCP, code mode, and sandbox execution. Use when a project uses TanStack AI or when the task needs its setup, implementation, debugging, testing, migration, or integration guidance.
Syntax-highlighting guidance for language support, selective loading, Markdown pipelines, themes, and annotations. Use when a project uses TanStack Highlight or when the task needs its setup, implementation, debugging, testing, migration, or integration guidance.
Markdown parsing, extensions, rendering, production pipeline, and framework-adapter guidance. Use when a project uses TanStack Markdown or when the task needs its setup, implementation, debugging, testing, migration, or integration guidance.
Full-stack application guidance for TanStack Start, including server functions, middleware, deployment, and framework adapters. Use when a project uses TanStack Start or when the task needs its setup, implementation, debugging, testing, migration, or integration guidance.
Create, modify, and maintain Taskfiles following Task (https://taskfile.dev) best practices. Use when: (1) Creating new tasks or Taskfiles, (2) Modifying existing task definitions, (3) Adding new task includes, (4) Debugging task execution issues, (5) Questions about Taskfile syntax or patterns, (6) Running or understanding "task" commands, (7) Questions about available tasks or task namespaces. Triggers: "taskfile", "Taskfile.yaml", "task command", "task:", "create task", "add task", "task --list", "task tg:", "task inv:", "task wt:", ".taskfiles/", "how to run", "available tasks", "task syntax", "taskfile.dev" This skill covers the repository's specific conventions in .taskfiles/ and the root Taskfile.yaml.
Create structured project tickets from user intent. Use when the user wants to create a ticket, formalize a feature request, document a bug or task, or turn a conversation into a structured ticket. Handles project prefix detection, ticket numbering, and context gathering automatically.
PyTorch-native graph neural networks for molecules and proteins. Use when building custom GNN architectures for drug discovery, protein modeling, or knowledge graph reasoning. Best for custom model development, protein property prediction, retrosynthesis. For pre-trained models and diverse featurizers use deepchem; for benchmark datasets use pytdc.
This skill should be used when working with pre-trained transformer models for natural language processing, computer vision, audio, or multimodal tasks. Use for text generation, classification, question answering, translation, summarization, image classification, object detection, speech recognition, and fine-tuning models on custom datasets.
Use this skill to triage the open PR queue before a release. Classifies every open PR into must-merge, candidate, superseded, or deferred; writes a working triage doc; and runs the merge loop end-to-end. Designed for the pre-release "PR speedrun" pass where a solo maintainer wants to clear the inbound backlog in a single session.
"How to build, sign, submit, and simulate transactions in @aptos-labs/ts-sdk. Covers build.simple(), signAndSubmitTransaction(), waitForTransaction(), simulate, sponsored (fee payer), and multi-agent. Triggers on: 'build.simple', 'signAndSubmitTransaction', 'transaction.build', 'waitForTransaction', 'signAsFeePayer', 'SDK transaction', 'sponsored transaction', 'multi-agent transaction'."
"How to integrate wallet connection in React frontends using @aptos-labs/wallet-adapter-react. Covers AptosWalletAdapterProvider setup, useWallet() hook, frontend transaction submission, and wallet connection UI. Triggers on: 'wallet adapter', 'connect wallet', 'useWallet', 'AptosWalletAdapterProvider', 'wallet-adapter-react', 'wallet connection'."
One ubiquitous language per bounded context, with a repository-declared glossary as the naming authority and explicit decisions for language changes. Covers the five-step language protocol (detect, propose, decide, record, rename), optional glossary-driven lint ratchets, and safe context-wide renames. Use when naming domain concepts, when a term is missing from or fights the glossary, when spotting synonyms or near-duplicates, when bootstrapping a glossary, or when renaming across a bounded context. For DDD building blocks see domain-driven-design; for acceptance-DSL vocabulary use the project's relevant installed skill.
Unity 6 ECS/DOTS development guide. Use when working with Entity Component System, data-oriented design, Jobs system, or Burst Compiler. Covers Entities, IComponentData, ISystem, EntityManager, baking, Jobs, and Burst. Based on Unity 6.3 LTS documentation.
Unity 6 UI development guide. Use when building user interfaces, menus, HUD, buttons, or any UI elements. Covers UI Toolkit (recommended for new projects — USS, UXML, UI Builder, data binding), uGUI/Canvas (legacy runtime UI), and IMGUI. Based on Unity 6.3 LTS documentation.
Operate Vite projects: inspect versions and configuration, run bounded development and production builds, diagnose dependency and asset failures, and configure environment-aware frontend delivery. Use when a task names Vite, vite.config, Vite plugins, import.meta.env, dev-server behavior, or Vite build output. Do not use for frontend architecture or visual implementation (route to frontend-engineering), CI/platform provisioning (route to platform-engineering), browser automation (route to playwright), or accessibility design (route to web-accessibility).
Design and integrate web interfaces via three paths: DirectDesign (write design inline with Anthropic frontend-design philosophy — the default workhorse), native /design + /design-sync Claude Code commands (preferred for code integration and design-system sync), or ClaudeDesign (drive claude.ai/design through Interceptor — experimental visual-review fallback). USE WHEN web design, UI design, create prototype, design system, design sync, redesign site, mockup, landing page, dashboard design, design-to-code, frontend design, polish UI, design audit, brutalist/editorial/retro UI. NOT FOR illustrations/logos (use Art) or video (use Remotion).
High-velocity solo development workflow. Idea to production same-day. 10 commands: plan, spike, ship, fix, review, spec-review, focus, done, drop, workflow. Auto-activates on: “plan,” “spec,” “ship,” “spike,” “fix,” “debug,” “repair,” “spec-review,” “review spec,” “analyze spec,” “challenge spec,” “focus,” “what should i do,” “prioritize,” “overwhelmed,” “what should i work on,” “done,” “finish,” “complete,” “drop,” “abandon,” “workflow,” “what's next,” “whats next,” “next step,” “what now.”
WordPress migration and upgrade review. Use when reviewing database migrations, option versioning, upgrade routines, data backfills, dbDelta usage, release compatibility, rollback risk, or when user mentions "migration review", "upgrade routine", "dbDelta", "plugin upgrade", "data migration", "version bump", "backfill", "schema change", or "backwards compatibility". Detects unsafe migrations, missing version guards, destructive data changes, and upgrade-flow risks in WordPress code.
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.