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 advisory editorial style diagnostics (sentence-length variation, configured phrase lists, vocabulary sampling) that never infer authorship or affect scoring. 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".

68

Quality

86%

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

68%Weight 40%Scale 1-5

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

The body is highly actionable with concrete checklists and output templates and is well-structured, but it repeats editorial caveats and, as a batch/destructive-oriented skill, lacks explicit validation checkpoints in its workflow. Progressive disclosure is strong structurally though referenced bundle files are absent.

Suggestions

Consolidate the repeated 'not a ranking factor / editorial use only / no authorship inference' caveats into one clearly labeled note instead of restating them in the intro, Step 3, and JSON schema.

Add explicit validation checkpoints to the workflow — e.g., verify extracted statistics trace to sources before scoring E-E-A-T source fidelity, and require a confirmation/preview step before the auto-applying rewrite command in batch mode.

Either include the referenced references/*.md and scripts/cognitive_load.py bundle files so navigation targets resolve, or mark them as optional/external so the dangling paths don't read as broken references.

DimensionReasoningScore

Conciseness

Content is mostly efficient with table-driven scoring rules, but repeats the same 'not a Google ranking factor / editorial use only / does not infer authorship' caveats across the intro, Step 3, and the JSON schema, and includes some E-E-A-T prose that could be tightened.

3 / 5

Actionability

Provides concrete per-category checklists with points and pass criteria, exact flags, an explicit cognitive_load command, and copy-paste-ready markdown/JSON/table output templates covering the common cases.

5 / 5

Workflow Clarity

The 5-step sequence is clearly numbered, but this is a batch/destructive skill (--batch audits all files; the rewrite command auto-applies changes) with no explicit validation or verification checkpoints, which caps workflow clarity at 3.

3 / 5

Progressive Disclosure

Good section structure with five one-level-deep reference paths listed up front and scoring detail appropriately referenced out, but the referenced references/ and scripts/ paths do not resolve against the actual (empty) bundle, leaving minor navigation gaps.

4 / 5

Total

15

/

20

Passed

Description

100%Weight 40%Scale 1-5

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 comprehensive, third-person, and explicitly provides both capabilities and concrete trigger phrases, with honest scoping of advisory limitations. It is a strong, low-conflict description that matches the top anchors on every dimension.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — auditing/scoring across five named categories, advisory style diagnostics, three export formats, batch analysis with sorting, and prioritized recommendations — giving comprehensive coverage beyond the several-actions anchor.

5 / 5

Completeness

Explicitly answers both what (5-category 100-point scoring with diagnostics, exports, batch, recommendations) and when (concrete trigger phrases), matching the explicit-both-with-triggers anchor exactly.

5 / 5

Trigger Term Quality

Provides a 'Use when user says' clause with eight natural quoted phrases ("analyze blog", "audit blog", "blog score", "blog review", "rate this blog", "blog health check") covering synonyms a user would actually say.

5 / 5

Distinctiveness Conflict Risk

Targets a clear blog-audit niche with blog-specific triggers, making overlap with other skills minimal.

5 / 5

Total

20

/

20

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.

Validation — 14 / 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.