Name: create-lab-guide
Rating: 88.2 (1 reviews)
Author: docker

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.

1.08x

Quality

92%

Does it follow best practices?

Impact

99%

1.08x

Average score across 2 eval scenarios

Securityby

Low

Low-risk findings worth noting

Quality

Content

92%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.

An actionable, tightly written workflow with concrete commands, a complete template, and explicit validation checkpoints. The main gap is structure: a single long file inlines template and style content that belongs in one-level-deep reference files.

Suggestions

Move the full Hugo page template (Step 3) into references/guide-template.md and keep only the file path and key frontmatter rules in SKILL.md, cutting the body roughly by a third.

Replace the inlined style-rules table in Step 4 with a pointer to a references/style-rules.md (or to the actual STYLE.md/COMPONENTS.md locations in the docs repo), since that table duplicates content the referenced files already hold.

Clarify where STYLE.md and COMPONENTS.md live (full paths in the target repo), since they are not part of this skill's bundle and a bare filename reference could fail to resolve.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes competence: file-extraction purposes are a terse table, style rules are an avoid/use table, and no concepts Claude already knows are explained. Every section carries non-obvious information (repo-specific paths, frontmatter fields, validation commands).	5 / 5
Actionability	Fully executable guidance: copy-paste commands ("git clone --depth 1 https://github.com/dockersamples/{REPO_NAME}.git", "npx --no-install rumdl fmt <file>", "docker buildx bake lint vale") and a complete fill-in page template with a single clearly-defined input (REPO_NAME).	5 / 5
Workflow Clarity	Five clearly sequenced steps with an explicit validation gate: format, lint, and re-read checks, plus "Do not proceed to commit until validation passes" and a conditional rule set mapping repo traits to template changes — a full feedback loop.	5 / 5
Progressive Disclosure	Good section structure, but this ~110-line skill is monolithic: the 40-line page template and the style-rules table (which restates content from the referenced "STYLE.md and COMPONENTS.md") are inlined where a references/ split would help, and no bundle files exist — the referenced STYLE.md/COMPONENTS.md are not part of the skill bundle.	3 / 5
	Total	18 / 20 Passed

Description

92%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.

A strong description: concrete, comprehensive capabilities paired with an explicit and varied 'Use when...' trigger clause. The only weakness is minor — a few natural trigger variations are absent.

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" — with comprehensive coverage. Voice is third person, so no penalty applies.	5 / 5
Completeness	Explicitly answers both what (detailed capability statement) and when ("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") with concrete trigger phrases, matching the 5 anchor.	5 / 5
Trigger Term Quality	"create a lab guide", "write a Labspace page", "add a Docker lab tutorial", "migrate a lab to docs", and "document a hands-on lab" give good natural-phrase coverage, but a few plausible variations (e.g. "publish a lab", plain "labspace docs") are missing — just short of the comprehensive synonym coverage of the 5 anchor.	4 / 5
Distinctiveness Conflict Risk	A clear niche — converting Docker Labspace repos into Hugo guide pages for the Docker docs site — with distinct trigger phrases, so conflict risk with other skills is minimal.	5 / 5
	Total	19 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: docker/docs
Path: .agents/skills/create-lab-guide/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.