skill-style-guide

Writing conventions for scannable, token-efficient skills and prompts. Use when creating or reviewing SKILL.md files, AGENTS.md files, or any markdown-based agent instruction documents.

Quality

88%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

87%

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

This is a strong, well-crafted skill that exemplifies its own principles—concise, scannable, and actionable. The before/after examples are particularly effective for teaching the style. The main weakness is the validation workflow, which references an external checklist but doesn't integrate it into a clear process with checkpoints.

Suggestions

Add a brief workflow section showing when/how to use assets/checklist.md during skill creation (e.g., '1. Draft skill → 2. Run checklist → 3. Fix issues → 4. Re-validate')

Dimension	Reasoning	Score
Conciseness	The skill is lean and token-efficient, using telegraphic style throughout. It practices what it preaches—no unnecessary explanations of concepts Claude would know, every section earns its place.	3 / 3
Actionability	Provides concrete, copy-paste ready examples throughout. Before/after comparisons are executable markdown, formatting patterns show exact syntax, and the RFC 2119 keywords section gives specific usage examples.	3 / 3
Workflow Clarity	While the document structure is clear and sequential, it lacks explicit validation checkpoints or feedback loops. The reference to 'assets/checklist.md' for validation is mentioned but not integrated into a clear workflow sequence.	2 / 3
Progressive Disclosure	Well-organized with clear h2/h3 hierarchy, appropriate content density per section, and a single external reference (assets/checklist.md) that's clearly signaled. Content is appropriately scoped for a style guide.	3 / 3
	Total	11 / 12 Passed

Description

89%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a well-structured description with explicit 'Use when' guidance and good trigger terms for the specific file types it handles. The main weakness is that the capabilities could be more concrete—it describes the purpose (conventions for scannable, token-efficient content) but doesn't enumerate specific actions like formatting, structuring, or optimizing.

Suggestions

Add 2-3 specific concrete actions to improve specificity, e.g., 'Defines formatting standards, frontmatter structure, and token optimization techniques for scannable, efficient skills and prompts.'

Dimension	Reasoning	Score
Specificity	Names the domain (writing conventions for skills/prompts) and mentions some actions (creating, reviewing), but doesn't list specific concrete actions like 'format headers', 'structure frontmatter', or 'optimize token usage'.	2 / 3
Completeness	Clearly answers both what ('Writing conventions for scannable, token-efficient skills and prompts') and when ('Use when creating or reviewing SKILL.md files, AGENTS.md files, or any markdown-based agent instruction documents').	3 / 3
Trigger Term Quality	Includes natural keywords users would say: 'SKILL.md', 'AGENTS.md', 'markdown-based', 'agent instruction documents', 'prompts'. These are specific file types and terms users would naturally mention.	3 / 3
Distinctiveness Conflict Risk	Has a clear niche focused specifically on SKILL.md and AGENTS.md files with distinct triggers. Unlikely to conflict with general writing or documentation skills due to the specific file type mentions.	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
license_field	'license' field is missing	Warning

	Total	15 / 16 Passed

Repository: josephmanghan/manghan-skills
Commit: 8802a2e

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