CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/docker-compose-tests

Authors a `compose.test.yaml` for tests - declares the SUT plus its real backing services as one declarative topology, wires healthcheck-driven `depends_on: condition: service_healthy` start ordering, isolates parallel CI jobs via per-job `--project-name`, gates the test step on `--wait` / `--wait-timeout` / `--exit-code-from`, and tears the stack down deterministically with `down --volumes --remove-orphans`. Use when the test environment is multi-service (app + db + cache + queue) and the topology is best expressed in YAML rather than imperative test code.

80

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Overview
Quality
Evals
Security
Files

Quality

Content

100%

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

A dense, well-structured skill that pairs complete executable examples with clearly sequenced steps, readiness validation, and one-level-deep reference files. It assumes Claude's competence and earns its length through concrete code rather than explanation of basics.

DimensionReasoningScore

Conciseness

Assumes Compose competence (no 'what is Docker/Compose' padding) and keeps prose load-bearing — e.g. 'service_started ... is almost never what a test wants' and the --volumes stale-data rationale — while length comes from complete, copy-paste code blocks rather than filler.

3 / 3

Actionability

Fully executable, copy-paste-ready material throughout: complete compose.test.yaml, migration-service YAML, a GitHub Actions matrix workflow, and concrete bash invocations for both CI shapes.

3 / 3

Workflow Clarity

A clearly sequenced 7-step process with explicit validation checkpoints — healthcheck service_healthy gates, --wait/--wait-timeout readiness gating before tests, and deterministic 'if: always()' teardown of a destructive 'down --volumes' step.

3 / 3

Progressive Disclosure

Overview lives in SKILL.md while detailed flag tables and the anti-pattern catalog are split one level deep into references/compose-flags.md and references/anti-patterns.md, both clearly signaled and verified to exist in the bundle.

3 / 3

Total

12

/

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.

A highly specific, third-person description that pairs concrete authoring actions with an explicit 'Use when' trigger clause and a distinctive multi-service test-infra niche. Voice is correctly third person and there is no vague fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Authors a compose.test.yaml', 'wires healthcheck-driven depends_on: condition: service_healthy', 'isolates parallel CI jobs via per-job --project-name', 'gates the test step on --wait / --wait-timeout / --exit-code-from', 'tears the stack down ... with down --volumes --remove-orphans'.

3 / 3

Completeness

Explicitly answers both what (authors/declares/wires/isolates/gates/tears down) and when via an explicit 'Use when the test environment is multi-service ...' clause.

3 / 3

Trigger Term Quality

The 'Use when' clause surfaces natural developer phrasing — 'multi-service (app + db + cache + queue)', 'topology is best expressed in YAML rather than imperative test code', 'parallel CI jobs' — terms a user would actually say when needing this skill.

3 / 3

Distinctiveness Conflict Risk

Niche is sharply defined — Compose-authored multi-service test topology with healthcheck ordering and per-job CI isolation — making it unlikely to trigger for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents