bapfernandez/article-creator
Content creator for tessl.io — generates publish-ready blog articles with SEO metadata, Tessl house style, and technical authority.
90
79%
Does it follow best practices?
Impact
92%
1.26xAverage score across 10 eval scenarios
Passed
No known issues
Quality
Discovery
100%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 strong skill description that clearly defines its scope (Tessl blog content), lists concrete actions and content types, and provides explicit trigger guidance via a 'Use whenever...' clause. The brand-specific focus and enumeration of content categories make it highly distinctive and unlikely to conflict with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Drafts, edits, or produces publish-ready blog articles' and enumerates content types including 'thought leadership, skill showcases, tutorials, news/analysis, or comparisons.' Also mentions specific outputs like 'SEO metadata' and 'house style rules.' | 3 / 3 |
Completeness | Clearly answers both 'what' (drafts, edits, produces publish-ready blog articles of various types) and 'when' with an explicit 'Use whenever...' clause listing specific trigger scenarios like asking for a tessl.io article, blog post draft, or content review. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'tessl.io article', 'blog post draft', 'content for the Tessl blog', 'write/review content', 'editorial standards', 'SEO metadata', and 'house style rules.' Good coverage of variations a user might naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific brand scope (tessl.io), the enumerated content types, and the mention of Tessl's editorial standards and house style rules. Unlikely to conflict with generic writing or blogging skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
39%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is comprehensive and well-structured in terms of workflow and article type coverage, but it is far too verbose for a SKILL.md file. It explains many concepts Claude already understands (SEO basics, blog structure, what meta descriptions are) and inlines extensive reference material that should be split into separate files. The voice reference section, while containing useful example patterns, could be condensed significantly.
Suggestions
Split article type templates, SEO guidelines, and voice reference into separate bundle files (e.g., ARTICLE_TYPES.md, SEO.md, VOICE.md) and reference them from a concise SKILL.md overview.
Remove explanations of concepts Claude already knows (what H2s are, what URL slugs are, what meta descriptions are) and replace with just the specific constraints (e.g., '130-155 chars, include primary keyword').
Add one complete worked example showing a full article output (metadata block + first few paragraphs) so Claude can see the exact expected format rather than inferring it from templates.
Condense the voice reference section to a compact list of do/don't patterns with one example each, rather than the current extended explanations with multiple example patterns.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | At ~2,500+ words, this skill is extremely verbose. It explains concepts Claude already knows (what a hook is, what SEO metadata is, how to write a meta description), provides extensive voice/tone coaching that could be condensed to a few bullet points, and includes full article type templates that repeat similar structural patterns. Much of this content (e.g., explaining what H2s are, what internal links are, what a URL slug is) is unnecessary for Claude. | 1 / 3 |
Actionability | The skill provides concrete structural templates for each article type, a clear output format, and a self-check checklist, which are actionable. However, it lacks executable examples of actual output (no sample article excerpt, no complete metadata block example filled in), and the voice reference section is more descriptive than instructive, showing patterns but not demonstrating a complete worked example. | 2 / 3 |
Workflow Clarity | The 6-step process at the end is clearly sequenced, and the self-check checklist serves as an explicit validation step before output. The workflow is straightforward (identify type → select keyword → build structure → write → generate metadata → self-check), and the checklist provides a concrete feedback loop for quality assurance. | 3 / 3 |
Progressive Disclosure | This is a monolithic wall of text with no bundle files or external references. The five article type templates, the full SEO guide, the voice reference section, and the house style rules are all inline, making this extremely long. The article type templates alone could be separate reference files, with the main SKILL.md providing a concise overview and routing to the appropriate template. | 1 / 3 |
Total | 7 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
Reviewed
Table of Contents