CtrlK
BlogDocsLog inGet started
Tessl Logo

blog-analyze

Audit and score blog posts on a 5-category 100-point scoring system covering content quality, SEO optimization, E-E-A-T signals, technical elements, and AI citation readiness. Includes AI content detection (burstiness, phrase flagging, vocabulary diversity). Supports export formats (markdown, JSON, table) and batch analysis with sorting. Generates prioritized recommendations (Critical/High/Medium/Low) with specific fixes. Works with any format (MDX, markdown, HTML, URL). Use when user says "analyze blog", "audit blog", "blog score", "check blog quality", "blog review", "rate this blog", "blog health check".

71

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-organized and actionable with a clear scoring workflow, but it is somewhat verbose due to repeated caveats and monolithic inline rubric content, and its reference targets cannot be verified in the bundle.

Suggestions

State the 'editorial diagnostics do not infer authorship or affect the score' rule once and remove its repetition across the prose, the JSON ai_detection fields, and the report template.

Move the full per-category scoring tables into the referenced quality-scoring.md, keeping only category weights and one-line summaries inline so SKILL.md reads as an overview rather than a monolithic rubric.

Ensure referenced files exist in the bundle — ./references, ./scripts, and ./assets are currently absent, so links like `skills/blog/references/quality-scoring.md` and `python3 scripts/cognitive_load.py` cannot be resolved.

DimensionReasoningScore

Conciseness

Mostly efficient with concrete scoring tables and templates, but the 'diagnostics never infer authorship or affect scoring' caveat is restated in prose, the JSON output fields, and the report template, adding repetition Claude does not need.

2 / 3

Actionability

Provides executable per-category scoring tables with pass criteria, concrete commands (e.g. `python3 scripts/cognitive_load.py <file> --format json`), and copy-ready markdown/JSON/table output templates.

3 / 3

Workflow Clarity

The analysis process is clearly sequenced Step 1 (Extraction) through Step 5 (Report) with named stages and an ordinal rating table; the skill is read-only analysis so no destructive-validation checkpoint is required.

3 / 3

Progressive Disclosure

References one level deep and clearly signaled, but the full per-category scoring checklist is inlined in the body while also pointing to quality-scoring.md, and the referenced files (skills/blog/references/*.md, scripts/cognitive_load.py) are absent from the bundle.

2 / 3

Total

10

/

12

Passed

Description

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.

The description is specific, uses natural trigger terms, explicitly covers both what and when, and is clearly distinguishable. It is somewhat long, but the description rubric has no conciseness dimension and nothing is vague or padded with fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Audit and score blog posts on a 5-category 100-point scoring system', 'advisory editorial style diagnostics', 'export formats (markdown, JSON, table)', 'batch analysis with sorting', 'prioritized recommendations (Critical/High/Medium/Low)'.

3 / 3

Completeness

Clearly answers both what (detailed capabilities) and when, with an explicit 'Use when user says ...' clause listing concrete triggers.

3 / 3

Trigger Term Quality

Provides natural trigger phrases a user would actually say: "analyze blog", "audit blog", "blog score", "check blog quality", "blog review", "rate this blog", "blog health check".

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (blog quality audit/scoring) with distinctive blog-specific triggers, making overlap with other skills unlikely.

3 / 3

Total

12

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

14

/

16

Passed

Repository
AgriciDaniel/claude-blog
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.