proofread-markdown

Proofreads Markdown files against Google guidelines.

Quality

66%

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/proofread_markdown/SKILL.md

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.

The content is a tight, well-structured checklist workflow with concrete rules, real examples, and an appropriately referenced helper script. Its only weak spots are the lack of an explicit script invocation command and a missing validate→retry feedback loop.

Dimension	Reasoning	Score
Conciseness	The body is lean and checklist-driven with minimal prose, but the overview vision statement ("Help us transform technical text into clear, concise, and machine-readable Markdown") and the re-explanation of front matter are minor instances of over-explanation that could be trimmed.	4 / 5
Actionability	Guidance is concrete and specific — an explicit forbidden-terms list, a copy-paste heading-id format, and No/Yes heading examples — but the primary mechanical step references scripts/wrap_lines.dart via a link without an executable invocation command, leaving a minor gap.	4 / 5
Workflow Clarity	The six numbered steps form a clear sequence with checkboxes and a verify checkpoint ("Verify that the file was wrapped correctly"), but there is no explicit validate→fix→retry feedback loop for the file-rewriting step, which keeps it below 5.	4 / 5
Progressive Disclosure	A clear overview precedes well-organized numbered sections, and the single external reference (scripts/wrap_lines.dart) is a real, well-signaled one-level-deep link with script logic appropriately split out of the body.	5 / 5
	Total	17 / 20 Passed

Description

53%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 and names a clear niche, but it states only a single action and omits any "Use when..." trigger guidance, leaving the "when to use" question unanswered. It is solid but not comprehensive.

Suggestions

Add an explicit "Use when..." clause (e.g., "Use when proofreading or styling Markdown documentation against the Google Developer Documentation Style Guide") to answer when Claude should invoke the skill.

Enumerate concrete actions beyond "Proofreads" (e.g., "Checks line length, voice and tone, word choice, heading style, and list formatting") to improve specificity and coverage.

Include natural trigger synonyms users actually say (e.g., "lint", "style check", "format Markdown") to broaden keyword coverage.

Dimension	Reasoning	Score
Specificity	"Proofreads Markdown files against Google guidelines" names the domain and one concrete action ("Proofreads") but offers no enumeration of what the proofreading covers, so it is not comprehensive — matching the 1-2 concrete actions anchor rather than the minimal/generic anchor below.	3 / 5
Completeness	It has a clear "what" (proofreads Markdown against Google guidelines) but no "Use when..." clause or equivalent trigger guidance, so per the rubric completeness is capped at 3.	3 / 5
Trigger Term Quality	"Markdown files" and "Google guidelines" are relevant natural terms, but common variations users would say ("lint", "style check", "format", "Google Developer Documentation Style Guide") are missing, fitting the some-keywords-but-missing-synonyms anchor.	3 / 5
Distinctiveness Conflict Risk	The Markdown + Google-style proofreading niche is mostly distinct with minimal conflict risk, though it could overlap with general markdown formatting skills; it lacks the explicit trigger clause that would push it to 5.	4 / 5
	Total	13 / 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: flutter/website
Path: .agents/skills/proofread_markdown/SKILL.md
Commit: 642fe42

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