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.
68
83%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
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 solid skill description with excellent trigger term coverage and a clear 'Use when' clause that makes it easy for Claude to select. Its main weakness is that the 'what' portion is somewhat general — it mentions writing style and conventions but doesn't enumerate specific concrete actions or structural elements unique to freek.dev posts. The strong domain specificity (freek.dev) compensates for the moderate specificity of capabilities.
Suggestions
Add more specific concrete actions, e.g., 'Structures posts with code examples, package announcements, and tutorial walkthroughs following freek.dev conventions' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description mentions writing, drafting, and outlining blog posts and references style/tone/structure conventions, but doesn't list specific concrete actions beyond those general writing tasks (e.g., no mention of formatting, code examples, SEO, categories, etc.). | 2 / 3 |
Completeness | Clearly answers both 'what' (write/draft/outline blog posts for freek.dev capturing its writing style and conventions) and 'when' (explicit 'Use when' clause with specific trigger phrases). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms: 'blog post,' 'write a post,' 'freek.dev post,' 'draft a post,' 'blogpost.' These are terms users would naturally say when requesting this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific domain anchor 'freek.dev' — this is unlikely to conflict with generic writing or blogging skills. The trigger terms are narrowly scoped to this particular blog. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%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, highly actionable writing style guide that gives Claude everything needed to convincingly mimic Freek Van der Herten's blog voice. The hard rules are crisp and unambiguous, and the real-world example phrases add significant value. The main weakness is moderate verbosity — some sections could be tightened, and the post type templates are somewhat repetitive in structure, though the content itself is useful and well-organized.
Suggestions
Consider extracting the 'Post Types' section into a separate reference file to reduce the main skill's token footprint while preserving the detailed templates.
Trim explanatory sentences that Claude doesn't need (e.g., 'Use contractions naturally: "don't" instead of "do not"' — Claude knows what contractions are; just say 'Use contractions naturally').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is well-written but somewhat verbose for its purpose. Sections like 'Common Phrases and Patterns' and 'Post Types' are useful but could be tightened. Some instructions (e.g., explaining what contractions are) assume less intelligence than necessary. The 'Hard Rules' section is admirably concise, but the body sections and closing guidance repeat patterns that could be consolidated. | 2 / 3 |
Actionability | The skill provides highly concrete, actionable guidance: specific phrases to use, exact formatting rules (no bold, no h3+, no dashes), real example opening lines pulled from actual posts, clear structural templates for each post type, and a pre-writing checklist. Claude can immediately produce a conforming blog post from this. | 3 / 3 |
Workflow Clarity | The workflow is clear and well-sequenced: gather information from user (Before Writing section), determine post type, follow the corresponding structure template, apply hard rules and voice guidelines, produce output in specified format. For a writing/drafting skill this is appropriately structured without needing validation checkpoints since the operation is non-destructive. | 3 / 3 |
Progressive Disclosure | The content is a single monolithic file at ~150+ lines. The post type templates and common phrases could reasonably be split into referenced files for better organization. However, for a writing style guide without bundle files, keeping everything inline is defensible. The internal organization with clear h2 sections is good but the overall length pushes toward needing better structure. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- freekmurze/dotfiles
- Commit
3974caa
- 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.