Skills
El registro abierto de Skills para agentes de IA: prompts estructurados y flujos de trabajo con modelos recomendados, ejemplos y herramientas compatibles.
Skills
199
Categorías
9
Herramientas compatibles
6
Colaboradores
1
Mostrando 85–100 de 100 Skills
Drafts clear product requirements documents from rough ideas or stakeholder notes. Structures the problem statement, goals and non-goals, user stories, acceptance criteria, success metrics, and open questions, and surfaces ambiguities and edge cases that need decisions before engineering starts.
Sets up and interprets mutation testing to measure real test-suite effectiveness beyond line coverage. Configures tools like Stryker, PIT, or mutmut, explains surviving mutants, recommends targeted tests to kill them, and tunes performance for CI. Helps teams find tests that assert nothing and coverage that lies.
Reviews cloud IAM policies for least-privilege violations, overly broad wildcards, privilege escalation paths, and risky trust relationships across AWS, GCP, and Azure. Explains the risk of each finding and rewrites policies to grant only the permissions actually needed.
Designs evaluation harnesses for LLM applications, covering dataset construction, task-specific metrics, LLM-as-judge rubrics with bias controls, and regression gates. Helps teams measure quality, catch regressions across model or prompt changes, and report results with confidence intervals rather than vibes.
Configures HTTP security headers to harden web applications. Covers Content-Security-Policy (including nonces and strict-dynamic), HSTS, X-Content-Type-Options, Referrer-Policy, Permissions-Policy, COOP/COEP/CORP, and cookie flags. Produces server/CDN configuration, explains tradeoffs, and provides a rollout plan using report-only mode to avoid breakage.
Designs data quality checks for tables, pipelines, and warehouses. Generates expectation suites covering schema conformance, null and uniqueness constraints, referential integrity, freshness, and statistical drift, then wires them into pipelines so bad data is caught before it reaches dashboards or models.
Turns reliability goals into concrete SLIs, SLOs, and error budgets. Helps choose the right service level indicators, set realistic targets from historical data, compute burn rates, and design multi-window multi-burn-rate alerting so teams get paged before the budget is exhausted.
Turns strategy into well-formed Objectives and Key Results. Coaches on ambitious yet measurable objectives, outcome-based (not output-based) key results, leading vs lagging indicators, alignment across teams, and quarterly cadence with check-ins and scoring. Flags common anti-patterns like task lists disguised as OKRs.
Designs routing layers that dispatch requests across multiple LLMs based on task type, difficulty, latency, cost, and reliability. Covers classifier-based and heuristic routing, fallbacks and retries across providers, quality scoring, and A/B evaluation of routing policies. Helps teams get frontier quality where it matters and cheap models everywhere else.
Analyzes cloud spend and produces a FinOps optimization plan. Covers rightsizing, autoscaling, spot/reserved/savings plans, storage tiering, idle resource cleanup, data transfer reduction, and tagging for cost allocation. Prioritizes actions by savings and risk, and defines guardrails and budgets to prevent regressions.
Generates and validates Software Bills of Materials in CycloneDX or SPDX formats. Covers dependency inventory, transitive resolution, license and vulnerability annotation, VEX statements, container image SBOMs, and CI integration for supply-chain compliance. Helps teams meet regulatory requirements and track what is actually shipped.
Curates high-quality datasets for supervised fine-tuning (SFT) and preference optimization (DPO/RLHF). Covers deduplication, quality filtering, formatting into chat/instruction templates, train/validation splits, label balancing, contamination checks against eval sets, and PII scrubbing. Produces clean, well-documented datasets ready for training.
Implements secure OAuth 2.0 and OpenID Connect flows including authorization code with PKCE, client credentials, and device code grants. Generates token exchange logic, refresh handling, state/nonce validation, and secure token storage. Flags common pitfalls like implicit flow usage, missing PKCE, and insecure redirect URI handling.
Designs recommendation systems end to end: candidate generation, ranking, and re-ranking. Covers collaborative filtering, content-based and embedding retrieval, two-tower models, cold-start strategies, feature stores, offline/online evaluation (NDCG, recall@k), and feedback loops. Produces an architecture and evaluation plan tailored to the product.
Adds production-grade observability to a codebase by instrumenting it with structured logs, metrics, and distributed traces. Recommends span boundaries, cardinality-safe labels, and OpenTelemetry conventions, then generates the wiring code and dashboards needed to make a service debuggable in production.
Designs and scaffolds ergonomic command-line tools with subcommands, flags, config files, shell completions, and helpful error output. Covers argument parsing conventions, exit codes, stdin/stdout piping, colored output, progress indicators, and cross-platform packaging. Produces maintainable CLIs that follow POSIX conventions and feel great to use.
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.