prowler-docs

Prowler documentation style guide and writing standards. Trigger: When writing documentation for Prowler features, tutorials, or guides.

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 ./bundled/skills/prowler-docs/SKILL.md

Quality

Content

65%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 body is a concise, actionable style guide with concrete examples and runnable MDX snippets. Its weaker dimensions are workflow clarity (no sequenced process or validation, though appropriate for a reference skill) and progressive disclosure (a mostly monolithic inlined standards block with a thin, vaguely signaled reference).

Suggestions

Add a short 'How to apply' sequence at the top (e.g. 1. Identify doc type → 2. Apply Brand Voice → 3. Apply Formatting/SEO → 4. Use MDX components → 5. Verify Title Case and proper-noun usage) to give the standards an actionable order.

Move the MDX component gallery and the docs/ directory tree into a separate reference file (e.g. references/mdx-components.md) and link to it from SKILL.md to reduce the inlined block and strengthen progressive disclosure.

Make the reference link specific — replace 'See references/' with a named pointer like 'See [references/documentation-docs.md](references/documentation-docs.md) for the local Mintlify dev-guide setup.'

Dimension	Reasoning	Score
Conciseness	The body is mostly lean bullet-pointed standards with good/bad examples and copy-paste MDX snippets; it does not over-explain concepts Claude already knows, with only minor phrasing that could be trimmed, fitting the 'efficient; minor instances of over-explanation' anchor.	4 / 5
Actionability	Concrete, executable guidance dominates — Title Case good/bad pairs, a bullet-point code template, and runnable MDX <VersionBadge>/<Warning>/<Danger> snippets — with only minor gaps, matching 'mostly executable guidance; concrete code or commands with minor gaps'.	4 / 5
Workflow Clarity	The skill is a reference of standards rather than a sequenced process; there is no explicit workflow or validation checkpoint, and the 'single action' is diffuse across many standards, so it sits at 'sequence/checkpoints missing or implicit' rather than the simple-skill top anchor.	3 / 5
Progressive Disclosure	Section structure is clear (H2/H3 headers) and the one bundle file (references/documentation-docs.md) is a single-level pointer, but most standards are inlined in a ~110-line body and the sole reference link ('See references/ for links to local developer guide') is vaguely signaled, fitting 'some structure but could be better organized'.	3 / 5
	Total	14 / 20 Passed

Description

77%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 well-structured with an explicit trigger clause and a distinct Prowler-scoped niche, scoring high on completeness and distinctiveness. Its main weakness is specificity: it characterizes the skill as a 'style guide' rather than naming concrete actions.

Suggestions

Replace the abstract 'style guide and writing standards' framing with concrete verbs, e.g. 'Applies Prowler brand voice, formatting, SEO, and MDX component standards to documentation.'

Add a few natural synonyms/file cues (e.g. 'MDX', '.mdx', 'release notes') to the trigger clause to broaden keyword coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Prowler documentation style guide and writing standards') but lists no concrete actions — it describes what the skill IS rather than what it does, matching the 'names the domain but actions are minimal or generic' anchor.	2 / 5
Completeness	It explicitly answers both 'what' (Prowler documentation style guide and writing standards) and 'when' (an explicit 'Trigger: When writing documentation...' clause with concrete trigger phrases), matching the top anchor.	5 / 5
Trigger Term Quality	'writing documentation for Prowler features, tutorials, or guides' supplies several natural terms a user would say (documentation, tutorials, guides, features); a few synonyms or file extensions are missing, so it sits above the midpoint but not at comprehensive coverage.	4 / 5
Distinctiveness Conflict Risk	Scoping to the named product 'Prowler' with Prowler-specific documentation triggers gives it a clear niche with minimal overlap risk against generic documentation skills.	5 / 5
	Total	16 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	14 / 16 Passed

Repository: foryourhealth111-pixel/Vibe-Skills
Path: bundled/skills/prowler-docs/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.