docs-writer

Documentation workflow that converts requirements into structured AsciiDoc sections, runs Vale for style compliance, and produces merge-ready content. Use when creating or updating AsciiDoc documentation from Jira tickets, GitHub issues, or feature descriptions.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Failed to scan

The risk profile of this skill

Quality

Content

88%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 tight, well-structured orchestrator overview with explicit error-handling and resume checkpoints. It scores high across the board, held back only by reliance on external files that are not part of the provided bundle.

Suggestions

Include the referenced bundle files (commands/, skills/controller.md, guidelines.md) or note that they are provided elsewhere so progressive disclosure navigation is verifiable.

Add a brief inline example of one phase (e.g., the /gather output shape) so the routing guidance is actionable even before the external files are loaded.

Clarify the 'skills/controller.md' path, which suggests a nested skill layout that may not match the bundle structure.

Dimension	Reasoning	Score
Conciseness	The body is lean with no padded concept explanations (no definition of AsciiDoc or Vale); every line is actionable routing guidance that assumes Claude's competence, matching the 'lean and efficient' anchor 5.	5 / 5
Actionability	Provides concrete, executable routing ('read commands/{command}.md', 'read skills/controller.md', 'check .artifacts/${ticket_id}/', 'execute the /gather phase') with specific paths and phases, but it delegates actual execution to external files not present in the bundle, leaving minor gaps versus copy-paste-ready anchor 5.	4 / 5
Workflow Clarity	Presents a clear sequenced Quick Start with an explicit validation/error checkpoint ('If a step fails... stop and report... Do not advance to the next phase. Offer to retry... or escalate') plus resume logic, matching the anchor 5 requirement for explicit validation steps and error-recovery feedback loops.	5 / 5
Progressive Disclosure	Well-signaled one-level-deep references (commands/{command}.md, skills/controller.md, guidelines.md) keep the body an overview, but the referenced bundle files are not present and the 'skills/controller.md' path is slightly unusual, leaving minor organization gaps versus the clean-navigation anchor 5.	4 / 5
	Total	18 / 20 Passed

Description

87%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 concise, specific, and clearly states both capabilities and trigger conditions, hitting near the top of the rubric. The only gap is the absence of file-extension trigger terms, which keeps trigger quality and specificity at 4 rather than 5.

Dimension	Reasoning	Score
Specificity	Names three concrete actions ('converts requirements into structured AsciiDoc sections', 'runs Vale for style compliance', 'produces merge-ready content') with only minor coverage gaps, fitting the 'several specific actions' anchor rather than the fully comprehensive anchor 5.	4 / 5
Completeness	Explicitly answers both what (convert, validate via Vale, produce merge-ready content) and when ('Use when creating or updating AsciiDoc documentation from Jira tickets, GitHub issues, or feature descriptions') with concrete trigger phrases, matching the anchor 5 example.	5 / 5
Trigger Term Quality	Includes natural terms users would say ('AsciiDoc documentation', 'Jira tickets', 'GitHub issues', 'feature descriptions') with good synonym coverage, but lacks file extensions like .adoc that the comprehensive anchor 5 calls for.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (AsciiDoc documentation from Jira/GitHub/feature sources with Vale validation) with distinct triggers and minimal overlap risk with generic doc skills.	5 / 5
	Total	18 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: flightctl/ai-workflows
Path: docs-writer/SKILL.md
Commit: 7efcedb

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