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

83%

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

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill body is highly actionable with concrete tool names, formats, and a well-sequenced review workflow including verification checkpoints. It loses points mainly for redundant repetition of the numbering/parallel-commenting rules and an external style-guide reference whose path does not resolve.

Suggestions

Consolidate the repeated sequential-numbering and single-parallel-response rules into one authoritative section to remove redundancy across Review process, Feedback format, PR review mode, and Final check.

Verify the `@./../_shared/metabase-style-guide.md` reference resolves to a real file, or inline the essential style-guide rules the checklist depends on so the skill is self-contained.

Consider trimming the duplicated IMPORTANT bullet list under PR review mode since the same constraints are already stated in the workflow steps.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and free of concept-explaining fluff, but the sequential-numbering and single-parallel-response rules are restated across the Review process, Feedback format, PR review mode, Final check, and IMPORTANT sections, which could be tightened into one authoritative statement.	2 / 3
Actionability	Guidance is concrete and copy-paste ready: exact tool names, the literal comment format `Issue N: [Brief title]`, event type "COMMENT", and a specific checklist of patterns to scan for.	3 / 3
Workflow Clarity	Both review modes are laid out as a clear numbered sequence with explicit final-check verification steps (verify sequential numbering, confirm format, confirm per-comment posting).	3 / 3
Progressive Disclosure	The body is well sectioned and self-contained with no nested references, but the only external reference (`@./../_shared/metabase-style-guide.md`) does not resolve to an actual file, so the bundle structure cannot be verified as one-level-deep and clearly signaled.	2 / 3
	Total	10 / 12 Passed

Description

90%

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 clearly answers both what the skill does and when to invoke it, with natural trigger terms and a distinct niche. Its only limitation is naming a single action rather than enumerating several concrete capabilities.

Dimension	Reasoning	Score
Specificity	Names a concrete action ("Review documentation changes for compliance with the Metabase writing style guide") and its domain, but lists a single action rather than multiple specific concrete actions, so it stops short of the top anchor.	2 / 3
Completeness	It answers both 'what' (review documentation changes for style-guide compliance) and 'when' via an explicit "Use when reviewing pull requests, files, or diffs..." trigger clause.	3 / 3
Trigger Term Quality	Phrases like "reviewing pull requests, files, or diffs containing documentation markdown files" are natural terms a user would actually say, giving good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	The Metabase style-guide niche plus documentation-markdown triggers make it clearly distinguishable and unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 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: f627ab5

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