doc-coauthoring

A structured workflow for co-authoring high-signal docs (PRD, RFC, design docs, proposals, decision records). Use when the user needs to turn messy context into a readable artifact with clear goals, tradeoffs, and next steps. Emphasizes context capture, outline-first drafting, and context-free reader testing to catch blind spots.

Quality

95%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

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 a well-structured, lean workflow with concrete actionable guidance, explicit feedback/validation loops, and appropriate one-level-deep reference use. It is a strong, high-signal skill body with no notable gaps.

Dimension	Reasoning	Score
Conciseness	The body is lean and purposeful with no over-explanation of concepts Claude already knows; every section (triggers, stages, quality bar) earns its tokens.	3 / 3
Actionability	As an instruction skill it gives concrete, copy-paste-ready guidance: seven specific context-capture questions, a verbatim reader-review prompt, and a four-step per-section iteration loop.	3 / 3
Workflow Clarity	Three sequenced stages with explicit gates ('Do not write full paragraphs until the outline is agreed'), a draft→review→revise feedback loop, and a dedicated reader-testing validation stage.	3 / 3
Progressive Disclosure	The body is a workflow overview that delegates detail to a single clearly-signaled, one-level reference ('Load references/templates.md'), which exists as a real file.	3 / 3
	Total	12 / 12 Passed

Description

90%

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, clearly stating both what the skill does and when to use it with explicit, natural trigger terms and a well-defined niche. Its only weakness is that the named methods are phrased as emphases with minor buzzword padding rather than crisp operations.

Dimension	Reasoning	Score
Specificity	It names the domain and three methods ('context capture, outline-first drafting, and context-free reader testing'), but these are framed as emphases rather than crisp concrete operations, and 'high-signal docs' leans slightly buzzwordy.	2 / 3
Completeness	It states what the skill does ('co-authoring high-signal docs') and gives an explicit 'Use when the user needs to turn messy context into a readable artifact...' trigger.	3 / 3
Trigger Term Quality	Strong natural-term coverage via 'PRD, RFC, design docs, proposals, decision records' plus 'docs' and 'readable artifact' — terms a user would actually say.	3 / 3
Distinctiveness Conflict Risk	The named artifact types plus a distinctive three-stage co-authoring method (with reader testing) carve a clear niche unlikely to trigger for unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: shareAI-lab/Kode-CLI
Path: packages/builtin-skills/skills/doc-coauthoring/SKILL.md
Commit: 4afba64

Reviewed: 3 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.