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.
86
83%
Does it follow best practices?
Impact
Pending
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 terms and completeness. Its main weakness is that the specificity of capabilities is somewhat general—it mentions writing, drafting, and outlining but doesn't detail what concrete stylistic or structural conventions it applies. The strong 'Use when' clause and site-specific focus make it highly functional for skill selection.
Suggestions
Add 2-3 specific concrete actions beyond 'write, draft, outline,' such as 'applies casual technical tone, structures posts with code examples, follows freek.dev heading conventions' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (blog posts for freek.dev) and mentions some actions ('write, draft, or outline a blog post'), but doesn't list specific concrete capabilities like formatting conventions, code snippet handling, SEO optimization, or other tangible actions beyond general writing. | 2 / 3 |
Completeness | Clearly answers both 'what' (write/draft/outline blog posts for freek.dev capturing its writing style, tone, and structure 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, including common variations. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific site 'freek.dev' and the explicit mention of its unique writing style and conventions. Unlikely to conflict with generic writing or blogging skills. | 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 writing style skill with excellent actionability — the hard rules are specific and unambiguous, the voice guidance includes concrete examples from real posts, and the post type templates provide clear structural patterns. The main weakness is moderate verbosity; some sections could be condensed without losing clarity, and the document could benefit from slightly tighter organization. Overall, it would effectively guide Claude to produce authentic freek.dev blog posts.
Suggestions
Condense the 'Post Types' section into a more compact format — the numbered steps repeat patterns already covered in 'Post Structure' and could be reduced to brief differentiators per type.
Consider moving 'Common Phrases and Patterns' into a compact inline list or separate reference file to reduce the main skill's token footprint.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly well-written but includes some sections that could be tightened. The 'Common Phrases and Patterns' section is useful, but the 'Post Types' section is somewhat verbose with patterns Claude could infer from the voice/tone guidance. The 'Before Writing' section adds value but the overall document could be ~30% shorter. | 2 / 3 |
Actionability | The skill provides highly concrete, actionable guidance: specific formatting rules (no bold, no dashes, no h3+), exact example phrases to use, clear structural patterns with real examples from freek.dev posts, and explicit output format requirements. Claude knows exactly what to do and what not to do. | 3 / 3 |
Workflow Clarity | The workflow is clear: gather information from user (or proceed if already provided), follow the structure conventions (opening → body sections → closing), apply hard rules throughout, and output in the specified format. For a writing/drafting skill, this is a well-sequenced single-task workflow with unambiguous steps. | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear h2 sections and logical grouping, but it's a fairly long monolithic document (~150+ lines). The post type templates and common phrases could potentially be split into reference files. However, for a writing style guide, keeping everything in one file is defensible since all sections are frequently needed. | 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
05d40bb
- 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.