CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

blog-audit

Full-site blog health assessment scanning all blog files for quality scores, orphan pages, topic cannibalization, stale content, and AI citation readiness. Runs canonical batch analysis before site-wide checks. Produces per-post scores and a prioritized action queue. Use when the user asks for a site-wide blog health check across many posts ("blog audit", "blog health", "audit all posts", "site audit of the blog"). For one post, or a quality score with fixes for a few named files, use blog-analyze 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.

A well-structured, largely executable orchestration skill: clear seven-step sequence, concrete analyzer command with path validation, and disciplined deferral of detail to referenced files. It stops short of top marks due to a description-repeating intro, fully inlined report templates, and no explicit validate-retry loop around the batch analysis.

Suggestions

Delete or compress the intro paragraph that restates the frontmatter description ('Performs a comprehensive blog health assessment... prioritized action queue.') — the description already covers it.

Move the six full report table templates to a reference file (e.g., a report-templates reference) and keep only the dashboard and one example table inline, trimming the body's token footprint.

Add an explicit validation checkpoint after Step 2: verify the analyzer JSON parses, that 'count' matches the files found in Step 1, and that parse failures ('error' fields) are collected and surfaced in the report before proceeding to site-wide checks — giving the batch workflow a feedback loop.

DimensionReasoningScore

Conciseness

The body is dense and operational (glob lists, the validated analyzer command, exact JSON shape, report schemas) with almost no explanation of concepts Claude already knows, but it is not fully lean: the opening paragraph 'Performs a comprehensive blog health assessment across all posts. Scans for quality scores, orphan pages...' repeats the frontmatter description nearly verbatim, and the six fully spec'd report tables could be tightened. This matches 'efficient; minor instances of over-explanation that could be trimmed' rather than the every-token-earns-its-place anchor.

4 / 5

Actionability

The core invocation is copy-paste ready with an absolute-path guard ('python3 "$BLOG_SCRIPT_DIR/analyze_blog.py" <blog-root> --batch --format json'), and steps name specific fields, paths, and data structures ('Build an adjacency map: { page -> [pages it links to] }'). Minor gaps remain: sitemap/robots/canonical checks list what to verify without commands, and several steps defer to sibling tools ('Use `blog-google` when available', 'run `/blog cannibalization`'), so guidance is mostly executable rather than fully so.

4 / 5

Workflow Clarity

Steps 1–7 are clearly sequenced with numbered sub-procedures, and some checkpoints exist: the case-statement guard exits on a non-absolute script dir, failed parses carry an 'error' field, 'If no blog files are found... ask for an allow-listed root', 'Report skipped optional checks with reasons', and 'Do not overwrite a previous audit report'. Because this batch workflow does include validation/verification, the batch-operation cap at 3 does not apply; the gap to 5 is the missing explicit validate-and-retry loop on the analyzer output (e.g., verifying count against files found before aggregating).

4 / 5

Progressive Disclosure

References are one level deep, clearly signaled, and each states its purpose ('Read the main reference `orchestration-details.md` before loading project context', "Bucket edges come from the 'Thresholds' table in .../quality-scoring.md", the Untrusted-Data Contract in ../blog/SKILL.md), and detail is appropriately deferred (thresholds, orchestration, canonical-cluster handling). It falls short of the top anchor because the ~265-line body inlines complete report templates and full layer checklists that could partly live in references, and the referenced sibling-bundle files cannot be verified from this bundle's structure — 'good structure... minor organization gaps'.

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 a model example: concrete third-person action list, explicit 'Use when' clause with quoted natural trigger phrases, and explicit boundary guidance against a sibling skill. Every dimension sits at the top anchor.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete actions — 'scanning all blog files for quality scores, orphan pages, topic cannibalization, stale content, and AI citation readiness', 'Runs canonical batch analysis', 'Produces per-post scores and a prioritized action queue' — comprehensively covering the skill's stated scope and outputs. It fits the anchor for multiple specific concrete actions with comprehensive coverage; score 4 would require a noticeable coverage gap, and none exists.

5 / 5

Completeness

It explicitly answers both 'what' (the enumerated scanning actions and outputs) and 'when' ('Use when the user asks for a site-wide blog health check across many posts' with concrete trigger phrases). It even adds an explicit negative boundary ('For one post, or a quality score with fixes for a few named files, use blog-analyze instead'), which exceeds the anchor-5 example.

5 / 5

Trigger Term Quality

Trigger guidance includes natural quoted phrases users would actually say: '"blog audit"', '"blog health"', '"audit all posts"', '"site audit of the blog"', plus the framing 'Use when the user asks for a site-wide blog health check across many posts'. Coverage of natural terms and synonyms is comprehensive for this domain; score 4 would require clearly missing common variations, and the dominant phrasings are all present.

5 / 5

Distinctiveness Conflict Risk

The niche is clear — site-wide audit 'across many posts' — and it explicitly disambiguates from the sibling skill by redirecting single-post and few-file requests to 'blog-analyze instead'. Distinct triggers ('site-wide', 'audit all posts') minimize conflict risk, matching the clear-niche anchor.

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-audit/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.