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 with specific actions, explicit 'Use when' guidance, and an extensive list of natural trigger terms. The description is well-structured, covering both capabilities and activation conditions comprehensively. The only minor note is that it's written in Portuguese, which is fine if the target audience uses Portuguese, and it uses appropriate third-person voice.
| 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' (explicit 'Use quando precisar...' clause plus a dedicated 'Trigger em:' list with specific 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. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly carved out niche around DevOps/infrastructure/deployment with highly specific trigger terms like 'Dockerfile', 'docker-compose', 'GitHub Actions', 'Kubernetes', 'nginx', 'SSL' 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 code examples covering the full deployment stack, which is its main strength. However, it is severely bloated—inlining hundreds of lines of configuration that Claude can generate from brief instructions, and duplicating content that it explicitly references in a separate guide file. The organization would benefit greatly from keeping only the strategy, constraints, and key patterns in SKILL.md while moving the full examples to the referenced guide.
Suggestions
Move the complete Dockerfile, docker-compose, nginx, and CI/CD examples to docs/skill-guides/deploy-docker.md (which is already referenced) and keep only brief patterns or key constraints in SKILL.md
Add a unified workflow sequence (numbered steps) showing the end-to-end deploy process from receiving approved code to production verification, with explicit validation checkpoints between stages
Remove explanations Claude already knows (e.g., 'Codigo deve priorizar clareza' section, basic feature flag patterns) and focus on project-specific constraints and non-obvious decisions
Consolidate the governance references into a single line or section header rather than listing 7+ policy files at the top
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~350+ lines, inlining complete Dockerfile, docker-compose, nginx config, CI/CD pipeline, env examples, and rollback scripts. Much of this is boilerplate that Claude already knows how to generate. The skill even references a separate guide file (docs/skill-guides/deploy-docker.md) but then includes all the examples inline anyway, defeating the purpose. | 1 / 3 |
Actionability | The content provides fully executable, copy-paste ready code examples: complete Dockerfile with multi-stage builds, full docker-compose.yml, nginx configuration, GitHub Actions workflow, rollback script, and environment variable templates. All examples are concrete and specific. | 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 and health check steps. However, the overall deploy workflow across sections is not clearly sequenced as a unified process, and validation/feedback loops between the various components (Dockerfile build, compose up, nginx config validation) are not explicit. | 2 / 3 |
Progressive Disclosure | Despite referencing docs/skill-guides/deploy-docker.md for 'complete examples,' the skill inlines all the detailed examples anyway, creating a monolithic wall of configuration files. The content that should be in the referenced guide file is duplicated here, and the references to multiple policy files (7+ governance docs) add noise without clear navigation structure. | 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
e9f6648
- 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.