CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

reverse-document

Writes missing design or architecture docs, or a game's brief, from code. Use when code or prototypes have no docs.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

81%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 exceptionally actionable, well-sequenced process skill with genuine validation checkpoints and disciplined anti-fabrication rules. Its main weakness is token efficiency: the same workflow and cautions are repeated across an example session, a summary protocol, and an overlapping template table, inflating the body by roughly a third.

Suggestions

Cut the Example Session and closing Collaborative Protocol sections — both restate the eight phases already specified in the Workflow section, saving ~50 lines without losing any operational content.

Merge the Template Selection Logic table into Phase 5's type/template/output table, which already covers the same mapping with output paths.

State the anti-fabrication rationale once (at Phase 4, where it is most load-bearing) and reference it from Phases 3b and 5 instead of re-arguing it in each place.

DimensionReasoningScore

Conciseness

The guidance is dense and free of background-concept padding, but the workflow is restated three extra times (the Example Session, the closing Collaborative Protocol list, and the Template Selection Logic table overlapping Phase 5), and the anti-fabrication rationale repeats across Phases 3b, 4, and 5 — roughly a third of the body could be trimmed without loss.

3 / 5

Actionability

Fully executable for an instruction-only skill: verbatim user-facing prompts, exact template and output paths per type and tier, a copy-paste provenance banner, concrete bash invocations, and a literal stop message for the sufficiency failure.

5 / 5

Workflow Clarity

Phases 1–8 are clearly sequenced with explicit validation checkpoints: the Phase 3b sufficiency check with a counting table and hard stop, the Phase 4 wait-for-clarification feedback loop, and Phase 6 approval gates that vary correctly by automation mode.

5 / 5

Progressive Disclosure

The single bundle reference (references/from-a-game.md) is well-signaled with explicit load/don't-load conditions and is one level deep, and section headers aid navigation; however the body is a long monolith whose redundant restatements belong elsewhere or nowhere, and it points at many project files outside the bundle that cannot be verified.

4 / 5

Total

17

/

20

Passed

Description

75%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 concise, third-person description that clearly states what the skill produces and when to use it, with concrete artifact names and an explicit trigger clause. It sits just below top marks on each dimension due to a missing concept-doc capability, thin synonym coverage, a single trigger phrase, and mild overlap with a forward-design sibling skill.

DimensionReasoningScore

Specificity

"Writes missing design or architecture docs, or a game's brief, from code" names three concrete output artifacts, matching the several-specific-actions anchor; it stops short of 5 because the body also supports concept docs, which the description omits.

4 / 5

Completeness

Both what ("Writes missing design or architecture docs, or a game's brief, from code") and when ("Use when code or prototypes have no docs") are answered explicitly; not 5 because the single when-clause omits the inherited-codebase and formalize-a-prototype triggers the body itself lists.

4 / 5

Trigger Term Quality

Natural terms are present ("design", "architecture", "docs", "brief", "code", "prototypes", "no docs"), giving good keyword coverage; a few natural variations users would say are missing ("documentation", "GDD", "ADR", "document this codebase").

4 / 5

Distinctiveness Conflict Risk

"from code" carves a distinct reverse-documentation niche with low conflict risk, but writing design docs overlaps with a closely related forward-design skill (the body references /design-system), keeping it at mostly-distinct rather than a clear isolated niche.

4 / 5

Total

16

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

Donchitos/Claude-Code-Game-Studios

Path

.claude/skills/reverse-document/SKILL.md

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.