CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

testcontainers-go

Use this skill when writing Go integration tests with Docker containers, using testcontainers-go modules (postgres, redis, kafka, etc.), setting up container-based test infrastructure, or configuring container networking and wait strategies. Covers 62+ pre-configured modules, cleanup patterns, and multi-container setups.

Quality

79%

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 ./plugins/testcontainers-go/skills/testcontainers-go/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 highly actionable, accurate testcontainers-go guidance with strong cleanup and wait-strategy patterns, but it is a monolithic 1255-line document that inlines reference material (module catalog, five full examples) instead of splitting it into bundled files. Tightening the padding and moving bulk content to references would improve both conciseness and progressive disclosure.

Suggestions

Move the 62+ module catalog and the five full worked examples into references/ files (e.g., references/modules.md, references/examples.md), keeping SKILL.md a concise overview with one-level-deep pointers to them.

Delete the redundant 'Description' section (it duplicates the frontmatter) and trim marketing copy such as 'Battle-tested: Used in production by thousands of projects'.

Make code snippets self-contained by including imports (wait, container, mount, nat, database/sql) so examples are fully copy-paste executable.

DimensionReasoningScore

Conciseness

The instruction sections (setup, cleanup-before-error-check, wait strategies, networking) are efficient and code-centric, but there is real padding: a "Description" section duplicating the frontmatter, marketing bullets like "Battle-tested: Used in production by thousands of projects", a full inline catalog of 62+ modules, and five complete worked examples. Not 4: the unnecessary explanation and inlined bulk goes beyond 'minor instances of over-explanation'; not 2: the core guidance itself is concrete rather than extensively explaining concepts Claude already knows.

3 / 5

Actionability

Concrete, mostly executable Go code throughout (postgres.Run with options, CleanupContainer, network.New, wait strategies, exec.Multiplexed) with exact commands and image tags. Not 5: many fragments omit imports (wait., container.HostConfig, nat.Port, mount.Mount, sql.Open in section 2), so they are not fully copy-paste ready; not 3: the code is real and executable, not pseudocode.

4 / 5

Workflow Clarity

Clear sequence (install → pick module → run with cleanup-before-error-check → connect → test), a numbered test-structure template, an explicit correct/wrong contrast for the cleanup ordering, and a troubleshooting section covering timeout, port-conflict, pull-failure, and cleanup-verification recovery. Not 5: there is no explicit validate → fix → retry feedback loop, though the troubleshooting section approximates one; not 3: checkpoints like SkipIfProviderIsNotHealthy and require.NoError after every step are consistently present.

4 / 5

Progressive Disclosure

Good internal section structure with numbered, headed parts, but the entire 1255-line skill is inlined in SKILL.md with no references/, scripts/, or assets/ files at all — the 62+ module catalog and five full worked examples are bulk content that clearly belongs in separate reference files loaded on demand. Not 4: nothing is split out and there are no in-skill reference pointers to offload content; not 2: the structure is well-organized, not 'minimal'.

3 / 5

Total

14

/

20

Passed

Description

88%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.

A strong description that clearly states both what the skill covers and when to use it, with concrete named triggers (testcontainers-go, postgres, redis, kafka, wait strategies). Minor room to tighten distinctiveness against generic Docker/Go-testing skills.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions — "writing Go integration tests with Docker containers", "setting up container-based test infrastructure", "configuring container networking and wait strategies", "cleanup patterns, and multi-container setups" — giving comprehensive coverage of the skill's capability surface. Not 4: coverage spans setup, modules (with named examples postgres/redis/kafka), networking, wait strategies, cleanup, and multi-container patterns with no significant gaps.

5 / 5

Completeness

Explicitly answers both: "what" via "Covers 62+ pre-configured modules, cleanup patterns, and multi-container setups" plus the enumerated capabilities, and "when" via the concrete trigger clause "Use this skill when writing Go integration tests with Docker containers, using testcontainers-go modules... setting up... or configuring...". Matches the anchor-5 pattern of both what AND when with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural-term coverage: "Go integration tests", "Docker containers", "testcontainers-go", "postgres, redis, kafka", "container networking", "wait strategies" — phrases users would naturally say. Not 5: a few common variations are absent (bare "testcontainers", "docker-compose", "ephemeral database in tests"); not 3: the module names and tool name give far more than 'some relevant keywords'.

4 / 5

Distinctiveness Conflict Risk

Clear niche (testcontainers-go for Go integration testing) with distinctive triggers like "testcontainers-go modules". Not 5: the generic phrases "Docker containers" and "integration tests" create minor overlap risk with broader Docker or Go-testing skills; not 3: the tool-specific framing keeps it mostly distinct.

4 / 5

Total

18

/

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

skill_md_line_count

SKILL.md is long (1255 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository

freightCognition/linehaulai-claude-marketplace

Path

plugins/testcontainers-go/skills/testcontainers-go/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.