Skills
101,323 packaged capabilities and playbooks for agents. Install any of them with one command.
All
General-purpose divination and I Ching metaphysics workflow skill. Centered on a rigorous "problem modeling → source verification → method selection → chart facts → method interpretation → real-world application" process, it guides users to choose the most appropriate divination method across fate analysis, divination, combined analysis, feng shui, date selection, and symbolic exploration; through a replaceable provider adapter layer it connects to the AOV public API and Mingyu MCP Server to perform true solar time correction, high-precision chart casting, and self-contained task brief prompt generation.
Social-listening signals for tracked portfolio companies via Apify Actors — Reddit sentiment (fatihtahta), Twitter/X real-time mentions (kaitoeasyapi pay-per-result), Trustpilot service quality (getwally.net). Use when the user asks for sentiment, social media mentions, customer reviews, brand perception, crisis signals, OSINT, social listening, "what are people saying about X". Reads tracked companies from data/companies.json. Do NOT use for news (use apify-financial-news) or registry lookups (use apify-public-registries).
Arco Design Vue UI component library reference for Vue 3 and `@arco-design/web-vue`. Use when the user asks to build Vue pages, create Vue UIs, write front-end code with Arco Vue, develop Vue dashboards or apps, or mentions Arco Design Vue, `@arco-design/web-vue`, `a-button`, `a-table`, `a-form`, `a-modal`, `a-select`, `Message`, or any Arco Vue component name. Covers installation, global registration, on-demand import, theming, internationalization, Vue 3 Composition API conventions, component props/events/slots, examples, forms, tables, modals, navigation, data entry, data display, feedback, and responsive layout.
Azure AD OAuth2/OIDC SSO integration for Kubernetes applications. Use when implementing Single Sign-On, configuring Azure AD App Registrations, restricting access by groups, or integrating tools (DefectDojo, Grafana, ArgoCD, Harbor, SonarQube) with Azure AD authentication.
File Beads or beads_rust epics/issues from a finalized plan/spec AND do the polish pass (clarity, acceptance criteria, sizing, deps). Use when asked to create Beads from a plan/spec (OpenSpec, PRD, design doc), convert an external plan into issue tracker structure, or review/refine an existing Beads set.
Apply communication best practices when generating or reviewing any document, presentation, report, memo, slide deck, proposal, or email. Use this skill when asked to write, create, draft, or generate a document or presentation — apply the principles at generation time, not as an afterthought. Also use when asked to "review my doc," "look at this deck," "does this make sense," "is this clear," "improve this proposal," "check this before I send it," "make this more effective," or any request to evaluate whether a document will land with its audience. Use this skill even when the request seems minor — a "quick look" or a "short memo" is exactly when these principles matter most.
Use when choosing Bevy 0.20 Cargo features — top-level `2d`/`3d`/`ui`/`audio`, mid-level `3d_api`/`3d_bevy_render`/`ui_api`/`common_api`, headless `default_app`, input opt-ins `mouse`/`keyboard`/`gamepad`, `bevy_curve` (was `bevy_math/curve`), `compressed_image_saver_universal`, `render_dev_tools`, or debugging missing UI, audio, or window after `default-features = false`
Create and review C4 software-architecture diagrams using Mermaid or Structurizr. Use when teams need a communication-ready system context, container, component, or code-level view, including audience, narrative, hierarchy, labels, legends, accessibility, and uncertainty. Do not use for Mermaid syntax/rendering work without C4 modeling, architecture decisions, or full accessibility conformance reviews.
Use this skill when an LLM should act inside a business process — choosing tools or next steps, calling systems, handing off to people — with guardrails, human review, or an audit trail, even if Camunda isn't mentioned, and before hand-coding an agent loop. Models Camunda 8 AI Agent sub-processes: tools as BPMN tasks, fromAi() parameters, prompts, and limits. Also covers v1/v2 element-template selection and upgrading v1 elements to v2.
Give the human a fast, plain-English catch-up on what changed in the project: what the agents did, why, and what decisions need their input. Use when the user asks to "catch me up", "what changed", "where are we", "recap", "brief me", "give me the rundown", "what did you do", "summarize the session", or "fill me in", or otherwise wants to get back up to speed after being away.
Generate and upsert a Ticket-scoped QA Report (PROGRESS or COMPLETION) for any CawPlan Ticket (anchor) + Version: collect anchor-relative subtree/relation/execution data, apply result rules, render ticket-qa-report.1 template, and persist via existing Portal qa_report POST/PUT. Use when: SQA asks for a test progress or completion QA report for a ticket and version (Story, requirement sub-ticket, or BUGFIX); republish/update an existing linked report; include related/blocking tickets in report scope. NOT for: Version Quality Report or AQA automation rollup; release risk assessment (use A5 separately); importing cases (A1), plan layout (A2), or defect filing (A4). V1 zero-BE: Agent-side upsert; approximate coverage; anchor-relative subtree depth ≤ 3.
Chat UI building blocks for React/Next.js from ui.inference.sh. Components: container, messages, input, typing indicators, avatars. Capabilities: chat interfaces, message lists, input handling, streaming. Use for: building custom chat UIs, messaging interfaces, AI assistants. Triggers: chat ui, chat component, message list, chat input, shadcn chat, react chat, chat interface, messaging ui, conversation ui, chat building blocks
Parallelize an approved spec across 5+ independent behavioural curds into reviewable PRs, running the whole pipeline fanned out at once. Use when the user has such a spec — phrases like "/cheese-factory .cheese/specs/<slug>.md", "send through the factory", "parallelize this spec", "many curds", "fan out the implementation", "cheese-factory this". Runs inline and spawns full-peer general-purpose sub-agents per phase (decomposer, per-curd workers, wiring, post-merge review, PR planner), ending in 1–N reviewable PRs via `/pr-stack`. Use even when the user mentions `/fromagerie` — `/cheese-factory` is the portable harness-agnostic sibling. Supports `--hard` propagation and `--resume <slug>` to continue a crashed pipeline. Do NOT use for single coherent specs (`/cook`, `/ultracook`), fuzzy planning (`/mold`), review-only work (`/age`), or specs with fewer than 5 curds (`/ultracook`).
Receive and verify Anthropic Claude Managed Agents (CMA) webhooks. Use when setting up Claude Managed Agents webhook handlers, debugging signature verification, or handling agent session and vault events like session.status_idled, session.status_terminated, session.thread_created, vault.created, or vault_credential.refresh_failed.
Create and optimize CLAUDE.md memory files or .claude/rules/ modular rules for Claude Code projects. Comprehensive guidance on file hierarchy, content structure, path-scoped rules, best practices, and anti-patterns. Use when working with CLAUDE.md files, .claude/rules directories, setting up new projects, or improving Claude Code's context awareness.
API reference for CoinMarketCap market-wide endpoints including global metrics, fear/greed, indices, trending topics, and charts. Use this skill whenever the user mentions market API, asks about fear/greed index, wants global metrics or BTC dominance data, needs k-line charts, or is working with market sentiment. This is the complete reference for CMC market-wide API questions. Trigger: "market API", "fear greed API", "global metrics API", "CMC charts API", "/cmc-api-market"
Generates production-ready code scaffolds, functions, classes, and project structures across Python, TypeScript, Java, and Go. Use when the user asks to generate code from templates, scaffold a new project, create boilerplate classes or modules, or automate repetitive code creation tasks.
Use this skill when the next step is locating or tracing code you have not found yet: where something is defined, who calls it, how a feature is wired end to end, every occurrence of a string or flag across a repo, or what a file's public surface is. It picks one search rung (LSP symbols, ripgrep, grep) from what is actually built for the file types involved, then falls through the ladder instead of re-asking a tool that returned nothing. Reach for it before your first grep, rg, find, or LSP query in a session, and again the moment a semantic tool comes back empty. Do not use it when the user already names the file and symbol and the work is the edit itself, when the question is about a search tool's flags or setup, when the task is profiling or speeding up a feature that happens to be called search, or when the target is logs, commit summaries, or non-code data rather than source.
World-class color theory expertise combining the scientific precision of Josef Albers' "Interaction of Color," the systematic thinking of color systems from Pantone and RAL, and the perceptual psychology insights from researchers like Bevil Conway. Color is not just aesthetics - it's communication, emotion, and usability compressed into wavelengths. Great color work is invisible when done right. Users don't notice "nice colors" - they notice when they can't read text, when buttons don't look clickable, when errors don't feel urgent, or when the interface feels "off" without knowing why. Color theory is the science of making the right thing feel obvious. Use when "color theory, color palette, color scheme, color harmony, complementary colors, analogous colors, contrast ratio, dark mode colors, light mode, color tokens, semantic colors, color accessibility, color blindness, color psychology, color system, brand colors, data visualization colors, color, design, accessibility, contrast, dark-mode, theming, tokens, wcag, palette, harmony" mentioned.
Diagnose GitHub Actions and coverage checks for Comet PRs using the PR's current accurate head, failing job logs, local reproduction boundaries, and mergeability state. Use when a PR shows CI errors, Codecov issues, stale checks, or unexplained red jobs.
Turn local Comet ideas, observed regressions, or improvement proposals into focused GitHub Issue drafts based on the current codebase. Use when the user asks to convert local investigations into issues, follow-up issues, bugs, features, or maintenance tasks.
Check ad copy, landing pages, VSLs, and emails for platform compliance issues — Meta/Facebook, Google, TikTok, YouTube, and ClickBank. Use this skill whenever the user asks to check compliance, run a compliance audit, review copy for platform policy violations, check if copy will get banned or flagged, audit for Meta/Facebook ad policy, or scan for trigger words. Also trigger for 'is this compliant', 'will this get rejected', 'check for banned words', 'platform policy check', or any task involving reviewing direct response copy against advertising platform rules.
Plan, run, and monitor Fireworks training from a coding agent. Covers managed SFT, DPO, ORPO, and RFT plus Training API serverless and dedicated workflows, complete cost and parameter confirmation, active monitoring, checkpoints, deployment, resume, and teardown. Use for explicit train, fine-tune, deploy, or resume requests. Use research when method, data, or evaluation is unclear; use debug for a stuck or failed run.
Configures SSO authentication and SCIM 2.0 provisioning for CockroachDB across four distinct layers — Cloud Console SSO (SAML/OIDC), DB Console SSO (OIDC), SQL/Cluster SSO (JWT or LDAP/AD), and SCIM 2.0 automated provisioning. Use when enabling centralized identity management, setting up SSO for compliance, or automating user lifecycle management.
Apply context-driven testing principles where practices are chosen based on project context, not universal 'best practices'. Use when making testing decisions, questioning dogma, or adapting approaches to specific project needs.
Master Coolify operator for self-hosted deployment platform. Use when the user mentions 'coolify', 'deploy on coolify', 'list/restart/redeploy applications', 'view coolify logs', 'coolify API/CLI', 'manage coolify servers/databases/apps', or 'coolify context'. Automates deployments and management via REST API or official CLI.
Predict construction project costs using Machine Learning. Use Linear Regression, K-Nearest Neighbors, and Random Forest models on historical project data. Train, evaluate, and deploy cost prediction models.
Create a RevOS Connection YAML that syncs data from a Source into the org's data warehouse. Use whenever the user asks to: add a connection, set up a sync, ingest a table, pipe data from a source, configure streams, pick which tables to ingest, or wire up a Source. The skill picks a sensible stream subset (especially important for databases — most projects don't want every table) and confirms the choice before writing YAML.
Create new dbt transformations (silver/gold models) in the RevOS dbt project. Use when asked to create a dbt model, build a transformation, add a new layer model, declare a raw source, or register a new raw table. Bronze is source-declarations only — no SQL files. Covers dbt project conventions, sources, materialization, schema.yml, and validation commands.
Creates a ticket-driven handover test for a Playwright E2E test suite. Names the test with the ticket prefix, places it in the handover test directory, and follows the promotion lifecycle. Use when asked to write a handover test, ticket test, functional test, or test for a specific ticket number.
Creates a regression or smoke test spec file for a Playwright E2E test suite. Generates the spec file, test data JSON, and fixture updates. Handles complete test scaffolding including beforeAll cleanup, POM usage, and parallel-safe data. Use when asked to write a regression test, smoke test, or E2E test for a feature.
Backtest crypto trading strategies from natural language ideas. Use when: user describes trading ideas, wants to validate strategies, mentions "backtest", "trading strategy", "buy low sell high", "RSI", "MACD", "oversold", "overbought", "crypto strategy", "validate strategy", "backtest", "DCA", or similar.
Assess latency, queueing, timeouts, missed or duplicate schedules, dispatch and concurrency pressure, refresh overlap, and data-source fan-out across existing Splunk dashboards, reports, and alerts without changing them. Use when object load, freshness, scheduled execution, or downstream timing is degraded and the requester needs an evidence-bounded performance finding, product and provider boundary, validation plan, and owner handoff. Route one-search SPL cost, structural authoring, functional object repair, acceleration, and deployment remediation to their owners.
Use this skill to assess, design, and evolve data architectures, including data platforms, data products, data mesh adoption, event-driven data flows, governance, modeling, and migration decisions. Load it when teams need workload-grounded tradeoffs, ownership and quality agreements, or a current-to-target data architecture. Do not use it for pipeline or platform operations, implementation details, interface contract semantics, SQL tuning, or statistical modeling; route those to data-engineering, platform-engineering, api-design-and-evolution, postgres, or data-scientist.
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.
