Skills
99,951 packaged capabilities and playbooks for agents. Install any of them with one command.
All
Simulates a panel of distinct beta-reader personas reacting to a manuscript chapter by chapter — where they're confused, bored, delighted, or lost. Use it when a writer wants a reader's-eye reaction to a draft before recruiting real beta readers, or between drafts to find the places the story isn't landing. It reacts as readers; it never writes or rewrites the author's prose.
Use when /better-harness reviews the outer coding-agent Harness for lifecycle controls, repeated work, project feedback, agent assets, session outcomes, repair planning, durable reports, finding-bound fixes, or manual direct fixes. Invoke only via slash command.
Core rules for bkit — PDCA methodology, level detection, agent triggering, quality standards, Sprint management (8-phase container with 4 auto-pause triggers, v2.1.13), and Trust Level scope (L0-L4 gates PDCA + Sprint auto-run). Triggers: bkit rules, core rules, methodology
Blender 5.x scene setup, render engines (Cycles/EEVEE), output formats, import/export (FBX/glTF/OBJ/USD/Alembic), linking/appending, color management (AgX/Filmic), view layers, viewport config, and world/environment setup via Python (bpy). Includes 5.1 changes (AVIF, HTJ2K, OpenColorIO 2.5, Light Path in World).
Resolve a named Arduino, ESP32, RP2040, or other embedded board to a source-backed exact profile, including pin/peripheral capability, voltage/current, buses, framework/core/toolchain, and variant or revision risks. Use this whenever a user asks for a board reference, pinout, GPIO restrictions, board capability, board profile, or safe handoff before pin assignment. Do not use it to choose a board from requirements; use board-selection for that decision.
Static analysis security vulnerability scanner for Ruby on Rails applications. Use when analyzing Rails code for security issues, running security audits, reviewing code for vulnerabilities, setting up security scanning in CI/CD, managing security warnings, or investigating specific vulnerability types (SQL injection, XSS, command injection, etc.). Also use when configuring Brakeman, reducing false positives, or integrating with automated workflows.
Create AI-optimized style guides for brand or personal voice. Extracts patterns from writing samples or AI-draft/final-sel calibration pairs, producing a reusable guide with tone rules, structure patterns, signature moves, anti-filler checklists, anti-pattern blacklists, and examples. Output is optimized for LLM consumption (Claude Projects, system prompts). Not for editing content (use copy-editor).
This skill should be used when the user asks to "test for broken authentication vulnerabilities", "assess session management security", "perform credential stuffing tests", "evaluate password policies", "test for session fixation", or "identify authentication bypass flaws". It provides comprehensive techniques for identifying authentication and session management weaknesses in web applications.
create and review ci/cd automation for bruno api tests. use when a user asks to run bruno collections in github actions, gitlab ci, jenkins, azure pipelines, bitbucket, kubernetes, or other pipelines; set up the official bruno github action or the official bruno cli docker image; generate junit, json, or html reports; configure environments, tags, secrets, safe mode, developer sandbox mode, workspace paths, or pull request api-test gates for bruno collections.
Develop architectural programs, space needs analyses, adjacency matrices, area schedules, and project briefs. Use when the user asks about programming a building, sizing spaces, determining area requirements, creating adjacency diagrams, building a space program, developing a brief, calculating net-to-gross ratios, analyzing space standards, comparing area benchmarks, constructing stacking diagrams, or validating a program against site capacity and budget. Also use when the user needs area tables for residential, office, healthcare, education, hospitality, retail, or cultural building types, or when checking compliance with NDSS, Neufert, NHS HBN, BB103, or ASHRAE standards.
Test an authorized web application for business-logic flaws and race conditions — the classes scanners cannot find. Model invariants (conservation of value, uniqueness, monotonicity, exclusivity), build an Actor x Action x Resource matrix, abuse state machines (skip/reorder/replay steps, limit-slicing), find numeric bugs (float-vs-decimal rounding, cross-currency refund arbitrage, negative amounts), stale feature gates, and saga gaps; prove concurrency bugs (double-spend, lost update, idempotency-key reuse) with controlled parallel requests. Use when the user mentions 'business logic testing,' 'race condition,' 'double spend,' 'TOCTOU,' 'concurrency bug,' 'idempotency,' 'coupon reuse,' 'workflow bypass,' 'limit bypass,' 'negative amount,' 'refund arbitrage,' 'parallel request attack,' or 'logic flaw'
The user is analyzing a stock or investment opportunity and needs to evaluate it from a "buying a business" rather than "buying a stock" perspective. Language signals: "how do this stock's technicals look" / "will the share price go up" / "what stock should I buy". Not applicable to: purely business management questions (when valuation is not involved).
When the user wants to measure, track, or reduce carbon emissions in the supply chain. Also use when the user mentions "carbon accounting," "GHG emissions," "Scope 1/2/3 emissions," "carbon footprint calculation," "emissions reporting," "carbon reduction," "climate impact," "decarbonization," or "emissions baseline." For circular economy approaches, see circular-economy. For sustainable sourcing, see sustainable-sourcing.
Builds geocoding workflows in CARTO that convert street addresses or place names into geographic coordinates. Triggers when the user mentions geocoding, address to coordinates, address resolution, geolocate addresses, "add geometry from addresses", lat/lon from address, place name to point, address matching, forward geocoding, converting addresses to points, or has tabular data with address columns but no spatial geometry column and needs to create one.
Builds Geographically Weighted Regression (GWR) workflows in CARTO. Triggers when the user mentions GWR, geographically weighted regression, spatially varying relationships, local regression, local coefficients, spatial regression, "what drives X in different areas", "why do prices vary spatially", "local factors affecting Y", varying coefficients, coefficient maps, spatial non-stationarity, or wants to model how the relationship between a dependent variable and predictors changes across geography. Produces per-cell regression coefficients that reveal how predictor importance shifts from place to place.
Preview an existing saved CARTO Builder map inline in the chat via the CARTO MCP server — resolve the map with read_maps (by name or search), then render it with view_map by map ID. Use whenever the user references a saved Builder map — by URL, by ID, or by name. Renders a lightweight read-only preview (layers, basemap, viewport, popups, legend). Widgets, SQL parameters, map description, and other Builder-only features are NOT included; the user can click "Open in Builder" for the full experience. Triggers on "show me the X map", "open the Y map", "preview the Z map", and inline previews of a freshly-created map. Distinct from carto-create-builder-maps (authoring), carto-render-inline-map (ad-hoc deck.gl spec), and carto-develop-app (developer app).
Render an ad-hoc interactive map inline in the chat from a deck.gl declarative spec via the CARTO MCP server's view_map tool. Use whenever the user asks to map, visualize, or show the geographic distribution of points, polygons, hexagons, quadbins, clusters, density (heatmaps), or raster — and the map is exploratory or throwaway, not meant to be saved as a permanent CARTO Builder map. Triggers on "show me X on a map", "visualize Y", "make a heatmap of Z", "render the points/clusters/raster of W". Distinct from carto-create-builder-maps (authoring permanent maps), carto-preview-builder-map (loading an existing saved Builder map), and carto-develop-app (writing a from-scratch deck.gl app in TypeScript / JavaScript).
Builds Moran's I spatial autocorrelation workflows in CARTO. Triggers when the user mentions spatial autocorrelation, Moran's I, spatial dependency, spatial correlation, spatial outliers, HH HL LH LL quadrants, high-high clusters, low-low clusters, spatial weight matrix, "is there clustering", "are values spatially correlated", local indicators of spatial association, LISA, spatial randomness test, or wants to determine whether a variable exhibits spatial clustering, dispersion, or randomness across a gridded dataset. Also relevant when the user needs to classify locations into cluster types (HH, HL, LH, LL) rather than just identifying hotspots and coldspots.
Guides the user through spatial enrichment workflows — triggered by requests to enrich, add demographics, estimate population around locations, compute spatial features, sociodemographic analysis, "what's around" queries, buffer/isochrone + join patterns, or trade area enrichment.
Use when the user asks to create, update, or review a source-controlled Cekura JSON CI/CD test suite for a voice AI repository; create Tests-as-Code specs; turn a voice-agent code change into regression coverage; add deterministic Cekura voice tests to CI; or test an STT, LLM, TTS, VAD, interruption, idle-timer, DTMF, or call-lifecycle pipeline; or set up a CI gate that blocks a merge when the voice pipeline regresses. Inspects the repository before authoring a compact JSON suite, validates it safely against Cekura, and wires the workflow that runs it.
Skill dedicated to the custom cabinet pitfall-avoidance guide. Covers the full process of countertop materials, cabinet doors and panels, hardware and accessories, wardrobes, shoe cabinets and sideboards, cabinet layout and dimensions, and whole-house customization pitfalls, integrating in reverse order the highlights of the Xi'an Renovation Classroom member-edition knowledge base to help users customize cabinets with less hassle and fewer pitfalls.
Build or review element charts — patent claim charts (infringement, invalidity, or examination) or civil element charts (any claim or defense), with precise citations in each cell and gap detection as the priority output. Use when the user requests element charts, claim charts, evidence charts, infringement or invalidity contentions, element-by-element mapping, or asks "what are we missing to prove [claim]"
Check ABAP code for compliance with Clean ABAP principles. Use this skill when users ask to check, validate, review, or analyze ABAP code for clean code compliance, code quality, best practices, or adherence to Clean ABAP guidelines. Triggers include requests like "check this ABAP code", "is this clean ABAP", "review my ABAP for clean code", "validate ABAP against clean code principles", or "analyze ABAP code quality".
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.