CtrlK
BlogDocsLog inGet started
Tessl Logo

write-docs

Collaborative document authoring workflow for proposals, technical specs, decision docs, README sections, ADRs, and long-form prose that must work for fresh readers. Use when asked to "write the docs", "draft a proposal", "write a spec", "write an RFC", "write the README", or when a document needs to be understandable by someone without this session's context. Three stages: gather context, iterate on structure, reader-test for a stranger.

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 findings from the security scan

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.

A tight, well-structured instruction skill: lean prose, concrete actionable guidance with real commands and a tool-call example, an explicit reader-test validation loop, and clean sectioning with no reference sprawl. No bundle files exist, which is appropriate for a process skill of this size.

DimensionReasoningScore

Conciseness

Lean, punchy prose ('Paths rot.', 'Documentation bloat kills docs.') with no concept re-explanation or padding; every section earns its place and it assumes Claude's competence, matching the top anchor.

3 / 3

Actionability

Gives concrete executable guidance such as target file paths (docs/<name>.md, README.md), the Agent(subagent_type=Explore) cold-reader offer, and appending to .gsd/DECISIONS.md; as an instruction-only skill this satisfies the actionable bar without needing code.

3 / 3

Workflow Clarity

Four clearly sequenced stages with numbered steps, an explicit reader-test validation checkpoint with a fix-and-recheck loop ('If no, identify the missing piece and add it'), and a success-criteria checklist, matching the 'clear sequence with explicit validation steps' anchor.

3 / 3

Progressive Disclosure

A single self-contained SKILL.md cleanly organized into semantic sections (<objective>, <process>, <anti_patterns>, <success_criteria>) with no external references needed and no nested reference chains, satisfying the well-organized-sections top anchor for a short, single-process skill.

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.

A strong description: concrete capabilities, natural trigger phrasings, an explicit Use-when clause, and a clearly bounded niche that separates it from templated doc workflows. Third-person voice is maintained throughout.

DimensionReasoningScore

Specificity

Enumerates multiple concrete document types ('proposals, technical specs, decision docs, README sections, ADRs, and long-form prose') and a three-stage process, matching the 'lists multiple specific concrete actions' anchor rather than the partial coverage of a 2.

3 / 3

Completeness

Clearly states both what (collaborative document authoring workflow) and when (an explicit 'Use when asked to...' clause with multiple triggers), matching the 'both what AND when with explicit triggers' anchor.

3 / 3

Trigger Term Quality

Explicit natural triggers users would say ('write the docs', 'draft a proposal', 'write a spec', 'write an RFC', 'write the README') give good coverage of common phrasings, satisfying the top anchor.

3 / 3

Distinctiveness Conflict Risk

Scopes to free-form docs living under docs/, mintlify-docs/, or gitbook/ and contrasts with GSD scaffolded templates, carving a distinct niche unlikely to trigger the wrong skill.

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
gsd-build/gsd-2
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.