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
199
Categorías
9
Herramientas compatibles
6
Colaboradores
1
Mostrando 1–21 de 100 Skills
Designs and drives computer-use agents that operate a desktop or browser directly via screenshots and UI actions (click, type, scroll, navigate). Plans multi-step GUI workflows, handles verification and recovery between steps, and structures guardrails for safe autonomous execution. Built for models exposing computer use as a native client-side tool.
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.
Converts a loosely defined opportunity into testable product requirements, user journeys, scope boundaries, assumptions, risks, success metrics, and discovery questions.
Defines repeatable quality evaluation for LLM outputs using representative datasets, scoring rubrics, model-graded checks, human review sampling, and regression thresholds.
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.
Designs reliable AI-assisted business and engineering automations with triggers, approvals, idempotency, observability, exception handling, and human handoff points.
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.
Synthesizes interviews, support tickets, reviews, and survey responses into evidence-based themes, opportunities, representative quotes, confidence levels, and product actions.
Converts product safety requirements into practical agent and LLM policies with abuse cases, escalation paths, safe defaults, audit events, and acceptance criteria.
Simulates realistic adversarial behavior against AI features to uncover prompt injection, data exfiltration, unsafe tool use, jailbreak, and authorization failures before launch.
Tests AI agent tool use with realistic fixtures, malformed inputs, permission boundaries, deterministic assertions, and recovery checks for failed or partially completed actions.
Converts a design specification or screenshot into accessible, responsive production UI while preserving component boundaries, design tokens, semantic structure, and states.
Optimizes prompts and agent workflows for finite context windows by prioritizing evidence, compressing history, managing retrieval budgets, and measuring token-cost trade-offs.
Designs durable memory for AI agents, including what to retain, how to retrieve it, privacy boundaries, expiration policies, and evaluation criteria for useful recall.
Reviews cloud and AI infrastructure spend to identify measurable savings while preserving reliability, performance, security, ownership, and product requirements.
Diagnoses failing browser and end-to-end tests by correlating assertions, traces, screenshots, network activity, timing, and application state into reproducible fixes.
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.