jedipadawan/tessl-article-reviewer
Review and structure blog articles for the Tessl blog (tessl.io/blog). Use this skill whenever someone asks to review, edit, improve, structure, or give feedback on an article or blog draft. Also use when someone wants to write a new article from scratch, needs help with an article outline, or asks about SEO optimization for Tessl content. Triggers include any mention of blog posts, articles, content review, editorial feedback, SEO for articles, or writing guidance for Tessl or AI Native Dev content.
86
86%
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 strong skill description with excellent trigger term coverage and completeness. It clearly defines both what the skill does and when to use it, with explicit trigger guidance. The main weakness is that the specific capabilities listed are somewhat generic editorial actions rather than highly concrete operations.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (blog articles for Tessl) and lists actions like 'review, edit, improve, structure, give feedback, write, outline, SEO optimization' but these are somewhat generic editorial actions rather than highly specific concrete capabilities. | 2 / 3 |
Completeness | Clearly answers both what ('Review and structure blog articles for the Tessl blog') and when ('Use this skill whenever someone asks to review, edit, improve...' plus explicit 'Triggers include' clause). Has explicit trigger guidance throughout. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'review', 'edit', 'improve', 'structure', 'feedback', 'article', 'blog draft', 'outline', 'SEO optimization', 'blog posts', 'content review', 'editorial feedback', 'writing guidance'. Includes both formal and casual variations. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive by scoping to 'Tessl blog (tessl.io/blog)' and 'AI Native Dev content'. The specific brand/site focus creates a clear niche that wouldn't conflict with generic writing or other company blog 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 well-structured, highly actionable skill for blog content review with clear article type templates, specific keyword clusters, and a comprehensive review checklist. The main weaknesses are its length (could benefit from splitting into multiple files) and some verbosity in explanatory sections that assume less of Claude's baseline competence than necessary.
Suggestions
Split keyword clusters into a separate KEYWORDS.md reference file to reduce main skill length
Move article type templates to an ARTICLE_TYPES.md file, keeping only a summary table in the main skill
Trim explanatory preambles (e.g., 'Every piece of content should serve a clear purpose...') that state obvious editorial principles
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some redundant explanations and could be tightened. Sections like 'What to avoid' and 'What to embrace' overlap conceptually, and some guidance (e.g., explaining what SEO is) assumes less competence than necessary for Claude. | 2 / 3 |
Actionability | Highly actionable with concrete examples, specific keyword clusters, detailed checklists, and clear templates for each article type. The review checklist provides numbered, specific criteria that Claude can directly apply. | 3 / 3 |
Workflow Clarity | Clear sequential workflow with the 10-point review checklist providing explicit validation steps. The instruction to 'identify the type before writing or reviewing' and 'select keywords before writing' establishes clear checkpoints. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear H2 sections and a quick reference table, but the entire skill is monolithic at ~2000 words. The keyword clusters, article type templates, and tone guidelines could be split into separate reference files for better navigation. | 2 / 3 |
Total | 10 / 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