Skills
100,928 packaged capabilities and playbooks for agents. Install any of them with one command.
All
Writes and reviews Swift observability code on Apple platforms - unified logging (Logger, OSLog, privacy redaction, log levels and persistence), signposts and Instruments, activity tracing, MetricKit metrics and diagnostics (launch, hangs, crashes, OOM, disk writes), crash reports and symbolication, OSLogStore log export, Xcode Organizer, and shipping telemetry to your own backend or third-party SDKs. Use when adding logging, instrumenting performance, wiring MetricKit, diagnosing production crashes or hangs, exporting logs for support, or choosing between print, Logger, signposts, and analytics SDKs.
Open-source bio-image data management. Use the omero-py client to connect to an OMERO server, retrieve images as numpy arrays, annotate with tags and key-value pairs, manage ROIs, and feed image data into Python analysis pipelines — programmatically, no GUI.
Meta-skill for building and managing agent persona skill packs (instruction-only; no bundled installer or auto-downloaded binaries). Credentials are never written into generated packs by the framework; publish/ACN/register require explicit user CLI. Use when the user wants to create a new agent persona, install/manage existing personas, or publish persona skill packs to OpenPersona.
Edit a video file from your agent with OpenClip - trim, crop, reframe to 9:16 or 1:1, resize, rotate, flip, compress to a target size, or mute the audio. FREE with just an OpenClip account, no subscription. Use when asked to "cut this video down", "trim to 30 seconds", "make it vertical", "crop to 9:16", "resize this video", "compress this, it is too big", "rotate this clip", "remove the audio", or "edit this video".
Create, test, evaluate, optimize, and package OpenCode skills with the opencode-skill-creator plugin. Use when users explicitly mention opencode-skill-creator, OpenCode Skill Creator, creating an OpenCode skill, editing an OpenCode SKILL.md, running skill evals, benchmarking skill performance, or optimizing an OpenCode skill description. Do not use for generic Claude Code or Superpowers skill creation unless the user asks to port that workflow to OpenCode.
OpenSpec spec-driven development assistant - an AI-assisted coding framework based on the OPSX workflow. Agree with the AI on requirements before writing code, and manage changes with a Schema-driven artifact dependency system. Triggers (any one of these): 1. The user mentions "openspec", "opsx", spec-driven development, spec-driven. 2. The user wants to start new feature development, refactoring, or exploring complex requirements. 3. The user complains about AI misunderstanding or frequent rework. 4. The user uses slash commands such as /opsx:new, /opsx:ff, /opsx:apply. 5. When initializing a project or preparing major changes. 6. When spec documents such as proposal, design, tasks need to be generated. Recommended for: improving existing projects (brownfield development), critical features requiring high-quality implementation, team collaboration. Not recommended for: rapid prototype validation (0→1 exploration), one-off small scripts, highly ambiguous exploratory innovation.
Run a candidate against the baseline over an Opik test suite and read the numbers back — which cases broke, which got fixed, the per-metric deltas, worst rows, and whether the two runs are comparable — with the Opik compare-view link. Runs via the SDK; reads results via the MCP when connected. Does not issue a ship/no-ship verdict. Use for "did my fix work", "compare against the baseline", "run the regression suite", "why did quality drop", "which cases regressed", "compare these two experiments". Not for the ship/hold decision itself (use verify), live production triage (use diagnose), building an evaluation from scratch (use evaluate), or capturing a single case (use test).
Turn a failing Opik trace (or a described failure) into a repeatable regression check — a test-suite item with the trace's input and one or two binary assertions — so a fix can be verified by the compare skill. Works over the SDK; uses the MCP write tool when connected. Returns the suite, the item, and the assertion. Use for "turn this into a test", "add a regression case for this trace", "make sure this doesn't happen again", "capture this failure", "add this to the test suite". Not for running the suite (use compare), building an evaluation from scratch (use evaluate), or explaining why the trace failed (use explain)
Step 1 of the PaperOrchestra pipeline (arXiv:2604.05018). Convert (idea.md, experimental_log.md, template.tex, conference_guidelines.md) into a strict JSON outline containing a plotting plan, literature search plan (Intro + Related Work), and section-level writing plan with citation hints. TRIGGER when the orchestrator delegates Step 1 or when the user asks to "outline a paper from raw materials" or "generate the paper structure".
Operator toolkit for nf-core/pacsomatic matched tumor-normal workflows from BAM inputs. Use this skill when the user needs to validate run inputs, generate pacsomatic-compliant samplesheets, prepare reproducible Nextflow launch artifacts, run locally or submit to schedulers (LSF/Slurm/PBS/SGE), and triage execution failures. Triggers on requests to run pacsomatic, prepare launch commands/scripts, perform dry-run checks, or troubleshoot pipeline startup and scheduler submission errors.
Coordinate safe, evidence-based paid-media work across Google Ads, Meta Ads, X Ads, LinkedIn Ads, Reddit Ads, TikTok Ads, Amazon, and ChatGPT Ads. Use for broad ads questions, multi-channel strategy, budgets, CPA or ROAS, campaign requests, spend, ad performance, or when routing to the right NotFair paid-ads skill.
Audit, diagnose, and safely operate connected TikTok Ads accounts through the NotFair MCP. Use for TikTok advertising, Spark Ads, short-form video ads, campaign or ad-group analysis, spend, conversions, targeting, creative, budgets, bids, creator briefs, campaign setup, or approved TikTok Ads changes.
Query live pathogen genomic surveillance data through the GenSpectrum LAPIS API to find which viral lineages are circulating now, how fast they are growing, and what mutations they carry. Use whenever a question depends on the current state of a pathogen population rather than on remembered facts - which SARS-CoV-2 variant is dominant, whether a Pango lineage is still designated or has been withdrawn, what clade or genotype of H5N1 is in a host or region, whether a PCR primer or assay target still matches circulating sequence, or how a lineage's prevalence has moved week to week. Triggers include "variant surveillance", "genomic surveillance", "what variant is circulating", "dominant variant", "Pango lineage", "lineage prevalence", "growth advantage", "SARS-CoV-2 variant", "XFG", "clade 2.3.4.4b", "H5N1 genotype", "influenza clade", "RSV/mpox/measles/dengue lineage", "CoV-Spectrum", "LAPIS", "Nextclade", "pango-designation", and any request to report what a pathogen population looks like today.
Reusable approval-loop pattern for fanning out lead personalization across parallel Claude Code Task sub-agents. Shows the user 1 sample personalization, collects feedback, runs 10 more, approves, runs 10 more — stops when 2 consecutive rounds have zero edits, then scales to the full list. ALWAYS uses Claude Code Task tool sub-agents — never an external Anthropic/OpenAI API key. Use when any skill needs per-lead custom variables (situation lines, value lines, CTAs).
This skill MUST be used for PESTEL or PEST analysis, 總體環境分析、外部環境掃描、 宏觀環境分析, and when SWOT needs macro-environment evidence. It SHOULD also be used when strategic planning, market entry, or competitive assessment requires mapping political, economic, social, technological, environmental, and legal changes affecting a company, industry, product, or target market.
Configure PetroPy fluid-property and multimineral formation evaluation from normalized LAS well logs. Use for calibrated porosity, water saturation, mineral and pore-volume estimation, missing-sample handling, and explicitly defined pay intervals. Requires documented log units, fluid parameters and mineral endpoints; standalone permeability correlations need separate methods.
Pi packages — npm/git distribution of extensions, skills, prompts, themes via keywords pi-package and package.json pi manifest; pi install paths and security expectations. Use when shipping or consuming pi-package, adding pi.skills entries, or explaining install vs project-local -l. Use for "publish pi skills on npm", "pi install", "pi-package.json", even without naming this skill.
First Time User Experience (FTUE) design that teaches through play, hooks players in 30 seconds, and retains them for lifeUse when "tutorial, onboarding, teach player, first time user, FTUE, new player experience, how to teach, teaching mechanics, tutorial level, intro sequence, player retention, drop-off, skip tutorial, contextual hints, help system, onboarding, tutorial, ftue, first-time-user-experience, player-retention, teaching, learning, progressive-disclosure, difficulty-curve, new-player-experience, hooks, engagement" mentioned.
Optimize CI/CD pipelines by caching Playwright browser binaries and dependencies to speed up test execution. Use when setting up Playwright in CI/CD pipelines, reducing build times by caching browser binaries, or configuring GitHub Actions or Azure DevOps for Playwright tests.
Tracking and metrics design generator. Starting from product requirements or the core user journey, output a complete tracking plan document (events, fields, trigger timing, metric definitions, QA validation checklist). Trigger conditions: the user mentions keywords such as "tracking", "event design", "data collection", "reporting plan", "tracking plan", "event spec", "field design", "metric definitions", "data acceptance", or "QA validation". Also applies when: the user provides a product PRD or requirements document and asks for a tracking plan; the user provides a core user journey and asks to break down events; the user asks to standardize event naming or field definitions; the user asks to design a data acceptance plan. Typical input: event naming spec + field dictionary + core journey description/flowchart. Not applicable to: pure data analysis (use pm-analytics), pure BI dashboard building, or pure SQL query writing.
Maintain an agent-created pull request after creation or after draft-to-ready transition: mark reviewable draft PRs ready, poll CI and review comments with gh, repair failures in the same worktree/session, reply in Japanese, escalate design loops, and squash merge when safe. This skill defines the maintenance POLICY (what to repair, when to merge/escalate); the autonomous re-polling LOOP that reschedules itself without human restarts lives in pr-autoloop. Use after creating PRs or when asked to continue PR maintenance automation.
Write production-ready print stylesheets. Covers @page rules, page breaks, visibility, color management, typography, images, links, tables, and framework-specific gotchas for Next.js/React/Tailwind. Use when the user asks to add print styles, make a page printable, or create a print-friendly layout.
This skill should be used when analyzing PostgreSQL performance reports, including pasted PostgreSQL reports, or when users mention db report, database performance, dead rows, VACUUM, sequential scans, unused indexes, or cache hit ratio. It provides PostgreSQL triage heuristics, priority ranking, and action-plan guidance for Drizzle ORM codebases.
Use this skill to design new products, iterate on product ideas, or develop product specifications. Triggers: "design product", "new product idea", "product concept", "product development", "product spec", "iterate on product", "product design", "invention", "prototype spec", "product requirements", "product engineering", "develop product" Outputs: Product specification, BOM estimate, feature breakdown, differentiation analysis.
Use this skill when troubleshooting production or test incidents such as slow endpoints, high latency, OOMKilled pod restarts, pod crashes or throttling, slow queries, Sentry-reported errors and traces, post-deploy watches, before/after deployment metrics, or 503 responses during or after a rollout
Query Prometheus API for cluster metrics, alerts, and observability data. Use when investigating cluster health, performance issues, resource utilization, or alert status. Triggers on questions like "what's the CPU usage", "show me firing alerts", "check memory pressure", "query prometheus for", or any PromQL-related requests.
protocols.io REST API: search and fetch wet-lab, bioinformatics, and clinical protocols by keyword, DOI, or category, with steps, reagents, materials, equipment, timing. Public access free; auth needed for private or publishing. Pair with opentrons-protocol-api or benchling-integration to execute.
Reads, inspects, writes, and transforms local DICOM files with pydicom 3.x (dcmread, dcmwrite, pydicom.pixels), including metadata, transfer syntaxes, compressed pixel data plugins, frame decoding, private elements, DICOM JSON, and bounded pseudonymization review using bundled helper scripts. Use when extracting aggregate metadata from DICOM datasets without printing PHI, checking which transfer syntaxes and codec plugins a deployment needs, planning frame or memory limits before decoding pixel data, rendering one non-diagnostic frame, compressing or decompressing pixel data, or building and auditing a pseudonymized derivative. Not for diagnostic viewing, or for claiming DICOM PS3.15, HIPAA, or GDPR compliance.
Respond to questions from Qian Xuesen's perspective - systems engineering thinking, interdisciplinary integration, and the unity of aerospace spirit and engineering philosophy. Use when the user explicitly asks to use this figure's perspective, mentions "qianxuesen-perspective", or wants to apply its core methods to analyze a problem; do not trigger automatically for general questions.
Opinionated Rails conventions: rich models, concerns, CRUD-everything, state-as-records, minimal dependencies, Minitest with fixtures. Load this skill BEFORE any code-level thinking, not only before editing a file. It is required the moment a task touches Rails code in ANY way: designing or even just discussing a data model, schema, migration, entity, association, field, validation, class, or method name; writing, planning, reviewing, analyzing, testing, debugging, or refactoring; or proposing any model, table, column, route, or code snippet inline in chat. If you are about to name a model or sketch a column you are already in scope, even in an exploratory back-and-forth where no file is written yet. Do not let a \"we're just discussing\" framing defer it. Do NOT use for non-Rails backends, NestJS, or general architecture (use nestjs-modular-monolith or coding-guidelines).
Software-cracking gateway. Orchestration: unpack the protected binary first → locate authorization checks → patch/keygen. Subskills: [[re-license]] [[re-patching]] [[re-keygen]] [[re-drm]]. Triggers: 破解, crack, registration code, serial number, license verification, bypass verification, patch, keygen, key generator, license bypass.
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.