blog-persona

Create and manage writing personas with NNGroup 4-dimension tone framework (Funny-Serious, Formal-Casual, Respectful-Irreverent, Enthusiastic-Matter-of-fact). Personas define readability targets, sentence length distribution, vocabulary tier, contraction frequency, and summary box label. Used by blog-write and blog-rewrite to enforce consistent voice. Use when user says "persona", "voice", "tone", "writing style", "brand voice", "create persona", "use persona".

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

75%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 well-structured, actionable instruction skill with a clear multi-step workflow, concrete defaults, and explicit error handling. It is slightly held back by minor over-explanation and validation steps that are described rather than given as explicit commands.

Suggestions

Tighten the voice-sample safety paragraph into a compact bullet list of constraints to reduce token overhead without losing the security detail.

Make post-generation validation an explicit ordered checklist (run check -> list violations -> suggest specific edit -> re-run) so the retry loop is copy-paste clear.

Consider moving the full Persona Profile Schema and Readability Bands table into a references file (e.g., references/persona-schema.md) referenced from the body to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Mostly dense reference-style content (tables, defaults, schema) with little padding, but includes a few sentences of explanation (e.g., the voice-sample safety block and framework framing) that could be trimmed. Not a 5 because minor over-explanation remains; not a 3 because the bulk is lean and load-bearing.	4 / 5
Actionability	Provides concrete executable guidance — explicit 6-step interview, exact file paths, a full JSON schema, and precise validation rules (clamp 0.0-1.0, reject path separators/.. /symlinks). Falls short of 5 because some validation steps (post-generation retry) are described loosely rather than as copy-paste commands.	4 / 5
Workflow Clarity	The create workflow is a clearly sequenced 6-step process with checkpoints (ask, wait, proceed) and a 3-phase validation sequence with error-recovery guidance. Not capped at 3 since validation checkpoints are present; not a 5 because the validation-retry loop is implicit rather than an explicit checklist.	4 / 5
Progressive Disclosure	Single well-organized SKILL.md with clear sections; the only bundle path (references/personas/) holds runtime-generated JSON, not separate docs. Not a 5 because the inline persona schema and readability-band tables could arguably live in a reference file; not a 3 because structure and signaling are good.	4 / 5
	Total	16 / 20 Passed

Description

100%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 comprehensive, concise, and uses third-person voice throughout. It explicitly covers capabilities, natural trigger terms, and a clear use-when clause with minimal conflict risk.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('Create and manage writing personas', 'define readability targets, sentence length distribution, vocabulary tier, contraction frequency, and summary box label') with comprehensive coverage, matching the score-5 anchor.	5 / 5
Completeness	Clearly answers 'what' (create/manage personas, define style constraints, enforce voice) and 'when' with an explicit 'Use when user says ...' clause and concrete trigger phrases.	5 / 5
Trigger Term Quality	Provides a comprehensive explicit trigger list users would naturally say — 'persona', 'voice', 'tone', 'writing style', 'brand voice', 'create persona', 'use persona' — including synonyms and command variants.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (writing voice/persona management) distinct from blog-write/blog-rewrite, with specific triggers that minimize conflict with unrelated skills.	5 / 5
	Total	20 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	14 / 16 Passed

Repository: AgriciDaniel/claude-blog
Path: skills/blog-persona/SKILL.md
Commit: 2500d4c

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