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".
75
71%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
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, lists concrete actions, provides explicit 'Use when' guidance, and includes an extensive list of natural trigger terms. The description is well-structured and would allow Claude to confidently select this skill when users mention infrastructure or deployment topics. The only minor note is that it's in Portuguese, but the trigger terms themselves are largely universal technical terms.
| 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. | 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. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly occupies a distinct DevOps/infrastructure niche with highly specific trigger terms like 'Dockerfile', 'docker-compose', 'Kubernetes', 'nginx', 'SSL', 'GitHub Actions' 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, production-ready configurations for Docker, nginx, CI/CD, and rollback, which is its main strength. However, it severely violates conciseness and progressive disclosure principles by inlining hundreds of lines of configuration that should be in referenced files, especially since it already references a guide document. The workflow could be clearer with an explicit step-by-step deploy process tying all the pieces together.
Suggestions
Move the complete Dockerfile, docker-compose.yml, nginx config, and CI/CD pipeline into `docs/skill-guides/deploy-docker.md` or separate files, keeping only a brief summary and key patterns in SKILL.md with clear references.
Add a concise, numbered end-to-end deploy workflow at the top that sequences all steps (build → validate → stage → verify → promote to prod) with explicit validation checkpoints and error recovery actions.
Remove the 'Codigo Limpo' section and 'Integração com Pipeline' section — these are meta-information that don't provide actionable deploy guidance and waste tokens.
Consolidate the 'Quando Usar/Nao Usar', 'Entradas/Saidas Esperadas', and 'Responsabilidades' sections into a brief 3-4 line scope statement to reduce overhead.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~350+ lines, inlining complete Dockerfile, docker-compose, nginx config, CI/CD pipeline, env vars, and rollback scripts that could easily live in referenced files. It also includes sections explaining obvious concepts ('Codigo Limpo' paragraph) and meta-information about pipeline integration that adds little actionable value. The skill itself references `docs/skill-guides/deploy-docker.md` for examples but then includes all the examples inline anyway. | 1 / 3 |
Actionability | The content provides fully executable, copy-paste ready configurations: a complete multi-stage Dockerfile, docker-compose.yml, nginx config with SSL, GitHub Actions pipeline, rollback script, and environment variable template. These are concrete and specific, not pseudocode. | 3 / 3 |
Workflow Clarity | There is a pre-deploy checklist and the CI/CD pipeline shows a clear sequence (quality → test → security → build → deploy), and the production deploy includes backup + health check. However, the overall deploy workflow across sections is not presented as a cohesive sequence with explicit validation checkpoints and error recovery loops. The relationship between the checklist, the CI/CD pipeline, and manual steps is implicit rather than explicitly sequenced. | 2 / 3 |
Progressive Disclosure | Despite referencing `docs/skill-guides/deploy-docker.md` for 'complete examples,' the skill inlines all the examples anyway, creating a monolithic wall of configuration. The SKILL.md should be an overview with pointers to detailed configs, but instead it contains ~300 lines of raw configuration files that should be in separate referenced documents. | 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 (599 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
d87ad31
- 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.