x-guide

Use when the user wants a complex input (file, function, directory, PRD, plan, spec, URL, pasted prose, or vague feature name) explained step by step in a comprehension-gated walkthrough — produces a persistent .x-guide/<slug>/GUIDE.md with full TOC and walks the user one part at a time, supports resume across sessions

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Advisory

Suggest reviewing before use

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-organized, concise orchestration overview whose references are correctly structured, but it delegates its executable core to step and bootstrap files that are missing from the bundle, weakening actionability, workflow clarity, and progressive disclosure.

Suggestions

Ship the steps/ directory: add steps/step-01-detect.md through steps/step-05-wrap.md so the Phase Dispatch table resolves to real, executable phase guidance.

Add gotchas.md and the referenced ../x-shared/capability-loading.md (and mcp-toolbox.md) to the bundle, or inline the minimal bootstrap rules so the MANDATORY bootstrap section is self-contained.

Surface at least one inline validation checkpoint in the body — e.g., the progress.json invariant check from progress-schema.md — so the core render→command→advance loop has an explicit feedback step rather than relying solely on the missing step files.

Dimension	Reasoning	Score
Conciseness	Lean, table-driven overview that assumes Claude's competence — no concept explanations, terse pointers to step files and references, every section earning its place; it is not the padded level-2 example.	3 / 3
Actionability	Routing (phase dispatch table, anti-trigger table, state tree) and file paths are concrete, but the executable guidance lives in steps/step-0X-*.md files that are not present in the bundle, leaving the actual instructions incomplete.	2 / 3
Workflow Clarity	The five phases are clearly sequenced with a bootstrap checklist, but per-phase validation/checkpoints and the core render-menu-command loop are delegated to the missing step files, so checkpoints are implicit rather than shown.	2 / 3
Progressive Disclosure	The existing references/.md files are well-signaled and one-level-deep, but the central steps/.md (5 files), gotchas.md, and ../x-shared/* paths referenced in the body are absent from the bundle, so navigation to the core detail breaks.	2 / 3
	Total	9 / 12 Passed

Description

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.

A strong, complete description: it states concrete capabilities, gives an explicit Use-when trigger with natural input terms, and carves a distinct niche with third-person voice and no over-claims.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "produces a persistent .x-guide/<slug>/GUIDE.md with full TOC", "walks the user one part at a time", "supports resume across sessions" — matching the anchor for listing several specific concrete actions, not merely naming the domain.	3 / 3
Completeness	Explicit "Use when the user wants..." clause answers when, and the producing/walking/resume actions answer what — clearly both, with explicit triggers, so it is not capped at 2.	3 / 3
Trigger Term Quality	Natural input terms a user would say ("file, function, directory, PRD, plan, spec, URL, pasted prose, or vague feature name" + "explained step by step") give good coverage; "comprehension-gated walkthrough" is mildly jargon-y but the surrounding terms are user-natural.	3 / 3
Distinctiveness Conflict Risk	The niche — a progressive comprehension-gated tutorial emitting a persistent GUIDE.md — is clearly stated and distinct; it would not naturally fire for the adjacent research/review/bugfix skills. Slight overlap risk on "vague feature name" keeps it from being unambiguous, but the stated niche is clear.	3 / 3
	Total	12 / 12 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: quangtran88/x-skills
Path: skills/x-guide/SKILL.md
Commit: c765280

Reviewed: 13 days 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.