Skills
97,725 packaged capabilities and playbooks for agents. Install any of them with one command.
Development
Advanced Odoo frontend development with comprehensive theme development, /create-theme command, theme.utils activation system, complete dynamic page reference (headers, footers, shop, blog), design workflow methodology, PWA support, modern JavaScript/TypeScript, testing frameworks, performance optimization, accessibility compliance, and real-time features. Features complete $o-website-values-palettes reference, theme mirror model architecture, publicWidget patterns with editableMode handling, and MCP integration. Supports Odoo 14-19 with auto-detection. <example> Context: User wants to create a new Odoo website theme user: "Create a new website theme for Odoo 17" assistant: "I will use the odoo-frontend skill to scaffold a complete theme module with primary_variables.scss, Bootstrap overrides, and mirror model page definitions." <commentary>Core trigger - new theme creation from scratch.</commentary> </example> <example> Context: User wants to add a section to an existing theme user: "Add a hero section to my Odoo website homepage" assistant: "I will use the odoo-frontend skill to create a publicWidget-based hero snippet with SCSS styling that follows Bootstrap 5.1.3 grid conventions." <commentary>Incremental theme work - adding components.</commentary> </example> <example> Context: User wants to implement a Figma design in Odoo user: "Implement this Figma design as an Odoo 17 theme" assistant: "I will use the odoo-frontend skill with Figma MCP to extract design tokens and convert them into Odoo theme SCSS variables and Bootstrap-compatible layouts." <commentary>Design-to-code workflow with Figma MCP integration.</commentary> </example>
Offline transaction support for TanStack DB. OfflineExecutor orchestrates persistent outbox (IndexedDB/localStorage), leader election (WebLocks/ BroadcastChannel), retry with backoff, and connectivity detection. createOfflineTransaction/createOfflineAction wrap TanStack DB primitives with offline persistence. Idempotency keys for at-least-once delivery. Graceful degradation to online-only mode when storage unavailable. React Native support via separate entry point.
OpenHarmony CAPI N-API wrapper test case generator (method 2). Automatically parses .h header files and generates C++ N-API wrappers and ETS/ArkTS test code. **Scenarios that trigger this skill**: - The user mentions CAPI, C tests, Native tests, native tests, .h file parsing - The user needs to generate N-API wrapper tests (not gtest) - The user mentions coverage reports, supplementary tests, missing tests - The user needs to compile or validate the CAPI test suite - The user mentions asynchronous compilation, background compilation, compilation validation - The user mentions XTS tests, OpenHarmony tests, subsystem tests **Core features**: 1. Header file parsing → extract API information 2. Test case generation → C++ N-API wrappers + ETS test code 3. Compilation validation → asynchronous compilation + error fixing 4. Code validation → triple N-API verification + format checks **Supported subsystems**: multimedia, bundlemanager, ability, arkui, hilog, etc. **When the user provides a coverage report**: automatically switches to coverage-report-driven mode (efficient and precise)
OpenAPI/Swagger specification. Covers schema definition, paths, and documentation. Use for API documentation. USE WHEN: user mentions "OpenAPI", "Swagger", "API spec", "API documentation", "schema definition", "OpenAPI 3.0", "Swagger UI", asks about "how to write OpenAPI spec", "document REST API", "API contract", "schema validation" DO NOT USE FOR: GraphQL schemas - use `graphql` instead; tRPC - use `trpc` instead; Generating clients from OpenAPI - use `openapi-codegen` instead; Spring Boot OpenAPI - use `springdoc-openapi` instead
Use when an AI coding assistant needs GIS/CAD/C#/AI/IoT/3D domain expertise. Index of 114 skills across 8 categories: gis (40), cad (21), csharp (12), ai (17), iot (4), 3d (6), demos (4), others (10). Tag-based search and on-demand loading for GDAL, GeoServer, MapServer, Leaflet, PROJ, PostGIS, DuckDB Spatial, GeoLibre, JTS, CesiumJS, FreeCAD, Blender, OpenSCAD, OCCT, NPOI, SqlSugar, Furion, Serilog, Dify, Ollama, LangChain, vLLM, MinerU, SuperSplat, Home Assistant, CHAGS and more.
Think through ideas, investigate problems, and clarify requirements before committing to a change using `/opsx:explore`. Use when the user says "explore an idea", "think through this", "investigate options", or wants to brainstorm before creating a formal change.
Use when the user asks to discover and deliver repository optimization work end to end: identify performance/reliability/maintainability/security/dx/cost optimization points, prioritize by impact-effort-risk, then execute fixes step by step with continuous testing and explicit commit policy (`final_only`, `per_step`, `milestone`). Default to `per_step` for implementation work so each feature is tested then committed before the next feature. Supports optional BDD (Given/When/Then).
Build, review, debug, configure, migrate, teach, or plan Oxfmt JavaScript/TypeScript formatting with current Oxc docs and a full usage guide. Use for oxfmt how-to, oxfmt.config.ts, defineConfig, .oxfmtrc.json, Prettier/Biome migration, --check/--write, printWidth, experimentalOperatorPosition, sortImports groups/customGroups, sortTailwindcss Tailwind class sorting (stylesheet/config/functions), sortPackageJson, jsdoc, ignorePatterns, oxfmt-ignore, YAML/JSON/CSS native language support, Vite+ fmt, VS Code/Cursor format-on-save (formatOnSaveMode file, source.format.oxc, source.fixAll.oxc), editors, CI format gates, and day-to-day format workflows.
Collaboratively design, implement, review, and refine software features with a human developer using an iterative pair programming workflow. Prioritize understanding, explicit approval, small reviewable changes, and synchronized specifications.
A team skill that designs, implements, and verifies a single feature through a 3-agent (Architect→Builder→Reviewer) loop. Triggered by the keywords "3a로 만들어줘", "3에이전트", "설계-구현-검토", "team-3a". Lighter than peach-team-dev, suited to single features and small-scale changes.
Verify codebase quality — architecture consistency, convention compliance, gap analysis. Triggers: code review, architecture check, quality, gap analysis default: bkit:code-analyzer validate: bkit:design-validator gap: bkit:gap-detector qa: bkit:qa-strategist team: bkit:cto-lead
A collection of deprecation and breaking-change patterns and fix recipes for baserCMS PHP version upgrades (8.2/8.4/8.5 and later). Refer to this when investigating or fixing upgrade warnings/errors caused by PHP itself, such as "implicitly nullable deprecation warning", "Creation of dynamic property ... is deprecated", "fgetcsv escape warning", "ReflectionProperty::setValue deprecation", "deprecation of non-canonical casts like (integer)/(boolean)", "deprecation of using null as an array offset", and "deprecation of auto-release functions such as curl_close/imagedestroy". When supporting a new PHP version, append per-version notes to this document. For issues caused by CakePHP itself, see the cakephp-migration skill.
Guide for building web apps with the Ping Orchestration JavaScript SDK (also referred to as the Ping Identity JavaScript SDK, formerly the ForgeRock JavaScript SDK / @forgerock/javascript-sdk; npm packages: `@forgerock/journey-client`, `@forgerock/davinci-client`, `@forgerock/oidc-client`). Use when the user wants to add Ping authentication to a web app — phrases like "add Ping auth to my web app", "use PingOne in React", "set up Journey in JavaScript", "build a Ping login page", "use DaVinci in my SPA", "integrate @forgerock/journey-client", "set up @forgerock/davinci-client", "migrate from @forgerock/javascript-sdk to the new SDK", or "add OIDC login to my React app". Detects framework (React active; Angular, Vue, vanilla JS on the roadmap), collects shared config, delegates Journey to ping-orchestration-reactjs-journey-sdk and DaVinci to ping-orchestration-reactjs-davinci-sdk, and handles OIDC centralized login inline. Covers both new sample app creation and integrating into an existing project.
Break down a user story into multiple testable tasks. Use when the user mentions: story, ticket, task breakdown, implement feature, plan implementation, create tasks, split into tasks, story breakdown, task decomposition, acceptance criteria, definition of done, sprint planning, backlog, user story, feature breakdown, ralph, ralph loop, autonomous implementation, .TASK.md, progress.txt, or run through ralph. Each task must be independently verifiable. NOTE: Ralph-loop task files (.TASK.md) are generated ONLY when explicitly requested — never automatically during normal story creation.
Adversarial cooperation loop for ONE ticket — player implements, verify reviews, every changed default turn is pushed to a draft PR, CI passes, and the PR is marked ready. Invoke only when the user explicitly asks for the player-coach loop. Do not use for an ordinary coding request. For a whole epic, use epic-runner instead.
Write a clear, structured pull request description from a git diff, branch summary, or commit list. Use when asked to write a PR description, draft a pull request, or document code changes. Produces a description with summary, motivation, changes made, testing steps, and reviewer guidance.
Write concise, useful project documentation (READMEs, guides, docs/) inspired by Philip Greenspun's pragmatic style. Use when creating or improving README.md, writing module docs, CONTRIBUTING.md, architecture docs, CHANGELOG, or structuring any project documentation for software projects. Use this skill whenever the user needs to write, rewrite, or review any form of project documentation — even if they just say "write a README" or "document this" without asking for a specific style.
Generate a full security-focused PRD (Product Requirements Document) from a plain-language feature description. Use this skill whenever someone wants to create a PRD, product spec, feature spec, requirements document, or says things like "write a PRD for", "create a spec for", "plan this feature", "document this feature", or "I need a requirements doc". The skill produces: (1) a structured PRD in a security-focused template format, (2) a Confluence page pushed to your configured space via Atlassian MCP (called directly), (3) a cursor-compatible .md plan file for .cursor/plans/, (4) a downloadable formatted markdown, (5) optionally: Linear/Asana tasks from the batch plan, Slack notification to stakeholders, Notion page mirror. Always use this skill for PRD and feature planning tasks.
Apply to multi-step work (sweeps, migrations, runs of similar edits) and to how you stack commits and PRs. Break work into small units that each end in a verifiable state, check each before the next, and order delivery so the sequence proves itself to a reviewer.
Writes, validates, and converts ProductSpec files (.product-spec.md), the Markdown format for recording product intent before implementation. Use when authoring a new Product Spec, converting an existing PRD or feature doc into one, validating spec files locally or in CI, or recording how a spec's intent changed over time in a Decision Trace. For implementing code against a Product Spec that already exists, use the productspec skill instead.
Use this skill for pull request workflows - creating PRs (branch, commit, push, open), reviewing PRs (code quality, test coverage, issue fixing), addressing PR review comments (fix feedback, respond to reviewers), or merging PRs (CI checks, merge, cleanup). Handles the complete PR lifecycle via gh CLI. Triggers include "create PR", "open PR", "review PR", "merge PR", "address PR comments", "fix review feedback", "respond to reviewer", "push for review", "submit PR".
Configures packaging for a Python library — pyproject.toml metadata, build backend, src layout, CLI entry points, uv lockfiles, where dev dependencies go (dependency-groups vs optional-dependencies), wheels and sdists. Use to make a project installable, set up pyproject.toml, build a wheel, move off requirements.txt, or switch to uv. Not for publishing to PyPI or release automation.
Use when the user needs to build, choose the pattern for, or optimize a SQL query against Protheus ERP tables -- covering Workarea (DbSelectArea/DbSeek) vs Embedded SQL vs TCSqlExec pattern choice, mandatory D_E_L_E_T_/xFilial filters, SIX index-aligned WHERE ordering, FWPreparedStatement parameterization to prevent SQL injection, and cross-database (PostgreSQL/MSSQL/Oracle) portability. Also triggers on Portuguese phrasing like "consulta SQL", "montar query", "otimizar consulta", "qual indice usar", "escolher entre DbSeek ou SQL", or "prevenir SQL injection no Protheus".
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.
