Skills
98,284 packaged capabilities and playbooks for agents. Install any of them with one command.
Development
Assists Capacitor developers migrating an iOS app or plugin from 8.4 to the 8.5 UIScene lifecycle, covering what `npx cap migrate` skips or only warns about: partially migrated projects, hand-rolled scene delegates, and custom application(_:open:) bodies that must move by hand. Audits first, reports findings, asks the developer at judgement points, merges surgically instead of overwriting, and hands off to `npx cap migrate` when the project matches the template shape. Branches for Capacitor plugin repos, auditing Swift for lifecycle assumptions without touching app-level files. Use when the user says “migrate my Capacitor app to UIScene”, “add SceneDelegate support”, “Capacitor 8.5 migration”, “update to Capacitor 8.5”, “adopt the scene lifecycle”, “Xcode 27 Capacitor build failing”, or mentions the “CLIENT OF UIKIT REQUIRES UPDATE” warning. Do not use for Cordova-to-Capacitor migration (use cordova-plugin-migrator), generating new plugins (use capacitor-plugin-generator), or Capacitor 9 migrations
Detects misplaced classes and fixes component hierarchy problems — finds code that should belong inside a component but sits at the root level. Use when asking "clean up component structure", "find orphaned classes", "fix module hierarchy", "flatten nested components", or analyzing why namespaces have misplaced code. Do NOT use for dependency analysis (use coupling-analysis) or domain grouping (use domain-identification-grouping).
Autonomously achieve a goal. Use when the endpoint, acceptance criteria, or budget is clear; when iterating until completion; or when starting work after “grill me.” Don’t use for planning and implementing a single feature (cs-feat), end-to-end breakdown of a large request (cs-epic), bug diagnosis and fixes (cs-issue), behavior-preserving refactors (cs-refactor), external documentation (cs-docs), or pure design, roadmaps, brainstorming, or audits without an implementation endpoint.
GitHub issue workflow ceremony using gh CLI — labels issues as in-progress, creates feature branches (issue/N-description), commits with issue references, posts progress comments, and links PRs with Closes #N. Keeps issues in sync with development work. Use when starting work on an issue, tracking progress, or completing work with a PR.
First-class incident-handling workflow — for bugs, runtime errors, incorrect behavior, "stuck approval," regressions, and production incidents. Orchestrates triage → repro-first gate (do not fix until reproduced) → scope narrowing (code-graph/impact-check/bisect) → fix via safe-change with red-to-green evidence → dual distillation (incident wiki + failure-flywheel + problem-tree). Do NOT use for new features (use propose/orca-workflow).
Instant release-notes viewer (like Claude CLI's /release-notes). Type /ovs-notes → immediately list the OVERSTACK framework changelog (newest first) to select and read; /ovs-notes <version|latest> prints it in full; /ovs-notes --here = release for the current PROJECT. READ-ONLY, no side effects — unlike /ship (release-cutting workflow). Triggers: /ovs-notes, “view release notes,” “which release notes version,” “changelog,” “released versions,” “what's in the latest version.”
Diagnose React runtime performance with React Doctor traces, live render outlines, Long Animation Frames, interaction timing, and component render evidence. Use when invoked as `/performance` for a slow interaction, unexpected re-renders, or a measured before-and-after comparison.
Generate leftover PlantUML types Mermaid cannot do easily (Salt wireframes, use case, timing, ArchiMate, nwdiag, WBS) and convert them to PNG/SVG. Use when asked for a wireframe, PlantUML image export, extract puml from markdown, or prepare Confluence uploads. Class, ER, state, sequence, and C4 default to design-doc-mermaid on GitHub wiki.
Raise an ISSUE with full context in the local ledger (draft) for another developer to pull and handle anywhere via /fdk without touching other branches/projects; automatically mirror it to a remote tracker if available (GitHub via gh / GitLab via glab / Gitea via tea) — the ledger is the source of truth. For feature gaps, tech debt, foundations, and architecture questions (unlike orca-issue, which handles incidents/bugs with repro-first). Includes a context template, owner assignment, and agent dispatch. Triggers: 'raise issue', 'tạo issue', 'ghi issue', 'mở issue', 'log gap này', 'issue để dev khác làm', '/raise-issue'.
Full code review for Keboola Python components — covers both code quality (architecture, config/client patterns, typing, Pythonic best practices) and backward compatibility (configSchema changes, sync actions, output tables, state files, telemetry impact). Use for PRs, pre-merge checks, and component audits. Invoke whenever someone asks to review code, check a PR, audit before release, or verify that changes are safe for existing users.
Workflow for finalizing PUSH/RELEASE/PR/MR — invoke when the user mentions 'release'/'push'/'ship'/'lên release'/'mở PR'/'tạo MR'. Run a pre-push checklist: (1) medic --ci (health gate: rule violations/drift/docs/code/eval), (2) UAT /fdk-uat via a real remote if the diff adds new capabilities (release/pr/mr only; medic --ci cannot prove the curl path), (3) clean git state (scratchpad/ephemeral untracked), (4) selftest, (5) version x.x.x+1 from the latest tag (release level only), (6) honest patch note/PR body (Added/Fixed/Removed/Known-limitations, no exaggeration). Supports 5 levels: 'ship push' = push only, no tag; 'ship release' = push + tag vX.Y.Z + release notes; 'ship pr' = push branch + gh pr create (GitHub); 'ship mr' = push branch + glab mr create (GitLab); 'ship merge' = list incoming repo PRs/MRs by remote, fetch branches, run gates and tests, merge only if GREEN. STOP for approval before side-effect steps. Triggers: /ship, 'release', 'push', 'ship', 'mở PR', 'tạo MR', 'ship pr', 'ship mr', 'ship merge', 'gom PR về merge', 'merge PR nếu test xanh', 'chuẩn bị push', 'lên release', 'checklist trước push', 'đủ điều kiện push chưa'.
Sui networks, gas costs, and epochs. Use when the user asks about Sui network environments (Mainnet, Testnet, Devnet, Localnet), gas cost calculations, gas budgets, epochs, or how the Sui network operates at a high level. For CLI client setup, address management, faucets, and explorers, see the `sui-client` skill. For installing the Sui CLI, see the `sui-install` skill.
Implements Syncfusion® .NET MAUI AI AssistView (SfAIAssistView) for AI-powered interactive chat interfaces. Use when working with AI chat interfaces, AI AssistView, SfAIAssistView, conversational UI, or chat with AI responses. Covers integrating AI services, creating chat UIs, implementing conversation flows, managing AI requests/responses, and displaying AI suggestions
Implements Syncfusion .NET MAUI Chips (SfChip or SfChipGroup). Use when working with chips, tags, tag controls, selection chips, input chips, or filter chips in .NET MAUI applications. Covers chip types, chip customization, chip events, chip selection, chip groups, removing chips, close button chips, and chip data binding.
Implements Syncfusion .NET MAUI Tab View (SfTabView) controls for tab navigation interfaces and tabbed content layouts. Use when working with tab controls, tab navigation, nested tabs, or swipeable content in .NET MAUI applications. This skill covers tab bar customization, tab item configuration, swipe gestures, events, and visual customization including indicators and Liquid Glass effects.
Use when a rebase is needed due to a change to the base branch or a conflict in a specific PR. Also accepts handoffs from active `tk-pr-sweep` or `tk-pr-respond` with the exact PR/base/head and approved rebase scope. Do not apply automatically to general branch work or review responses without verified rebase justification
Trust Wallet open-source libraries — Wallet Core (HD wallets, address derivation, tx signing in Swift/Kotlin/TypeScript/Go for 140+ chains), Web3 Provider (dApp connection for Ethereum/Solana/Cosmos/Bitcoin/Aptos/TON/Tron), deep linking, browser extension integration, WalletConnect, token assets repository, and Barz ERC-4337 smart wallet. Use when working with trustwallet/wallet-core, @trustwallet/wallet-core, trust-web3-provider, Trust Wallet deep links, token logos/metadata from trustwallet/assets, or Barz account abstraction.
Use when auditing an agent codebase against the 12-Factor Agents methodology, reviewing LLM-powered system architecture, or assessing agentic app compliance. Triggers on "analyze agent architecture", "12-factor audit", "how compliant is this agent", or "evaluate this LLM app". Also applies when comparing frameworks or planning agent improvements. Not for quick checklists — this performs deep per-factor codebase analysis with file-level evidence.
Use when UI is slow, scrolling lags, animations stutter, or when asking “why is my SwiftUI view slow”, “how do I optimize List performance”, “my app drops frames”, “view body is called too often”, “List is laggy” — SwiftUI performance optimization with Instruments 26 and WWDC 2025 patterns
CCXT cryptocurrency exchange library for Go developers. Covers both REST API (standard) and WebSocket API (real-time). Helps install CCXT, connect to exchanges, fetch market data, place orders, stream live tickers/orderbooks, handle authentication, and manage errors in Go projects. Use when working with crypto exchanges in Go applications, microservices, or trading systems
Build and debug cuEquivariance irreps, custom Irrep subclasses, Clebsch-Gordan tensor products, and equivariant or segmented polynomials. Use for cuequivariance core descriptors and IrDictPolynomial layout or shape questions; framework execution requires the matching JAX or PyTorch API.
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.
Builds ASP.NET Core APIs, EF Core data access, gRPC, SignalR, and backend services with middleware, security (OAuth, JWT, OWASP), resilience, messaging, OpenAPI, .NET Aspire, Semantic Kernel, HybridCache, YARP reverse proxy, output caching, Office documents (Excel, Word, PowerPoint), PDF, and architecture patterns. Spans 32 topic areas. Do not use for UI rendering patterns or CI/CD pipeline authoring.
Build, run and manage multi-step AI workflows that chain EachLabs models into one API call. Create a workflow from a JSON definition, trigger it, read its results and manage versions. Use when a task chains several models, reuses a fixed prompt, needs a fallback model, runs steps in parallel, routes on a condition, or calls an HTTP API between model steps
Enforces the project's core TypeScript standards, including explicit typing, import organization, class member ordering, and code safety rules. ALWAYS apply when creating, modifying, or reviewing any TypeScript (.ts/.tsx) file.
Expert blueprint for First-Person Shooters: fps_camera_look, fps_movement_logic, hitscan_weapon_query, weapon_bobbing_system, procedural recoil, and FPS NEVER rules. Shared TPS/cover theory links to godot-genre-shooter. Keywords: FPS, movement physics, weapon bobbing, camera sway, hitscan, viewmodel, air control.
Develop and optimize custom operators using AscendC programming language. Analyze operator performance bottlenecks and conduct optimization validation. Based on AscendC and CANN toolkit Use this skill when the user wants to: (1) optimize performance-critical operators on Ascend NPU, (2) develop custom operators for specific workloads, (3) improve model inference performance through operator optimization Trigger: user mentions "AscendC", "operator optimization", "custom operator", "performance", "NPU optimization", "Ascend operator", "算子优化", "自定义算子", "算子开发", "AscendC算子", "性能优化"
Implement real-time Hotwire behavior: Turbo Streams over WebSocket/SSE, custom stream actions, inline stream tags, live list updates, and cross-tab state synchronization. Prefer this skill when the core problem is push-based updates or stream action orchestration. Use hwc-navigation-content for pull-based pagination/tab/lazy-navigation flows, hwc-forms-validation for form lifecycle and validation, hwc-media-content for media upload/playback behavior, hwc-ux-feedback for generic loading/progress/transitions, and hwc-stimulus-fundamentals for non-stream Stimulus fundamentals.
Use for Luau performance work focused on profiling hotspots, allocation-aware code structure, table and iteration costs, builtin and function-call fast paths, compiler/runtime optimization behavior, and environment constraints that change execution speed.
Best practices for building charting applications using MMT real-time crypto market data with TradingView Lightweight Charts. Use when creating price charts, volume charts, indicator overlays, multi-chart dashboards, or any visualization that renders MMT data using the TradingView Lightweight Charts library.
Cross-platform Python library for quantum computing, quantum machine learning, and quantum chemistry. Enables building and training quantum circuits with automatic differentiation, seamless integration with PyTorch/JAX/TensorFlow, and device-independent execution across simulators and quantum hardware (IBM, Amazon Braket, Google, Rigetti, IonQ, etc.). Use when working with quantum circuits, variational quantum algorithms (VQE, QAOA), quantum neural networks, hybrid quantum-classical models, molecular simulations, quantum chemistry calculations, or any quantum computing tasks requiring gradient-based optimization, hardware-agnostic programming, or quantum machine learning workflows
Authoritative reference for Pi (@earendil-works/pi-coding-agent): installation, configuration, execution, and extension. Use for the CLI and configuration, providers and models, extensions, skills, MCP, codemode, the SDK/RPC, security and trust, design philosophy, and the pi repository's internals and contribution rules
Comprehensive Python development skill covering coding standards, CLI development, linting, testing, debugging, refactoring, code review, auditing, documentation, project planning, and bulk operations. Use when writing, reviewing, refactoring, debugging, or documenting Python code; configuring linters; setting up CLI tools; planning features; performing code audits; checking Python antipatterns, forbidden methods, or bad style; or handling bulk operations (10+ files) that benefit from batch workflows instead of per-file iteration
Use when working in a Quarkus project and the user wants to check if their build files are up-to-date, compare project structure against a reference, or upgrade their Quarkus version. Triggers on "check project", "update quarkus", "is my project up to date", "compare build", "quarkus upgrade".
Best practices for writing idiomatic Relay code. ALWAYS use this skill when writing or modifying React components that use Relay for data fetching. Covers fragments, queries, mutations, pagination, and common anti-patterns. Use when you see `useFragment`, `useLazyLoadQuery`, `usePreloadedQuery`, `useMutation`, `usePaginationFragment`, `graphql` template literals, `react-relay` imports, or `__generated__/*.graphql` files. Also use when asked to explain Relay concepts, debug Relay issues, or review Relay code
Automates GitHub releases with semantic versioning, changelog generation from merged PRs, and gh CLI integration. Supports draft, prerelease, and standard release workflows with task-tracked multi-phase execution. Use when creating releases, tagging versions, or publishing changelogs
Projetar e revisar logs, métricas, traces, correlação, SLOs, alertas e dashboards para explicar comportamento de sistemas. Use quando a tarefa envolve instrumentação, incidentes, telemetry ou operação; use também para definir o sinal que decide um rollout ou dispara um alerta; não confunda volume de logs com observabilidade, e para o diagnóstico de causa de latência específica use `$specsfy-specialist-performance-engineering`.
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.