CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

docker-execution

Agentes DEVEM executar containers e scripts, não apenas mostrar comandos

Quality

60%

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-execution/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 body delivers concrete, executable docker guidance with clear sequences and verification checkpoints, and it wisely avoids concept explanations. Its weaknesses are repetition of the same rule across multiple contrast blocks, a missing error-recovery loop (what to do when the container fails), and a Makefile section that mandates creating targets without ever showing one.

Suggestions

Add a feedback loop after log verification: e.g. 'Se logs mostram erro: identificar causa, corrigir (Dockerfile/compose/config), re-executar docker compose up -d --build, verificar novamente' — this would raise workflow_clarity.

Consolidate the repeated PROIBIDO/CORRETO contrast blocks into one golden-rule section; each section (scripts, containers, Makefile) currently re-states the same execute-don't-show rule, which could be trimmed.

Make the Makefile section concrete: show an example target (e.g. 'up: docker compose up -d --build') or reference a standard Makefile layout instead of only instructing 'criar no Makefile, depois executar'.

DimensionReasoningScore

Conciseness

The body uses concrete commands and explains no basic concepts, but the repeated '❌ PROIBIDO / ✅ CORRETO' contrast blocks and the recurring 'SEMPRE'/'OBRIGATÓRIO' restatements of the same execute-don't-show rule pad the document — 'mostly efficient but includes some unnecessary explanation or could be tightened'. It is not 2 because there is no concept-level over-explanation, and not 4 because the golden rule is restated in at least four sections and the checklist repeats earlier requirements.

3 / 5

Actionability

Concrete executable commands are provided throughout: 'docker compose up -d --build', 'docker compose ps', 'docker compose logs --tail=50', and a jq-based health check — 'mostly executable guidance with concrete commands and minor gaps'. It is not 5 because the Makefile section instructs 'Se não tem → criar no Makefile, depois executar' without any example target or command, and 'Reportar o resultado' is direction rather than instruction.

4 / 5

Workflow Clarity

The container workflow is a clear numbered sequence with verification checkpoints (execute → 'docker compose ps' → 'docker compose logs --tail=50' → report), plus a final checklist — anchor 4. It is not 5 because there is no error-recovery feedback loop: the content says to 'Reportar se está funcionando ou se há erros' but never what to do when logs show errors (fix, restart, re-check). Container execution is not a destructive/batch operation, so the workflow-clarity cap of 3 does not apply.

4 / 5

Progressive Disclosure

The body has clear section headers (golden rule, when to execute, Makefile priority, scripts, log analysis, checklist) with no nested or broken references — anchor 4 'good structure, most content appropriately placed'. It is not 5 because at ~135 lines it exceeds the lean-SKILL.md scope the simple-skill exception covers (under 50 lines), and the log-analysis command catalog is inline content that could live in a reference file.

4 / 5

Total

15

/

20

Passed

Description

37%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 single clear behavioral rule but fails as a trigger description: it lacks any 'when to use' guidance, omits the domain's core vocabulary (docker, compose, build, logs, Makefile), and names no concrete capabilities beyond a generic 'execute'. It reads as a policy statement rather than a capability description.

Suggestions

Add an explicit trigger clause, e.g. 'Use quando o usuário pedir para subir/build containers, ver logs, executar scripts ou testar docker-compose' — this lifts completeness above the 3 cap.

Include the domain's natural keywords in the description itself: docker, docker compose, build, logs, Makefile, script execution (the frontmatter `triggers` list is not part of the description field the model matches on).

Name concrete capabilities instead of one generic verb, e.g. 'Executa containers com docker compose (up, build, logs, health check) e scripts, verificando status e reportando erros' instead of just 'executar containers e scripts'.

DimensionReasoningScore

Specificity

The description 'Agentes DEVEM executar containers e scripts, não apenas mostrar comandos' names the domain (containers/scripts) with one generic action ('executar'), matching anchor 2 ('Names the domain but actions are minimal or generic'). It does not reach 3 because it enumerates no concrete capabilities such as building images, checking logs, or verifying health.

2 / 5

Completeness

A clear 'what' is present ('executar containers e scripts, não apenas mostrar comandos') but the 'when' is entirely absent — no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. It is not 2 because the 'what' is a concrete behavioral statement rather than a vague one.

3 / 5

Trigger Term Quality

Only two generic keywords ('containers', 'scripts') appear; the natural phrases users would actually say — docker, compose, 'subir container', build, logs, Makefile — are all absent, matching anchor 2 ('One or two generic keywords; missing the natural phrases users say'). It is not 3 because the core vocabulary of the domain (docker/compose) is entirely missing.

2 / 5

Distinctiveness Conflict Risk

'Executar containers e scripts' is somewhat specific as a behavioral directive but could still overlap with generic docker, scripting, or dev-workflow skills — anchor 3. It is not 4 because the description lacks distinctive trigger phrases (docker, compose, Makefile) that would separate it from neighboring skills.

3 / 5

Total

10

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

14

/

16

Passed

Repository

fernandezbaptiste/cursor-multiagent-system

Path

skills/infrastructure/docker-execution/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.