CtrlK
BlogDocsLog inGet started
Tessl Logo

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 CI/CD", "GitHub Actions", "nginx", "SSL", "produção", "staging", "Kubernetes", "AWS", "infraestrutura", "ambiente", "build", "release".

62

Quality

75%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/07-deploy-docker/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill excels at actionability with production-ready, executable code examples covering the full deployment stack (Docker, compose, nginx, CI/CD, SSL, rollback). However, it is severely bloated — the IaC principles section explains concepts Claude already knows, and multiple rollback pattern variations inflate the document unnecessarily. The content would benefit greatly from moving detailed implementations to referenced files and keeping SKILL.md as a lean overview with quick-reference examples.

Suggestions

Remove or drastically reduce the IaC principles section — Claude already understands idempotency, declarative infrastructure, and drift. Keep only the tooling mapping table and the 'when to apply' guidance.

Move the detailed rollback variations (.last-tag pattern, GitHub Actions integration, docker-compose pattern) to a referenced file like `docs/skill-guides/rollback-strategies.md` and keep only the basic rollback script inline.

Move the full nginx config, SSL init script, and docker-compose to referenced files, keeping only a minimal example or summary inline with links to the complete versions.

Add a clear numbered top-level workflow sequence (e.g., '1. Build images → 2. Deploy to staging → 3. Validate → 4. Promote to prod') at the top of the skill to tie all the individual components together.

DimensionReasoningScore

Conciseness

The skill is extremely verbose at ~500+ lines. It includes lengthy explanations of IaC principles Claude already knows (idempotency, declarative vs imperative, drift), a full mapping table from a book, extensive philosophical framing ('gado, não bicho de estimação'), and multiple variations of the same rollback pattern. The IaC section alone could be reduced by 80% without losing actionable value.

1 / 3

Actionability

The skill provides fully executable, copy-paste-ready code throughout: complete multi-stage Dockerfile, full docker-compose.yml with healthchecks, complete nginx config with SSL and rate limiting, full GitHub Actions CI/CD pipeline, executable rollback scripts, and SSL init script. All examples are concrete and production-ready.

3 / 3

Workflow Clarity

While individual components are well-defined with health checks and rollback steps, the overall deployment workflow lacks a clear sequenced process tying everything together. The pre-deploy checklist is good but appears at the end rather than framing the workflow. The SSL init section has good validation (certificate expiry check), but the relationship between first deploy, SSL setup, and nginx startup could be clearer as a unified sequence. Blue-green and canary sections are bullet-point descriptions without concrete implementation steps.

2 / 3

Progressive Disclosure

The skill references external files (GLOBAL.md, policies/*, docs/skill-guides/deploy-docker.md) which is good, but then proceeds to inline massive amounts of content that could live in those referenced guides. The IaC section, SSL init details, and rollback variations would be better as separate referenced documents. The skill tries to be both an overview and a complete reference, defeating progressive disclosure.

2 / 3

Total

8

/

12

Passed

Description

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 capabilities, explicit trigger guidance, and comprehensive natural keywords. The explicit 'Use quando' clause and 'Trigger em' list make it highly effective for skill selection. The only minor note is that it's written in Portuguese, which is appropriate if the skill ecosystem is Portuguese-language, and it uses third-person voice correctly.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: creating Dockerfile, docker-compose, configuring CI/CD pipelines, cloud deployment, nginx configuration, and SSL setup. These are clearly defined, actionable capabilities.

3 / 3

Completeness

Clearly answers both 'what' (dockerization, CI/CD, deployment, nginx/SSL configuration, infrastructure operations) 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, explicitly listing 'deploy', 'Docker', 'Dockerfile', 'docker-compose', 'CI/CD', 'GitHub Actions', 'nginx', 'SSL', 'Kubernetes', 'AWS', 'infraestrutura', 'build', 'release', and environment terms like 'produção' and 'staging'.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear DevOps/infrastructure niche with highly specific trigger terms like 'Dockerfile', 'docker-compose', 'Kubernetes', 'nginx', 'SSL', and 'GitHub Actions' that are unlikely to conflict with non-DevOps skills.

3 / 3

Total

12

/

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.

Validation9 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (838 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
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.