Skills
El registro abierto de Skills para agentes de IA: prompts estructurados y flujos de trabajo con modelos recomendados, ejemplos y herramientas compatibles.
Skills
153
Categorías
9
Herramientas compatibles
5
Colaboradores
2
Mostrando 22–42 de 100 Skills
Defines versioned data contracts between producers and consumers, with ownership, schemas, quality expectations, compatibility rules, and operational change management.
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.
Designs reliable AI-assisted business and engineering automations with triggers, approvals, idempotency, observability, exception handling, and human handoff points.
Converts product safety requirements into practical agent and LLM policies with abuse cases, escalation paths, safe defaults, audit events, and acceptance criteria.
Converts a design specification or screenshot into accessible, responsive production UI while preserving component boundaries, design tokens, semantic structure, and states.
Defines repeatable quality evaluation for LLM outputs using representative datasets, scoring rubrics, model-graded checks, human review sampling, and regression thresholds.
Synthesizes interviews, support tickets, reviews, and survey responses into evidence-based themes, opportunities, representative quotes, confidence levels, and product actions.
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.
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.
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.
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.
Creates accessible color palettes for brands and UIs from a brief or a seed color. Produces primary, secondary, and neutral scales with hex values, suggests semantic tokens (success, warning, error, info), and checks foreground/background pairings against WCAG contrast ratios. Outputs ready-to-use CSS variables or design tokens.
Explains what a SQL query does in plain language and how it executes. Breaks down joins, subqueries, CTEs, and window functions step by step, describes the result set, reads EXPLAIN/EXPLAIN ANALYZE output to identify slow scans and missing indexes, and flags correctness pitfalls. Helps developers understand, review, and trust unfamiliar SQL.
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.
Designs caching strategies across the stack to cut latency and load. Chooses cache layers (browser, CDN, application, database), picks patterns (cache-aside, read-through, write-through, write-behind), sets TTLs and eviction policies, and plans invalidation to avoid staleness and stampedes. Produces a layered plan with keys, TTLs, and invalidation rules.
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.
Drafts long-form blog posts from a topic, outline, or set of notes. Handles title and hook generation, logical section structure, SEO-aware headings, tone matching, internal linking suggestions, and a clear call to action. Produces publish-ready Markdown with meta description and suggested tags.
Reviews and rewrites resumes and CVs to be clear, achievement-focused, and ATS-friendly. Rewrites bullet points using strong action verbs and quantified impact, aligns wording to a target job description, flags gaps and red flags, and checks formatting for applicant tracking system compatibility.
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.
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.