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.
72
88%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
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.
This is an excellent skill description that clearly defines a narrow, specialized task with multiple concrete actions listed. It includes an explicit 'Use when...' clause with natural trigger terms and variations. The description is concise yet comprehensive, making it easy for Claude to select this skill precisely when needed.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: converts AsciiDoc to Hugo Markdown, updates code to latest Testcontainers API, splits into chapters with stepper navigation, verifies code compiles and tests pass, validates against Docker docs style rules. | 3 / 3 |
Completeness | Clearly answers both 'what' (converts AsciiDoc to Hugo Markdown, updates API, splits into chapters, verifies code, validates style) and 'when' with an explicit 'Use when...' clause listing trigger scenarios. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'migrate a testcontainers guide', 'TC guide', 'testcontainers.com', 'Docker docs', 'port content'. Covers common variations including the abbreviation 'TC'. | 3 / 3 |
Distinctiveness Conflict Risk | Extremely specific niche — migrating Testcontainers guides from testcontainers.com to Docker docs. This is unlikely to conflict with any other skill due to its highly specialized domain and toolchain (AsciiDoc, Hugo, Testcontainers API). | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a highly actionable, well-sequenced migration skill with excellent validation checkpoints and copy-paste-ready commands for all five supported languages. Its main weakness is length — the monolithic structure packs ~400 lines of detailed reference material (guide inventory, per-language API patterns, per-language Docker commands, macOS workarounds) that could be split into supporting files for better progressive disclosure. The workflow is exemplary with explicit feedback loops at both the code verification and style validation stages.
Suggestions
Extract the 21-row guide inventory table and per-language API update patterns into separate reference files (e.g., INVENTORY.md, API_PATTERNS.md) to reduce the main skill's token footprint and improve progressive disclosure.
Compress the macOS Docker Desktop workarounds into a concise table or checklist rather than paragraph explanations — Claude can infer why these flags are needed from the flag names and values.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The guide inventory table (21 rows) and per-language API patterns are valuable domain-specific knowledge Claude wouldn't have, but there's some redundancy — the macOS Docker Desktop workarounds section is verbose with explanations Claude could infer, and the style rules in Step 3 could be more compressed (e.g., a simple table). The repeated 'check the latest version' advice across languages is also redundant. | 2 / 3 |
Actionability | Extremely actionable with copy-paste-ready docker run commands for every supported language, exact frontmatter YAML templates, specific file paths, concrete git clone commands, and precise environment variable settings. The macOS workarounds with specific flags like `-Dspotless.check.skip=true` and `TESTCONTAINERS_HOST_OVERRIDE=host.docker.internal` are highly specific and executable. | 3 / 3 |
Workflow Clarity | The 9-step workflow is clearly sequenced with explicit validation checkpoints: Step 6 has a detailed verify-fix-rerun loop (6a baseline → 6b update → 6c compile → 6d test → 6e fix until green), Step 8 has a multi-tool validation pipeline (prettier → lint → vale → dev server → URL checks) with error recovery guidance. The 'do not proceed until verified' gates are explicit. | 3 / 3 |
Progressive Disclosure | The skill references external files like STYLE.md, COMPONENTS.md, and AGENTS.md but these aren't provided in the bundle. The content is quite long (monolithic) — the guide inventory table, per-language API patterns, and per-language test commands could be split into separate reference files. However, the section headers provide good navigation within the single file. | 2 / 3 |
Total | 10 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- docker/docs
- Commit
2ea4a02
- 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.