CtrlK
BlogDocsLog inGet started
Tessl Logo

brain-to-docs

Use when the user wants to extract project vision, decisions, and preferences from his head into clear documentation (README + ADRs) through a back-and-forth Q&A loop. Triggers on "brain-to-docs", "build out the docs", "extract the vision", "let's document this project".

80

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

The body is concise, actionable, and well-organized with a clear numbered loop and explicit checkpoints, and it correctly stays self-contained without external references. It satisfies all four content dimensions.

DimensionReasoningScore

Conciseness

Lean and efficient at under 30 lines with no concept padding — it assumes Claude knows what READMEs and ADRs are and gives only behavioral guidance, so every token earns its place; not score 2 because there is no unnecessary explanation to trim.

3 / 3

Actionability

Concrete, executable guidance — 'Ask 5 different questions in plain text (never a questions UI)', ADR format 'NNNN-slug.md, Status + Context + Decision + Consequences', 'Update docs after EVERY answer' — fully actionable for an instruction-only skill; not score 2 because the key details (count, format, location, mode) are all specified.

3 / 3

Workflow Clarity

A clearly sequenced 4-step loop with explicit per-iteration checkpoints ('Check docs first, every time', 'Update docs after EVERY answer — no exceptions') and a defined termination ('Repeat until the user says we're done'); not score 2 because checkpoints are explicit, and the cap-at-2 rule for destructive/batch ops does not apply to a conversational Q&A loop.

3 / 3

Progressive Disclosure

A self-contained skill under 50 lines with no external references, organized into clear sections ('## The loop', '## Rules'); per the rubric's simple-skill note, well-organized sections alone warrant a 3 with no bundle files needed.

3 / 3

Total

12

/

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.

The description is strong: it states concrete actions in third person, includes an explicit 'Use when' clause plus natural trigger phrases, and occupies a clear niche. It fully satisfies all four dimensions.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'extract project vision, decisions, and preferences', 'into clear documentation (README + ADRs)', 'through a back-and-forth Q&A loop' — in third-person voice, matching the score-3 anchor for specific concrete actions.

3 / 3

Completeness

Clearly answers both what ('extract... into clear documentation (README + ADRs) through a back-and-forth Q&A loop') and when ('Use when the user wants to...' + 'Triggers on...'), matching the score-3 anchor for explicit what-and-when.

3 / 3

Trigger Term Quality

Explicit triggers 'build out the docs', 'let's document this project', and 'extract the vision' are natural phrases a user would say, giving good coverage of natural terms; not score 2 because it provides multiple common variations rather than just one.

3 / 3

Distinctiveness Conflict Risk

A clear niche — extracting vision/decisions into README + ADRs via Q&A — with distinct triggers unlikely to fire for unrelated skills; not score 2 because the domain and triggers are specific rather than broadly overlapping.

3 / 3

Total

12

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
mishatojk/davidskills
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.