create-lab-guide
Create a guide page for a Labspace. This includes writing the markdown content for the guide, structuring it according to Docker docs conventions, and ensuring it provides clear instructions and information about the Labspace. Includes learning about the lab itself, extracting out its learning objectives, and combining all of that into a well-structured guide markdown file.
75
61%
Does it follow best practices?
Impact
100%
2.22xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agents/skills/create-lab-guide/SKILL.mdQuality
Discovery
57%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 identifies a clear niche (Docker Labspace guide pages) with reasonable specificity about the task, giving it good distinctiveness. However, it lacks an explicit 'Use when...' clause, which limits completeness, and the trigger terms could be broader to capture more natural user phrasings. The description is also somewhat repetitive, restating the same concept (creating a guide) in slightly different ways.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to create or write a guide, tutorial, or documentation page for a Docker Labspace.'
Include natural trigger term variations such as 'lab guide', 'tutorial page', 'Docker lab documentation', 'lab instructions', or 'hands-on lab guide'.
Reduce repetition — the description says 'guide page', 'guide markdown file', and 'clear instructions and information about the Labspace' which all convey the same idea. Use the freed space for more distinct actions or trigger terms.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (Labspace guide pages) and some actions (writing markdown content, structuring according to Docker docs conventions, extracting learning objectives), but the actions are somewhat repetitive and not as concrete as listing distinct operations like 'extract text, fill forms, merge documents'. | 2 / 3 |
Completeness | The description answers 'what does this do' reasonably well (create guide pages for Labspaces with markdown, learning objectives, etc.), but there is no explicit 'Use when...' clause or equivalent trigger guidance telling Claude when to select this skill. | 2 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'guide page', 'Labspace', 'markdown', 'Docker docs', and 'learning objectives', but these are fairly niche terms. Missing common variations a user might say such as 'lab guide', 'tutorial page', 'Docker lab', or 'documentation page'. | 2 / 3 |
Distinctiveness Conflict Risk | The description targets a very specific niche — Labspace guide pages following Docker docs conventions — which is unlikely to conflict with other skills. The combination of 'Labspace', 'Docker docs conventions', and 'learning objectives' creates a distinct identity. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides strong actionability with a complete markdown template and specific file paths, making it clear what Claude should produce. However, it lacks validation checkpoints (e.g., verifying frontmatter validity or style compliance), has a duplicate Step 2 heading that breaks the workflow sequence, and could be tighter by removing some explanatory text and properly referencing external style guides rather than partially inlining them.
Suggestions
Fix the duplicate 'Step 2' heading — rename the second to 'Step 3' and adjust subsequent steps accordingly.
Add a validation step after writing the markdown, such as checking that frontmatter parses as valid YAML and that all required fields are present.
Either fully reference STYLE.md/AGENTS.md as bundle files or commit to inlining the rules — the current partial inline creates ambiguity about the authoritative source.
Add a brief verification checklist at the end (e.g., 'Confirm: no hedge words, no "we", aliases present if AI lab, labs tag included').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably structured but includes some unnecessary verbosity, such as explaining repo structure details Claude could infer and repeating information (e.g., the numbered Step 2 appears twice). The style rules section is lengthy but domain-specific enough to justify inclusion. | 2 / 3 |
Actionability | Provides concrete, executable git clone commands, specific file paths to read, a complete sample markdown template with frontmatter, and detailed conditional logic (e.g., model-download parameter, AI-related aliases). Claude has everything needed to produce the output. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced (clone → extract info → write markdown → apply style), but there are no validation checkpoints — no step to verify the generated markdown renders correctly, no check that frontmatter is valid YAML, and no feedback loop for style rule compliance. The duplicate 'Step 2' heading is also a sequencing error. | 2 / 3 |
Progressive Disclosure | The content is self-contained in a single file with reasonable section headers, but references STYLE.md and AGENTS.md without linking to them. The style rules are inlined rather than referenced, and no bundle files are provided to support the references mentioned. | 2 / 3 |
Total | 9 / 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.