CtrlK
BlogDocsLog inGet started
Tessl Logo

write-freek-dev-blogpost

When the user wants to write, draft, or outline a blog post for freek.dev. Also use when the user mentions 'blog post,' 'write a post,' 'freek.dev post,' 'draft a post,' or 'blogpost.' This skill captures the writing style, tone, and structure conventions of freek.dev original posts.

75

Quality

93%

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

92%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-structured instruction-only skill with concrete, actionable rules and a clear workflow. The only marginal improvement is trimming a few redundant illustrative examples to tighten conciseness.

Suggestions

Trim a few redundant illustrative examples (e.g., the 'I think maybe' hedging list) since the governing rules already convey the intent, to lift conciseness from 4 to 5.

Consider consolidating the 'Common Phrases and Patterns' list into prose or numbered form to match the skill's own anti-bullet-list guidance and save tokens.

DimensionReasoningScore

Conciseness

Mostly lean and efficient, assuming Claude's competence without explaining basic concepts, but a few illustrative examples (e.g., the 'I think maybe' anti-patterns) are slightly redundant with their governing rules.

4 / 5

Actionability

Highly concrete and executable guidance: exact prohibited phrases, heading-level limits, specific opening/closing sentence patterns, and a precise markdown output spec with language identifiers.

5 / 5

Workflow Clarity

Clear sequenced workflow from 'Before Writing' (ask the user) through drafting to 'Output Format', with an explicit checkpoint ('If the user has already provided this information, proceed directly to writing').

5 / 5

Progressive Disclosure

Single-purpose skill with no external references needed and well-organized h2 sections that make navigation easy; absence of bundle files is appropriate here.

5 / 5

Total

19

/

20

Passed

Description

95%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, third-person description that clearly states the skill's purpose and provides comprehensive natural trigger phrases. Minor specificity gains could come from mentioning editing or revising existing posts.

DimensionReasoningScore

Specificity

Lists several concrete actions ('write, draft, or outline a blog post for freek.dev') plus style/tone/structure conventions, with only minor coverage gaps such as editing existing posts.

4 / 5

Completeness

Explicitly answers both what (captures writing style, tone, and structure conventions) and when (explicit 'Use when...' clause with concrete trigger phrases).

5 / 5

Trigger Term Quality

Comprehensive natural trigger phrases including synonyms ('blog post,' 'write a post,' 'freek.dev post,' 'draft a post,' 'blogpost') that users would naturally say.

5 / 5

Distinctiveness Conflict Risk

Scoped to a clear niche (freek.dev posts) with distinct, named triggers, yielding minimal conflict risk with other writing skills.

5 / 5

Total

19

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 missing

Warning

Total

15

/

16

Passed

Repository
freekmurze/dotfiles
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.