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.
90
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, explicit trigger guidance, and highly distinctive terminology. It follows third-person voice throughout and provides enough detail for Claude to confidently select this skill only when appropriate.
| 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 specific trigger scenarios. | 3 / 3 |
Trigger Term Quality | Includes natural trigger terms users would say: 'migrate a testcontainers guide', 'add a TC guide', 'port content from testcontainers.com to Docker docs', plus domain-specific terms like 'AsciiDoc', 'Hugo Markdown', 'testcontainers.com', 'docs.docker.com'. | 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 given the highly specialized domain and toolchain (AsciiDoc, Hugo, Testcontainers API, Docker docs style rules). | 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-structured migration skill with excellent workflow clarity including explicit validation checkpoints and feedback loops. Its main weakness is length — the inline guide inventory, per-language API patterns, and per-language test commands make it quite long when some of this could be split into referenced files. The content is domain-specific and valuable (not explaining things Claude already knows), but the sheer volume could benefit from better progressive disclosure.
Suggestions
Extract per-language API patterns (Step 4) and test commands (Step 6d) into separate reference files (e.g., LANGUAGES.md or per-language files) and reference them from the main skill to reduce inline bulk.
Compress the Step 3 style rules into a more compact table format rather than individual bullet points with before/after examples — Claude can apply style rules from a concise list.
| 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 and COMPONENTS.md but keeps a large amount of inline content (the full guide inventory, all language-specific API patterns, all docker run commands for 5 languages, macOS workarounds). The language-specific API patterns and test commands could be split into per-language reference files. However, the overall section structure is clear and navigable. | 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
c0aa985
- 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.