Skills
100,928 packaged capabilities and playbooks for agents. Install any of them with one command.
All
Comprehensive Cloudflare platform skill covering Workers, Pages, storage (KV, D1, R2), AI (Workers AI, Vectorize, Agents SDK), networking (Tunnel, Spectrum), security (WAF, DDoS), and infrastructure-as-code (Terraform, Pulumi). Use for any Cloudflare development task. Favors retrieval from Cloudflare docs over pretrained knowledge.
Code refactoring expert for improving code quality, readability, maintainability, and performance. Specializes in Java and Python refactoring patterns, eliminating code smells, and applying clean code principles. Use when refactoring code, improving existing implementations, or cleaning up technical debt.
Review a specific diff, pull request, or commit range with independent reviewers for correctness, security, maintainability, and repository rules, check each finding against the code, and check fixes against earlier findings. Use when the user asks to review changes, a PR, or commits, or when another skill runs it to review a change or check fixes. Not for whole-codebase or current-state subsystem audits.
TOM and ADOMD.NET guidance via PowerShell for connecting to Power BI Desktop's local Analysis Services instance. Covers model enumeration, DAX queries, metadata modification, annotations, calendar definitions, field parameters, query tracing, DAX library package management (daxlib.org), and the Desktop Bridge for reloading and screenshotting the report canvas. Automatically invoke when the user mentions "Power BI Desktop", "Analysis Services port", "TOM", "ADOMD", "daxlib", "DAX library", "DAX UDF package", or asks to "connect to PBI Desktop", "query PBI Desktop with DAX", "modify PBI Desktop model", "add a measure to PBI", "capture visual queries", "create a field parameter", "validate DAX", "intercept DAX queries", "install daxlib", "add DAX SVG", "add IBCS", "reload the report canvas", "screenshot a report page", "Desktop Bridge", or to work with the model and report in Power BI Desktop together.
When the user wants to plan their YouTube publishing schedule, batch content, balance content pillars, or design a content calendar. Also use when the user says 'plan my content,' 'build a content calendar,' 'what should I publish this week,' 'batch planning,' 'content schedule,' 'publishing cadence,' 'what videos should I make next.' For generating specific video ideas, see idea-generation. For content pillar design, see channel-strategy.
Linearize complex control flow with early returns, guard clauses, nested ifs, and natural-language conditions. Use when flattening nested conditions, linearizing try/catch logic, or separating mixed throw-and-return handlers, not for a broad "simplify this" pass over a diff or package, which belongs to collapse-pass.
Use this skill when an outline exists and you need to fill in the actual teaching content — lecture notes, sample materials (CSV / YAML / MD samples), quiz items, and any course-specific artifacts like prompt templates or worksheets. Triggers on phrases like "寫講義", "補素材", "出測驗題", "提示詞範本", "撰寫課程內容", "lecture notes", "course material", "quiz questions", "quiz authoring", "prompt templates". Always invoke AFTER `course-outline-design` is stable, BEFORE `static-spa-conversion`. This skill produces only the raw `.md`/`.csv`/`.yaml` artifacts — turning them into a website is the next stage's job.
Open a ready-for-review GitHub pull request for completed local changes, including any needed commit and push. Use when the user asks to open, create, or publish a PR for work that is already done, or when another skill runs it to publish its work.
Generate 5-10 tailored content concepts for a creator partnership that feel native to the creator's style rather than brand-dictated. This skill should be used when brainstorming content ideas for a creator campaign, generating influencer content concepts, ideating creator deliverables, coming up with content angles for an influencer partnership, developing video concepts for TikTok or Reels or YouTube Shorts, creating content hooks for a creator collab, building a concept menu for a creator brief, generating native-feeling content ideas for a sponsored post, or planning what a creator should actually make. For writing the full content brief after selecting concepts, see content-brief-builder. For building the campaign brief that precedes content planning, see campaign-brief-generator. For adapting a single concept across platforms, see multi-platform-format-adapter.
Use when implementing, refactoring, or reviewing `@crowdin/crowdin-api-client` usage in any JavaScript or TypeScript project, especially for endpoint selection, request/response typing, pagination, uploads, retries, timeouts, or `CrowdinError` handling.
Audit application source code and configuration for cryptography and secrets hygiene issues: hardcoded API keys, committed .env files, private keys, weak hashes, insecure encryption modes, unsafe randomness, bad KDF/password hashing, JWT signing mistakes, disabled TLS verification, and dangerous serialization. Runs a dependency-free offline scanner for high-recall findings, then the model confirms impact and writes concrete fixes with redacted evidence. Use when reviewing app code that handles encryption, tokens, sessions, certificates, or credentials; when asked to scan for hardcoded secrets, exposed API keys, weak crypto, AES-ECB/CBC misuse, MD5/SHA1 password hashing, insecure random tokens, verify=False, InsecureSkipVerify, rejectUnauthorized false, alg none JWTs, or committed private keys. Not for Terraform/Kubernetes-only audits (use infra-security), package install-hook risk (use supply-chain-security), or vetting an agent skill before install (use skill-security).
Pure CSS page scroll effects via the Native CSS Scroll-Driven Animations API (animation-timeline scroll()/view(), animation-range) — ZERO JavaScript. Call when the user says "css scroll driven animation", "animation-timeline", "scroll animation không js", "css thuần cuộn trang", "scroll-driven CSS", or /css-scroll-driven-native. DIFFERENT from `skills/scroll-effects` (that uses IntersectionObserver JS, runs in EVERY modern browser) — this skill is 0 JS but browsers do NOT yet fully support it (Firefox/Safari still behind flag/rollout), use as progressive enhancement on top of scroll-effects, not a replacement when it must reliably run in every browser.
Expert UK Cyber Essentials and Cyber Essentials Plus advisor — the NCSC-owned, IASME-delivered baseline certification. Covers the current Danzell question set (Requirements for IT Infrastructure v3.3, mandatory for assessment accounts from April 27, 2026) and the Willow transition, the five control themes (firewalls, secure configuration, security update management, user access control, malware protection), scoping rules for cloud services, BYOD and home working, the 14-day critical-update rule, mandatory MFA for cloud services and the new auto-fail questions, CE Plus technical audits, pricing, annual renewal, the included cyber liability insurance, and procurement mandates (PPN 014, MoD Defence Cyber Certification, NHS). Use this skill whenever a user mentions Cyber Essentials, CE Plus, IASME, the UK government cyber certification, Danzell or Willow question sets, UK public-sector or MoD supply-chain security requirements, or wants a readiness gap assessment.
Query FDA drug labels (DailyMed) via REST API. Search structured product labels (SPLs) by name, NDC, set ID, or RxCUI; get indications, dosage, warnings, adverse reactions, packaging. No auth. For adverse events use fda-database; for DDIs use ddinter-database.
Use when the user wants Codex to learn DaVinci Resolve through Blackmagic Design lesson homework, operate the Resolve UI with Computer Use, validate skills against real Resolve behavior, or build a capstone workflow that turns local/T7 media into Instagram and YouTube cuts.
Audit column types and precision — money stored as float/double (severity 5), naive timestamp vs timestamptz/UTC, jsonb used to evade schema, enum-vs-lookup-table choice, and charset/collation (utf8mb4, case-insensitive collation). Module M4. Feeds the Design & Integrity score (Tipos category).
Use when designing or critiquing aggregate boundaries — phrases like "aggregate", "aggregate root", "should these be one entity or two", "consistency boundary", "transactional consistency", "this aggregate is huge", "should I reference by ID or by object". Defines aggregates as transactional consistency boundaries and the rules for entity references within and across them
Use when identifying DDD anti-patterns and smells in code or design — phrases like "anemic domain model", "primitive obsession", "leaky repository", "smart UI", "transaction script", "god aggregate", "big ball of mud". Catalogs the common DDD anti-patterns with symptoms, why each is wrong, and the pattern skill that explains the fix
Provides comprehensive guidance for COLA architecture including adapter layer, application layer, domain layer, and infrastructure layer. Use when the user asks about COLA, needs to implement COLA architecture, structure applications with COLA, or work with COLA patterns.
Use when mapping relationships between bounded contexts — phrases like "context map", "how do these two services talk", "should we use an anticorruption layer", "shared kernel vs separate ways", "upstream/downstream", "what integration pattern fits here". Catalogs the seven relationship patterns (Shared Kernel, Customer-Supplier, Conformist, Anticorruption Layer, Open Host Service, Published Language, Separate Ways) and the signals that pick one.
Use when the model is "working but feels off" and the user wants to deepen it — phrases like "supple design", "refactor toward deeper insight", "implicit concept", "the model isn't quite right yet", "what would a better model look like", "intention-revealing interfaces", "side-effect-free functions", "assertions in the domain", "conceptual contours". Covers Evans's Part III techniques for evolving a model past its first draft.
Use when behavior does not naturally belong to a single entity or value object—phrases like “domain service”, “this logic spans multiple aggregates”, “where does this go”, “the entity is starting to know too much”, “we need a calculator/coordinator that isn't a thing”. Defines when to introduce a stateless domain service instead of forcing behavior onto an entity. Distinguishes domain services from application and infrastructure services.
Use when creation of an aggregate or complex value object requires non-trivial work — phrases like "factory", "the constructor is doing too much", "construction has business meaning", "how do I create this aggregate", "constructor with twelve parameters". Defines when to introduce a factory and when a constructor or static creation method suffices
Use when designing how aggregates are persisted and retrieved—phrases like “repository”, “how should I load this aggregate”, “JPA repository vs DDD repository”, “leaky repository”, “finder methods”, “the repository is doing too much”. Defines a repository as the abstraction that gives the illusion of an in-memory collection of aggregates. One repository per aggregate root.
Use when the user asks for a PR-style code review for DDD smells—phrases like “is this DDD-clean”, “review this for domain modeling issues”, “what's wrong with this aggregate”, “audit this module for DDD”. Scans a file, diff, or module against the DDD anti-pattern catalog and reports specific violations with citations to the relevant pattern skill. Do NOT use when the user wants new code (route to ddd-implement) or wants to design from scratch (route to ddd-design).
Use when deciding where to spend modeling effort — phrases like "core domain", "supporting subdomain", "generic subdomain", "what's worth building vs buying", "where should the senior engineers work", "is this our competitive edge or just plumbing". Distinguishes Core (competitive edge), Supporting (custom but not differentiating), and Generic (commodity, buy/library) subdomains
Use when the user is modeling a descriptive concept with no identity — phrases like "value object", "Money", "Address", "DateRange", "primitive obsession", "wrap this primitive into a type", "two instances with the same attributes are the same". Distinguishes from entities; pairs with ddd-entity
Build trading systems in the style of D.E. Shaw, the pioneering computational finance firm. Emphasizes systematic strategies, rigorous quantitative research, and world-class technology infrastructure. Use when building research platforms, systematic trading strategies, or quantitative finance infrastructure.
Comprehensive framework for deep analysis of articles, papers, and long-form content using 10+ thinking models (SCQA, 5W2H, critical thinking, inversion, mental models, first principles, systems thinking, six thinking hats). Use when users want to: (1) deeply understand complex articles/content, (2) analyze arguments and identify logical flaws, (3) extract actionable insights from reading materials, (4) create study notes or learning summaries, (5) compare multiple sources, (6) transform knowledge into practical applications, or (7) apply specific thinking frameworks. Triggered by phrases like 'analyze this article,' 'help me understand,' 'deep dive into,' 'extract insights from,' 'use [framework name],' or when users provide URLs/long-form content for analysis.
Deep learning for drug discovery. 60+ models (GCN, GAT, AttentiveFP, MPNN, ChemBERTa, GROVER), 50+ featurizers, MoleculeNet benchmarks, HPO, transfer learning. Unified load-featurize-split-train-evaluate API. For fingerprints use rdkit-cheminformatics; for featurization-only use molfeat.
Deneb visual creation, Vega/Vega-Lite spec authoring, and Deneb best practices for PBIR reports. Automatically invoke whenever the user mentions "Deneb" in any context, or asks about Vega/Vega-Lite specs in Power BI, Deneb cross-filtering, Deneb interactivity, pbiColor theme integration, Deneb field name escaping, or Deneb rendering issues.
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.