Skills
97,222 packaged capabilities and playbooks for agents. Install any of them with one command.
All
Governs biometric data processing for employee timekeeping and access control under Art. 9 GDPR special category rules. Covers fingerprint, facial recognition, iris scanning, and voice recognition. Applies necessity tests, evaluates less intrusive alternatives, and implements employee objection procedures. Keywords: biometric data, Art. 9, fingerprint, facial recognition, access control, timekeeping, special category.
TRIGGER THIS when designing employee engagement surveys, analyzing employee feedback, creating action plans based on survey results, tracking engagement trends, planning pulse surveys, or improving employee experience. Designs comprehensive surveys that measure engagement, belonging, and satisfaction with actionable insights and accountability-driven improvement plans.
Comprehensive 2026 engineering best practices for agentic coding. Apply when writing, reviewing, or refactoring code across Node.js, Next.js, NestJS, Java, Spring Boot, Python, Elixir, Phoenix, Erlang, Rust, Go, React, Vue, Nuxt, Astro, and SQL/NoSQL databases. Covers security (OWASP Top 10, zero trust, supply-chain hardening), performance (async I/O, caching, connection pooling, N+1 prevention), idempotency, atomicity, concurrency, observability (OpenTelemetry, structured logging), and accessibility (WCAG 2.2 AA). Includes per-stack version baselines, idiomatic patterns, known CVEs and gotchas (e.g. Next.js CVE-2025-29927, Valkey 9.1 RC), and pre-merge/pre-production checklists. Use for any programming task regardless of language or framework.
Write a weekly engineering status report for a team, service, or initiative. Use when asked to write a team update, weekly engineering report, sprint status email, or standing team communication to stakeholders. Produces a concise, scannable weekly report covering shipping progress, metrics, decisions, blockers, and next-week priorities.
Generate deterministic INSERT SQL seed data from Go Ent schemas and mixed inputs. This skill is REQUIRED whenever you need to create seed SQL for development or testing - it handles entity inference, relationship integrity, stable IDs, and dialect-specific SQL generation including JSON, arrays, and complex types. Use this skill for any task involving seed data, test fixtures, demo initialization, or database population from Ent schema definitions, even if the user doesn't explicitly mention "seed" or "SQL".
Plan and audit enterprise onboarding and implementation programs covering kickoff, success criteria, stakeholder mapping, SSO/SCIM, integrations, data migration, sandboxing, training, go-live gates, risk escalation, support handoff, and adoption proof. Use when a sold customer must become live and successful without heroic project management.
Search the company's enterprise knowledge index. Use this FIRST when starting any task that touches company-specific context - projects, people, policies, internal docs, prior decisions - before searching individual sources like Drive, Slack, or Jira directly. Also use it when the user asks "do we have a doc about X", "what's our policy on Y", or references internal initiatives by name. Always start from this skill when interacting with this service — its bundled scripts and recipes are the fastest path.
Entity compliance tracker — initialize, report upcoming deadlines, update status, run a health audit, export to CSV. Maintains compliance-tracker.yaml built from the entity roster, calculates filing deadlines by entity and jurisdiction, and surfaces items due within the next 30/60/90 days. Use when the user says "entity compliance," "filing deadlines," "annual report due," "entity tracker," "what filings are due," "entity health," or "good standing."
Maintain or migrate EF6-based applications with realistic guidance on what to keep, what to modernize, and when EF Core is or is not the right next step. USE FOR: EF6 codebases; runtime versus ORM migration decisions; EDMX, code-first, ObjectContext, and legacy data-access review. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.
Master error handling patterns across languages including exceptions, Result types, error propagation, and graceful degradation to build resilient applications. Use when implementing error handling, designing APIs, or improving application reliability.
Structure and package support escalations for engineering, product, or leadership with full context, reproduction steps, and business impact. Use when an issue needs to go beyond support, when writing an escalation brief, or when assessing whether an issue warrants escalation.
Guides EU Code of Conduct adherence under GDPR Articles 40-41 including EDPB approval requirements, monitoring body accreditation, code drafting, adherence declaration, compliance verification, and complaint handling. Covers sector-specific codes, transnational codes, and Art. 40(3) approval by supervisory authorities. Keywords: code of conduct, Article 40, Article 41, EDPB, monitoring body, adherence.
Guides assessment and use of the EU-US Data Privacy Framework adequacy decision for transatlantic data transfers. Covers DPF self-certification with the Department of Commerce, DPF principles compliance, Data Protection Review Court, and annual EC review. Keywords: DPF, EU-US, adequacy, Privacy Shield, transatlantic transfers.
Guides event-driven systems—pub/sub, point-to-point, event sourcing, CQRS, schema versioning (Avro/JSON Schema), ordering, partitioning, delivery guarantees, idempotency, exactly-once tradeoffs, transactional outbox/inbox, choreography vs orchestration, sagas, dead-letter queues, replay, stream vs discrete events, microservice boundaries. Use when the user asks for event-driven architecture, event sourcing, CQRS, pub/sub, Kafka events, outbox pattern, idempotent consumer, event choreography, saga orchestration, dead letter queue, or event schema versioning—not microservice code only (microservices-developer), enterprise API/iPaaS only (enterprise-integration-api-developer), EDI (edi-engineer), classified promotion (classified-software-devsecops-engineer), solvers (operations-research-algorithm-developer), generic CRUD (senior-software-engineer).
Create editable Excalidraw diagrams in Obsidian, standard or animated formats. This skill MUST be used when the user names Excalidraw. It SHOULD be selected from natural-language requests for standalone diagrams, concept relationships, mind maps, editable whiteboards or diagrams whose elements appear in sequence (draw, flowchart, mind map, relationships, whiteboard, step-by-step presentation), without requiring the user to know the skill name. Choose by content and destination; illustration or photo requests need other tools. For diagrams inside HTML Artifacts, MUST prefer HTML/CSS/SVG or the artifact's existing diagram tools; use Excalidraw there only when explicitly requested or a concrete Excalidraw capability is needed. Hand-drawn styling alone is insufficient. Explicit Mermaid requests MUST use mermaid-visualizer instead.
(NS) Execute a GitLab issue end-to-end — first-act status, branch-reuse and source-branch gates, single-worktree isolation, atomic delivery, MR lifecycle, mandatory code review gate with bounded fix loop. Use when the user provides a GitLab ISSUE_URL or asks to implement a GitLab issue directly — not for local-only ad-hoc coding (use code-coder) or non-GitLab autonomous runs (use code-autonomous standalone). Delegates actual coding to the code-autonomous engine. Requires mcp-gitlab-usage for MCP and code-reviewer for the review gate.
Launch a GrowthBook A/B test end-to-end via the REST API — create the experiment, prep the feature flag, wire the experiment-ref rule, and start the experiment. Use when the user says "launch this experiment", "create the experiment", "wire up the A/B test", "kick off the test", "set up X as an experiment in GrowthBook", "start the experiment for flag Y", or "I already have a flag and want to run an experiment on it". Works for both experiment-first (creates the flag) and flag-first (detects the existing flag via the reuse path and wires the experiment to it). For designing the spec first, use experiment-design. For stopping a running experiment, use experiment-stop. For interpreting results, use experiment-analyze.
Stop a running GrowthBook experiment via the REST API, optionally declaring a winning variation and rolling it out to 100% of eligible traffic. Use when the user says "stop this experiment", "end the A/B test", "declare a winner for X", "ship the winning variation", "roll back the test", or "we're done with this experiment". For interpreting results before deciding, use experiment-analyze first.
Use when the user wants to understand a technical concept, compare options, see code examples, assess the impact of adopting something in the current repository, or see candidate high-level designs for a request. Produces an explanation or exploration brief. Do not use when the user has a settled direction and wants requirements, design, or implementation.
All-in-one FASTQ QC and adapter trimming. Auto-detects Illumina adapters, filters low-quality reads, corrects paired-end overlaps, emits HTML+JSON QC in one pass. 3-10x faster than Trim Galore/Trimmomatic. First step before STAR, BWA-MEM2, or Salmon.
Build, review, debug, configure, migrate, or plan Feedsmith v3+ TypeScript/JavaScript feed parsing and generation. Use for feedsmith, parseFeed, parseRssFeed, parseAtomFeed, parseRdfFeed, parseJsonFeed, parseOpml, generateRssFeed, generateAtomFeed, generateJsonFeed, generateOpml, detectRssFeed, RssFeed, AtomFeed, JsonFeed, namespaces (itunes, podcast, media, dc), parseDateFn, maxItems, extraOutlineAttributes, strict mode, DetectError, MalformedError, ParseError, GenerateError, OPML, and v2→v3 migration.
High-quality Feishu/Lark Docx writing via OpenClaw. Covers tool selection, chunked writing, native tables, $ symbol escaping, and all known pitfalls. Trigger on Feishu doc/docx links, "write to Feishu doc", "generate a Feishu doc", "append/replace docx", or when users want consistently good doc formatting.
Comprehensive Feishu/Lark integration skill for OpenClaw. Covers messaging, group management, Bitable (multi-dimensional tables), documents, calendar, video conferencing (vc.v1), meeting minutes (minutes.v1), task management, approval workflows, contacts, cloud drive, wiki/knowledge base. Requires the official Lark MCP server to be configured and running.
Extract reusable visual systems from reference technical diagrams, architecture diagrams, scientific schematics, roadmaps, workflows, frameworks, and technical infographics. Create complete modular prompts, generate style-consistent PNG figures from new content, and save, search, name, validate, or reuse Style Packs with their original reference images. Use for 参考图风格抽取、技术图视觉语法、同风格技术图、技术路线图、架构图、科研示意图、方法框架图、风格模板库、保存或复用图片风格.
Perform an in-depth analysis of the financial statements of a single A-share listed company, assessing earnings quality, financial health, financial fraud risk, and operational efficiency. Use this skill when users request an in-depth review of a company's financial statements, DuPont analysis, earnings quality checks, balance sheet analysis, cash flow analysis, Z-score, M-score, working capital analysis, or any detailed single-company financial review
Use when the user wants verbatim customer or prospect quotes, voice-of-customer evidence, theme validation, objection evidence, product-friction examples, or support for a product area, use case, or sales narrative. Retrieve from transcripts, call notes, supplied transcript-like recordings or exports, and other grounded call material using explicit speaker-confidence and provenance rules.
Search the Karma Funding Map for funding programs (grants, hackathons, bounties, accelerators, VC funds, RFPs) via the public API. Use when user says "find grants", "search hackathons", "look for bounties", "explore funding", "programs on Optimism", "what can I apply to", "funding opportunities", or asks about programs over or under a budget.
Find new B2B leads in Germany for InboxMate outreach. Validates each lead against legal requirements (UWG), checks email is publicly visible, documents justification, and adds to CRM. Germany only — Austrian law (TKG) is stricter. Parameters: number of leads, optionally a track ('inbox' for email-automation leads only, 'chatbot' for chatbot leads only; default mixed).
Helps users discover and install capabilities from the open agent skills ecosystem. Use when users ask "how do I do X" for specialized tasks, request "find a skill for X", want to extend agent capabilities, or need help with specific domains (testing, design, deployment, etc.).
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
Publish a GrowthBook feature flag draft revision, resolve merge conflicts, revert to a prior revision, or discard a draft. Use when the user says "publish this draft", "push this live", "go live with revision X", "there's a merge conflict on my flag", "rebase my draft", "fix the merge conflict on flag X", "revert flag X to a previous version", "roll back this flag change", "discard this draft", or "abandon these changes". For requesting or submitting an approval review before publish, use flag-review. For listing and inspecting drafts, use flag-revisions.
Create or manage a multi-step ramp schedule for a GrowthBook feature flag rule — progressively increasing traffic exposure over time with defined intervals between steps. Use when the user says "gradually roll this out", "increase traffic from 5% to 100% over a week", "set up a ramp schedule", "advance to the next ramp step", "pause the rollout", "roll back the ramp", or "set a cutoff date on this rollout". For rollouts that also need guardrail metric monitoring and automatic signals, use flag-monitoring — it builds on this skill with monitoring configuration. For simple on/off time windows, use flag-schedule.
List, inspect, and manage draft revisions for a GrowthBook feature flag. Use when the user asks "what drafts are open for flag X", "show me pending approvals", "who owns this draft", "discard this draft", "start a new draft", "what revision is my flag on", "list all my pending changes", "what's waiting for review", or any question about the state of in-progress changes to a flag. Every flag write operation — rules, metadata, default value, toggles — works through a draft revision; use this skill to see what's in flight before making changes. For requesting or submitting an approval review, use flag-review. For publishing a draft live or resolving merge conflicts, use flag-publish. For making flag changes, use the relevant flag-* write skill.
Entry point for working with rules on a GrowthBook feature flag. Use when the user asks "what rules does flag X have", "show me the rules on this flag", "add a rule", "delete a rule", "reorder the rules", or describes a flag operation without specifying the rule type. Routes to specialized skills for creating and editing specific rule types. Also handles listing, reordering, and deleting rules directly. For specific rule types, use flag-targeting for force/rollout rules, flag-experiment for experiment-ref rules, flag-schedule for timed activation, flag-ramp for progressive rollouts, flag-monitoring for monitored rollouts, flag-prerequisites for feature-level prerequisite gates.
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.