Skills
97,222 packaged capabilities and playbooks for agents. Install any of them with one command.
All
Write competitive research proposals for NSF, NIH, DOE, DARPA, and Taiwan NSTC. Agency-specific formatting, review criteria, budget preparation, broader impacts, significance statements, innovation narratives, and compliance with submission requirements.
Use when the user explicitly asks to "update the project guide", "sync the guide", "capture insights into the guide", or requests the skill by its former name guide-updater. Captures reusable writing insights from the conversation into the project guide file in real time, keeping terminology consistent, the structure stable, and the content testable and reproducible. The guide file path must be specified when invoking.
Comprehensive multi-wave web research with strategic source selection. Gathers information from official docs, community resources, and advanced sources. Use for deep technical research, API documentation, best practices. Triggers: research web, deep research, comprehensive research, find documentation.
Plan and optimize resource allocation. Trigger with "resource planning", "capacity", "utilization", "staffing plan", "who should work on what", "we're stretched thin", or when the user needs help allocating people, budget, or time across projects and teams.
Draft professional, empathetic customer-facing responses adapted to the situation, urgency, and channel. Use when responding to customer tickets, escalations, outage notifications, bug reports, feature requests, or any customer-facing communication.
Help users generate a professional Chinese resume (in both HTML and DOCX) in one pass based on any background material (old resume, JD, work log, etc.), with ATS optimization, role-specific skill dimensions, page-count control, and automatic senior job-search advisor suggestions after generation. Trigger scenarios: user requests "帮我生成简历", "写简历", "改简历", "我要投一个岗位", or any request involving creating, editing or optimizing a resume.
Designs and implements data retention schedules compliant with GDPR Article 5(1)(e) storage limitation principle. Maps data categories to retention periods with legal basis justification, regulatory minimum holding periods, and automated review triggers for schedule maintenance. Activate for retention policy, storage limitation, data lifecycle, retention period queries.
Use when a Claude Code or Codex session ends or is declared finished, a friction needs fixing, a reusable learning needs capturing, local memory needs promoting upward, or for cross-session audits — detect friction AND learnings, route each to the right destination, and gate 'done'. Triggers: /retro, /retro done, 'retrospective', 'capture this learning', 'fix this skill', 'promote memory', 'audit', 'alles erledigt'.
Review and approve (or reject) pending update proposals from the review guideline monitoring agent, and apply approved changes to the practice-area configuration. Use when the review guideline monitoring agent proposes suggestions, or when the user says "review review guideline suggestions," "what pending review guideline updates are there," or wants to work through deviation-driven review guideline changes one by one.
Write an engineering RFC (Request for Comments) for a technical decision, architectural change, or significant implementation approach. Use when asked to write an RFC, document a technical proposal, create a design doc, write an architecture decision for review, or produce a technical specification for team feedback. Produces a complete RFC document covering problem statement, motivation, proposed solution, alternatives rejected, implementation plan, migration plan, security and performance implications, observability changes, rollout plan, and open questions.
Identify, assess, and mitigate operational risks. Trigger with “what are the risks”, “risk assessment”, “risk register”, “what could go wrong”, or when the user is evaluating risks associated with a project, vendor, process, or decision.
Generates RESTful API documentation (OpenAPI 3.0 / Swagger spec) by scanning route definitions in code for Flask, FastAPI, Express, Gin, and other frameworks. Trigger when users ask about API documentation, OpenAPI, Swagger, endpoint docs, generating docs from code, or extracting endpoints.
Search Reddit posts through the browser via CDP. Returns structured results (title, subreddit, author, score, comments, permalink URL, selftext, media URLs) for any query, with optional subreddit restriction and sort/time filters. Use when the user asks to search Reddit, find discussions or posts, or gauge community sentiment on a topic. Requires browser-harness-js on PATH and a Chromium-based browser with remote debugging; no Reddit API key — works logged-out, and a logged-in reddit session is used automatically if present.
Use this in code repositories whenever an agent needs to run terminal commands, inspect files, search code, view Git status or diffs, run builds, tests, linters, type checks, package managers, logs, Docker, Kubernetes, or database commands. This skill makes the agent prefer RTK wrappers to reduce noisy command output and save context tokens. Do not use for non-coding conversations.
End-to-end Coval audio-quality testing workflow. Launches one run per audio-robustness scenario against the same voice agent + test set + metrics, polls for completion, and produces the multi-run report URL grouped by Persona. Use when a user wants to follow the Testing Across Audio Qualities cookbook (https://docs.coval.dev/guides/testing-across-audio-qualities) without doing each step by hand.
Installing the Rust toolchain on Windows (including projects that need a C compiler, such as rusqlite). Covers rustup mirror acceleration in China, fixing "Missing manifest", choosing MinGW/MSVC, and the PATH pitfalls of dlltool/ld. Use when setting up a Rust environment on Windows or hitting 'Missing manifest' / 'dlltool not found' errors.
Diagnose what's maintaining an entrenched behavior and design the right intervention to shift it. Covers habits, routines, and behavioral defaults. Triggers: 'how do I change this behavior', 'why does this habit persist', 'how do I make this stick', 'behavior change', 'breaking a habit', 'building a habit', 'why can't I stop doing X', 'how do I get people to consistently do Y', 'implementation intentions', 'habit loop'.
Assess the fast-thinking pattern at work — when it's reliable, when it misleads, and whether to trust or override it. Triggers: 'should I trust my gut', 'is my intuition right here', 'fast thinking', 'heuristic', 'when does instinct work', 'System 1 vs System 2', 'pattern recognition', 'am I just pattern matching', 'is this a gut check or analysis question'.
Produces executive summaries, 1-page briefs, and board-level documents by extracting the situation, key findings, implications, and recommendation — answer-first, one page maximum. Use when a lengthy document needs a senior-audience brief that enables a decision. Triggers: 'executive summary', 'summarise this for a senior audience', '1-page brief', 'TL;DR for leadership', 'distil this', 'board summary', 'write a brief'.
Senior SaaS CFO / Financial Analyst (15+ years) specialized in financial modeling, projections, and exit strategy for bootstrapped and VC-backed SaaS companies. Activate when user needs: (1) Revenue projections (1-5 years), (2) Exit valuation and multiples, (3) Unit economics analysis (CAC, LTV, payback), (4) Scenario modeling (conservative/base/optimistic), (5) Fundraising narratives with financial backing, (6) M&A due diligence financials, (7) SaaS metrics benchmarking, (8) Cohort analysis and churn modeling. Triggers: "proyecciones", "projections", "exit", "valuation", "ARR", "MRR", "multiples", "revenue forecast", "financial model", "exit strategy", "CAC", "LTV", "unit economics", "churn", "fundraising", "M&A", "acquisition", "5 year plan".
Reference: SaaS subscription agreement review, focusing on the clauses most critical in subscription deals — automatic renewal mechanics, price adjustments, data portability, uptime SLAs and subprocessor rights. Loaded when /commercial-legal:review detects a SaaS or subscription agreement.
Kit (formerly ConvertKit) platform help — email marketing, visual automations, sequences, landing pages, forms, Creator Profile, Commerce (digital products, paid newsletters), Creator Recommendations, subscriber tagging and segmentation, engagement scoring, API. Use when Kit emails aren't sending or formatting right, automations not triggering, subscribers stuck or not tagging correctly, digital product sales not working, or Kit API calls failing. Do NOT use for cross-platform email marketing strategy (use /sales-email-marketing), cross-platform deliverability (use /sales-deliverability), funnel strategy (use /sales-funnel), newsletter monetization strategy (use /sales-newsletter), audience growth strategy (use /sales-audience-growth), or digital product strategy (use /sales-digital-products).
Newsletter monetization — paid subscriptions, sponsorships, ad sales, paid recommendations, premium tiers, pricing strategy, subscriber-to-revenue conversion. Use when your newsletter isn't generating revenue, paid subscribers aren't converting, can't find sponsors, unsure how to price a premium tier, or torn between ad-supported and subscription models. Do NOT use for sending email campaigns (use /sales-email-marketing), growing your subscriber list (use /sales-audience-growth), or platform-specific setup (use /sales-kit, /sales-mailchimp, etc.).
SafetyMails platform help — bulk email verification (up to 2M emails, 19-step algorithm), real-time API validation (JavaScript embed for forms), Email Finder (B2B corporate lookup), list cleaning, spamtrap/disposable/catch-all detection, integrations. Use when your email list has too many bounces, SafetyMails verification results look wrong, the JavaScript embed isn't catching bad emails on your forms, Email Finder isn't returning corporate addresses, or integrations aren't syncing verified results. Do NOT use for general deliverability strategy across tools (use /sales-deliverability), general enrichment strategy (use /sales-enrich), building prospect lists (use /sales-prospect-list), or connecting tools generically (use /sales-integration).
Query, read, create, update, and describe Salesforce records — Accounts, Contacts, Opportunities, Leads, Cases, and custom objects. Use this whenever the user wants to look up a Salesforce record, run a SOQL query, update an Opportunity, check an object's fields, or asks "what's in Salesforce" — even if they don't say "API". Also use it for any URL under *.salesforce.com / *.lightning.force.com or a mention of a Salesforce record ID or SOQL. Always start from this skill when interacting with this service — its bundled scripts and recipes are the fastest path.
Scaffold Codex hooks into a real project after auditing the repo, verifying the live official docs, schemas, and runtime source, inspecting the effective `hooks` feature flag, and enabling it in project or user config if needed. Use when a user wants Codex hooks, `.codex/hooks.json`, managed Codex hook refreshes, repo-local lifecycle hooks, reusable agent scripts, or help with `SessionStart`, `SubagentStart`, `PreToolUse`, `PermissionRequest`, `PostToolUse`, `PreCompact`, `PostCompact`, `UserPromptSubmit`, `SubagentStop`, or `Stop`. Trigger on: Codex hooks, hooks.json, hooks feature flag, codex_hooks legacy alias, .codex/config.toml, managed hook scaffold. Do NOT use for Claude Code hooks, `.claude/settings.json`, Husky-only setups, or non-Codex agents.
This skill should be used when scientists need help with research problem selection, project ideation, troubleshooting stuck projects, or strategic scientific decisions. Use this skill when users ask to pitch a new research idea, work through a project problem, evaluate project risks, plan research strategy, navigate decision trees, or get help choosing what scientific problem to work on. Typical requests include "I have an idea for a project", "I'm stuck on my research", "help me evaluate this project", "what should I work on", or "I need strategic advice about my research".
Use when the user has a scientific draft (with its dataset, figures, and optional analysis code) and wants it iteratively revised until it clears a quality bar. Five specialist judges (figures, scientific content, style, formatting, code) critique the draft; a fresh, independent peer_reviewer grades it on those same axes (1-5 each → a percentage) with honesty guardrails; a scientific_writer revises prose, figures, and code — regenerating figures by running the user's plot command — until the peer-review score clears the threshold or the budget is hit. Not for writing a paper from a blank page, and not for a standalone literature survey.
Core skill for the deep research and writing tool. Write scientific manuscripts in full paragraphs (never bullet points). Use two-stage process with (1) section outlines with key points using research-lookup then (2) convert to flowing prose. IMRAD structure, citations (APA/AMA/Vancouver), figures/tables, reporting guidelines (CONSORT/STROBE/PRISMA), for research papers and journal submissions.
Assess a reported issue from supplied and bounded read-only evidence before implementation. Use to triage, validate, reproduce, classify, or choose the next step for a report. An explicit target authorizes relevant read-only investigation; provider comments and other mutations require separate authority.
Search for prior art relevant to a specific invention or patent claim. Covers patent literature, non-patent literature (academic papers, products, open source), defensive publications, and standard-essential patents. Use when evaluating whether an invention is novel and non-obvious before filing, challenging the validity of an existing patent, supporting a freedom-to-operate analysis, documenting a defensive publication, or responding to a patent office action questioning novelty or obviousness.
Detect and prevent hardcoded secrets in Git repositories and codebases using Gitleaks. Identifies passwords, API keys, tokens, and credentials through regex-based pattern matching and entropy analysis. Use when: (1) scanning repositories for exposed secrets and credentials, (2) implementing pre-commit hooks to prevent secret leakage, (3) integrating secret detection into CI/CD pipelines, (4) auditing codebases for compliance violations (PCI-DSS, SOC2, GDPR), (5) establishing baseline secret detection and tracking new exposures, (6) remediating historical secret exposures in Git history.
Use for a standard, single-pass security audit of an entire repository or a scoped path, package, folder, or submodule with no diff to review. This is the default repository scan. Do not use for PR, commit, branch, or working-tree diffs, or for deep, multi-pass scans.
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.