Skills
96,770 packaged capabilities and playbooks for agents. Install any of them with one command.
Development
Implement TrueSkill rating system for multiplayer and team-based competitive ranking. Use this skill when the user needs to rate players in team games, handle multiplayer (non-1v1) matchups, or build a matchmaking system with uncertainty tracking — even if they say 'team rating system', 'multiplayer ranking', or 'matchmaking rating'.
Use a repo-root `.editorconfig` to configure free .NET analyzer and style rules. Use when a .NET repo needs rule severity, code-style options, section layout, or analyzer ownership made explicit. USE FOR: the repo needs a root .editorconfig; analyzer severity and style ownership are unclear; the team wants one source of truth for rule configuration. DO NOT USE FOR: choosing analyzers with no config change; formatting-only execution with no config ownership question. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.
Software development engine for coding. A production-grade skills system for web apps and mobile architecture, APIs, databases, web, mobile, AI, security, UX, SaaS, and ERP engineering. Encodes reusable engineering judgment through layered baseline and specialist skills to help generate secure, scalable, maintainable, high-performance software systems
Generates production-ready API clients with TypeScript types, retry logic, rate limiting, authentication (OAuth, API keys), error handling, and mock responses. Use when user says "integrate API", "API client", "connect to service", or requests third-party service integration.
Implementation planning for existing tracked work items. Use when asked to plan an existing GitHub issue, Agile Accelerator story, or PRD before coding begins. Produces ordered tasks, file-level changes, test strategy, acceptance-criteria mapping, and synchronized docs/<ID>-IMPLEMENTATION_PLAN.md plus docs/<ID>-progress.txt artifacts. Do not use to create new user-story backlogs.
Use the open-source free `ArchUnitNET` library for architecture rules in .NET tests. Use when a repo needs richer architecture assertions than lightweight fluent rule libraries usually provide. USE FOR: the repo uses or wants ArchUnitNET; architecture testing needs richer modeling than simple dependency checks. DO NOT USE FOR: the lightest possible architecture rule checks. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.
Author pre/post-iteration hooks for an autoresearch session. Use when the user asks to add research fetching, Slack/webhook notifications, persistent learnings, auto-tagging, anti-thrash intervention, idea rotation, or any side effect around iterations.
Use when SecItem calls fail — errSecDuplicateItem from unexpected uniqueness, errSecItemNotFound despite item existing, errSecInteractionNotAllowed in background, keychain items disappearing after app update, access group entitlement errors, or Mac keychain shim issues. Covers systematic error diagnosis with decision trees.
Use when needing SecItem function signatures, keychain attribute constants, item class uniqueness constraints, accessibility level details, SecAccessControlCreateFlags, kSecReturn behavior per class, LAContext keychain integration, or OSStatus error codes. Covers complete keychain API surface.
Use when monitoring a PR (or a full Graphite stack of PRs) that needs CI fixes or review comment responses. Runs as a long-running session with intelligent sleep intervals. Handles failing checks, reviewer feedback, and pushes verified fixes autonomously.
A specialist team for the coding agent you already use: 12 roles, 21 workflows and 33 skills that plan, build in parallel, review and debug, leaving plans, ADRs and results as files. Gates wait for your own tests. Also research, slides and video. One .agents/ folder for Claude Code, Codex, Cursor and 11 more.
bclearer pipeline implementation skill. Extends ob-engineer with bclearer-specific pipeline code conventions, interop usage patterns, and orchestration wiring. Use when: implementing a bclearer pipeline from an approved architecture design, reviewing bclearer pipeline code for convention compliance, or adding stages to an existing pipeline. Delegates BIE domain implementation to bie-data-engineer.
Backend code quality for clean, production-ready, maintainable code. Adapts to the existing language, framework, and style. Covers functions, reusability, modern syntax, error prevention, readability, and security awareness. Use when writing, reviewing, or refactoring backend code for quality, maintainability, or production readiness.
(NS) Onboard an existing codebase into spec-driven planning — map stack, modules, rule adherence, and gaps without modifying code. Use when the user says analyze existing project, brownfield bootstrap, or before first requirements on a repo with code but no requirements. Outputs brownfield-map.md for requirements-generator. Read-only on source code.
Use when the user needs creative divergence, requirements exploration, or product planning (whether creating a feature, building a component, adding functionality, or changing behavior). This skill turns ideas into a complete design plan and requirements specification through collaborative dialogue.
Use when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. Don't use during clear 'mechanical' processes
Bulk engineering approaches, tools, and implementation strategies for mass-generating PLC/DCS control logic, HMI displays, and I/O configurations from engineering databases. Use when planning or implementing automation of DCS engineering workflows.
Deploy, configure, and use camofox-browser — the Camoufox-engine anti-detection browser server (REST API on port 9377) for AI agents. Use when code hits `http://localhost:9377/tabs`, `/sessions/:userId/cookies`, or `/youtube/transcript`; when scripts install `@askjo/camofox-browser`, run `npm start` in the `camofox-browser` repo, or call `make up`/`make fetch`; when agents invoke OpenClaw `camofox_*` tools (`create_tab`, `snapshot`, `click`, `type`, `navigate`, `scroll`, `screenshot`, `close_tab`, `list_tabs`, `import_cookies`); when the user asks about Camoufox fingerprint spoofing, bypassing Cloudflare/Google bot detection, element refs (`e1`, `e2`), accessibility snapshots, search macros (`@google_search`, `@reddit_subreddit`), Netscape cookie import, session isolation, backconnect proxy rotation with GeoIP, VNC/noVNC login, writing `plugins/<name>/index.js` with `register(app, ctx)`, `CAMOFOX_*`/`PROXY_*` env vars, or deploying to Docker/Fly.io/Railway.
[BETA] Transform feature descriptions or requirements into structured implementation plans grounded in repo patterns and research. Use when the user says 'plan this', 'create a plan', 'write a tech plan', 'plan the implementation', 'how should we build', 'what's the approach for', 'break this down', or when a brainstorm/requirements document is ready for technical planning. Best when requirements are at least roughly defined; for exploratory or ambiguous requests, prefer ce:brainstorm first.
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
Rewrites code to fix clean coding violations. Use when: acting on a violation report from clean-code-reviewer, fixing specific code-level issues (function size, naming, error handling, smells) in existing code, or as the final step in a refactoring workflow after an architect has designed the target structure. Does NOT make architectural changes — structural redesign is the responsibility of the appropriate data-engineer in Implement Mode, working from an architect's design. Supports Python, JavaScript/TypeScript, C#, and Rust. Supports both general (Clean Code) and OB (BORO Quick Style Guide) convention sets via the `standard` parameter.
Design and build a CLI that an AI agent can operate safely and a human can supervise. Use when the user wants to build a CLI, wrap an API in a command-line tool, build a CRUD or local-first tool over a database or filesystem the user already owns, add --json or --dry-run to an existing CLI, design a trust ladder or approval gate for risky commands, wrap an async API so agents do not write their own poll loop, or decide how to distribute a CLI (npm, native binary, source). Runs on its own when the contract is yours to define; follows a surface-recon report when the target is someone else's service
Builds and deploys remote Model Context Protocol (MCP) servers on Cloudflare Workers in TypeScript with @modelcontextprotocol/sdk: McpAgent class patterns for tools, resources, and prompts, all four authentication patterns (token validation, remote OAuth with DCR, OAuth proxy via workers-oauth-provider, and a full OAuth provider), GitHub/Google/Azure OAuth, Durable Objects for per-session state, WebSocket hibernation for cost savings, and dual SSE plus Streamable HTTP transports. Ships templates for basic servers, OAuth proxy, stateful Durable Object servers, and wrangler.jsonc configs, and prevents 15+ errors including McpAgent export mistakes, OAuth redirect URI mismatches, WebSocket state loss, Durable Objects binding errors, and CORS misconfiguration. Use when creating, authenticating, debugging, or deploying an MCP server on Cloudflare Workers.
Complete knowledge domain for Cloudflare Workflows - durable execution framework for building multi-step applications on Workers that automatically retry, persist state, and run for hours or days. Use when: creating long-running workflows, implementing retry logic, building event-driven processes, scheduling multi-step tasks, coordinating between APIs, or encountering "NonRetryableError", "I/O context", "workflow execution failed", "serialization error", or "WorkflowEvent not found" errors. Keywords: cloudflare workflows, workflows workers, durable execution, workflow step, WorkflowEntrypoint, step.do, step.sleep, workflow retries, NonRetryableError, workflow state, wrangler workflows, workflow events, long-running tasks, step.sleepUntil, step.waitForEvent, workflow bindings
Manage cloud development sandboxes with cloudrouter. Create, sync, and access remote VMs with GPU support, Docker, and browser automation. Use when asked to create a sandbox, spin up a dev environment, run code in the cloud, use GPUs, automate a browser, or interact with remote VMs.
(NS) Ad-hoc coding agent for focused implementation without full SDD planning — bug fixes, isolated components, small refactors, scripts, migrations. Use when the user says "just implement this", "quick fix", "add a field to the form", or gives a concrete coding task without execution-handoff — even without naming an agent. When a planned version has execution-handoff.md, follow execution-handoff-generator run-implementation workflow instead of this skill's ad-hoc cycle. Redirect large multi-day features to planning. Do NOT generate requirements.md, task files, or execution-handoff.
Code simplification skill for improving clarity, consistency, and maintainability while preserving exact behavior. Use when simplifying code, reducing complexity, cleaning up recent changes, applying refactoring patterns, or improving readability. Triggers on code cleanup, simplification, refactoring, or readability improvements.
TypeScript style rules for writing, reviewing, and refactoring `.ts` code. Use when working on TypeScript formatting, semicolon conventions, object layout, function call structure, or interface definitions. Also use when reviewing or writing TypeScript interfaces, type aliases, or any nested object type shapes.
Create detailed implementation plan using GPT-5.4 with xhigh reasoning. Use when the user wants to plan a feature, refactor, bug fix, infrastructure change, or any multi-step coding task before implementation. 觸發詞：/codex-plan、plan this、implementation plan、幫我規劃、寫實作計畫、規劃功能
Use when the user asks to commit, push, commit-and-push, open/draft a PR/MR, write a PR description with a Test plan, or tag/cut a release — especially when changes should be split into logical commits, or when tempted to dump everything into one commit or push to a protected branch.
Use this skill when a product engineer wants to audit existing code for Earth Design System (EDS, `@adaptavant/eds-core`) anti-patterns, misuse, deprecated APIs, or HTML accessibility violations. Triggers include 'audit EDS usage', 'check for EDS anti-patterns', 'review this file for EDS violations', 'is this EDS-compliant', 'lint my EDS code', or any request to scan a file or directory for design-system misuse. Detection-only — produces a findings report with suggested fixes and refers remediation to the `co-author` skill. Do NOT use this skill for authoring new EDS code (use `co-author`), reviewing PRs (use `pull-request-reviewer`), or fixing bugs inside `packages/core`.
Implement the Kantara Initiative consent receipt specification including machine-readable receipt structure, JWT-based verification mechanisms, receipt lifecycle management, and integration patterns for consent management platforms. Supports ISO/IEC 27560 consent record information structure.
Use for persistent, one-question-at-a-time consultation on an ambiguous repository change: inspect supplied territory, save decisions, produce an approved plan, run a scored bounded adversarial review with explicit targets and automatic-review limits, resolve or accept human-owned risks, and hand off to a fresh builder without implementing. Trigger on explicit /consultant or requests for durable consultation, plan approval, adversarial review, or builder handoff; exclude ordinary plan editing, standalone review or brainstorming, PRD writing, implementation, testing, and generic technical advice.
Format commit messages using the Conventional Commits specification. Use when creating commits, writing commit messages, or when the user mentions commits, git commits, or commit messages. Ensures commits follow the standard format for automated tooling, changelog generation, and semantic versioning.
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.