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
21
Categorías
9
Herramientas compatibles
5
Colaboradores
1
Mostrando 1–21 de 21 Skills
Converts a design specification or screenshot into accessible, responsive production UI while preserving component boundaries, design tokens, semantic structure, and states.
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 reliable JSON and typed outputs for LLM features, including schemas, validation, recovery paths, versioning, examples, and contracts for downstream consumers.
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.
Builds robust webhook producers and consumers. Covers signature verification, idempotency keys, retry with exponential backoff, dead-letter handling, event ordering, and replay endpoints, and generates handler code plus tests so integrations survive duplicates and outages.
Adds clear, accurate inline comments and API doc blocks to existing code without changing behavior. Generates docstrings and structured comments (JSDoc, Google/NumPy style, Javadoc, Rustdoc) that explain intent, parameters, return values, side effects, and edge cases, while avoiding noisy comments that merely restate the code.
Generates mobile application prototypes and implementations for iOS and Android. Creates SwiftUI views, Jetpack Compose layouts, and React Native components from descriptions or wireframe images. Handles navigation patterns, state management, and platform-specific design guidelines.
Analyzes and resolves git merge conflicts by understanding the intent of both sides. Examines the conflict markers, surrounding context, and commit history to produce a correct merged result that preserves both changes without breaking functionality.
Designs and implements comprehensive error handling for APIs. Covers error response formats (RFC 7807 Problem Details), HTTP status code selection, error logging strategies, retry logic, and client-friendly error messages with proper i18n support.
Generates TypeScript type definitions from various sources — JSON data, API responses, database schemas, or plain descriptions. Produces strict types with proper generics, utility types, discriminated unions, and JSDoc comments.
Explains complex code in plain language at the requested level of detail. Breaks down algorithms, design patterns, and architecture decisions. Adapts explanation depth from high-level overview to line-by-line walkthrough based on audience.
Generates complete OpenAPI 3.1 specifications from API descriptions, existing code, or route definitions. Includes request/response schemas, authentication, error responses, examples, and server configurations. Produces valid YAML ready for Swagger UI.
Generates production-ready React components with TypeScript, proper props interfaces, accessibility attributes, responsive design, and test files. Follows modern patterns including Server Components, Suspense boundaries, and composition over inheritance.
Translates code between programming languages while preserving logic, idioms, and best practices of the target language. Handles differences in type systems, error handling, concurrency models, and standard library APIs. Produces idiomatic target code, not line-by-line transliteration.
Guides systematic code refactoring while preserving exact behavior. Identifies code smells, suggests appropriate refactoring patterns, and executes transformations incrementally with verification at each step. Follows Chesterton's Fence principle — understands why code exists before changing it.
Designs, optimizes, and iterates on prompts for LLM applications. Covers system prompt design, few-shot examples, chain-of-thought reasoning, output formatting, and prompt testing strategies. Helps build reliable AI-powered features.
Systematic debugging workflow that helps identify, isolate, and fix bugs. Follows a structured approach: reproduce, localize, reduce, fix, guard. Analyzes error messages, stack traces, and logs to pinpoint root causes rather than symptoms.
Identifies and resolves performance bottlenecks in code and systems. Covers algorithmic complexity analysis, memory optimization, caching strategies, database query tuning, and frontend performance (Core Web Vitals). Follows a measure-first approach.
Revisión automatizada de código que ofrece comentarios aplicables sobre calidad, posibles errores, problemas de rendimiento, vulnerabilidades de seguridad e incumplimientos de estilo. Analiza los cambios con el rigor de un ingeniero sénior y aporta sugerencias concretas con ejemplos de código.
Diseña API RESTful y GraphQL siguiendo principios de contrato primero. Abarca la estructura de endpoints, los esquemas de solicitudes y respuestas, la gestión de errores, el versionado, la paginación, la autenticación y los límites de uso. Produce especificaciones OpenAPI/Swagger y scaffolding de implementación.
Builds, explains, and tests regular expressions from natural language descriptions. Supports multiple regex flavors (PCRE, JavaScript, Python, Go). Provides step-by-step breakdowns, test cases, and performance considerations for complex patterns.
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.