Skills
101,323 packaged capabilities and playbooks for agents. Install any of them with one command.
All
Analyze images, video, speech, motion, products, and websites; route local media models; auto-edit, replicate, enhance, caption, voice, assemble, annotate, validate, and export editable Timeline Studio projects and videos. Use for reference-video remakes, filter and repeated-shot reconstruction, subject-aware reframing, clip splitting, split-screen layouts, reference-frame synchronization, source-time speed curves, Color Wheels grading, ramps and holds, person or product cutout, person or object outline, authorized face swap, shot and timing reconstruction, editable beat templates, timeline markers, chapters, beat cues, review notes and ranges, supplied or web-sourced footage, cleanup, highlights, product promotion, website walkthroughs, image-to-video assisted edits, optical-flow editing, depth-assisted relighting, grayscale depth-video conversion, depth/2.5D/transition finishing, AI voiceover, subtitles, short-form production, .timeline automation, or editor evaluation.
Sets up Enonic XP event listeners, webhook configurations, and external system integrations triggered by content lifecycle events. Covers lib-event listener registration, node event filtering, outbound webhook configuration via com.enonic.xp.webhooks.cfg, custom HTTP service controllers for inbound webhooks, task-based async processing with lib-task, and outbound HTTP calls with lib-httpClient. Use when listening for content publish/create/update/delete events, configuring outbound webhooks, building HTTP service endpoints for inbound webhooks, or triggering async processing on content changes. Do not use for content querying, frontend component development, non-Enonic event systems, or GitHub webhook configuration.
Extract text from each page of a PDF into a markdown file using pdftotext. Produces slide_ascii.md with a heading, image reference, and extracted text per slide. USE FOR: extract text from PDF slides, get slide text content, PDF to markdown text, slide_ascii.md.
Design how one feature or screen in an iOS app behaves while it works: loading, showing saved data while refreshing, success, empty, error and retry, with the motion, haptics and words for each state, backed by real shipped apps. Use when asked to add or improve loading states, success or error feedback, empty states, retry flows, or "what should happen while this loads". SwiftUI and UIKit, iOS only.
Use when the user wants to organize, tidy, or restructure a messy directory (Downloads, Desktop, documents folder). LLM-powered file organizer that scans content, proposes a structure, and executes moves in chunks with a mandatory user confirmation gate.
Generate animated HTML pages for educational and popular-science flowcharts, concept diagrams, and principle demonstrations. Draw nodes and connectors with CSS/SVG, with animation effects such as flowing arrows, step-by-step appearance, and hover highlighting. Suited to technical explanations, science videos, and PPT illustrations.
GitHub Actions workflow authoring for CI/CD pipelines. Covers workflow syntax, triggers, jobs, steps, matrix strategies, caching, artifacts, reusable workflows, composite actions, secrets management, OIDC authentication, and permissions hardening. Use when creating workflows, configuring jobs, setting up caching, or automating releases. Use for github-actions, workflow, ci, cd, actions, jobs, steps, matrix, cache, artifact, secrets, reusable-workflow.
Gingiris growth toolkit main entry point. Call it when the user asks growth questions such as “how to drive growth,” “how to launch on PH,” “SEO traffic dropped,” “write a blog post,” or “analyze competitors.” Automatically routes to the corresponding sub-skill based on the question type (gr-seo-patrol / gr-blog-post / gr-ph-launch, etc.).
GraphQL performance optimization and best practices for building scalable APIs. This skill should be used when writing, reviewing, or refactoring GraphQL schemas, resolvers, or query execution code. Triggers on tasks involving GraphQL APIs, resolver optimization, query performance, or data fetching patterns.
Stress-test a design, idea, or approach by interviewing the user one question at a time. Each question comes with a recommended answer AND a one-line self-critique of that recommendation. After each user answer, briefly stress-test the answer against prior decisions before moving on. Use when the user wants a sharp grill on a design or decision tree without persistence overhead. Lighter than `/chief-grill` (which adds codebase verification and a session log).
Migrate workloads from Heroku to AWS. Triggers on: migrate from Heroku, Heroku to AWS, move off Heroku, migrate Heroku app, migrate Heroku Postgres to RDS, migrate Heroku Redis to ElastiCache, migrate Heroku Kafka to MSK, migrate dynos to Elastic Beanstalk, migrate dynos to Fargate, Heroku migration, move from Heroku to AWS, migrate Heroku Private Space, Heroku to Elastic Beanstalk, Heroku to ECS, Heroku to Fargate, leave Heroku, migrate off Heroku platform, what-if workshop, reprice Heroku migration, compare migration scenarios, workshop mode. Runs a 6-phase process: discover Heroku resources live via the authenticated Heroku CLI (read-only, consent-gated) and/or from Terraform files, Procfile/app.json, and optional billing exports, clarify migration requirements, design AWS architecture, estimate costs, generate migration artifacts, and collect optional feedback. After Estimate, an optional what-if workshop can reprice region/HA/compute/Graviton scenarios without re-discovery. Clarify must finish before Design, Estimate, or Generate. Uses a flat resource model (no clustering or dependency graphs) with deterministic mapping tables for core services (Dynos → Elastic Beanstalk by default, Postgres → RDS/Aurora, Redis → ElastiCache, Kafka → MSK) and a fast-path table for 13+ common add-ons. Cedar/Fir generation detection is detect-only in v1. Pipeline/Review Apps are detect-only. Do not use for: GCP migrations to AWS (see gcp-to-aws), Azure migrations to AWS (see azure-to-aws), AWS-to-Heroku reverse migration, general AWS architecture advice without migration intent, Heroku-to-Heroku refactoring, or multi-cloud deployments that do not involve migrating off Heroku.
Code-vs-artifacts review for OpenSpec's tempa-spec schema — checks implemented code against specs/**/*.md, design.md, and tasks.md once every task is complete. A loop of up to 3 passes, each run in a fresh subagent session with no memory of the implementer, HIGH/MEDIUM/LOW severity with MECHANICAL/DECISION resolution tagging, hard-gated on passing tests and lints, with a bundled diff floor guard that flags suppressions, skips, deleted tests, dropped assertions, and stubs. Use during the tempa-spec schema's `apply` Phase 2 review.
Huawei Cloud RDS (Relational Database Service) full-scenario intelligent service covering all database engines (MySQL, PostgreSQL, SQL Server, MariaDB, GaussDB for MySQL, TaurusDB). Provides six capability domains: (1) Basic intelligent Q&A for RDS product features, best practices, and specifications; (2) SQL statement performance optimization with slow log analysis, top SQL, execution plan guidance, and index recommendations; (3) Database instance daily O&M including health inspection, restart, flavor resize, disk expansion, primary-standby switchover, and read replica management; (4) Online fault localization and troubleshooting via error logs, replication status, connection diagnostics, and recovery time window; (5) Parameter tuning with parameter group management, modification suggestions, and performance parameter adjustment guidance; (6) Backup and recovery guidance including backup policy management, manual backup creation, restore to new/existing instance, and point-in-time recovery. Uses CLI→SDK→API three-level fallback for maximum compatibility. All mutating operations require explicit user confirmation. Triggers include: “RDS,” “关系型数据库,” “数据库实例,” “慢SQL,” “SQL优化,” “数据库运维,” “数据库故障,” “故障排查,” “参数调优,” “备份恢复,” “数据库巡检,” “RDS诊断,” “数据库诊断,” “DBA,” “数据库性能,” “主从延迟,” “连接数,” “数据库备份,” “数据恢复,” “RDS智能服务,” “database instance,” “RDS troubleshooting,” “slow query,” “SQL performance,” “database backup,” “parameter tuning,” “RDS ops,” “database diagnose.”
Iskron’s door and session start: use /iskron or speak naturally. “Start” comes first, before readiness: graph and role, iskron_stand for watch and records, greet the person. Handles “why was this decided,” “what about this,” “write it down,” “think it through,” “what’s pending,” “who will it affect,” “is it working,” “tidy up,” “put the picture together,” “roadmap,” “can’t hear,” “connect the graph,” “remember this about me,” “update” (bridge, plugin, software, SUPPLY IS OUTDATED), “stand by the person,” “start graph role place,” and the older “enter the room” and “handle the matter.” Selects and executes a skill.
Turn spoken scripts into Chinese slide images in one click with NotebookLM, and convert PDFs to images for use in Jianying. Use when the user says “生成PPT,” “生成幻灯片,” “做PPT图片,” “幻灯片,” or “PPT,” or mentions background images or visual assets for a spoken script.
Conduct a structured literature review on a given topic by defining a search strategy, applying inclusion and exclusion criteria, extracting key findings, and synthesizing results into a coherent academic review. Use when the user requests literature review or provides relevant inputs for this workflow.
Correct or update existing wiki content when newer evidence shows the wiki is wrong, stale, incomplete, or contradicted. Use this when the agent discovers the wiki says X but we now know Y, when code or real-world changes invalidate a wiki claim, or when the user asks to fix or amend the wiki. Not for adding new sources, routine learnings capture, structural normalization, or health checks; use /loam::adding-to-memory, /loam::learning-from-session, /loam::normalizing-memory, or /loam::linting-memory.
Surface and classify all open questions, unresolved contradictions, stale claims, and knowledge gaps from existing memory. Use this when the user wants to see what's still open, what needs attention, what's unresolved, or what still needs research or ingest. Does not classify incomplete goals as memory gaps. Not for answering questions, fixing issues, or adding new material; use /loam::querying-memory, /loam::linting-memory, /loam::amending-memory, /loam::adding-to-memory, or /loam::learning-from-session.
Guides PostHog engineers through dashboard widget platform work — ship a new widget_type (WIDGET_REGISTRY, catalog, run_widgets, WidgetCard) or update a shipped type (config, query, layout, RBAC, tile filter bar, list footer, titleHref, throttles). Use for WidgetSpec, widget_specs/, widget-configs.zod.ts, hogli build:openapi, error_tracking_list, session_replay_list, widgetFilters, formatWidgetListCountFooter, widget_query_throttle, or WidgetCard composition. New types need widget-intake confirmation first. Not for MCP batch-add of existing types or adding tiles to a dashboard.
Load this skill whenever the project contains static or interactive maps, embedded map widgets (Google Maps, Leaflet, Mapbox, OpenStreetMap), or any geographic visualizations. Under no circumstances embed a map without a text-based alternative conveying the same information. Absolutely always ensure map controls are keyboard-accessible and that all meaningful map content is available without the visual map.
Covers the full meeting lifecycle for engineering managers — produces guidance on whether to schedule a meeting, how to run it well, how to protect team focus time, how to kill recurring waste, and how to evaluate a past meeting from a transcript or description. Use when the user says "too many meetings," "meetings are a waste of time," "how do I run this meeting," "meeting agenda," "meeting culture," "nobody comes prepared," "meetings go nowhere," "how do I decline meetings," "distractions," "focus time," "engineers can't focus," "context switching," "protect engineering time," "review this meeting," or "transcript."
Touch-first mobile UI for native-feeling web apps, PWAs, and React Native/Flutter screens: touch targets, bottom navigation, gestures, safe areas, thumb zones, sheets, mobile forms, and motion. Use when the user asks to "design for mobile", "build a mobile UI", "make it mobile-friendly", "create a mobile app", "build a responsive mobile layout", "design a bottom sheet", "mobile navigation", "iOS/Android style", or any mobile-specific work. For general responsive rules on desktop-first sites use ui-design; for app-store screenshots or device mockups use product-mockup.
Build an iOS interaction by copying one that already shipped. Use when asked to design or implement any animation, transition, gesture or micro-interaction in SwiftUI: a bottom sheet, a pull-to-refresh, a card morph, an onboarding sequence, a loading state, a success moment. Also use when asked "how does app X do Y" about mobile motion, or for a reference clip to copy. iOS and SwiftUI only.
Give an iOS app one consistent motion language: a small set of named timings, springs and haptics in a single Motion.swift, derived from the app's own code and from real shipped apps with the same feel. Use when asked to make an app's animations consistent, create motion tokens or a motion system, clean up scattered animation values, or define how the app should move. SwiftUI, iOS only.
When the user wants to launch a product across multiple platforms, plan a Product Hunt launch, build a waitlist, or execute a multi-channel launch strategy. Also use when the user mentions 'product launch,' 'Product Hunt,' 'launch strategy,' 'waitlist,' 'beta launch,' 'BetaList,' 'Hacker News,' 'launch day,' 'AppSumo,' 'multi-channel launch.' This skill covers multi-platform launch execution from pre-launch through post-launch optimization.
Compatibility guide for developers moving from MySQL to MariaDB, and for developers with MySQL experience working with MariaDB. Use when migrating a MySQL application to MariaDB, when MySQL syntax or habits cause unexpected behavior in MariaDB, when asking about MySQL/MariaDB compatibility, or when adapting code written for MySQL to run on MariaDB. IMPORTANT — MariaDB diverges significantly from MySQL 8.0 and is not a simple drop-in replacement for modern MySQL. Authentication plugins, JSON handling, GTID replication, and several SQL features differ in important ways.
Use this skill for provider-independent reality capture that turns photographed or video-derived real places, objects, aerial sites, interiors, or people into photogrammetric meshes, NeRFs, or 3D Gaussian splats. It guides representation choice, capture planning, calibration and scale, reconstruction or training, cleanup, compression and LOD, coordinate and interchange handoff, visual/geometric QA, archival records, and property, location, people, and cultural rights checks. Do not use it for text-to-3D generation, synthetic asset invention, guaranteed metrology, or broad downstream finishing after handoff.
How to apply an ngrok endpoint and Traffic Policy on whichever surface the user is actually working in - the agent CLI and ngrok.yml, the ngrok SDKs (Go, JavaScript, Python, Rust), the REST API at api.ngrok.com, the Terraform provider, and the Kubernetes Operator. Routes from signals in the user's project to the right surface, then to that surface's reference file. Other ngrok skills point here once they know what to build. Not a standalone task - load when another skill references it.
Prepares a complete EB-2 NIW (National Interest Waiver) self-petition package in a local case folder — free evaluation from a Google Scholar profile or CV, evidence checklist and citation pipeline, drafting the Proposed Endeavor Statement, Petition Letter and support letters in the structure of real approved filings, filling official USCIS/DOL PDFs, assembling the filing package, and running a deadline-driven response if USCIS issues an RFE. Use when the user mentions NIW, EB-2, national interest waiver, I-140 self-petition, RFE response, Request for Evidence, NOID, 国家利益豁免, 补件, 补充材料通知, or preparing a U.S. green-card petition from their research record. Document preparation only, not legal advice.
Automate source-grounded research with Google NotebookLM. Create notebooks from URLs, text, or local files; ask cited questions; run fast or deep web research; create articles and social drafts; and generate or download audio, video, cinematic video, slides, reports, study guides, quizzes, flashcards, mind maps, infographics, and data tables. Use when a user asks for NotebookLM, cited source analysis, research-to-content workflows, podcasts, slides, study material, artifact generation, RSS digests, or trend research.
Handle a hand-edited Office artefact that is now the authoritative version: repair a feature-rich Excel workbook in place through COM (broken slicers or dropdowns, #REF!, circular reference warnings), or promote a generated .docx/.pptx/.xlsx to canonical hand-edited source and retire its generator. Use when Ane reports a damaged workbook or declares an edited file the source of truth. Distinct from office-review-pass (Word review cycle), the ane_package.reporting builders (generate new branded files), and check-deliverable (read-only QA verdict on prose).
Work on a Word deliverable inside the .docx itself: read and engage reviewer comments, insert review findings as margin comments authored as Ane into her working copy, apply real Word tracked changes a counterparty can accept or reject, make scoped formatting-preserving fixes via Word COM, or add a branded glossary and verified source annex. Use when Ane hands over a commented or hand-edited .docx for review, markup, or in-file edits. Distinct from ane-voice (prose voice only, never touches the file), localise (target-language work), check-deliverable (read-only QA verdict), meeting-notes marginalia (reads comments, never writes them), and tor-procurement (builds ToRs).
Runtime diagnosis for Olares apps and the system via olares-cli — find the root cause when an app won't install or start, crashes, cannot pull an image, is `running` but unreachable, or is slow; includes doctor images and thirdleveldomain. Use for diagnosing catalog and dev app failures, not for authoring or editing charts.
Complete guide to using @openserv-labs/client for managing agents, workflows, triggers, and tasks on the OpenServ Platform. Covers provisioning, authentication, x402 payments, ERC-8004 on-chain identity, and the full Platform API. IMPORTANT - Always read the companion skill openserv-agent-sdk alongside this skill, as both packages are required to build any agent. Read reference.md for the full API reference.
Decide what a papercut reel should be. Picks the topic, one familiar format, the audience level, the comment-keyword funnel and caption, studies competitor reels, and runs the post-publish autopsy. Use before any hook or script, or when reviewing how a posted reel did
Every Trigger.dev management endpoint, plus offline FTS over runs, span-cost rollups, and zombie-schedule detection no other tool gives you. Trigger phrases: `trigger.dev failed runs`, `trigger.dev cost rollup`, `trigger.dev schedule health`, `audit trigger.dev env vars`, `watch trigger.dev failures`, `use trigger-dev`, `run trigger-dev`.
Load this skill when building any web feature, reviewing architecture decisions, or evaluating JavaScript dependencies. Under no circumstances build features that break completely when JavaScript is unavailable or fails. Absolutely always start with semantic HTML, layer CSS enhancements, and add JavaScript as the final, optional layer. Prioritize resilience and universal access over cutting-edge features.
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.