Skills
100,928 packaged capabilities and playbooks for agents. Install any of them with one command.
All
Discover where your audience actually pays attention online using Rand Fishkin's behavioral intelligence methodology—beyond demographics to actionable media affinity data. Use when: **Find where to reach your audience** beyond Google and Facebook ads; **Discover podcasts, YouTube channels, and publications** your audience follows; **Identify influencers and accounts** with real audience overlap; **Plan PR and media outreach** with data-backed target lists; **Improve ad targeting** on YouTube,...
Build, edit, validate, publish, and deploy a MuleSoft Agent Broker (Agent Network V2) project end-to-end. Use whenever the user asks to build, create, scaffold, configure, edit, validate, publish, or deploy an Agent Broker, agent network V2, AgentScript, `.agent` file, or `agentNetwork: 2.0.0` project. Do NOT trigger for V1→V2 migration (use the converter skill).
CesiumJS 3D Tiles - Cesium3DTileset, compressed and CAD-style glTF content, MVTDataProvider, UrlTemplate3DTilesDataProvider, styling, metadata, feature picking, voxels, point clouds, I3S, Gaussian splats, clipping. Use when a task involves loading 3D Tiles or Mapbox Vector Tiles, draping vector tiles on terrain, rendering KHR meshopt/CAD content, styling or querying features, working with voxels or point clouds, or clipping spatial data
CesiumJS interaction and picking - ScreenSpaceEventHandler, multi-key KeyboardEventModifier input actions, Scene.pick, Scene.drillPick, Scene.pickPosition, Scene.snap edge snapping (1.144), mouse and touch events. Use when handling user clicks on the globe, selecting entities or 3D Tiles features, registering modifier-key shortcuts, implementing hover effects, snapping to model edges for measurement, or building drag-based interactions
Colyseus 0.18 multiplayer game servers and clients: rooms, Schema state synchronization, state callbacks, reconnection, matchmaking, client SDKs, and client-side prediction. Use when colyseus, @colyseus/schema, @colyseus/sdk, or colyseus.js appears in the task or package.json, before writing any Room or Schema code, and when a project contains pre-0.17 code such as getStateCallbacks(), Room<State> generics, onLeave(client, consented), @filter(), or new Server().
Expert Keboola Python component developer for ongoing development work — implementing features, extending extractors/writers/applications, adding incremental loads, designing configuration schemas, separating API clients, applying self-documenting workflow patterns, and maintaining code quality with Ruff. Use this skill whenever the user is working on component logic, implementation, or architecture — whether building something new or extending existing code. Do NOT use for initial project scaffolding (that's get-started) or UI-only schema work (that's build-component-ui).
Expert-level Git version control with advanced workflows, branching strategies, and best practices for team collaboration. Use when the user mentions version control, collaboration, or workflow, or when the task involves Essential Git Commands, Advanced Git Techniques, Branching Strategies, or Conflict Resolution.
Post-training 4-bit quantization for LLMs with minimal accuracy loss. Use for deploying large models (70B, 405B) on consumer GPUs, when you need 4× memory reduction with <2% perplexity degradation, or for faster inference (3-4× speedup) vs FP16. Integrates with transformers and PEFT for QLoRA fine-tuning.
Workplace health and wellness expertise for employee wellness programs, mental health initiatives, ergonomics and safety, healthcare benefits strategy, and health analytics. Use when designing wellness programs, improving workplace safety, or analyzing health metrics.
Hunt LDAP injection and XPath injection—authentication bypass, blind character-by-character attribute exfiltration, AD user/group enumeration, and XML-store XPath bypass. Covers the LDAP special-character set (* ( ) \\ NUL /), search-filter context vs. DN injection, parenthesis balancing, AND/OR filter logic, and {SSHA}/{CRYPT} userPassword exfiltration on non-AD directories. Use when the target uses LDAP/AD authentication, corporate SSO with a directory backend, an address-book/people-search API, or XML-based data stores queried with XPath.
The Jobs-to-be-Done framework as an applied product methodology. Job statements, struggling moments, hire and fire criteria, and the difference between feature-thinking and job-thinking. Honest about where JTBD adds clarity (discovery, prioritization, positioning) and where it becomes performative ritual (job-statement workshops that do not drive decisions, persona-theater disguised as JTBD). Trigger on jobs-to-be-done, JTBD, job statements, struggling moments, hire criteria, fire criteria, switch triggers, functional, emotional, and social jobs, and outcome-driven innovation. Also trigger when a team is over-relying on feature-request lists or persona archetypes that do not drive product decisions, when a positioning conversation needs the framing JTBD provides, or when discovery is producing outputs that do not connect to product strategy.
Interpret medical lab/test reports (blood panels, urine, liver/kidney function, thyroid, tumor markers, coagulation, cardiac enzymes, hormones, etc.) uploaded as images, PDFs, or text. Trigger whenever the user uploads a lab report, medical test result, or clinical diagnostic sheet — or says things like "help me read this report", "what do these results mean", "化验单", "检验报告", "帮我看看这个报告", "blood test results", "lab results", "体检报告", "检查报告单", "血常规", "尿常规", "肝功能", "肾功能", "甲功", "凝血", "interpret my labs", "are these results normal", "这些指标正常吗". Also trigger when the user uploads ANY medical-looking document with tables of values, reference ranges, or clinical test names — even if they don't explicitly ask for interpretation. Do NOT trigger for symptom triage (use emergency-triage instead), drug interaction queries, or general medical Q&A without an actual report to interpret.
Builds phased data and system migrations using feature flags, dual writes, backfills, and validation. Includes rollback plans and risk mitigation. Use for “data migration”, “system migration”, “database migration”, or “platform migration”.
Next.js App Router best practices covering file conventions, RSC boundaries, async APIs, data patterns, hydration errors, metadata, route handlers, image/font optimization, and bundling. Use when writing or reviewing Next.js code to prevent hydration errors, RSC violations, data waterfalls, and configuration mistakes.
Diagnose why an application deployed by qwencloud-deploy to Alibaba Cloud International (alibabacloud.com) is unavailable or slow, and — only after explicit user confirmation — perform a safe recovery and verify the result. Reads the local .qwencloud-deploy state file to identify ECS (and optional RDS MySQL) resources, runs minimal read-only diagnostics, then proposes one recovery action at a time (start ECS, restart the app service, reload Nginx), each gated by a confirmation that states impact. Use when: the user says the app is down / returns 502 / cannot connect to the database, or asks to restart and verify the app. Do not use when: no .qwencloud-deploy state file exists, the target is Aliyun China (use qianwenai-operate), or the user only wants a status/cost overview (use qwencloud-observe).
Create reminders and calendar events when the user mentions future tasks, appointments, or events they need to remember. Trigger on phrases such as “remind me,” “set a reminder,” “I have a meeting,” “don’t forget,” or any mention of a future time-based task.
Same-design migration—re-platform a site to AEM Edge Delivery (or any clean front end) keeping its current design near pixel-perfect. Recreates key pages (one archetype per page type) as clean re-authored HTML/CSS (never DOM copies), verifies each against the live site with a measured source-fidelity gate (structural + visual + stitched pixel diff per breakpoint), then hands off to migrate/deploy/rollout for site-wide delivery (subsumes prepare-migration's prep cascade—never chain the two). The only permitted design changes are entries in an explicit inconsistency register. Use when the user says “migrate this site keeping its current design”, “same-design migration”, “pixel-perfect replatform to AEM”, or “keep the design, change the platform”. NOT for redesigns—those are the stardust core pipeline (direct/prototype) or uplift.
Comprehensive best practices for robot perception systems covering cameras, LiDARs, depth sensors, IMUs, and multi-sensor setups. Use this skill when working with RGB image processing, depth maps, point clouds, sensor calibration (intrinsic, extrinsic, hand-eye), object detection, semantic segmentation, 3D reconstruction, visual servoing, or perception pipeline optimization. Trigger whenever the user mentions OpenCV, Open3D, PCL, RealSense, ZED, OAK-D, camera calibration, AprilTags, ArUco markers, stereo vision, RGBD, point cloud filtering, ICP registration, coordinate transforms, camera intrinsics, distortion correction, image undistortion, sensor streaming, frame synchronization, or any computer vision task in a robotics context. Also covers multi-camera rigs, time synchronization across sensors, perception latency budgets, and production deployment of perception pipelines.
Diagnose organic traffic changes (drops, stalls, or unexpected wins) using Ahrefs MCP plus Search Console data. Use this skill when traffic suddenly dropped, has been flat despite investment, after an algorithm update, after a migration or deploy, or when a competitor seems to be taking share. Triggers on traffic dropped, traffic decline, traffic stalled, organic decline, lost rankings, why is traffic down, algorithm update, post-migration traffic loss, traffic diagnosis. Also triggers when stakeholders are panicking about an organic traffic number they cannot explain. A panic about tracking, event, or dashboard setup is a measurement problem, not a traffic problem: route those to `analytics-strategy`.
Socratic code review using probing questions instead of direct critique. Based on Feynman's principle that teaching reveals gaps in understanding. Helps developers articulate reasoning, surface hidden assumptions, and discover issues themselves.
Verify a released archon binary works end-to-end via a specific install path. Use when: cutting a new release, reproducing a user bug report on the released version, or validating that a hotfix binary actually works after a re-tag. Triggers: "test the release", "test 0.3.1 via brew", "verify the curl install", "smoke test the binary", "did the release binary work", "run /test-release", "verify the release". NOT for: testing dev work (use bun link directly), testing unreleased changes (build locally via scripts/build-binaries.sh first), or running the full validate suite (bun run validate is separate).
Trust Wallet CLI (`twak`) — install, create wallets, check balances, send tokens, swap, view history, set price alerts, DCA automations, limit orders, manage ERC-20 approvals, check token risk, browse trending/DApps, and run x402 micropayments. Use whenever the user wants to use the twak CLI, manage a crypto wallet from the terminal, send or swap tokens via command line, check portfolio, create price alerts, set up DCA, create limit orders, approve ERC-20 spenders, or interact with Trust Wallet from a shell. Also covers MCP server setup for AI agents
Query VictoriaTraces via curl using the Jaeger-compatible API. Use when discovering traced services and operations, searching traces by service/operation/duration/tags, retrieving traces by ID, or mapping service dependencies. Triggers on: trace queries, span search, trace ID lookup, service discovery, operation discovery, service dependencies, distributed tracing, Jaeger API.
Audit and optimize tweets, X articles, and threads for X's recommendation algorithm. Use when the user wants to review content before posting, improve engagement potential, or get algorithm-friendly suggestions. Triggers on /x-content-optimizer or requests to “review tweet,” “optimize for X algorithm,” “audit my post,” or “improve engagement.”
Alibaba Cloud generic CLI skill for installing, configuring, and using aliyun CLI to call OpenAPI actions across products. Use when users need command-line operations on Alibaba Cloud resources (list/query/create/update/delete), credential/profile setup, region/endpoint selection, or API discovery from CLI.
Spartan UI (shadcn for Angular) best practices. Covers Brain/Helm architecture, Tailwind integration, and accessible headless components. Activates when working with @spartan-ng/brain and @spartan-ng/ui. Do not use for Angular Material, PrimeNG, or other component libraries. Install alongside angular-best-practices for full coverage.
Defines caching strategies with cache keys, TTL values, invalidation triggers, consistency patterns, and correctness checklist. Provides code examples for Redis, CDN, and application-level caching. Use when implementing "caching", "performance optimization", "cache strategy", or "Redis caching"
Manage Claude Code permissions via Dippy config files (global and project-level) and settings.json (for non-Bash/non-MCP permissions like Read, WebFetch, Skill). Use when user asks to "permit", "allow", "whitelist", or "add permission" for a command or tool. Also use when troubleshooting "permission denied" errors, reviewing current permissions, or cleaning up stale entries.
Installs and configures Prettier, ESLint, EditorConfig, and other code quality tools to enforce consistent code style across the team. Generates config files, npm scripts, editor settings recommendations, and CI integration suggestions. Use when users request "setup prettier", "add eslint", "configure code formatting", or "enforce code style".
Canonical template files for Keboola Python components — Dockerfile, pyproject.toml, push.yml, build_n_test.sh, docker-compose.yml, pre-commit-config.yaml, and config-schema.md. Load this whenever creating or modifying any of these files in a component, or when checking whether non-source files are aligned with the official cookiecutter template. Any deviation from these templates must have an explicit reason. Internal utility — usually invoked via Task from develop-component or migrate-to-uv, but should be consulted any time one of these files is being touched.
Orchestrate comprehensive content research across X, Instagram, YouTube, and TikTok platforms. Runs all research skills in parallel via subagents, then aggregates findings into actionable content plans and platform-specific intelligence playbooks. Use when asked to: - Create a content plan for social media - Research content across all platforms - Generate content ideas from multiple sources - Build a content strategy playbook - Aggregate research from X, Instagram, YouTube, TikTok - Run comprehensive content research - Create platform playbooks Triggers: "content plan", "content planner", "research all platforms", "comprehensive research", "content strategy", "multi-platform research", "create playbooks", "aggregate research"
This skill should be used when debugging frontend/UI bugs that need runtime evidence. USE THIS SKILL (instead of adding console.log) when you're about to: "add console.log and ask user to check", "open DevTools and tell me what you see", "reproduce the bug and share the output", "check the browser console". Triggers: "debug this", "fix this bug", "why isn't this working", "investigate this issue", "trace the problem", "figure out why X happens", "UI not updating", "state is wrong", "value is null/undefined", "click doesn't work", "modal not showing". Automates log collection server-side - you read logs directly, no user copy-paste needed.
A workflow for synchronizing documentation, the website, and public skills for the weapp-vite monorepo. Use after source capabilities change to synchronize configuration, CLI, React/Wevu/Vue SFC, multi-platform support, mpcore, README, packaged docs, scaffold `AGENTS.md`, AI skills metadata, and regression trigger entry points.
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.