Skill do DevOps/Deployer para dockerização, CI/CD, e deploy de aplicações. Use quando precisar criar Dockerfile, docker-compose, configurar pipeline CI/CD, deploy em cloud, configurar nginx, SSL, ou qualquer operação de infraestrutura. Trigger em: "deploy", "Docker", "Dockerfile", "docker-compose", "CI/CD", "pipeline", "GitHub Actions", "nginx", "SSL", "produção", "staging", "Kubernetes", "AWS", "infraestrutura", "ambiente", "build", "release".
89
Quality
88%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description that excels across all dimensions. It clearly defines the DevOps/Deployer domain with specific capabilities, provides comprehensive trigger terms that users would naturally use, and explicitly states both what the skill does and when to use it. The description uses proper third-person voice and maintains a clear, distinct niche.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'dockerização', 'criar Dockerfile', 'docker-compose', 'configurar pipeline CI/CD', 'deploy em cloud', 'configurar nginx', 'SSL', and 'operação de infraestrutura'. These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both WHAT (dockerização, CI/CD, deploy, nginx, SSL, infrastructure operations) AND WHEN with explicit 'Use quando precisar...' clause and a dedicated 'Trigger em:' section listing specific trigger terms. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say, explicitly listing: 'deploy', 'Docker', 'Dockerfile', 'docker-compose', 'CI/CD', 'pipeline', 'GitHub Actions', 'nginx', 'SSL', 'produção', 'staging', 'Kubernetes', 'AWS', 'infraestrutura', 'ambiente', 'build', 'release'. These are terms users naturally use when needing DevOps help. | 3 / 3 |
Distinctiveness Conflict Risk | Clear DevOps/infrastructure niche with highly specific triggers like 'Dockerfile', 'docker-compose', 'GitHub Actions', 'Kubernetes', 'nginx', 'SSL'. These are distinct from general coding or document skills and unlikely to conflict with other skill types. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a highly actionable deployment skill with production-ready, executable configurations for Docker, nginx, CI/CD, and rollback strategies. The workflow clarity is strong with explicit validation checkpoints and health checks. However, the document is lengthy and could benefit from moving some complete configurations to referenced files, and trimming governance/philosophy sections that don't add operational value.
Suggestions
Move complete configuration examples (full docker-compose.yml, nginx.conf, GitHub Actions workflow) to referenced files like 'examples/docker-compose.yml' and keep only essential snippets inline
Remove or condense the 'Codigo Limpo' section - this is general advice Claude already knows and doesn't add deployment-specific value
Consolidate 'Quando Usar/Nao Usar' and 'Entradas/Saidas Esperadas' sections into a brief trigger summary to reduce overhead
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some unnecessary sections like 'Codigo Limpo' philosophy and verbose explanations of when to use/not use. The governance references at the top add overhead, though the core examples are efficient. | 2 / 3 |
Actionability | Excellent executable examples throughout - complete Dockerfile, docker-compose.yml, nginx config, GitHub Actions workflow, and rollback script are all copy-paste ready with real-world configurations including health checks and security hardening. | 3 / 3 |
Workflow Clarity | Clear multi-step workflows with explicit validation: CI/CD pipeline shows quality→test→security→build→deploy sequence, production deploy includes backup before deploy and health check after, rollback script has verification step. Pre-deploy checklist provides comprehensive validation. | 3 / 3 |
Progressive Disclosure | References external docs appropriately (docs/skill-guides/deploy-docker.md, policies/*) but the main file is quite long (~400 lines) with full configurations inline. Some content like the complete nginx config or GitHub Actions workflow could be split into referenced files. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (599 lines); consider splitting into references/ and linking | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
Total | 9 / 11 Passed | |
524725e
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.