Skills
97,501 packaged capabilities and playbooks for agents. Install any of them with one command.
Data & databases
Expert guidance for systematic backtesting of trading strategies. Use when developing, testing, stress-testing, or validating quantitative trading strategies. Covers "beating ideas to death" methodology, parameter robustness testing, slippage modeling, bias prevention, and interpreting backtest results. Applicable when user asks about backtesting, strategy validation, robustness testing, avoiding overfitting, or systematic trading development.
For all content creators who want to turn "gut feeling" into calibratable predictions. The methodology is general — the loop of scoring → blind prediction → T+3d retrospective → evolving the rubric applies to any content that can be quantified (views / reads / listens / clicks). The rubric is the content of the loop, not the loop itself — it currently ships with one opinion-video rubric (fitted against 25+ videos from a reference creator); other formats can start from it and bump the weights. Strongly recommended to import benchmark accounts as the initial signal source (/cheat-learn-from). Trigger words: "initialize" / "score this one" / "start prediction" / "published" / "retrospective" / "upgrade rubric" / "recommend topics" / "grab trends" / "status" / "find benchmarks" / "learn from". First-time use must run /cheat-init first.
contract-cli field configuration lookup skill: query the field configuration definitions of vendor, legal_entity, and vendor_risk. Triggered when the user wants to confirm the master data field structure with `contract-cli mdm fields list`. The bot identity currently supports only vendor/legalEntity.
Design and assess Splunk index, retention, capacity, archive, storage-tier, bucket-lifecycle, and SmartStore plans from supplied requirements and evidence without changing a deployment. Use for index placement, searchable and archive windows, growth and capacity models, storage choices, restore planning, SmartStore readiness, and evidence-backed change validation. Route active incidents and provider-owned operations to their operational owners.
Design implementation-ready Splunk ingestion pipelines from known source requirements. Use for input and collector choice, processor placement, ingestion-time parsing, transformation, filtering, routing, capacity, reliability, security, validation, ownership, and implementation handoff for Splunk Cloud Platform or Splunk Enterprise. Do not use for source-onboarding discovery, production configuration, SPL, HEC endpoint work, fleet rollout, deployment, mutation, or active incident remediation.
Analyzes database migration scripts for lock contention, downtime, rollback strategy, and deployment risk. Triggers on: "analyze this migration", "migration risk", "is this migration safe", "schema change risk", "DDL risk", "rollback strategy", "migration review".
ModelScope unified operations entrypoint. Covers model/dataset search, download, and upload; repository management; Studio deployment; MCP service search, deployment, and configuration; and Skills Center search, install, and publish. Use this skill whenever the user mentions ModelScope or any platform operation. Use ms-studio-deploy for complex Studio deployment workflows; see this skill's references for the expanded MCP and Skills Center details.
Every PostHog resource in one CLI — with offline search, agent-native output, and cross-resource analytics no... Trigger phrases: `check my PostHog feature flags`, `query PostHog events`, `show experiment results in PostHog`, `what errors are spiking in PostHog`, `LLM costs in PostHog`, `is it safe to ramp this flag`, `use posthog`.
Read-only evo run reporting. Use when the user invokes /evo:report, asks what happened overnight, asks what improved recently, asks for the best/frontier candidates, asks for a quick score chart without opening the dashboard, or wants the scatter plot in chat output. Never run benchmarks, gates, Slurm commands, evo run, or ad-hoc verification scripts for report requests.
Execute raw DAX queries and inspect metadata of Microsoft Fabric Power BI semantic models via the MCP server ExecuteQuery tool. Use when the user already knows the DAX to write, wants to run EVALUATE statements, or needs to inspect model metadata (tables, columns, measures, relationships, hierarchies) using INFO functions. For natural-language business questions (where you generate the DAX), use `fabriciq`. For creating, deploying, or managing semantic model definitions, use `semantic-model-authoring`. Triggers: "run DAX query", "execute EVALUATE", "semantic model metadata", "list semantic model tables", "INFO.VIEW.TABLES", "get measure expression", "DAX against", "query the model".
Market intelligence: strategy screener, popularity rankings, top movers with news correlation, quote anomalies, index/ETF constituent stocks, morning briefings, catalyst monitoring for watchlist, event-driven strategies, ETF fund flows, sector rotation, market microstructure, supply chain analysis, industry overviews, and ARK-style disruptive innovation analysis. Triggers: "筛选", "策略筛选", "排行", "热度", "异动", "成分股", "晨报", "早报", "催化剂", "事件驱动", "ETF资金流", "板块轮动", "产业链", "行业概览", "颠覆式创新", "ARK", "篩選", "排行", "異動", "成分股", "晨報", "ETF資金流", "板塊輪動", "產業鏈", "screener", "rank", "anomaly", "constituent", "morning brief", "catalyst", "event strategy", "ETF flow", "ETF申赎", "etf flow", "资金申赎", "etf 资金", "sector rotation", "supply chain", "disruptive innovation", "板块筛选", "行业筛选", "板塊篩選", "強勢板塊", "弱勢板塊", "top sectors", "催化劑", "事件驅動", "行業概覽", "顛覆式創新", "策略篩選", "熱度"
This skill should be used when analyzing weekly price charts for stocks, stock indices, cryptocurrencies, or forex pairs. Use this skill when the user provides chart images and requests technical analysis, trend identification, support/resistance levels, scenario planning, or probability assessments based purely on chart data without consideration of news or fundamental factors.
Best practices and API reference for Terra API Lab Reports (pre-release) – convert clinical lab report PDFs and images into structured, standardized biomarker data. Use when parsing blood test results, extracting biomarkers, mapping to LOINC or UCUM unit codes, handling reference ranges, handling lab_report.completed / lab_report.failed webhooks, or working with PDF lab results and lab report OCR. Covers the async upload/standardize/deliver lifecycle, the event envelope (event_id, upload_id), the layered result model (source, biomarker, measurement, interpretation, reference ranges), unmatched-biomarker handling, snowflake IDs, and idempotent webhook processing.
Guides uniCloud cloud development in uni-app including project setup, cloud database CRUD operations, cloud function deployment, cloud storage file management, and datacom component data binding. Use when the user needs to integrate uniCloud services, work with cloud databases, create cloud functions, or manage cloud storage in a uni-app project.
Curate claude_code/codex session transcripts into a corpus of RAW .jsonl trajectory material for agentic analysis. Scans candidates by workspace/topic, lets an agent screen them and a human mark keep/drop, then copies the kept sessions byte-for-byte with a sha256 manifest. Use when extracting trajectory material, building a dataset of past agent sessions, filtering sessions by workspace, project, or topic, or when the user wants to pick conversations to keep from their agent history.
Call Alibaba Cloud SLS from Python (alibabacloud_sls20201230): ListProject (list projects), ListLogStores (list log stores), GetLogsV2 (query logs). Suitable for scenarios such as "list projects", "list LogStores", "query SLS logs", and "search and analyze logs". See reference/*.yml for the API contract; see scripts/ for runnable examples; see scripts/requirements.txt for dependencies.
Analyze whether ClickHouse indexes (PRIMARY KEY, ORDER BY, skipping indexes, projections) are effective for the actual query patterns. Use when investigating index effectiveness, ORDER BY key design, query-to-index alignment, or when queries scan far more data than expected.
Copy, clone, duplicate, rebind, and execute Gen1 dataflow save-as upgrade operations via CLI (az rest / curl) against Power BI REST and Fabric REST APIs. Covers Gen1 to Gen2.1 upgrade save-as, cross-workspace Gen1-to-Gen2.1 copy flows, connection rebinding, output changes, readiness snapshots, and SaveAsNativeArtifact execution. Use when the user wants to: (1) discover Gen1 dataflows, (2) assess save-as readiness, (3) upgrade Gen1 into Gen2.1, (4) create a Gen2.1 copy from a Gen1 dataflow in another workspace, (5) rebind connections or validate saved data. For creating/editing Gen2 dataflows from scratch, previewing candidate M, binding ordinary authoring connections, or copying Gen2 dataflows, use `dataflows-authoring-cli`. Triggers: "save Gen1 dataflow", "upgrade dataflow", "Gen1 Gen2 readiness", "Gen1 Gen2 save-as", "saveAsNativeArtifact", "copy Gen1 dataflow", "duplicate Gen1 dataflow", "clone Gen1 dataflow", "rebind Gen1 dataflow connections".
TanStack DB core concepts: createCollection with queryCollectionOptions, electricCollectionOptions, powerSyncCollectionOptions, rxdbCollectionOptions, trailBaseCollectionOptions, localOnlyCollectionOptions. Live queries via query builder (from, where, join, select, groupBy, orderBy, limit). Optimistic mutations with draft proxy (collection.insert, collection.update, collection.delete). createOptimisticAction, createTransaction, createPacedMutations. Entry point for all TanStack DB skills.
Governs Event Schema Sets, the Fabric registries of event types and message payload schemas. Covers create, rename, update and delete of a definition, and listing, property reads or base64 decoding. Every Event Schema Set task belongs here. Ingestion pipelines are eventstream-cli.
List, inspect, and monitor Fabric Eventstream real-time ingestion pipelines via the Items REST API. Discover Eventstreams across workspaces, decode base64 graph topologies tracing event flow from source through operators to destination nodes. Validate connection IDs, wiring, retention policies (1-90 days), and throughput levels. Retrieve Custom Endpoint Kafka credentials via Topology API. **Invoke this skill** to: (1) list Eventstreams, (2) inspect Eventstream topology showing sources and destinations, (3) validate Eventstream configurations, (4) check Eventstream retention policy and throughput level, (5) get connection strings. Triggers: "list eventstreams", "inspect eventstream", "describe eventstream topology", "eventstream operator nodes", "eventstream sources and destinations", "eventstream health", "eventstream status", "eventstream configuration", "eventstream retention", "eventstream throughput level", "eventstream connection string", "custom endpoint credentials", "check eventstream".
Create and populate Feishu (Lark) Bitable (multidimensional tables) with automated cleanup. Use when the user needs to: 1. Create a new Bitable from scratch with clean structure (no placeholder rows/columns) 2. Batch create fields and records in a Bitable 3. Convert structured data into a Bitable format 4. Create data tables for research, comparison, or tracking purposes Automatically handles: empty placeholder row cleanup, default column removal, intelligent primary field naming, and batch record creation.
GoldRush x402 — pay-per-request blockchain data access using the x402 protocol (HTTP 402 Payment Required). Use this skill whenever the user is building an AI agent that needs blockchain data without API keys, wants wallet-based micropayments for on-chain data, needs autonomous or no-account access to the GoldRush API, mentions the x402 protocol, or wants no-signup/no-onboarding blockchain data access. This is the right skill for autonomous agents, serverless applications, and prototyping without onboarding. Provides access to 60+ Foundational API endpoints through a transparent reverse proxy with stablecoin payments on Base. If the user needs a traditional API key with monthly billing, use goldrush-foundational-api instead. If the user needs real-time streaming data via WebSocket, use goldrush-streaming-api instead.
Replicate the macbook-metrics setup on any Mac — a local, always-on system-metrics collector (CPU, GPU, RAM, disk, network, battery, thermals) built as a Swift CLI, run by launchd every 60s, stored in SQLite, and backed up to a private GitHub repo. Use when someone wants long-term Mac performance tracking, asks how macbook-metrics works, or wants to set up the same monitoring on a new machine. Differentiator: covers the full architecture and setup ideology, not day-to-day querying of an existing install.
Pull, analyze, manage, and CREATE Meta ads (Facebook, Instagram, Messenger, Threads, Click-to-WhatsApp) via the Marketing API. Use when the user mentions Meta/FB/IG ads, Ads Manager, ROAS, CPA, CPM, CTR, ad spend, campaign or ad set performance, creative fatigue, frequency, CTWA, audience/placement breakdowns, A/B ad tests, or wants to pause an ad, change a budget, duplicate a winner, or launch a new campaign from scratch. Trigger on Hebrew terms like פרסום בפייסבוק/באינסטגרם, פרסומות מטא, ביצועי קמפיין, פרסומות, צור קמפיין, השק קמפיין, A/B טסט. Trigger on questions like how are my ads doing, which creative is winning, is my ad fatigued, what's my CPA, drop a 30-day report, launch an A/B test for my course, build a campaign with these 3 angles. Trigger even if auth isn't set up — the skill walks through one-time setup. Do NOT use for organic Instagram analytics, Reels view counts on non-promoted posts, or organic Threads engagement; those need the Instagram Graph API.
Multi-tenant architecture patterns. Database-per-tenant, schema-per-tenant, shared-schema with tenant ID, row-level security, tenant resolution, and data isolation. USE WHEN: user mentions "multi-tenant", "multitenancy", "SaaS architecture", "tenant isolation", "row-level security", "tenant ID", "subdomain routing" DO NOT USE FOR: general database design - use database skills; authentication - use auth skills
Guide for using Netlify DB (managed Neon Postgres). Use when the project needs a relational database, structured data storage, SQL queries, or data that will grow over time. Covers provisioning, raw SQL via @netlify/neon, Drizzle ORM integration, migrations, and deploy preview branching. Also covers when to use Netlify Blobs instead.
Integrate Open-Meteo Weather Forecast, Air Quality, and Geocoding APIs: query design, variable selection, timezone/timeformat/units, multi-location batching, and robust error handling. Use when fetching weather forecasts, air quality/pollen data, or geocoding place names to coordinates via Open-Meteo. Keywords: Open-Meteo, /v1/forecast, /v1/air-quality, geocoding-api, hourly, daily, current, timezone=auto, timeformat=unixtime, models, WMO weather_code, CAMS, GeoNames, httpx, FastAPI, pytest.
This skill should be used whenever the user mentions "pbir", "pbir-cli", "Power BI reports", or "PBI reports", works with .pbir, .pbip, or .pbix files, or wants to refresh, screenshot, or visually verify a report that is open in Power BI Desktop. Covers creating, exploring, formatting, validating, and publishing Power BI reports through the pbir CLI and object model, plus driving Power BI Desktop (canvas reload, page screenshots) and querying connected or local semantic models.
PostgreSQL best practices: multi-tenancy with RLS, schema design, Alembic migrations, async SQLAlchemy, and query optimization. Use when designing multi-tenant tables with Row-Level Security, debugging tenant isolation, creating/changing Alembic migrations, or optimizing PostgreSQL queries. Keywords: PostgreSQL, RLS, Alembic, SQLAlchemy, multi-tenancy.
Provides comprehensive guidance for Redis including data structures (string/hash/list/set/zset/geo/hyperloglog/bitmap/stream), common commands with examples, caching patterns, persistence (RDB/AOF), replication & sentinel, cluster, Lua scripting, transactions, pub/sub, pipelining, security hardening, and production best practices. Use when the user asks about Redis, needs to implement caching, choose Redis data structures, configure persistence or cluster, or troubleshoot Redis performance.
Define evidence-bounded Splunk report contracts and readiness findings for scheduled and ad hoc reports without creating, running, scheduling, editing, or sending them. Use when a requester needs the business question, search-definition handoff, time range and timezone, cadence and schedule window, recipients and formats, permission prerequisites, acceptance evidence, Cloud or Enterprise ownership, or a report-specific incident handoff. Route SPL to Splunk Search, broad ownership and ACL work to Knowledge Object Governance, action delivery to Alerting and Notable Workflows, acceleration to Data Model and Search Acceleration, and active platform incidents to platform operations.
Use when working with RisingWave — streaming SQL database, materialized views, sources, sinks, CDC from PostgreSQL/MySQL, Kafka ingestion, time windows (TUMBLE/HOP/SESSION), watermarks, EMIT ON WINDOW CLOSE, port 4566, risingwave-mcp, event streaming pipeline design, real-time analytics, stream processing
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.