create-lab-guide
Clone a dockersamples Labspace repo, extract learning objectives and module structure from labspace.yaml, and produce a Hugo guide page under content/guides/ with correct frontmatter, labspace-launch shortcode, and Docker docs style compliance. Use when asked to create a lab guide, write a Labspace page, add a Docker lab tutorial, migrate a lab to docs, or document a hands-on lab.
91
88%
Does it follow best practices?
Impact
97%
1.42xAverage score across 3 eval scenarios
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 articulates specific concrete actions, provides explicit trigger guidance via a 'Use when...' clause, and occupies a highly distinctive niche. It uses proper third-person voice throughout and balances detail with conciseness effectively.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: clone a dockersamples Labspace repo, extract learning objectives and module structure from labspace.yaml, produce a Hugo guide page under content/guides/ with correct frontmatter, labspace-launch shortcode, and Docker docs style compliance. | 3 / 3 |
Completeness | Clearly answers both 'what' (clone repo, extract objectives/structure, produce Hugo guide page with specific elements) and 'when' (explicit 'Use when...' clause with five distinct trigger scenarios). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'lab guide', 'Labspace page', 'Docker lab tutorial', 'migrate a lab to docs', 'hands-on lab'. These cover multiple natural phrasings a user might use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a very specific niche: Docker Labspace repos, labspace.yaml, Hugo guide pages, labspace-launch shortcode. Unlikely to conflict with other skills due to the specificity of the domain and tooling. | 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 strong, actionable skill with a clear multi-step workflow, concrete template output, and proper validation gates. The main weakness is some redundancy in inlining style rules that are already covered by referenced files (STYLE.md, COMPONENTS.md), which slightly hurts both conciseness and progressive disclosure. Overall it provides excellent guidance for a domain-specific task with good structure.
Suggestions
Replace the inline style rules table in Step 4 with a brief reminder to follow STYLE.md and COMPONENTS.md, since the detailed rules are presumably already in those files.
Consider moving the full frontmatter template to a separate reference file and keeping only a minimal example inline to improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient with good use of tables for style rules and file purposes, but the style rules table in Step 4 is somewhat lengthy and could reference STYLE.md/COMPONENTS.md instead of inlining common writing guidance Claude already knows. The frontmatter template is appropriately detailed since it's domain-specific. | 2 / 3 |
Actionability | Provides a complete, copy-paste-ready markdown template with exact frontmatter fields, executable shell commands for cloning, specific file paths to read, concrete shortcode syntax, and explicit conditional rules. The output format is unambiguous. | 3 / 3 |
Workflow Clarity | Clear 5-step sequence with explicit validation in Step 5 including linting commands, formatting, and a checklist of items to verify. The instruction 'Do not proceed to commit until validation passes' provides a clear gate, and the validation step covers multiple dimensions (frontmatter, formatting, linting, content accuracy). | 3 / 3 |
Progressive Disclosure | References STYLE.md and COMPONENTS.md appropriately for style details, but the style rules table is inlined rather than fully deferring to those files. The skill is well-organized with clear sections, but with no bundle files provided, the references to STYLE.md and COMPONENTS.md cannot be verified, and the inline style table partially duplicates what those files presumably contain. | 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.