Skills
101,174 packaged capabilities and playbooks for agents. Install any of them with one command.
All
Registers external HTTP endpoints as iii functions using registerFunction(meta, HttpInvocationConfig). Use when adapting legacy APIs, third-party webhooks, or immutable services into triggerable iii functions, especially when prompts ask for endpoint maps like { path, id } iterated into registerFunction calls.
Builds trigger-transform-action automation chains on the iii engine. Use when building Zapier/n8n-style automations, webhook-to-action pipelines, or simple event-driven chains where each node is a small registered function chained via named queues.
Builds reactive real-time backends on the iii engine. Use when building event-driven apps where state changes automatically trigger side effects, clients receive live updates via streams or websockets, or you need a real-time database layer with pub/sub and CRUD endpoints.
Selects how functions are invoked — synchronous calls that return results, fire-and-forget void dispatches, or durable enqueue through named queues with retries. Use when deciding between blocking RPC calls, background job dispatch, async workers, or reliable message delivery with acknowledgement.
Continue pretraining from an existing KERMT checkpoint. The skill validates the user's checkpoint and pretrain CSV, prepares the data into shard/vocab/features form, then launches pretrain_ddp.py inside the kermt container (detached for long runs). Auto-dispatches `--pretrain_mode` based on the checkpoint type (grover_base vocab-only, cmim, or hybrid).
Two scopes: (1) Drives Kimi.app via computer-use for Work/Agent data-plugin queries (天眼查、同花顺 iFinD、SEC、IMF etc.) and Chat's built-in 深度研究 report; (2) kimi-cu macOS desktop-automation playbook — AX set_value / keyboard / click channel selection, foregrounding, AX-tree recovery, form & dialog recipes. Use for "用 Kimi 查" / "操作 Kimi 客户端" / "Kimi 插件" / "Kimi 深度研究" / driving any macOS desktop app (Electron/webview/native) via kimi-cu. Not for kimi.com browser automation (use kimi-webbridge) or direct iFinD API access.
This skill should be used when working with LaminDB, an open-source data framework for biology that makes data queryable, traceable, reproducible, and FAIR. Use when managing biological datasets (scRNA-seq, spatial, flow cytometry, etc.), tracking computational workflows, curating and validating data with biological ontologies, building data lakehouses, or ensuring data lineage and reproducibility in biological research. Covers data management, annotation, ontologies (genes, cell types, diseases, tissues), schema validation, integrations with workflow managers (Nextflow, Snakemake) and MLOps platforms (W&B, MLflow), and deployment strategies
Cổng sức khoẻ tổng / tuyến phòng thủ cuối của framework overstack — gõ /medic (hoặc `medic` ở CLI) để CHỨNG MINH hệ còn khoẻ trong MỘT lệnh: luật còn cắn (harness-doctor fire-drill), validator không lệch bản (drift), docs khớp đĩa, code compile, eval không regress, backstop git sống. Hub 1-tên — mô tả PHẠM VI thay vì nhớ subcommand (`medic` = all · `medic rules` · `medic docs eval`). Dùng trước commit/PR, sau khi pull/đổi máy, khi nghi một rule không chặn nữa, hoặc vừa thêm skill/rule/generator (medic tự báo nếu quên hàng rào). Trigger: /medic, "medic", "chạy medic", "hệ còn khoẻ không", "rà luật có cắn không", "cổng phòng thủ cuối", "health gate", "last line of defense".
Build NEAR Protocol dApps. Use for: (1) creating new NEAR dApps with `create-near-app` (Vite+React, Next.js), (2) adding NEAR wallet connection to existing apps with `@hot-labs/near-connect` and `near-connect-hooks`, (3) building frontend UI for NEAR smart contracts, (4) integrating wallet sign-in/sign-out, contract calls, and transaction signing into web applications.
TypeScript library for NEAR Protocol blockchain interaction. Use this skill when writing code that interacts with NEAR Protocol, including viewing contract data, calling contract methods, sending NEAR tokens, building transactions, creating type-safe contract wrappers, integrating wallets (Wallet Selector, HOT Connect), React hooks and providers (@near-kit/react), managing keys, testing with sandbox, meta-transactions (NEP-366), and message signing (NEP-413).
Use this skill when choosing or running NeMo Relay installation for an agent runtime, application language, framework integration, or plugin bundle, or checking a runtime's native Relay readiness. Do not use it for first-run instrumentation or export configuration.
KRACK (CVE-2017-13077..082) and FragAttacks (CVE-2020-24586..588 + 26139-26147) — key reinstallation, fragmentation, and aggregation attacks against WPA2 supplicants. Covers Vanhoef's test scripts, viability against modern patched stacks (mostly mitigated post-2021), residual unpatched embedded devices and IoT vendors, and the practical limitations of these attacks in modern engagements. Use when assessing legacy supplicants, embedded clients, or vendors with poor patch cadence.
WPA3 / SAE (Simultaneous Authentication of Equals) attack methodology — transition-mode (mixed WPA2/WPA3) downgrade, Dragonblood side-channel attacks (CVE-2019-9494, 9495, 13377, 13456), SAE auth flooding for AP CPU exhaustion, Hash-to-Element (H2E) timing analysis, group downgrade, and 6 GHz / Wi-Fi 6E spec implications (PMF mandatory, no transition mode allowed). Use when target advertises WPA3-SAE or WPA3-Personal/Enterprise, or operates in 6 GHz where WPA3 + PMF are required by spec.
WPS (Wi-Fi Protected Setup) PIN attack methodology — Pixie Dust offline attack against vulnerable chipsets (Ralink, Realtek, Broadcom, MediaTek), online PIN brute-force with reaver/bully, lockout handling, time-of-day evasion, WPS push-button vulnerability windows, and PIN-to-PSK derivation. Use when a target SOHO router exposes WPS — common on consumer ISP gear, often left enabled by default even when WPS attacks have been known for over a decade.
Use when the user invokes Pipa or asks to plan a service-business workday, shut down work for the day, or prepare tomorrow. Routes business operations to get work, define work, deliver work, get paid, keep clients, improve operations, Manage Pipa, or Pipa Tools.
Handle event-triggered automations for Pipa. Use whenever the user wants Pipa to run a workflow when an external event occurs, such as a GitHub PR opening, a Linear issue being created, a Slack channel changing, or a new ticket arriving, or asks to list, inspect, or delete existing event triggers. This skill handles trigger proposals, confirmation, and gateway trigger-subscription API calls.
Generate leftover PlantUML types Mermaid cannot do easily (Salt wireframes, use case, timing, ArchiMate, nwdiag, WBS) and convert them to PNG/SVG. Use when asked for a wireframe, PlantUML image export, extract puml from markdown, or prepare Confluence uploads. Class, ER, state, sequence, and C4 default to design-doc-mermaid on GitHub wiki.
Create and configure surveys in PostHog through guided conversation. Use this skill when a user wants to create a survey, collect user feedback, run NPS/CSAT/CES/PMF surveys, gather product feedback, or understand user sentiment. The skill guides Product Managers through survey design by matching their goals to proven templates (or creating custom surveys), then configuring targeting and scheduling before creating via PostHog MCP tools.
Python interface to OpenMS for mass spectrometry data analysis. Use for LC-MS/MS proteomics and metabolomics workflows including file handling (mzML, mzXML, mzTab, FASTA, pepXML, protXML, mzIdentML), signal processing, feature detection, peptide identification, and quantitative analysis. Apply when working with mass spectrometry data, analyzing proteomics experiments, or processing metabolomics datasets
Build a phased reputation recovery plan after a crisis — from damage assessment through stakeholder communication, trust-rebuilding actions, and sentiment tracking. Use when: rebuilding brand reputation post-crisis, designing a public apology and accountability strategy, creating stakeholder-specific recovery communications, tracking sentiment recovery metrics, planning a PR damage-control roadmap, or recovering from a data breach, product recall, or public backlash.
Generates RSpec tests in Ruby with describe/context/it blocks, matchers, let/before hooks, and mocking. Use when user mentions "RSpec", "describe do", "expect().to", "Ruby test". Triggers on: "RSpec", "expect().to eq()", "describe do", "Ruby test", "spec file".
Methodology playbook for analyzing tokenized real-world assets (RWA) on Allium—tokenized treasuries, money market funds, tokenized equities/pre-IPO stocks, commodities, and private credit. Use whenever a question touches RWA supply, AUM, market cap, holders, mint/burn activity, or classification—even if the user just says "tokenized treasuries," "BUIDL," "tokenized stocks," "money market fund AUM growth," or names a specific RWA product/issuer. Covers aggregation mistakes, classification pitfalls, and data-quality exclusions that commonly arise in real RWA questions before writing SQL
Deep-dive security posture assessment by analyzing IAM policies, encryption configs, network rules, and security controls in code to produce evidence-backed findings aligned with the Well-Architected Security pillar
Generate advertising video prompts for e-commerce products using Seedance 2.0 (Higgsfield). Use when the user wants a product ad, e-commerce video, product showcase, unboxing, product demo, shopping ad, fashion ad, beauty ad, food ad, or any commercial product video for online sales. Triggers include product ads, e-commerce, product showcases, Amazon videos, Shopify ads, Instagram shops, TikTok shops, product commercials, fashion videos, beauty ads, food ads, product demos, dropshipping videos, or any product promotion video request. Also triggers for requests like “make a video for my product” or “product promotion.”
Complete ready-to-use page templates built with SGDS components and utilities. Use this skill whenever a user asks to build a page, dashboard, login page, form page, settings page, list page, or any full-page UI — even if they don't say “template”. Apply when starting a new app, building internal tools, dashboards, admin portals, authentication flows, or data table views
Validate simulations across three stages — run pre-flight checks on configuration files (parameter ranges, required fields, disk space), monitor runtime logs for residual growth, NaN/Inf, and adaptive dt collapse, and perform post-flight validation of results (physical bounds, mass/energy conservation, convergence). Diagnose failed simulations with probable-cause analysis and recommended fixes. Use when preparing to launch a simulation, checking whether a running job is healthy, verifying that finished results are trustworthy, or debugging a crash or blow-up, even if the user only says "my simulation crashed" or "can I trust these results."
Implements Syncfusion .NET MAUI Avatar View (SfAvatarView) for displaying user profile pictures, initials, or group avatars. Use when working with avatar views, profile pictures, user images, initials display, profile icons, or contact images. Ideal for implementing user profile displays, contact lists, chat interfaces, or social feeds.
Implements Syncfusion .NET MAUI Busy Indicator (SfBusyIndicator) for showing loading states, data processing, and app activity indicators. Use when displaying loading indicators, busy animations, activity spinners, or processing feedback in .NET MAUI apps. Covers busy indicator setup, animations, and visual feedback during long-running operations.
Search and analyze Tencent Cloud CLS (Cloud Log Service) logs. Use whenever the user asks to: search logs, debug API errors, trace requests by trace ID, find 5xx errors, run CQL/SQL analytics over log topics, extract structured fields. Backed by the official tencentcloud-sdk-python CLS client
Dodo Payments test mode and production launch, covering test cards and payment methods, success and decline scenarios, renewal simulation, local webhook testing with the CLI, copying products from test to live, and a go-live checklist. Use when verifying payment flows, switching from test_mode to live_mode, or preparing to launch
Trust Wallet open-source libraries — Wallet Core (HD wallets, address derivation, tx signing in Swift/Kotlin/TypeScript/Go for 140+ chains), Web3 Provider (dApp connection for Ethereum/Solana/Cosmos/Bitcoin/Aptos/TON/Tron), deep linking, browser extension integration, WalletConnect, token assets repository, and Barz ERC-4337 smart wallet. Use when working with trustwallet/wallet-core, @trustwallet/wallet-core, trust-web3-provider, Trust Wallet deep links, token logos/metadata from trustwallet/assets, or Barz account abstraction.
Draft or review an Upwork proposal (cover letter) using the five-move method extracted from a Top Rated Plus freelancer's winning proposals, corrected for the AI era. Use when the user shares an Upwork job post and wants a proposal drafted, or shares an existing proposal draft and wants it reviewed. Triggers include "write a proposal", "apply for this job", "bid on this", "cover letter for this Upwork job", "review my proposal". Works for design, dev, and adjacent creative/tech freelance jobs
Provider-independent VFX compositing direction for generated video, ads, trailers, product films, social clips, explainers, mixed-source edits, and image/video composites. Use when an agent must plan, brief, generate, integrate, repair, or quality-check visual effects composites involving plates, alpha/mattes, keying, roto, tracking, stabilization, matchmove, lighting/color integration, grain/noise/sharpness, shadows/reflections/contact, depth/atmosphere, AI-generated elements, clean plates, editor/colorist handoff, rights/safety, or compositing QA.
Translate a creative brief, brand system, or reference set into an original, portable visual-direction system for image and video production. Use for art direction, reference analysis without imitation, design tokens, palette and contrast, typography, composition, texture and material, lighting, lens and camera language, motion language, cross-shot continuity, accessibility, production handoff, visual review, and repair; do not use for provider-specific API syntax or model-specific prompt recipes.
Collection of essential Vue Composition Utilities. ALWAYS use when writing code that imports "@vueuse/core" or "@vueuse/shared" (VueUse). Provides the v15.0.0 API surface, v14 to v15 migration rules, new composables (useWebMCP, useTemporalNow, useLiveAnnouncer, useElementOverflow), deprecations, and configuration best practices.
Enforces a disciplined widget/layout/golden/a11y test surface — one pumpApp harness that pins tester.view.physicalSize x devicePixelRatio and layers MediaQuery (textScaler/boldText/accessibleNavigation) above MaterialApp, an overflow net that never suppresses (one testWidgets per device x scale x bold tuple because overflow reports once per RenderObject), a computed getSize/getRect fit-and-geometry gate instead of goldens, two golden lanes (Ahem geometry + one pinned-OS real-font) with loadAppFonts and blocked --update-goldens, RTL goldens under Directionality, pure-Dart WCAG/APCA contrast on colour VALUES, and honest limits on meetsGuideline. Use when writing test/support/harness.dart, calling pumpWidget/pumpApp, chasing an "overflowed by N pixels" failure, reaching for takeException/ignoreOverflowErrors/FittedBox/withClampedTextScaling, adding matchesGoldenFile, or writing a11y_test.dart with isSemantics/simulatedAccessibilityTraversal/meetsGuideline.
Integrate any number of feature branches from parallel worktrees through one safe integration branch, validating after each merge and running the project's full check suite before touching the main line. Use when parallel worktree development is done and the branches need to be merged, or when the user says "merge my worktrees", "integrate these branches", or invokes /worktree-merge.
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.