Name: testcontainers-guide-migrator
Rating: 74.4 (1 reviews)
Author: docker

testcontainers-guide-migrator

Migrate a Testcontainers guide from testcontainers.com into the Docker docs site (docs.docker.com). Converts AsciiDoc to Hugo Markdown, updates code to the latest Testcontainers API, splits into chapters with stepper navigation, verifies code compiles and tests pass, and validates against Docker docs style rules. Use when asked to migrate a testcontainers guide, add a TC guide, or port content from testcontainers.com to Docker docs.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

85%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 is a highly actionable, well-sequenced migration playbook with strong validation feedback loops, held back mainly by its monolithic structure — no reference files despite clearly separable content (inventory, per-language commands, style rules) — and minor duplication plus stale-prone inline version pins. Conciseness and organization could both improve by moving per-language detail into references/.

Suggestions

Move the 21-guide inventory table, the Step 4 per-language API patterns, and the Step 6d per-language test commands into references/ files (e.g. references/inventory.md, references/api-patterns.md, references/test-commands.md), keeping SKILL.md a lean overview with clearly signaled one-level-deep links.

Remove the duplicated https://github.com/testcontainers/claude-skills/ paragraph in Step 4 — state it once in the Best practices reference callout and drop the closing 'For all languages' repetition.

Consolidate time-sensitive version pins (testcontainers-go v0.41.0, testcontainers-java 2.0.4, api.version=1.47, Go 1.25+, Quarkus 3.22.3) into a single dedicated versions section or reference file so stale numbers are easy to locate and update.

Dimension	Reasoning	Score
Conciseness	Almost entirely dense, actionable material (tables, commands, exact env vars) with no explanation of concepts Claude already knows, so above the 'mostly efficient' anchor. Held below 5 by the duplicated https://github.com/testcontainers/claude-skills/ reference in Step 4 and scattered time-sensitive version pins (Go v0.41.0, Java 2.0.4, api.version=1.47) not placed in a dedicated versions/old-patterns section.	4 / 5
Actionability	Fully executable throughout: copy-paste docker run commands per language with flags and images, exact Hugo frontmatter templates, an AsciiDoc-to-Markdown conversion table, validation commands with grep, a commit message format, and an inventory table resolving every placeholder. Covers all five language cases.	5 / 5
Workflow Clarity	Steps 0-9 are clearly sequenced with explicit validation checkpoints and feedback loops: baseline verification before changes (6a), 'Fix until green... Do not proceed until verified' (6e), 'Re-run docker buildx bake vale after fixes until no errors remain' (Step 8), plus dev-server and curl-200 verification. Matches the 5 anchor's validate-fix-retry structure.	5 / 5
Progressive Disclosure	The body is a well-sectioned ~400-line monolith with no bundle files at all: the 21-guide inventory table, per-language API patterns, per-language test commands, and style rules are all inlined where they clearly belong in separate reference files. It has structure (so above anchor 2's unstructured inline dump) but content that should be split out is inline with no one-level-deep references, matching the 3 anchor.	3 / 5
	Total	17 / 20 Passed

Description

100%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 is exemplary: third-person, concrete, and comprehensive on capabilities, with an explicit 'Use when' clause containing natural trigger phrasings and synonyms. It clearly delineates the skill's niche with minimal conflict risk.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions with comprehensive coverage: "Converts AsciiDoc to Hugo Markdown, updates code to the latest Testcontainers API, splits into chapters with stepper navigation, verifies code compiles and tests pass, and validates against Docker docs style rules". Matches the anchor 'lists multiple specific concrete actions; comprehensive coverage'; not 4 because no meaningful capability gaps remain.	5 / 5
Completeness	Explicitly answers both questions: a detailed 'what' (converts, updates, splits, verifies, validates) and an explicit trigger clause "Use when asked to migrate a testcontainers guide, add a TC guide, or port content...". Matches the 5-anchor example structure exactly.	5 / 5
Trigger Term Quality	Covers natural synonyms users would say: "migrate a testcontainers guide", "add a TC guide", "port content from testcontainers.com to Docker docs", plus named sites (testcontainers.com, docs.docker.com). Distinct domain vocabulary with several phrasing variants; no common variation is missing.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (Testcontainers guide migration into Docker docs) with distinct trigger phrases; no other plausible skill would fire on these terms. Not 4 because there is no overlap with even closely related skills.	5 / 5
	Total	20 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
relative_links	Relative link issues: 1 missing, 1 suspicious	Warning

	Total	15 / 16 Passed

Repository: docker/docs
Path: .agents/skills/testcontainers-guides-migrator/SKILL.md
Commit: 4d3cbcd

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.