Skills
99,951 packaged capabilities and playbooks for agents. Install any of them with one command.
All
Reviews PostHog's warehouse suggestions with a person and acts on them. Explains why a view should be materialized, unmaterialized, certified or deprecated using the numbers in the suggestion, changes a materialize suggestion's refresh mode, keys or interval when the person wants something else, then accepts, dismisses or assigns it. Use when the user asks what PostHog suggests for their data warehouse, whether to materialize a view, why a view should refresh incrementally or every few hours, or wants to accept, change, dismiss or assign a warehouse suggestion.
Judges whether RHDH Jira work that already exists is ready to move forward — in RHIDP, RHDHPLAN, RHDHBUGS, and RHDHSUPP. Checks an issue, a JQL result, a sprint, or a backlog against the exit criteria for its status, then reports missing fields, hierarchy gaps, likely duplicates, unaddressed comments, stale work, and Feature Exploration readiness. Use for "is RHIDP-1234 ready", "refine this", "refine the backlog", "backlog hygiene", "what's missing on this epic", "run the Feature Exploration checklist", or "which of these are stale". Assesses existing work; it does not open new issues and does not build a sprint.
Builds the planning package for an RHDH scrum team's next sprint from Jira RHIDP, RHDHPLAN, RHDHBUGS, and RHDHSUPP: carryover from the active sprint, three-sprint velocity, per-member capacity, the ready-for-planning queue, available capacity, suggested fill, critical customer bugs, and retro action items. Use for "plan the sprint", "sprint planning prep", "what's our capacity next sprint", "what can we commit to", or "what's carrying over". Works on a team and a sprint, not on one issue — a bare key such as RHIDP-1234 is not a sprint. Looks forward at the sprint that has not started; summarizing the one that just ended is a different job.
Daily reports, weekly reports, work summaries, status updates: form a complete report based on verifiable facts. Use when the user asks to report on a period of work, follow an existing report template, organize progress and risks, or when odai judges that professional reporting craft would improve the result.
Source, verify and wire the sound for a Roblox game from the Creator Store by asset id - footsteps, gunshots, animal calls, UI clicks, ambience, music - with no upload, no Open Cloud audio quota and no API key. Searches the same unauthenticated toolbox endpoints Studio's own audio tab uses, then PROVES each candidate in Studio (IsLoaded plus a measured Sound.TimeLength) before anything is chosen, because the toolbox's own duration field is wrong often enough to be dangerous. Emits a SoundBank data module, an Sfx runtime helper that fails inert, and an install script so the bank can be heard in an open place immediately. Use whenever the user wants sound effects, audio, SFX, music or ambience for a Roblox game, wants sounds found and wired rather than dragged in by hand, is picking audio for a build, or asks why a Sound is silent, has no length, or will not load in their place.
Design a Rust public API — trait design, generics versus dyn, sealed traits, what is exported, and which changes break semver. Use when designing or reviewing a crate public surface, when choosing between a generic parameter and a trait object, when adding a trait method or enum variant to a released crate, or when the user asks whether a change is a breaking change.
Build and review bracket-lib style Rust 2D game loops, state structs, game modes, input handling, rendering calls, and restart flow. Use when creating a small Rust game with bracket-lib, porting a tutorial loop, or debugging tick/update/render state behavior.
Plan small, playable Rust game implementation slices from a short design brief, MVP, stretch goals, and acceptance checks. Use when starting a Rust game, scoping a prototype, converting a game idea into work items, or preventing an AI coding agent from overbuilding.
Design and review Rust ECS gameplay code using Legion-style entities, components, resources, systems, schedules, queries, command buffers, and spawners. Use when building ECS-driven Rust game features, migrating game state into ECS, or debugging system ordering and component composition.
Email engagement tracking for sales — open tracking, click tracking, attachment views, real-time notifications, follow-up timing, and engagement analytics. Use when you can't tell if prospects are opening emails, open data looks inflated or unreliable (Apple MPP, pixel blocking), you don't know when to follow up based on engagement, tracking isn't set up yet and you need to pick a tool, or click/attachment tracking isn't working as expected. For Yesware-specific help, use /sales-yesware. Do NOT use for email deliverability (use /sales-deliverability), cadence design (use /sales-cadence), buying intent signals beyond email (use /sales-intent), SendGrid-specific config (use /sales-sendgrid), Postmark-specific config (use /sales-postmark), Customer.io-specific config (use /sales-customerio), Mailgun-specific config (use /sales-mailgun), Klaviyo-specific config (use /sales-klaviyo), or ActiveCampaign-specific config (use /sales-activecampaign).
This skill should be used when users request code review, refactoring, or code quality improvements for Ruby codebases. Apply Sandi Metz's four rules for writing maintainable object-oriented code - classes under 100 lines, methods under 5 lines, no more than 4 parameters, and controllers instantiate only one object. Use when users mention "Sandi Metz", "code quality", "refactoring", or when reviewing Ruby code for maintainability.
Evaluate research rigor and scientific claims. Assess methodology, experimental design, statistical validity, biases, confounding, and evidence quality using GRADE, Cochrane ROB, and preregistration standards. Use for critical analysis of research papers, evaluating AI/ML study claims, reviewing preprints, or fact-checking scientific assertions in any domain.
Spectacle, budgeted. Scroll-driven animation with native CSS first and GSAP ScrollTrigger when needed, smooth scrolling with Lenis and when to turn it off, split-text reveals, pinned scenes, canvas and WebGL on a performance budget, shaders as material, pausing off-screen, loading strategy, and the reduced-motion and no-JS fallbacks that keep the page readable. Use for marketing pages, portfolios, launches and hero sections. Never for product UI.
Guides users through implementing and optimizing ScyllaDB Vector Search for semantic similarity, RAG, and similar use cases. Use this skill when users need to store and query embeddings, build vector indexes (HNSW), run approximate nearest neighbour (ANN) queries, apply filtering (global/local secondary indexes), configure quantization, integrate with LLM frameworks (e.g. LangChain), or run Vector Search locally with Docker for testing. Schema design outside the vector column goes to scylladb-data-modeling. Triggers on "vector", "embeddings", "similarity search", "ANN", "nearest neighbor", "RAG", "semantic search", "recommendation system", "vector index", "HNSW", "vector-store"
【Internal suite skill · Users usually don’t need to invoke it directly in the full workflow; simply describe the request to the orchestrator short-drama-director, which will route it to this skill automatically】【漫剧老李 V7.4.26 suite · Subskill · Track ③ Commentary and narrative】Specialist engine for commentary/narrative videos: complete rule sets for three tracks—historical biographies / historical events and battles / educational explainers. Core capabilities—voice-over script (VO Script) writing standards (commentary speed 4.5–6.5 characters/second / short sentences ≤25 characters / prioritize analogies / reduce cognitive load / hooks and memorable lines), audio-visual information gap discipline, history visual standards prioritizing period settings, hit formulas for three subtypes, storyboard adaptation from narration lines to images, C14 exemption from off-screen voice quotas. Triggers: commentary, shot analysis, roundups, historical figures, historical events, educational explainers, fun facts, educational content, understand at a glance, documentary commentary, talking-head narration. This skill is a suite member; enter the complete workflow through the orchestrator short-drama-director; the track is selected and locked by the orchestrator at 〇·0.
SDD step 2 (optional, repeatable). Read an existing feature.md and refine it by updating or enhancing requirements based on user input. Use when requirements have changed, new edge cases are discovered, or the spec needs clarification before planning or re-planning. Run before /sdd-plan if plan.md already exists.
Search X/Twitter in real-time with Grok-4 and Grok-4.20 - Responses API with x_search tool orchestration, multi-agent research, keyword/semantic/user/thread search modes, image search, prompt caching, and batch API. Full citations with engagement stats.
Write secure-by-default Node.js and TypeScript applications following security best practices. Use when: (1) Writing new Node.js/TypeScript code, (2) Creating API endpoints or middleware, (3) Handling user input or form data, (4) Implementing authentication or authorization, (5) Working with secrets or environment variables, (6) Setting up project configurations (tsconfig, eslint), (7) User mentions security concerns, (8) Reviewing code for vulnerabilities, (9) Working with file paths or child processes, (10) Setting up HTTP headers or CORS.
Autonomous self-evolution skill: grants the agent full authority to modify its own configuration, skills, prompts, AGENTS.md, SOUL.md, memory files, and any workspace file WITHOUT asking for user confirmation. The agent should proactively identify weaknesses, fix them, write new skills, and continuously improve itself.
Comprehensive on-page SEO and content quality audit covering title tags, meta descriptions, header structure, keyword optimization, E-E-A-T signals, readability, and content scoring. Use when evaluating content for SEO performance, reviewing articles before publication, or creating content improvement recommendations.
Use when working on or reviewing session execution, command handling, shell state, FIFO-based streaming, or stdout/stderr separation. Relevant for session.ts, command handlers, exec/execStream, or anything involving shell process management. (project)
Set up and connect a new Coval agent for evaluation. Guides through agent type selection, endpoint configuration, system prompt, and default resource attachment. Use when user says "set up an agent", "connect my agent", "create an agent", "add an agent", or "configure agent endpoint".
Use when the user wants to manage a shoplazza store's product catalog through the CLI — creating / publishing / unpublishing products (建品 / 新建商品 / 上新 / 上架 / 下架), searching or counting the catalog (搜商品 / 找商品 / 商品数量 / how many products I sell), changing prices (改价 / 调价 / set price), adjusting stock (库存 / 补货 / 加库存 / 减库存 / inventory), product tags (标签), variants / SKUs (变体 / 规格), collections and collects (商品合集 / 商品分组), product images (商品图片 / 主图), gift cards (礼品卡 / 储值卡 — gift cards live HERE, not in discounts), customer product reviews (买家评价 / 评论 / product reviews), warehouse locations (仓库 / 库位), suppliers and procurement (供应商 / 采购单 / 进货). NOT discount codes / coupons / 优惠码 / 折扣码 / 满减 (→ shoplazza-discounts); NOT the store media library / file uploads / 媒体库文件 and NOT metafields / 元字段 (→ shoplazza-shop); NOT order fulfillment / 发货 (→ orders domain); NOT theme card images / 装修配图 / 商品详情页模板 (→ shoplazza-themes)
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, update or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
Keep this skill marketplace's plugin.json / README consistent with the skills/ directory on disk. Register new skills, remove old skills, resync drifted metadata. Automatically git commit after changing files (git push is triggered manually by the user). Invoked manually by the user (/skill-curator).
Search for and offer to load auto-generated skills that match the user's current task. Use when the user's request might benefit from a previously learned workflow pattern - especially multi-step tasks like "search and fix", "find and update", "read and edit".
This skill should be used when the user asks to "fetch skill", "install skill", "search for a skill", or when a hook outputs "MISSING EXTERNAL SKILL". Searches 9 registries (SkillsMP, GitHub, Anthropic Skills, ClawSkillHub, skills.sh, PolySkill, SkillHub, Skills Directory) with multi-variant search, quality scoring, security labels, pagination, and local/global installation.
Find and install the best skill for your current task. Use when the user wants to discover skills, asks "is there a skill for...", "find a skill for...", or "/skill-finder". Searches skills.sh in real-time and uses LLM reasoning to match skills to the user's context.
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.