writing-guidelines

Review docs/prose for Writing Guidelines compliance. Use when asked to "review my docs", "check writing style", "audit prose", "review docs voice and tone", or "check this page against the writing handbook".

Quality

71%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/writing-guidelines/SKILL.md

Quality

Content

63%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 compact, well-structured skill body that sequences its single-purpose workflow clearly. Its main weaknesses are duplicated workflow sections and deferring the actual review rules entirely to a fetched external document.

Suggestions

Merge the redundant 'How It Works' and 'Usage' step lists into a single workflow to remove the duplicated 4-step sequence.

Inline at least the most important Writing Guidelines rules (or a concise summary) so the skill is actionable even before or without a successful WebFetch.

Add a fallback note for when the guidelines fetch fails (e.g., retry, or surface the error) to strengthen the workflow's robustness.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean, but the 'How It Works' and 'Usage' sections repeat nearly identical 4-step workflows, which is unnecessary redundancy that could be merged.	3 / 5
Actionability	It provides a concrete source URL, names WebFetch, and specifies the `file:line` output format, but the substantive review rules are deferred to fetched content rather than included, leaving the skill a thin wrapper.	3 / 5
Workflow Clarity	Numbered steps give a clear sequence for a single-purpose, non-destructive review skill (so the validation cap does not apply); the duplicated workflow sections are a minor clarity gap.	4 / 5
Progressive Disclosure	Under 50 lines with no bundle files and well-organized sections (How It Works / Guidelines Source / Usage) plus a single one-level external reference, satisfying the simple-skill exception for a top score.	5 / 5
	Total	15 / 20 Passed

Description

78%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 strong, complete description that clearly states what the skill does and when to use it with concrete, natural trigger phrases. Minor room to improve specificity of actions and distinctiveness of the broadest trigger terms.

Suggestions

Add one or two more concrete actions (e.g., 'flag violations', 'suggest rewrites') to lift specificity above a single 'review' verb.

Tighten the most generic trigger ('review my docs') toward writing-style-specific phrasing to reduce overlap with general doc-review skills.

Dimension	Reasoning	Score
Specificity	Names the domain ('docs/prose', 'Writing Guidelines') and one concrete action ('Review ... for compliance'), matching the anchor for a single concrete action without comprehensive coverage.	3 / 5
Completeness	Explicitly answers both what ('Review docs/prose for Writing Guidelines compliance') and when (concrete 'Use when asked to ...' trigger phrases), matching the top anchor.	5 / 5
Trigger Term Quality	Five natural user phrasings ('review my docs', 'check writing style', 'audit prose', 'review docs voice and tone', 'check this page against the writing handbook') give good keyword coverage, though it stops short of synonym/file-extension completeness.	4 / 5
Distinctiveness Conflict Risk	The writing-style/voice-and-tone niche is mostly distinct, but generic triggers like 'review my docs' carry minor overlap risk with other doc-review skills.	4 / 5
	Total	16 / 20 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: millionco/react-doctor
Path: .agents/skills/writing-guidelines/SKILL.md
Commit: 83466a8

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