CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

dockerfile-generator

Skill para gerar Dockerfiles, entrypoints, Makefiles e .dockerignore automaticamente seguindo melhores práticas.

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/infrastructure/dockerfile-generator/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

56%Weight 40%Scale 1-5

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

The skill is well-structured and rule-oriented with a useful validation checklist, but its actionability is undermined by relying on template files that aren't shipped in the bundle, and its efficiency is hurt by duplicated examples and speculative roadmap content. Fixing the dangling references would be the highest-impact improvement.

Suggestions

Ship the actual templates in a references/ (or templates/) directory inside the bundle and reference them with real relative paths, or inline minimal executable versions — the currently referenced 'core/templates/...' paths don't exist in the skill bundle.

Remove the duplicated curl API example (keep it in one place only) and cut or compress the 'Roadmap (Futuro)' and 'Integração com Claude Code / Cursor' sections to reclaim tokens.

Add a runtime verification step to the checklist (e.g., 'make build' succeeds and container responds to healthcheck) with a fix-and-retry loop when a checklist item fails.

DimensionReasoningScore

Conciseness

The rules and parameter sections are dense and useful, but there is clear tightening to do: the identical curl POST example appears twice (Opções de Geração and Exemplos de Uso), the 'Roadmap (Futuro)' section speculatively describes an unimplemented micro-service, the 'Integração com Claude Code / Cursor' prompt examples largely repeat earlier usage sections, and a trailing 'Última Atualização' date adds noise. This fits 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than the padded anchor at 2.

3 / 5

Actionability

There are concrete cp/curl commands, parameter tables, and a checklist, but the primary recommended path (Option 1: copy from 'core/templates/django/Dockerfile' etc.) references files that are not present in this skill bundle — no references/, scripts/ or assets/ directories exist — and the 'FastAPI entrypoint' example references 'core/templates/entrypoint/fastapi-entrypoint.sh' which is not in the earlier template listing. The Dockerfile structure example is comment-only pseudocode ('# Instala dependências, roda testes, coleta static files'). This matches 'some concrete guidance but incomplete; pseudocode instead of executable code'.

3 / 5

Workflow Clarity

The flow is clear and sequenced: Quando Usar → Opções de Geração (templates vs. future API) → adjust parameters → Regras Obrigatórias → Checklist de Validação as an explicit validation gate. It fits 'clear sequence with most checkpoints present; minor validation gaps': the checklist verifies static file properties but never verifies the result builds or runs (e.g., no 'make build && docker run' step), and there is no instruction on what to do when a checklist item fails.

4 / 5

Progressive Disclosure

The body is one ~310-line file with no bundle files at all, yet it points to paths like 'core/templates/django/', 'skills/infrastructure/docker-entrypoint/SKILL.md' and 'core/templates/django/DOCKERFILE_GUIDE.md' that do not exist in the bundle and cannot be resolved from it, and inline content (roadmap, API examples, integration prompts) that would belong in separate files. Sections are well-headed so it's above the anchor-2 'minimal structure' case, matching 'some structure but could be better organized; references present but not clearly signaled'.

3 / 5

Total

13

/

20

Passed

Description

66%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description clearly states what the skill generates and covers a good range of natural trigger terms, but it lacks any 'when to use' guidance, which caps completeness and overall quality. The trailing 'seguindo melhores práticas' is mild fluff that adds no concrete information.

Suggestions

Append an explicit trigger clause, e.g. 'Use quando iniciar ou migrar um projeto para Docker, ou quando o usuário pedir Dockerfile, containerizar, entrypoint ou Makefile' — this raises completeness from 3 to 5.

Add natural synonyms such as 'containerizar'/'container image'/'Docker setup' to broaden trigger-term coverage.

Drop the vague 'seguindo melhores práticas' in favor of a concrete distinguishing detail like 'multi-stage builds com usuário não-root' to sharpen distinctiveness.

DimensionReasoningScore

Specificity

The description names the domain and enumerates concrete artifacts: 'gerar Dockerfiles, entrypoints, Makefiles e .dockerignore automaticamente'. This lists several specific actions with only minor gaps (e.g., it doesn't hint at multi-stage builds or framework coverage), matching the 'lists several specific actions' anchor rather than the comprehensive 5 anchor.

4 / 5

Completeness

The 'what' is clear ('gerar Dockerfiles, entrypoints, Makefiles e .dockerignore') but there is no 'when' — no 'Use when...' clause or equivalent trigger guidance inside the description, which caps completeness at 3 per the judging guidelines. The separate frontmatter `triggers` field is not part of the description field being evaluated.

3 / 5

Trigger Term Quality

Natural terms users would say are present: 'Dockerfiles', 'entrypoints', 'Makefiles', '.dockerignore'. Coverage is good but misses common variations like 'containerize', 'Docker setup', or 'docker image', so it fits the 'good keyword coverage; a few natural terms missing' anchor rather than the comprehensive synonym/file-extension anchor at 5.

4 / 5

Distinctiveness Conflict Risk

Generating Dockerfiles, entrypoints, Makefiles and .dockerignore is a mostly distinct niche with minor overlap risk against closely related skills (generic Docker or docker-compose skills; the body even references sibling Docker skills). It is more distinct than the anchor-3 'somewhat specific but could still overlap' case, but doesn't reach the minimal-conflict clarity of anchor 5.

4 / 5

Total

15

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

fernandezbaptiste/cursor-multiagent-system

Path

skills/infrastructure/dockerfile-generator/SKILL.md

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.