Skills
El registro abierto de Skills para agentes de IA: prompts estructurados y flujos de trabajo con modelos recomendados, ejemplos y herramientas compatibles.
Skills
22
Categorías
9
Herramientas compatibles
5
Colaboradores
1
Mostrando 1–21 de 22 Skills
Reviews cloud and AI infrastructure spend to identify measurable savings while preserving reliability, performance, security, ownership, and product requirements.
Produces blameless, actionable incident postmortems with a precise timeline, contributing factors, impact, decisions, corrective actions, owners, and measurable follow-through.
Designs traces, metrics, structured events, privacy controls, dashboards, and alerts for LLM applications so teams can diagnose quality, cost, latency, and tool-use behavior.
Guides containment, evidence collection, root-cause analysis, customer communication, and remediation when an AI agent takes an unsafe, incorrect, or unauthorized action.
Optimizes prompts and agent workflows for finite context windows by prioritizing evidence, compressing history, managing retrieval budgets, and measuring token-cost trade-offs.
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.
Writes idempotent Ansible playbooks and roles from a described target state. Structures tasks with proper handlers, variables, and templates; favors modules over shell commands; applies role-based layout and inventory grouping; and adds check-mode safety and tags. Produces playbooks that are re-runnable without unintended side effects.
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.
Writes reusable, well-structured Terraform modules with clean input/output interfaces, sensible defaults, validation rules, and examples. Covers module composition, variable typing and validation, remote state and backends, provider version pinning, and testing with terraform validate/plan and tools like Terratest. Emphasizes least-privilege IAM and safe defaults.
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.
Generates and refactors Helm charts to package Kubernetes applications. Produces templated manifests, values.yaml with sensible defaults, helpers, chart dependencies, and hooks, and parameterizes images, resources, probes, and ingress so a workload can be deployed consistently across environments.
Reviews and rewrites Dockerfiles for smaller images, faster builds, and better security. Applies multi-stage builds, optimal layer ordering and caching, minimal base images, non-root users, and .dockerignore tuning, and flags vulnerabilities and bloat while keeping the build reproducible.
Designs feature-flagging and progressive-delivery strategies and generates the integration code. Covers flag naming and lifecycle, targeting and segmentation rules, percentage rollouts, kill switches, and cleanup of stale flags across providers like LaunchDarkly, Unleash, Flagsmith, or a homegrown config service.
Parses and analyzes application, system, and access logs to surface errors, anomalies, and root causes. Correlates events across services, identifies recurring patterns and spikes, extracts structured fields from unstructured lines, and produces a prioritized summary with likely causes and recommended next steps.
Generates production-ready Kubernetes manifests — Deployments, Services, Ingresses, ConfigMaps, Secrets, HPAs, and more — from a plain-language description of the workload. Applies best practices for resource limits, health probes, security contexts, and rolling update strategies, with optional Kustomize overlays or Helm chart scaffolding.
Generates production-ready infrastructure as code (IaC) configurations for cloud deployments. Supports Terraform, Pulumi, CloudFormation, and CDK. Creates modular, reusable infrastructure components with proper networking, security groups, IAM policies, and monitoring configurations.
Generates and assists with incident response procedures for production systems. Helps with root cause analysis, creates runbooks for common failure modes, builds communication templates for stakeholders, and produces post-incident review documents. Supports SRE and on-call workflows.
Builds and explains cron expressions from natural language schedules. Supports standard cron (5-field), extended cron (6-field with seconds), and cloud-specific formats (AWS EventBridge, Google Cloud Scheduler). Validates expressions and shows next run times.
Plans and generates migration strategies for framework upgrades, language versions, database changes, and architecture shifts. Produces step-by-step migration guides with rollback plans, risk assessment, and automated codemods where possible.
Generates Docker Compose configurations from application requirements. Handles service dependencies, networking, volumes, health checks, environment variables, and multi-stage builds. Supports development and production profiles.
Generates .env files, configuration schemas, and environment variable documentation from application requirements. Includes validation rules, default values, required vs optional flags, and example values. Supports multiple environments (dev/staging/prod).
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.