CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

docker-entrypoint-pattern

Padrão para criar entrypoint.sh com múltiplos comandos para containers Docker, permitindo execução flexível de diferentes operações.

Quality

63%

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/docker-entrypoint/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 content is a well-organized, mostly executable reference with clear rules, a checklist, and validation guidance, but its core entrypoint template is an empty skeleton, stack sections lack actual implementations, and it carries redundant/dated material in a single monolithic file with dangling external references. Filling in one complete worked example per stack and pruning the conceptual and duplicated sections would lift actionability and conciseness.

Suggestions

Replace the empty case branches in the base template with at least one fully worked, copy-paste-ready entrypoint.sh (e.g., a complete Django or FastAPI implementation) so the core artifact is executable rather than pseudocode (actionability)

Remove the duplicated variable-validation block (rule 5 vs. best practice 2), trim the 'Vantagens' rationale Claude already knows, drop the 'Última Atualização' date, and consolidate the inconsistent 'Referências' paths (conciseness)

Either move the per-stack templates into actual bundle files under references/ (or drop the dangling core/templates/... pointers), keeping SKILL.md as a concise overview with one-level-deep, clearly signaled links (progressive_disclosure)

DimensionReasoningScore

Conciseness

The body is mostly efficient, code-heavy template content, but it pads with conceptual benefit explanations in 'Por Que Usar Entrypoint.sh?/Vantagens' that Claude already knows, duplicates variable validation (rule 5 and best practice 2), repeats the template references in a 'Referências' section with inconsistent paths, and carries a time-sensitive 'Última Atualização: 2026-01-21' date outside any old-patterns section. This fits 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than the lean anchor 5.

3 / 5

Actionability

The Dockerfile, docker-compose, wait_for_service, and validation snippets are concrete and executable, but the central base entrypoint template is a skeleton with empty case branches ('dev) # Development server ;;') and the per-stack sections only list typical command names without implementations. This matches 'some concrete guidance but incomplete' rather than anchor 4's 'concrete code or commands with minor gaps', because the gaps sit in the skill's core artifact.

3 / 5

Workflow Clarity

The sequence is clear and well-ordered (base template → mandatory rules → stack templates → best practices → Dockerfile/compose integration → checklist), and validation checkpoints are present (critical-variable validation, health check, dependency waiting). It falls short of anchor 5 because there are no explicit error-recovery feedback loops and the checklist items are not wired into an ordered procedure for creating a new entrypoint.

4 / 5

Progressive Disclosure

Section structure is good, but the skill is a monolithic ~345-line file with no bundle files, while its references point to repo paths (core/templates/entrypoint/*.sh) that are not part of the skill bundle and are inconsistent (core/templates/django/entrypoint.sh vs core/templates/entrypoint/django-entrypoint.sh). Per-stack template content is inlined rather than split into reference files, matching 'some structure but could be better organized' rather than anchor 4.

3 / 5

Total

13

/

20

Passed

Description

53%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 states a clear, specific purpose (multi-command entrypoint.sh for Docker containers) in third person, but it lacks any explicit 'when to use' trigger guidance and only gestures vaguely at flexibility rather than enumerating concrete operations. Adding a 'Use when...' clause with natural trigger phrases (Dockerfile, docker run, entrypoint, init script) would raise both completeness and trigger quality.

Suggestions

Add an explicit 'Use when...' clause in the description, e.g., 'Use when creating or modifying Dockerfiles, configuring container entrypoints, or running multiple container commands (dev, test, migrate, prod).' (completeness)

Enumerate the concrete operations the pattern supports (migrations, health checks, dev/test/prod commands) instead of the generic 'execução flexível de diferentes operações' (specificity)

Include natural trigger variations users would say — 'Dockerfile', 'docker run', 'docker exec', 'startup/init script' — to broaden keyword coverage (trigger_term_quality)

DimensionReasoningScore

Specificity

"Padrão para criar entrypoint.sh com múltiplos comandos para containers Docker" names the domain and one concrete action (creating entrypoint.sh with multiple commands), but "permitindo execução flexível de diferentes operações" is generic. It does not list several specific actions (e.g., migrations, health checks, dev/test/prod commands), so it matches anchor 3 rather than 4.

3 / 5

Completeness

The 'what' is clear (pattern for creating an entrypoint.sh with multiple commands), but there is no 'Use when...' clause or equivalent explicit trigger guidance — the 'when' is only weakly implied by 'permitindo execução flexível'. Per the judging guideline, a missing 'Use when...' clause caps completeness at 3.

3 / 5

Trigger Term Quality

Relevant keywords are present ("entrypoint.sh", "containers Docker", "múltiplos comandos") but common natural variations users would say are missing ("Dockerfile", "docker run", "docker exec", "init/startup script"), matching the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The Docker entrypoint-script niche is fairly distinct, but the description overlaps with general Dockerfile/container-configuration skills, matching the 'mostly distinct; minor overlap risk with closely related skills' anchor rather than the clear-niche anchor 5.

4 / 5

Total

13

/

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/docker-entrypoint/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.