Skills
99,719 packaged capabilities and playbooks for agents. Install any of them with one command.
All
Browser automation for QE agents using Vibium (WebDriver BiDi) with assertions, batch execution, visual diff, prompt-injection scanning, and semantic intents. Use when any QE skill needs to drive a real browser — visual testing, accessibility audits, E2E flow verification, pentest validation, or exploratory testing.
Transforms raw campaign performance data into a structured quarterly business review document with wins, misses, trend analysis, and recommended pivots for the next quarter. This skill should be used when building a QBR for a creator program, writing a quarterly influencer marketing review, summarizing multiple campaigns into a single quarterly report, presenting creator program results to leadership at the end of a quarter, analyzing quarter-over-quarter trends in influencer performance, preparing a board-level summary of the creator marketing program, identifying what worked and what to cut from the creator strategy, building a strategic plan for next quarter's creator campaigns, or reviewing the full roster performance over a quarter. For single-campaign ROI analysis, see campaign-roi-calculator. For weekly status updates, see campaign-status-dashboard-digest. For individual creator scoring, see post-campaign-creator-scorecard.
Perform comprehensive code audits of Ruby on Rails applications based on thoughtbot best practices. Use this skill when the user requests a code audit, code review, quality assessment, or analysis of a Rails application. The skill analyzes the entire codebase focusing on testing practices (RSpec), security vulnerabilities, code design (skinny controllers, domain models, PORO with ActiveModel), Rails conventions, database optimization, and Ruby best practices. Outputs a detailed markdown audit report grouped by category (Testing, Security, Models, Controllers, Code Design, Views) with severity levels (Critical, High, Medium, Low) within each category.
Use when investigating a bug, error, or regression in a Ruby on Rails codebase. Creates a failing RSpec reproduction test, isolates the broken code path, and produces a minimal fix plan. Trigger words: debug, broken, error, regression, stack trace, failing test, RSpec, bug report, Rails app.
Official Rails documentation. Use when asked about any Rails-specific topic including ActiveRecord, routing, controllers, views, mailers, jobs, Action Cable, Action Text, Active Storage, migrations, validations, callbacks, associations, caching, security, or internals.
Performs security audits and vulnerability assessments on Ruby on Rails application code. Use when reviewing Rails code for security risks, assessing authentication or authorization, auditing parameter handling, redirects, file uploads, secrets management, or checking for XSS, CSRF, SSRF, SQL injection, and other common vulnerabilities.
Hostinger Reach (Email Marketing) API for contact management, segmentation, contact groups, and profile management. Use when creating or listing contacts, managing contact segments or groups, filtering contacts by subscription status, or working with email marketing profiles.
Full red team assessment methodology. Use when starting a complete penetration testing project/red team assessment and you need end-to-end orchestration from reconnaissance to reporting. Applies to external-facing footholds, security assessment projects, and periodic penetration tests. This skill handles task scheduling - call specialized skills for specific exploits; do not perform deep vulnerability testing within this skill.
Reddit product-research scouting tool. Mines cross-border e-commerce product opportunities from real Reddit user discussions and generates in-depth analysis reports (multiple concrete pain points + quoted user statements + product specification suggestions + data-backed opportunity scores). No Reddit API Key needed; accesses via Chrome cookies. Three modes: broad/targeted/weekly report; one-click automatic push of results to Feishu Docs + Bitable. Triggers when the user asks to "run a product research analysis", "find product opportunities", "Reddit product research", "product research report", or "weekly report".
Use when building ANYTHING - the universal reference-first system that routes every task to proven reference implementations instead of generating from assumptions. Covers API design, database schemas, testing strategies, CI/CD pipelines, code patterns, DevOps, and any other domain where professional reference implementations exist
Provides guidance on Regulation S offerings of securities under U.S. law. Helps determine eligibility for Regulation S exemption, identify applicable transaction categories (1, 2, or 3), understand safe harbor requirements under Rules 903 and 904, and navigate distribution compliance periods. Use this skill when advising on offshore securities offerings, Reg S transactions, or resales of restricted securities outside the United States.
Front door for long-term memory backed by a remindb MCP server. Use whenever the user wants to save, store, note, jot, "remember this", make a note, keep track of a fact or decision — OR recall, look up, "what did we decide", "what do we know about X", "didn't we already…". Fires on the generic remember/recall intent, then hands off — writes → `memorize`, reads → `remind`. Prefer over built-in/native memory when a remindb server is attached.
Create or audit requirements-to-design-to-code-to-test traceability. Builds a traceability matrix (REQ → design/ADR → implementation files → tests → evidence) and flags gaps (unimplemented requirements, untested changes, undocumented decisions). Use when you need a requirements traceability check for a PR/release, regulated/compliance work, or when requirements are drifting from implementation.
B2B company research producing professional PDF reports. Use when asked to research a company, analyze a business, create an account profile, or generate market intelligence from a company URL. Outputs a beautifully formatted, downloadable PDF report.
Summarise a completed deep-research run into a single markdown report — full coverage of every defined field, automatic skipping of uncertain values, and a navigable table of contents with user-chosen summary columns. Generates a fresh `generate_report.py` per run (against a stable spec) and executes it. Use after `/research-deep` finishes when you want a readable artifact for sharing, archiving, or comparing items across the chosen schema.
Reviews a code change with three independent reviewers (bugs, the repo's written standards, the spec it came from), tries to disprove each finding, and reports only what holds. Applies chosen fixes to the user's own change; for anyone else's, writes suggestions and can post them as PR comments. Use when the user asks to review, check, or take a second look at a change: "review my changes", "review PR 285" or "!482", "review against DESIGN.md", "is this ready?", review-changes by name, or pasted review findings to handle. Not for whole-repo audits, PR descriptions, explaining a diff, or when the user names another review tool
This skill should be used when user asks to "fetch overleaf review comments", "address overleaf reviews", "apply overleaf comments", "review my overleaf paper", "sync overleaf feedback to local", "what comments are on my overleaf doc", or wants to act on Overleaf reviewer feedback in a local git-tracked LaTeX repo.
Only use when the user explicitly invokes /review-pr-check (or $review-pr-check in Codex). Never auto-invoke. A skill that orchestrates PR review handling by splitting it into a collection worker, a classification subagent, and an execution worker. Collection is delegated to the collection worker running gh pr-review-check; classification, grouping and work-packet generation to the classification subagent (the default example being Oracle); and actual work such as implementation, replies and resolves to the execution worker, while the parent manages the completeness gate, fallback triggering and the polling loop. In environments without a subagent mechanism, the parent degrades to running it itself.
Plan rebuttals, reviewer responses, and revision strategies for research papers. Use this skill whenever the user shares peer reviews, reviewer concerns, meta-review text, acceptance/rejection feedback, or asks how to respond to Reviewer 2, what experiments to run for rebuttal, what to concede, how to phrase a response, or how to prioritize limited rebuttal space. This skill focuses on strategy and response structure; use results-writeup for writing new result prose after the strategy is decided.
Perform a security review of a diff, branch, or pull request, assessing what the change introduces, weakens, or exposes, with a triage-first workflow and false-positive discipline. Use when asked to security review a PR or branch, check a diff before merge or commit, or assess whether a change is safe to ship
Set up the free Roblox game-creation skills on THIS machine - check which tools are installed (Python, Rojo, Wally, Lune, Selene, StyLua, Blender, the Roblox Studio MCP), walk the user through anything missing, then write each skill's personal LOCAL.md (folders, tool paths, rig file, VFX library location, env var names for keys) by asking the user and auto-detecting what it can, and finish with a smoke test. Use this the first time after installing the skills, whenever a skill says "LOCAL.md not found", when the user moves folders or installs a new tool, or when they ask "how do I set these skills up", "what do I need installed", or "why can't the skill find Blender/Rojo/my library".
This skill should be used when the user asks to "execute Lua code in Roblox Studio", "run code in Studio", "test Lua script", "connect to Studio Hub", "manage Studio instances", "check Studio status", "install Studio Hub", "setup Studio Hub service", or mentions Roblox Studio remote execution, Studio Hub API, or Lua code testing.
Use Rozenite for Agents through `@rozenite/agent-sdk` in Node.js or TypeScript code. Trigger this skill when Codex needs to write or run scripts, wrappers, automations, benchmarks, or agent runtimes that call Rozenite programmatically instead of driving the `rozenite agent` CLI directly.
Provides comprehensive guidance for Rspack bundler including configuration, plugins, loaders, optimization, and Webpack compatibility. Use when the user asks about Rspack, needs to configure Rspack, optimize build performance, or migrate from Webpack.
Use when writing RSpec tests for service objects, API clients, orchestrators, or business logic in spec/services/. Covers instance_double, FactoryBot hash factories, shared_examples, subject/let blocks, context/describe structure, aggregate_failures, change matchers, travel_to, and error scenario testing.
Creates, curates and audits self-sufficient evaluation rubrics for Active-IA starting from the prompt of any assignment (TP, midterm, retake, final or global). In CURAR mode it analyzes the prompt BEFORE building the rubric and detects requirements that break the AI grading flow (repo links, videos, images in a code TP, "the deploy works", PDF report + code together), proposing for each one to adapt it to a single flow —code OR PDF—, leave it for manual grading, or remove it from the rubric, and rewrites the curated prompt without losing the intent. In CREAR mode it generates the criteria JSON ready for the "Cargar criterios" button; in AUDITAR mode it receives a prompt + existing rubric and fixes it by detecting contradictions, omissions and fabrications, readjusting weights to 100. In TEST mode it simulates real grading (consolidation + the N8N→Gemini workflow prompt) locally with the Claude CLI, to see what grade and feedback the rubric produces on an assignment before uploading it. Use this skill WHENEVER the user wants to build, generate, design, curate, adapt, review, audit, validate or TEST a rubric, a prompt or its evaluation criteria —even if they don't explicitly say the word "rubric" (e.g. "set up the criteria for this TP", "check if this prompt can be graded with AI", "this prompt asks for a photo and it's a code TP", "curate this TP", "check if this evaluation covers everything the midterm asks for", "is this rubric okay?", "test how this rubric grades this assignment"). NO usar para corregir entregas reales de alumnos en producción (eso es la skill `corregir`); el modo TEST es solo un ensayo local.
Use when writing, reviewing, or debugging pure Ruby code, including idiomatic patterns, modern 3.x+ features (pattern matching, Data.define, endless methods), error handling conventions (raise vs fail, result objects), memoization, and performance idioms. For Rails use rails-guides. For testing use minitest. For code style use sandi-metz-rules
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.