docs-review

Review documentation changes for compliance with the Metabase writing style guide. Use when reviewing pull requests, files, or diffs containing documentation markdown files.

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

92%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 highly actionable, well-structured review skill body with a clear sequenced workflow and validation checkpoints. The only meaningful improvement is reducing the repetitive emphasis on the mandatory sequential numbering requirement.

Suggestions

Consolidate the sequential-numbering requirement into a single clearly marked statement instead of restating it as REQUIRED, MANDATORY REQUIREMENT, NON-NEGOTIABLE, CRITICAL, and MUST across multiple sections.

Dimension	Reasoning	Score
Conciseness	Mostly efficient checklists and concrete workflow steps, but the sequential-numbering requirement is restated redundantly across sections (REQUIRED, MANDATORY, NON-NEGOTIABLE, CRITICAL, MUST, multiple do-NOT reminders) and could be tightened.	4 / 5
Actionability	Provides concrete MCP tool names, exact comment-format templates, the specific 'COMMENT' event type, and a worked checklist with examples — fully executable guidance for the review task.	5 / 5
Workflow Clarity	A clearly sequenced 5-step PR-mode workflow with an explicit collection checkpoint before posting, a parallel-posting step, a submit step, and a final-check feedback loop that re-verifies numbering and format.	5 / 5
Progressive Disclosure	Well-organized sections with a single well-signaled one-level-deep external reference (@./../_shared/metabase-style-guide.md) and appropriately inlined review guidance; no bundle files exist to further split.	5 / 5
	Total	19 / 20 Passed

Description

82%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, well-formed description that clearly states both its purpose and its activation triggers with a distinctive Metabase niche. Its only weakness is that it names a single primary action rather than enumerating several concrete capabilities.

Dimension	Reasoning	Score
Specificity	Names the documentation domain and one concrete action ('Review documentation changes for compliance with the Metabase writing style guide'), but does not enumerate multiple distinct actions, so it stops at the 1-2 concrete actions anchor.	3 / 5
Completeness	Explicitly answers both what ('Review documentation changes for compliance with the Metabase writing style guide') and when ('Use when reviewing pull requests, files, or diffs containing documentation markdown files') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural terms users would say ('pull requests, files, or diffs containing documentation markdown files') with good coverage, though synonyms like 'docs' and file extensions are missing.	4 / 5
Distinctiveness Conflict Risk	Scoped to the 'Metabase writing style guide' with specific documentation/PR triggers, giving it a clear niche with minimal overlap against unrelated skills.	5 / 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
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	15 / 16 Passed

Repository: foryourhealth111-pixel/Vibe-Skills
Path: bundled/skills/docs-review/SKILL.md
Commit: d5ae560

Reviewed: 1 day 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.