Skills
100,696 packaged capabilities and playbooks for agents. Install any of them with one command.
All
Takes existing content markdown files and builds production-final resource center pages on client websites using their existing tech stack and design system. Output is live-ready — no review pass, no placeholder content, no prototype styling. Implements hub pages, section listings, article pages, and cross-linking for Blog, Guides, Learn, and Comparisons sections.
Defeat root, jailbreak, emulator, debugger, and Frida detection in mobile apps using Magisk DenyList, Zygisk modules, objection, and targeted Frida hooks, and understand where hardware-backed attestation like Play Integrity cannot be hooked. Use when an app exits, shows “device not secure,” or silently fails on a rooted device or emulator, or when Frida attaches and the app immediately dies.
Generates C4 model architecture diagrams using Structurizr DSL (primary) or Mermaid C4 (fallback). Use when: user asks to "draw a diagram", "create a C4 diagram", "show architecture as a diagram", "generate architecture diagram", "document the system". DO NOT USE for code explanation or walkthroughs (use `explain-code`), class/sequence/ER diagrams (C4 is system-architecture only), or when a diagram is incidental to a code change — only when a C4 diagram is the primary deliverable.
Manage the lifecycle of multi-tenant SAP CAP applications on Kubernetes using CAP Operator custom resources (CAPApplication, CAPApplicationVersion, CAPTenant, Domain, ClusterDomain). Use when deploying, upgrading, configuring domains, rotating credentials, troubleshooting CAP Operator-managed apps, or generating Helm charts with the CAP Operator Plugin.
When the user wants to plan production or distribution capacity, analyze capacity requirements, optimize resource utilization, or balance capacity with demand. Also use when the user mentions "capacity analysis," "resource planning," "bottleneck analysis," "capacity expansion," "load balancing," "throughput planning," "utilization optimization," or "capacity modeling." For production scheduling, see master-production-scheduling. For long-term network capacity, see network-design.
Captures deterministic, visually verified screenshots of a running web or native app (named screens, states, viewports, dark mode) with a manifest. Use when the user says "take screenshots", or when asked for screenshots of an app or its screens. Not for attaching images to a PR; use attaching-pr-screenshots
Builds site selection and cannibalization analysis workflows in CARTO. Triggers when the user mentions site selection, cannibalization, cannibalizing, new store location, where to open, optimal location, facility placement, network impact, overlapping catchments, twin areas, similar locations, look-alike areas, find locations like my best, store overlap, revenue impact of new store, commercial hotspots, demand hotspots, location scoring, location ranking, expand network, new branch, franchise placement, EV charging siting, or wants to evaluate candidate sites, quantify overlap between trade areas, or find areas that resemble top-performing locations.
Ultra-compressed communication mode. Cuts token usage ~75% by dropping filler, articles, and pleasantries while keeping full technical accuracy. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman.
Turn a set of flagged production call logs into evaluator scenarios for a Cekura agent — cluster the failures into reproducible modes and create one scenario per cluster. Use when the user says "create scenarios from failed calls", "build evaluators for prod failures", "turn call logs into scenarios", "simulate the failures we saw in prod", "replay these bad calls as tests", "regression-test the agent on prod issues", or hands over a set of flagged call IDs to harden the agent against. The flagged set normally comes from `cekura-flag-call-log-failures`; if the user hasn't triaged yet, run that skill first. This skill takes the flagged calls as given — it does NOT re-mine or re-triage — clusters by failure mode, drafts one scenario per cluster, and optionally creates them via the scenarios API (or the call-logs → scenarios endpoint). Also supports a single-call fast path: given one call log ID (or an observe URL), reproduce just that call as one evaluator scenario.
Use when a B2B SaaS founder needs to choose, prioritize, or rebalance customer acquisition channels — deciding outbound vs inbound, paid vs PLG, where to put marketing budget, or sanity-checking CAC, LTV:CAC, and payback. Also for channel-specific playbooks (cold email, LinkedIn, paid social, community, partnerships) and channel-mix audits. Not for closing tactics (use sales-skill) or copy (use copywriter-skill).
Check and fix accessibility (a11y) on front-end projects (web and mobile web), including Next.js, React, Vue, Angular. Use when the user asks about accessibility, a11y, WCAG, screen readers, voice control, Voice View, keyboard navigation, focus management, ARIA, semantic HTML, color contrast, or fixing accessibility issues in HTML, React, Next.js, Vue, or other front-end code. For native mobile apps (React Native, iOS, Android), see reference; patterns differ.
This skill should be used when the user asks to "create a team", "spawn agents", "assign tasks", "coordinate multiple agents", "check team status", "view kanban board", "send messages between agents", "manage team tasks", "monitor team progress", or mentions "oh", "multi-agent coordination", "team collaboration", "agent inbox", "task board", "spawn worker". This skill should also be triggered when the current task is complex enough to benefit from splitting into subtasks and delegating to multiple agents — for example when the user asks to "build a full-stack app", "refactor the entire codebase", "implement multiple features in parallel", or when the agent determines that the work scope exceeds what a single agent can efficiently handle alone. Provides comprehensive guidance for using the ClawTeam CLI to orchestrate multi-agent teams with task management, messaging, monitoring, runtime profiles, git context, and recovery tooling.
When writing Clojure code with unfamiliar Java interop or macros, use this skill to explore and gather context. For Java interop, search for Clojure wrapper libraries first (via WebSearch), then explore Java classes if needed. For macros, expand them to understand what code they generate. This prevents bugs from incorrect API usage. Use this skill when encountering Java classes or unclear macros.
Provides comprehensive guidance for Azure Virtual Machines including VM creation, configuration, networking, and Azure VM management. Use when the user asks about Azure VMs, needs to create Azure VMs, configure Azure compute, or manage Azure virtual machines.
Cloud object storage integration with AWS S3, Azure Blob Storage, and Google Cloud Storage. Covers presigned URLs, multipart uploads, bucket policies, lifecycle rules, and CDN integration. USE WHEN: user mentions "S3", "blob storage", "cloud storage", "object storage", "presigned URL", "file upload to cloud", "GCS", "Azure Blob", "bucket" DO NOT USE FOR: local file uploads - use `file-upload`; database BLOB columns; local filesystem operations
Add headless Chrome automation with Puppeteer/Playwright on Cloudflare Workers. Use when: taking screenshots, generating PDFs, web scraping, crawling sites, browser automation, or troubleshooting XPath errors, browser timeouts, binding not passed errors, or session limits.
View and edit cmux settings in ~/.config/cmux/cmux.json. Use when the user wants to change cmux preferences (appearance, sidebar, notifications, automation, browser, shortcuts), set a value by JSON path, validate the file, open it in an editor, or look up which keys cmux recognizes. Triggers on '/cmux-settings', 'change cmux setting', 'set <something> in cmux', 'cmux config', 'cmux.json', or 'rebind a cmux shortcut'.
Development assistant for the cross-platform 2D/3D game engines Cocos Creator 3.8.x and COCOS 4. Use for writing and debugging TypeScript components, node and component systems, event systems, Tween/Animation, physics and collisions, UI (Label/Sprite/Button/Widget/Layout), asset loading and AssetBundle, scene management, performance and DrawCall optimization, and publishing to platforms such as WeChat Mini Games, Douyin Mini Games, H5, iOS, Android, and HarmonyOS Next. Use when the user mentions Cocos, Cocos Creator, Creator 3.8, COCOS 4, cocos-cli, cc modules, .scene/.prefab/.meta files, @ccclass/@property decorators, mini-game publishing, Spine animation, or game engine performance.
Review one GitLab merge request or local WIP for concrete risks and proportionate fixes, preserving agreed scope and prior decisions in follow-ups. Include GitLab labels, SemVer, and manual publication commands for remote reviews. Use when the user asks to review a GitLab merge request or local work-in-progress changes. Russian discovery terms: ревью кода.
When the user wants to plan YouTube collaborations, write outreach to other creators, design cross-promotion strategies, or pitch guest appearances. Also use when the user says 'collab strategy,' 'YouTube collaboration,' 'outreach to creators,' 'cross-promotion,' 'guest appearance,' 'collab pitch,' 'partner with another creator,' 'grow through collaborations,' 'collaboration outreach.' For audience research to inform collab targets, see audience-research. For channel growth strategy, see channel-strategy.
Integrate App Builder Database Storage (@adobe/aio-lib-db) into an Adobe Commerce app and scaffold a runtime action that reads and writes documents. Use when the user wants persistent, queryable storage backing a Commerce app — either from a web action (HTTP-invokable) or from an event/webhook handler. Requires a base app initialized with commerce-app-init.
When the user wants to research, profile, or analyze competitors from their URLs. Also use when the user mentions "competitor profile," "competitor research," "competitor analysis," "profile this competitor," "analyze competitor," "competitive intelligence," "competitor deep dive," "who are my competitors," "competitor landscape," "competitor dossier," "competitive audit," or "research these competitors." Input is a list of competitor URLs. Output is structured competitor profile markdown files. For creating comparison/alternative pages from profiles, see competitor-alternatives. For sales-specific battle cards, see sales-enablement.
Compile a Beamer LaTeX slide deck with XeLaTeX (3 passes + bibtex). Use when user says "compile", "build the slides", "rebuild the PDF", "run latex", "render the tex", or asks why a `.tex` file isn't producing a PDF. Operates on `Slides/*.tex`.
Conducts source-backed, goal-directed research that combines a scholarly evidence review with an institution, company, or funding map. Use when the user says "deep research", or when a request needs both an evidence review and an organization or funding map. Not for quick lookups or general research write-ups.
Search top conferences such as CVPR, ICCV, ECCV, ICLR, AAAI, NeurIPS, and ICML via DBLP and Semantic Scholar, score the papers, and generate an annual Obsidian recommendation note. Use when the user asks for a conference/year paper list, top-conference recommendations, or papers filtered by venue.
Read project config from .agents.yml and .agents.local.yml with local overrides. Supports dot notation for nested fields. Invoke when agents/skills reference `config_read("field", "default")` pseudocode. Args format "FIELD DEFAULT".
Advisory-only Kafka tuning for Confluent Cloud or Confluent Platform by priority: latency, throughput, availability, or durability. Use when asked to size a planned topic or tune an existing cluster, topic, producer, or consumer for a quantified target such as lower p99 latency or no lost acknowledged writes. Inspects configuration read-only and recommends changes, trade-offs, and validation; the administrator applies them. Do NOT trigger for: WarpStream or Apache Kafka OSS-only clusters; Flink SQL or UDF authoring, tuning, or debugging (use confluent-cloud-flink-sql or flink-udf); Kafka Connect tuning; new Java/Python client implementation (use developing-kafka-java-client or developing-kafka-python-client); Kafka Streams/KStream/KTable development (use kafka-streams-programming); or CDC, Tableflow, or Iceberg pipelines (use confluent-cloud-cdc-tableflow).
Turn a finished plan, spec, or decision map into a build effort with ready-for-agent tickets, or resume its filing and check progress. Use when asked to file the build tickets, break this spec into issues, turn the plan into tickets, slice the work, resume filing build tickets, check progress and close out a build effort, or /conjure.
Takes a campaign brief and submitted creator content description and produces a structured pass/fail checklist against every brief requirement. This skill should be used when checking if creator content matches the brief, reviewing influencer deliverables against requirements, auditing submitted content for brief compliance, verifying a creator hit all the brief requirements, running a content QA check before approval, comparing a draft to the original brief, grading content against campaign specifications, or reviewing creator submissions before giving approval. For converting raw feedback into a polished revision request to send to a creator, see content-approval-feedback-formatter. For FTC disclosure compliance specifically, see ftc-disclosure-spot-checker.
This skill provides screenplay continuity tracking systems and templates. Covers character registry, timeline registry, location registry, prop registry, and wardrobe registry for maintaining story consistency. Use when: setting up tracking systems, checking consistency, managing timelines, or tracking characters, props, and locations across scenes.
Integrate Cartridge Controller into backend services using Node.js, Rust, or headless mode. Use when building server-side applications, game backends, automated bots, or any non-browser environment that needs to execute Starknet transactions. Covers SessionProvider for Node.js, Rust SDK setup, and headless Controller with custom signing keys.
Integrate Cartridge Controller into native mobile applications (iOS, Android, React Native) and web wrappers (Capacitor). Use when building mobile games or apps that need Controller wallet functionality with local keypair signing. Covers SessionConnector for native auth flows, Controller.c FFI bindings, passkey configuration with Apple App Site Association, and platform-specific setup.
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.