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
Quality
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 well-crafted skill description with excellent trigger term coverage and clear 'when to use' guidance. The main weakness is that the 'what' portion could be more specific about concrete actions (drafting, outlining, formatting) rather than just mentioning style/tone/structure conventions abstractly.
Suggestions
Add specific concrete actions like 'draft introductions, structure sections, format code examples, write conclusions' to improve specificity
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (blog posts for freek.dev) and mentions 'writing style, tone, and structure conventions' but doesn't list specific concrete actions like 'draft introductions, format code examples, structure sections.' | 2 / 3 |
Completeness | Clearly answers both what ('captures the writing style, tone, and structure conventions of freek.dev original posts') and when ('when the user wants to write, draft, or outline a blog post' plus explicit trigger terms). | 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 exactly what users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche - freek.dev blog posts specifically. The explicit site name and blog-specific triggers make it unlikely to conflict with general writing skills or other blog platforms. | 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, actionable skill that clearly captures a specific writing voice with concrete rules and examples. The hard rules are unambiguous and the example phrases provide excellent guidance. The main weakness is length—the detailed post type breakdowns and common phrases could be split into reference files to improve token efficiency.
Suggestions
Consider moving the 'Post Types' section to a separate EXAMPLES.md file and referencing it, reducing the main skill's token footprint
Tighten the 'Voice and Tone' section by removing redundant guidance (e.g., 'Simple words over complex ones' and 'Short sentences' convey similar ideas)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some redundancy. The 'Common Phrases and Patterns' section and detailed post type breakdowns add value, but some explanations could be tighter (e.g., the voice/tone section repeats concepts). | 2 / 3 |
Actionability | Highly actionable with concrete examples throughout. The 'Hard Rules' are specific and enforceable, opening patterns show exact phrases to use, and the 'Before Writing' checklist provides clear steps. Examples are copy-paste ready. | 3 / 3 |
Workflow Clarity | Clear workflow: gather requirements via specific questions, then write following the structure. Post types provide distinct workflows for different scenarios. The 'Before Writing' section creates an explicit checkpoint before proceeding. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear h2 sections, but this is a long monolithic file (~150 lines) that could benefit from splitting detailed post type templates into separate files. All content is inline rather than referenced. | 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 | |
355d067
Table of Contents
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.