deploy-docker
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".
60
71%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/07-deploy-docker/SKILL.mdQuality
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 strong skill description that clearly defines its DevOps/deployment domain with specific concrete actions, explicit 'Use when' guidance, and an extensive list of natural trigger terms. The description is well-structured, covering what the skill does, when to use it, and providing a comprehensive keyword list for disambiguation. The only minor note is that it's written in Portuguese, but the trigger terms include many universal technical terms that would match regardless of language.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: dockerização, CI/CD, criar Dockerfile, docker-compose, configurar pipeline CI/CD, deploy em cloud, configurar nginx, SSL, operações de infraestrutura. | 3 / 3 |
Completeness | Clearly answers both 'what' (dockerização, CI/CD, deploy de aplicações, criar Dockerfile, configurar pipeline, etc.) and 'when' with an explicit 'Use quando precisar...' clause and a dedicated 'Trigger em:' list of keywords. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'deploy', 'Docker', 'Dockerfile', 'docker-compose', 'CI/CD', 'pipeline', 'GitHub Actions', 'nginx', 'SSL', 'produção', 'staging', 'Kubernetes', 'AWS', 'infraestrutura', 'ambiente', 'build', 'release'. These are all terms users would naturally use when requesting DevOps tasks. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly occupies a distinct DevOps/infrastructure niche with highly specific trigger terms like 'Dockerfile', 'docker-compose', 'CI/CD', 'GitHub Actions', 'nginx', 'SSL', 'Kubernetes' that are unlikely to conflict with non-DevOps skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides highly actionable, executable infrastructure code covering Docker, nginx, CI/CD, SSL, and rollback strategies. However, it is severely over-inlined — nearly every configuration is dumped directly into the SKILL.md despite referencing an external guide file. The result is a ~400+ line monolith that wastes token budget on boilerplate Claude can generate, with poor progressive disclosure and a workflow that reads as disconnected reference sections rather than a coherent deployment process.
Suggestions
Move the complete Dockerfile, docker-compose.yml, nginx config, and CI/CD pipeline into the referenced `docs/skill-guides/deploy-docker.md` and keep only the strategy principles, key patterns (e.g., multi-stage builds, health checks), and the pre-deploy checklist in SKILL.md.
Replace inlined boilerplate with concise decision rules — e.g., 'Use multi-stage builds; final image should be alpine-based with non-root user and HEALTHCHECK' rather than a full Dockerfile that Claude can generate from such instructions.
Add a unified deployment workflow sequence at the top (e.g., '1. Build images → 2. Push to registry → 3. Deploy to staging → 4. Validate health → 5. Promote to prod with approval → 6. Monitor') that ties all the scattered sections together.
Remove explanatory sections like 'Problema/Solução' narratives for the .last-tag pattern and ssl-init — these explain reasoning Claude doesn't need. Reduce to the pattern itself with a one-line comment on when to use it.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~400+ lines, inlining complete Dockerfile, docker-compose, nginx config, CI/CD pipeline, SSL scripts, rollback scripts, and multiple deployment patterns. Much of this is boilerplate that Claude already knows how to generate. The content mentions a `docs/skill-guides/deploy-docker.md` reference but then proceeds to inline everything anyway, defeating the purpose of progressive disclosure. | 1 / 3 |
Actionability | The skill provides fully executable, copy-paste-ready code examples: complete Dockerfile with multi-stage builds, full docker-compose.yml, nginx config with SSL, GitHub Actions pipeline, rollback scripts, and SSL init scripts. All examples are concrete and runnable. | 3 / 3 |
Workflow Clarity | There is a pre-deploy checklist and the CI/CD pipeline has a clear sequence (quality → test → security → build → deploy), and the rollback scripts include health checks. However, the overall deploy workflow across all the sections is not clearly sequenced as a unified process — it reads more like a reference dump of individual components. The relationship between ssl-init, first deploy, and subsequent deploys is scattered across multiple sections without a clear master sequence. | 2 / 3 |
Progressive Disclosure | Despite referencing `docs/skill-guides/deploy-docker.md` for 'complete examples,' the skill inlines everything anyway — complete Dockerfile, compose, nginx, CI/CD, rollback, SSL scripts, blue-green patterns, and feature flags. Multiple policy files are referenced but no bundle files are provided to verify they exist. The content is a monolithic wall of configuration that should be split across referenced files. | 1 / 3 |
Total | 7 / 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 (796 lines); consider splitting into references/ and linking | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
Total | 9 / 11 Passed | |
- Repository
- felvieira/claude-skills-fv
- Commit
7577622
- Reviewed
Table of Contents
Is this your skill?
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.