documentation

Use when writing blog posts or documentation markdown files - provides writing style guide (active voice, present tense), content structure patterns, and SEO optimization. Overrides brevity rules for proper grammar.

Quality

81%

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

78%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.

A well-organized, efficient SKILL.md body that uses tables and bullet lists to deliver concrete guidance and cleanly offloads detail to real one-level-deep reference files. It could tighten its opening and add an explicit verification feedback loop to reach the top tier.

Suggestions

Trim the opening line "This skill provides comprehensive guidelines for AI coding assistants working on documentation." — the title and When-to-Use section already convey this.

Add an explicit validate-then-fix feedback loop (e.g. run the humanizer pass, re-check the Checklist, iterate) so the workflow ends in a clear verification cycle rather than a flat checklist.

Add a couple of concrete, copy-paste-ready admonition/code-group examples alongside the table entries to lift actionability from illustrative to fully executable.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient, using compact tables and bullet lists (Writing Patterns, Modal Verbs, Component Patterns) without explaining concepts Claude already knows; not a 5 because of minor padding such as "This skill provides comprehensive guidelines for AI coding assistants working on documentation."	4 / 5
Actionability	Provides concrete, specific guidance via example tables (pattern-to-example pairs, concrete filenames like `multipart-form-data.md`, modal-verb semantics, admonition syntax); not a 5 because several entries are illustrative rather than fully copy-paste-ready executable units.	4 / 5
Workflow Clarity	As a style/guidance skill it is not a destructive or batch operation, so the destructive-cap does not apply; the Checklist and When-to-Use/What-It-Does framing give a clear sequence with a verification list, but there is no explicit feedback loop, capping it below 5.	4 / 5
Progressive Disclosure	A clear overview with an Available References table (purpose column) plus a "Load based on context" mapping that signals one-level-deep references; all four referenced files (writing-style.md, content-patterns.md, seo-optimization.md, humanizer.md) exist under ./references/, matching the clear-overview anchor.	5 / 5
	Total	17 / 20 Passed

Description

83%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 well-constructed description that clearly states both what the skill does and when to use it, with concrete capabilities and natural trigger phrasing. The main room for improvement is broader synonym coverage in trigger terms.

Dimension	Reasoning	Score
Specificity	Names the domain ("writing blog posts or documentation markdown files") and several concrete capabilities (writing style guide with active voice/present tense, content structure patterns, SEO optimization), matching the "lists several specific actions; minor gaps" anchor; not a 5 because the actions are framed as deliverables rather than a comprehensive enumerated action set.	4 / 5
Completeness	Explicitly answers both what ("provides writing style guide..., content structure patterns, and SEO optimization") and when ("Use when writing blog posts or documentation markdown files") with concrete trigger phrases, matching the anchor for clearly and explicitly answering both.	5 / 5
Trigger Term Quality	Includes natural user phrasing ("writing blog posts or documentation markdown files", "SEO optimization") with good coverage; not a 5 because common synonyms and variations (e.g. "docs", "articles", "technical writing") are absent.	4 / 5
Distinctiveness Conflict Risk	The documentation/prose-writing niche with SEO framing is mostly distinct with a clear trigger, but it has minor overlap risk with general writing or markdown-formatting skills, so it sits at the "mostly distinct" anchor rather than the minimal-conflict 5.	4 / 5
	Total	17 / 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
relative_links	Relative link issues: 8 suspicious	Warning

	Total	15 / 16 Passed

Repository: kubb-labs/kubb
Path: .agents/skills/documentation/SKILL.md
Commit: 1bbf973

Reviewed: about 18 hours 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.