Skills
El registro abierto de Skills para agentes de IA: prompts estructurados y flujos de trabajo con modelos recomendados, ejemplos y herramientas compatibles.
Algunas descripciones forman parte del piloto de traducción automática y aún no han sido revisadas.
Skills
80
Categorías
9
Herramientas compatibles
6
Colaboradores
2
Mostrando 1–21 de 80 Skills
Builds regression suites for prompts and agent instructions so teams can detect quality, safety, format, and tool-selection regressions before deploying changes.
Defines versioned data contracts between producers and consumers, with ownership, schemas, quality expectations, compatibility rules, and operational change management.
Synthesizes interviews, support tickets, reviews, and survey responses into evidence-based themes, opportunities, representative quotes, confidence levels, and product actions.
Designs reliable AI-assisted business and engineering automations with triggers, approvals, idempotency, observability, exception handling, and human handoff points.
Turns merged work, pull requests, issues, and user-visible behavior changes into accurate, audience-specific release notes with breaking-change and upgrade guidance.
Designs reliable JSON and typed outputs for LLM features, including schemas, validation, recovery paths, versioning, examples, and contracts for downstream consumers.
Converts a loosely defined opportunity into testable product requirements, user journeys, scope boundaries, assumptions, risks, success metrics, and discovery questions.
Convierte un repositorio desconocido en una guía de ingeniería concisa que explica la arquitectura, las convenciones, la configuración local, las rutas de ejecución principales y las primeras contribuciones de bajo riesgo.
Designs trustworthy product analytics events, properties, identity rules, validation, privacy boundaries, dashboards, and governance for product and growth decisions.
Produces clear, reviewable architecture decision records that capture context, alternatives, trade-offs, consequences, rollout steps, and reversal criteria.
Produces blameless, actionable incident postmortems with a precise timeline, contributing factors, impact, decisions, corrective actions, owners, and measurable follow-through.
Audita interfaces de producto según requisitos prácticos de accesibilidad, incluidos la estructura semántica, el acceso mediante teclado, el comportamiento del foco, el contraste de color, los lectores de pantalla y los formularios.
Designs and implements rate limiting for APIs and services. Recommends an algorithm (token bucket, leaky bucket, fixed or sliding window) for the use case, defines per-key and per-endpoint limits, plans distributed enforcement with Redis, and specifies response headers and 429 handling with retry-after. Produces a design plus reference implementation.
Produces structured test plans for features and releases. Defines scope and objectives, derives test cases from requirements and acceptance criteria, covers functional, edge, negative, performance, and accessibility cases, sets entry/exit criteria, and maps risk to test priority. Outputs a clear plan with a traceability matrix linking tests to requirements.
Produces operational runbooks for services and common incidents. Documents prerequisites, step-by-step diagnosis and remediation, exact commands, verification checks, rollback steps, and escalation paths. Structures each runbook so an on-call engineer can follow it under pressure, and keeps destructive steps clearly flagged with safeguards.
Sets up and maintains Git hooks for a repository. Recommends a manager (Husky, Lefthook, or pre-commit), wires up pre-commit and commit-msg hooks for linting, formatting, type checks, secret scanning, and conventional-commit validation, and keeps hooks fast with staged-file filtering. Produces config plus a short contributor guide.
Produces production-ready nginx configuration for common scenarios: reverse proxy, load balancing, TLS termination, static file serving, HTTP/2, gzip/brotli, caching, rate limiting, and security headers. Explains each directive, warns about risky defaults, and includes a validation step so the config can be tested before reload.
Decodes and reviews JSON Web Tokens and their surrounding auth flow for correctness and security. Explains header and claims, checks algorithm and key handling, validates expiration and audience/issuer claims, and flags common pitfalls such as the alg:none attack, weak secrets, missing validation, and over-long token lifetimes. Never treats token contents as trusted secrets to echo back.
Inspects messy tabular data and produces a repeatable cleaning plan plus code. Detects and fixes common issues: inconsistent types, duplicate rows, missing values, malformed dates, mixed encodings, whitespace and casing problems, and outliers. Outputs pandas or Polars code, a summary of changes, and a validation checklist.
Translates requirements and user stories into behavior-driven development scenarios in Gherkin. Writes clear Given/When/Then steps, covers happy paths, edge cases, and negative cases, uses scenario outlines with examples for data-driven tests, and keeps steps declarative and reusable. Optionally scaffolds step definitions for Cucumber or Behave.
Generates and refactors dbt models for analytics engineering. Writes staging, intermediate, and mart models following layered conventions, adds schema.yml tests and descriptions, applies incremental and materialization strategies, and structures sources and refs correctly. Produces SQL plus YAML that fits dbt best practices and is ready to run.
Skills frente a servidores MCP
¿cuál es la diferencia?Skillsel «qué hacer»
Una Skill reúne conocimientos prácticos —instrucciones, un prompt de ejemplo y modelos recomendados— para que un agente realice una tarea de forma consistente. Las Skills aportan conocimiento, no nuevas conexiones.
Servidores MCPel «cómo conectarse»
Un servidor MCP proporciona nuevas capacidades a un agente conectándolo con sistemas reales —bases de datos, API o archivos— mediante un transporte. MCP añade conexiones y acciones, no instrucciones de tarea.
Regla práctica: usa una Skill cuando necesites que el modelo realice bien una tarea y un servidor MCP cuando necesites conectarlo con una herramienta o sistema. Se complementan: una Skill puede utilizar las herramientas que proporciona un servidor MCP.
¿Has creado una Skill útil?
Envía un archivo SKILL.md: es de código abierto y está mantenido por la comunidad.