CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

blog-analyze

Score one blog post (or a folder of posts) on a 5-category 100-point scale covering content quality, SEO, E-E-A-T, technical elements, and AI citation readiness. Runs the deterministic analyzer first, then adds judgment and prioritized Critical/High/Medium/Low fixes. Advisory style diagnostics never infer authorship or affect the score. Exports markdown, JSON or table; works with MDX, markdown, HTML or a URL. Use when the user asks to analyze, score, rate or check the quality of specific posts ("analyze blog", "blog score", "check blog quality", "rate this post"). For a site-wide health check (orphan pages, cannibalization, stale content, schema across all posts) use blog-audit instead.

Quality

89%

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

75%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 and well-sequenced: exact commands with safety guards, a complete flag reference, JSON schemas, and output templates, with clear analyzer-first workflow gating and batch error handling. Its main weakness is token efficiency — the per-category scoring tables, readability bands, style-phrase list, and report templates duplicate content that the body itself delegates to reference files, inflating the SKILL.md footprint.

Suggestions

Since the body already directs loading quality-scoring.md for the full checklist, keep only the category names and point maximums inline and move the per-check point tables and Readability Bands table entirely into quality-scoring.md.

Move the 18-item configured style-phrase list (and the em-dash rule) into a reference file or note that the analyzer reports them, keeping only the instruction to report occurrences as advisory diagnostics.

Trim the full markdown report template to just the required headings and field names, trusting Claude to format the details, and shorten the URL safety checklist to the key rules (scheme allowlist, private-IP block, size/timeout caps).

DimensionReasoningScore

Conciseness

Quotes: the body says "Load ${CLAUDE_SKILL_DIR}/../blog/references/quality-scoring.md for the full checklist. Score each:" and then restates the full per-category point tables (30/25/15/15/15 breakdowns plus a Readability Bands table), and inlines an 18-item configured phrase list ("1. \"It's important to note\" ... 18. Em dash code point U+2014") plus complete report templates. It is mostly efficient with no explanations of concepts Claude already knows, but the duplicated checklist content and inline phrase list could be tightened or moved to the referenced files, matching the score-3 anchor ("mostly efficient but includes some... that could be tightened"). It is not score 2 because there is no padded or tutorial-style writing, and not score 4 because the duplication with quality-scoring.md and the long inline lists are more than minor trims.

3 / 5

Actionability

Quotes: "BLOG_SCRIPT_DIR=\"${CLAUDE_BLOG_SCRIPTS_DIR:-${CLAUDE_SKILL_DIR}/../../scripts}\"; case \"$BLOG_SCRIPT_DIR\" in /*) ;; *) echo \"ERROR: script dir must be absolute\" >&2; exit 1 ;; esac; python3 \"$BLOG_SCRIPT_DIR/analyze_blog.py\" \"<file>\" --format json", a complete argparse flag table ("--batch", "--sort score|name|words", "--format json|markdown|table", "--category", "--fix", "--output PATH"), and "run python3 \"$BLOG_SCRIPT_DIR/cognitive_load.py\" <file> --format json". The guidance is copy-paste ready with concrete commands, exact flags, JSON schemas, and full output templates covering the common cases, matching the score-5 anchor; there are no pseudocode gaps that would lower it to score 4.

5 / 5

Workflow Clarity

Quotes: "Always run the deterministic analyzer before forming any judgment", "Fetch with WebFetch only after URL safety checks: allow http and https only... resolve DNS and block loopback/private/link-local/reserved IPs", "Per-file errors appear as an error field on that file's entry and do not abort the batch", and "If your judgment moves a category score, say which sub-score you changed and why; never silently replace the analyzer's total". The Step 0 through Step 5 sequence is clear with most checkpoints present (analyzer-first gate, URL safety validation, absolute-path check, batch error isolation, judgment transparency), matching the score-4 anchor. It is not score 5 because there is no explicit validate-and-retry feedback loop, and not score 3 because validation checkpoints are explicit rather than missing or implicit — the read-only analysis nature means the destructive-operation cap does not apply.

4 / 5

Progressive Disclosure

Quotes: a reference list with one-line descriptions ("${CLAUDE_SKILL_DIR}/../blog/references/quality-scoring.md: full scoring checklist", ".../eeat-signals.md: E-E-A-T evaluation criteria", ".../editorial-heuristics.md: ordinal 0-4 rubric, P0-P3 severity", ".../cognitive-load.md: per-section concept density") all one level deep, plus clearly headed sections (Input Handling, Step 0, Scoring Process, Export Formats, Batch Mode). This matches the score-4 anchor (good structure, references mostly clear, minor organization gaps). It is not score 5 because substantial detail is inlined that duplicates the referenced files (per-category scoring tables, the 18-phrase list), and the references live in a sibling skill's directory (${CLAUDE_SKILL_DIR}/../blog/) rather than this skill's own bundle, creating coupling; it is not score 3 because the references are clearly signaled and well organized, not buried or disorganized.

4 / 5

Total

16

/

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 exemplary: it states concrete capabilities in third person, gives explicit quoted trigger phrases covering natural synonyms, answers both what and when, and includes boundary guidance that separates it from the sibling blog-audit skill. No changes are needed.

DimensionReasoningScore

Specificity

Quotes: "Score one blog post (or a folder of posts) on a 5-category 100-point scale covering content quality, SEO, E-E-A-T, technical elements, and AI citation readiness", "Runs the deterministic analyzer first, then adds judgment and prioritized Critical/High/Medium/Low fixes", "Exports markdown, JSON or table; works with MDX, markdown, HTML or a URL". This lists multiple concrete actions with comprehensive coverage of inputs, process, outputs, and fix prioritization, matching the score-5 anchor; it exceeds score 4 because there are no meaningful capability gaps, and it is nowhere near the vague "names the domain but actions are minimal" level of score 2. Third person voice ("Score", "Runs", "Exports") is used throughout, so no voice penalty applies.

5 / 5

Completeness

Quotes: "Score one blog post... on a 5-category 100-point scale... Runs the deterministic analyzer first, then adds judgment and prioritized... fixes" (clear what) and "Use when the user asks to analyze, score, rate or check the quality of specific posts" (explicit when with concrete trigger phrases). Both what and when are explicitly and concretely answered, matching the score-5 anchor; it is not score 4 because the when-clause is fully explicit rather than improvable, and not score 3 because nothing is missing or merely implied.

5 / 5

Trigger Term Quality

Quotes: "Use when the user asks to analyze, score, rate or check the quality of specific posts (\"analyze blog\", \"blog score\", \"check blog quality\", \"rate this post\")" plus file formats "MDX, markdown, HTML". This provides comprehensive natural-term coverage including synonyms (analyze/score/rate/check) and explicit quoted phrases users would actually say, matching the score-5 anchor; score 4 would apply only if a few natural terms were missing, but the quoted trigger list covers the common phrasings.

5 / 5

Distinctiveness Conflict Risk

Quotes: "Score one blog post (or a folder of posts)..." and "For a site-wide health check (orphan pages, cannibalization, stale content, schema across all posts) use blog-audit instead". The skill occupies a clear niche (per-post quality scoring) with distinct trigger phrases and explicitly disambiguates against its closest sibling skill, matching the score-5 anchor; the boundary guidance rules out the overlap risk that would justify score 4.

5 / 5

Total

20

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

AgriciDaniel/claude-blog

Path

skills/blog-analyze/SKILL.md

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.