CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

blog-style

Measure writing-style statistics (sentence length, vocabulary, transitions, phrasing) from 5 to 10 posts you or your client wrote, and produce a voice profile for VOICE.md, blog-persona, and blog-write. Use for "learn my style", "build a writing baseline". It describes style; it does not detect or attribute authorship, and it is not for scoring a post (blog-analyze) or writing brand rules (blog-brand).

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

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.

A well-built instruction skill: executable commands with a path guard, an explicit confirm-before-overwrite checkpoint for the one destructive operation, enumerated profile fields, and honest limits around small samples, consent, and untrusted sample data. The consistent gaps are minor: no concrete example invocation, no post-generation validation step, and reference navigation that requires parsing a dense path-substitution paragraph.

Suggestions

Add one concrete example invocation with realistic arguments (e.g., `python3 "$BLOG_SCRIPT_DIR/style_learn.py" posts/*.md --format markdown`) and name the actual flag behind the "requested minimum sample count" so the commands are fully copy-paste ready.

Convert the prose reference to `orchestration-details.md` into a standard markdown link and simplify or move the host path-substitution rules so the reference is reachable without parsing the dense opening paragraph; verify the referenced file actually ships with the skill bundle.

Add a light validation step after profile generation (e.g., sanity-check that sentence-length mean and type-token ratio are plausible before writing VOICE.md) to close the workflow's only remaining feedback-loop gap.

DimensionReasoningScore

Conciseness

The body is efficient: it never explains concepts Claude already knows, and the limits section (small-sample instability, consent, untrusted sample data) earns every token. It sits at anchor 4 rather than 5 because of minor trims available — e.g., "The profile captures measurable style signals so future drafts can preserve the author's cadence, vocabulary, and tone" largely restates the opening — but it is clearly above anchor 3, which requires unnecessary explanation or padding.

4 / 5

Actionability

It provides real, executable bash commands with a path-resolution guard (the `case "$BLOG_SCRIPT_DIR"` absolute-path check), three concrete invocations for markdown/json/VOICE.md output, enumerated profile fields, and per-failure error handling — squarely anchor 4. It misses anchor 5 because `<paths>` is never shown in a concrete example invocation and the "requested minimum sample count" is never tied to an actual flag; it is above anchor 3 because the commands are executable, not pseudocode.

4 / 5

Workflow Clarity

The sequence (gather 5–10 samples → run the learner → choose output format → drop into VOICE.md or feed blog-persona) is clear, and the one destructive operation has an explicit checkpoint: "if VOICE.md already exists, write to voice-profile.md first, show the user a diff, and overwrite only after they confirm", with an Error Handling section covering the batch's failure modes (skip + warn). It is anchor 4 rather than 5 because there is no post-generation validation step (e.g., sanity-check the profile before consuming it) and the sequence is not explicitly numbered; it is above anchor 3 because checkpoints for the destructive overwrite and batch failures are present, not missing.

4 / 5

Progressive Disclosure

Sections are well-organized and appropriately sized for a SKILL.md overview, and references are one level deep and clearly signaled ("Read the main reference `orchestration-details.md` before loading project context"). It reaches only anchor 4, not 5, because the bundle ships no references/ or scripts/ directories — the referenced files resolve only through the convoluted sibling-directory substitution paragraph ("${CLAUDE_SKILL_DIR}/../blog/references"), and references are named in prose rather than linked, making navigation harder than the anchor-5 clear-link pattern.

4 / 5

Total

16

/

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 description that answers what and when with concrete quoted trigger phrases and explicitly fences off neighboring skills (blog-analyze, blog-brand, authorship detection). Its main deductions are the second-person phrasing ("posts you or your client wrote"), which the rubric penalizes on specificity, and missing natural synonyms like "voice" or "tone" in the triggers.

Suggestions

Rewrite "from 5 to 10 posts you or your client wrote" in third person (e.g., "from 5 to 10 of the user's or their client's posts") to satisfy the third-person voice rule and recover the specificity penalty.

Add one or two natural trigger synonyms such as "learn my voice" or "writing baseline from my posts" so trigger coverage reaches users who say "voice" or "tone" instead of "style".

DimensionReasoningScore

Specificity

The description names the domain and two concrete, well-detailed actions ("Measure writing-style statistics (sentence length, vocabulary, transitions, phrasing)" and "produce a voice profile for VOICE.md, blog-persona, and blog-write"), which is anchor-4 territory. However, the phrase "from 5 to 10 posts you or your client wrote" uses second person, which the rubric guideline penalizes by reducing the specificity score by 1, bringing it to 3.

3 / 5

Completeness

It clearly answers "what" (measure writing-style statistics and produce a voice profile, with outputs named) and "when" with concrete quoted trigger phrases ('Use for "learn my style", "build a writing baseline"'), matching the anchor-5 pattern of explicit what-and-when with concrete triggers. It even adds explicit scope exclusions, so it does not fit anchor 4's 'when could be more explicit'.

5 / 5

Trigger Term Quality

It includes explicit natural trigger phrases users would say — 'Use for "learn my style", "build a writing baseline"' — plus terms like "writing-style", "voice profile", and "posts". It falls short of anchor 5 because common synonyms such as "voice", "tone", "my writing", or file formats (.md/.mdx) are missing, but it is well above the generic-keyword level of anchor 3.

4 / 5

Distinctiveness Conflict Risk

It carves out a clear niche (style learning for a writing baseline) and explicitly disambiguates from adjacent skills — "it does not detect or attribute authorship, and it is not for scoring a post (blog-analyze) or writing brand rules (blog-brand)" — giving minimal conflict risk, which matches anchor 5 rather than anchor 4's 'minor overlap risk'.

5 / 5

Total

17

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

AgriciDaniel/claude-blog

Path

skills/blog-style/SKILL.md

Reviewed

Table of Contents

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.