CtrlK
BlogDocsLog inGet started
Tessl Logo

dev-guide-generator

Generates complete technical tutorials from prerequisites and environment setup to core steps, troubleshooting, and a final cheatsheet. Trigger on requests to write a tutorial, create a setup guide, organize steps for beginners, or keywords like step-by-step, quickstart, or how-to guide.

66

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/dev-guide-generator/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is a well-sequenced, validated workflow with strong actionability and excellent workflow clarity, but it is a single monolithic file with no progressive disclosure and carries noticeable verbosity in self-check and template sections. Splitting detailed templates into referenced bundle files and trimming redundant rules would materially improve it.

Suggestions

Move the large inline templates (e.g., the Phase 8 full document template and cheatsheet structure) into referenced files under references/ and link to them one level deep, so SKILL.md stays a concise overview.

Trim the repeated per-phase 'Self-check rules' and 'Output' lines into a single consolidated checklist to reduce token overhead while preserving the validation guidance.

Include at least one fully concrete end-to-end worked example (e.g., a short Docker tutorial produced via the SOP) so the templates are demonstrably executable rather than schematic.

DimensionReasoningScore

Conciseness

The SOP is mostly efficient and well-structured, but repeated self-check rule blocks, large inline templates, and verbose per-phase Output lines add padding that could be trimmed without losing clarity, placing it just above the score-2 verbose anchor but short of the lean score-4 level.

3 / 5

Actionability

Provides concrete templates with real commands (e.g., 'brew install xxx', 'sudo apt update && sudo apt install -y xxx'), placeholder conventions ('YOUR_API_KEY', 'YOUR_PROJECT_NAME'), and per-step verification formats — mostly executable, though examples are schematic templates rather than fully copy-paste-ready end-to-end examples.

4 / 5

Workflow Clarity

Clear eight-phase sequence with explicit validation/verification checkpoints in every phase, a pre-output Quality Checklist, and an Iterative Refinement feedback loop (identify phase → re-execute → cascade downstream), matching the score-5 anchor with checklists and error-recovery loops.

5 / 5

Progressive Disclosure

The entire ~370-line SOP is a monolithic single file with no references/, scripts/, or assets/ bundle and no one-level-deep pointers; all detailed templates and reference material are inlined rather than split into separate navigable files, fitting the score-2 'content that belongs in separate files is inlined' anchor.

2 / 5

Total

14

/

20

Passed

Description

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

The description is strong: it clearly states the skill's capability and provides rich, natural trigger terms covering both phrasings and explicit keywords. Specificity and distinctiveness are slightly above the midpoint rather than maximal because the action verbs are somewhat generic and there is minor overlap risk with general writing skills.

DimensionReasoningScore

Specificity

Lists several concrete actions spanning the tutorial lifecycle — 'prerequisites and environment setup to core steps, troubleshooting, and a final cheatsheet' — giving good coverage, though the verbs ('Generates', 'setup', 'steps') are somewhat generic compared to the score-5 anchor's fuller enumeration.

4 / 5

Completeness

Explicitly answers both what ('Generates complete technical tutorials from prerequisites and environment setup to core steps, troubleshooting, and a final cheatsheet') and when ('Trigger on requests to write a tutorial, create a setup guide... or keywords like step-by-step, quickstart, or how-to guide') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural trigger coverage including 'tutorial', 'setup guide', 'organize steps for beginners', and the explicit keyword list 'step-by-step, quickstart, or how-to guide', matching the synonym-rich score-5 anchor.

5 / 5

Distinctiveness Conflict Risk

Occupies a fairly distinct tutorial-generation niche with specific triggers, but 'write a tutorial'/'setup guide' could lightly overlap with general writing or documentation skills, so it stops just short of the score-5 minimal-conflict anchor.

4 / 5

Total

18

/

20

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
zebbern/claude-code-guide
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.