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 'what' portion could be more specific about concrete capabilities (e.g., formatting conventions, code snippet handling, specific post types). The strong explicit trigger clause and domain-specific anchoring to freek.dev make it highly functional for skill selection.
Suggestions
Add more specific concrete actions beyond 'write, draft, or outline' — e.g., 'Applies freek.dev formatting conventions, includes code examples, structures posts with intro/explanation/conclusion sections.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description mentions writing, drafting, and outlining blog posts and references capturing writing style, tone, and structure conventions, but it doesn't list multiple concrete actions beyond those general writing tasks. It names the domain (freek.dev blog posts) and some actions but isn't comprehensive about specific capabilities. | 2 / 3 |
Completeness | Clearly answers both 'what' (write/draft/outline blog posts for freek.dev, capturing writing style, tone, and structure conventions) and 'when' (explicit 'Use when' clause with specific trigger phrases). Both components are well-articulated. | 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 domain anchor of 'freek.dev' — this is unlikely to conflict with generic writing or blogging skills. The trigger terms are scoped to a specific blog, making it clearly distinguishable. | 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, well-crafted skill that provides clear, actionable guidance for mimicking a specific author's writing style. Its greatest strengths are the concrete 'Hard Rules' with explicit prohibitions and the real examples drawn from actual freek.dev posts. The main weakness is moderate verbosity — some sections (Post Types, Common Phrases) could be tightened or extracted, and a few explanatory sentences tell Claude things it could infer from the examples alone.
Suggestions
Consider extracting the 'Post Types' section into a separate reference file and linking to it, keeping SKILL.md focused on voice rules and structure essentials.
Tighten the 'Voice and Tone' section by removing sentences that restate what the Hard Rules already cover (e.g., the calm/confident note overlaps with the no-exclamation-marks rule).
| 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 use what's provided), then write following the structure (opening → body sections → closing). The 'Before Writing' section establishes a clear pre-writing checkpoint. For a content generation skill, this is an appropriate level of workflow definition with no destructive operations requiring validation loops. | 3 / 3 |
Progressive Disclosure | The content is entirely contained in one file with no references to external resources. While the skill is under the threshold where this matters less, the Post Types section and Common Phrases section could potentially be split out to keep the main skill leaner. The organization within the file is good with clear h2 sections, but it's a moderately long monolithic document. | 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
2c6f6e8
- 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.