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
153
Categorías
9
Herramientas compatibles
5
Colaboradores
2
Mostrando 1–21 de 100 Skills
Finds, validates, and fixes security vulnerabilities end to end, going beyond audit-only review to produce verified patches. Reproduces the issue, proposes a minimal fix, and confirms the vulnerability is closed without breaking existing behavior. Models a CodeMender-style workflow where multiple agents detect, validate, and patch code security issues at scale.
Designs trustworthy product analytics events, properties, identity rules, validation, privacy boundaries, dashboards, and governance for product and growth decisions.
Diagnoses failing browser and end-to-end tests by correlating assertions, traces, screenshots, network activity, timing, and application state into reproducible fixes.
Designs reliable JSON and typed outputs for LLM features, including schemas, validation, recovery paths, versioning, examples, and contracts for downstream consumers.
Plans safe database schema and data migrations with backwards compatibility, staged rollout, validation, rollback, performance safeguards, and application coordination.
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.
Evaluates retrieval quality for search and RAG systems using grounded test sets, relevance metrics, failure taxonomy, chunking experiments, and actionable remediation.
Converts a loosely defined opportunity into testable product requirements, user journeys, scope boundaries, assumptions, risks, success metrics, and discovery questions.
Guides containment, evidence collection, root-cause analysis, customer communication, and remediation when an AI agent takes an unsafe, incorrect, or unauthorized action.
Designs traces, metrics, structured events, privacy controls, dashboards, and alerts for LLM applications so teams can diagnose quality, cost, latency, and tool-use behavior.
Produces clear, reviewable architecture decision records that capture context, alternatives, trade-offs, consequences, rollout steps, and reversal criteria.
Turns merged work, pull requests, issues, and user-visible behavior changes into accurate, audience-specific release notes with breaking-change and upgrade guidance.
Produces blameless, actionable incident postmortems with a precise timeline, contributing factors, impact, decisions, corrective actions, owners, and measurable follow-through.
Designs low-risk secret rotation for applications and agents, covering inventory, overlapping credentials, automation, audit evidence, emergency revocation, and rollback.
Designs durable API evolution plans with compatibility guarantees, deprecation policy, version negotiation, consumer communication, migration tooling, and operational telemetry.
Reviews Model Context Protocol servers for excessive permissions, unsafe tool design, prompt injection exposure, secret handling, authorization gaps, and auditability.
Builds regression suites for prompts and agent instructions so teams can detect quality, safety, format, and tool-selection regressions before deploying changes.
Crea evaluaciones repetibles para agentes de IA que miden el éxito de las tareas, el uso correcto de herramientas, la fundamentación, la latencia, el coste y la recuperación segura en escenarios realistas de extremo a extremo.
Optimizes prompts and agent workflows for finite context windows by prioritizing evidence, compressing history, managing retrieval budgets, and measuring token-cost trade-offs.
Designs and implements secure, ergonomic Model Context Protocol servers with precise tool schemas, transport selection, authentication boundaries, error contracts, and tests.
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.
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.