blog-locale-audit

Audit a directory of multilingual blog content for completeness, consistency, hreflang correctness, meta-tag parity, and freshness. Builds a translation coverage matrix, flags stale translations, validates hreflang and schema, and emits a prioritized report with runnable fix commands. Use when user says "locale audit", "blog locale-audit", "check translations", "multilingual audit", "translation check", "hreflang check", "Uebersetzungen pruefen".

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

77%

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

A high-quality, well-sequenced audit skill with concrete commands, example outputs, and validation checkpoints. Its main weaknesses are minor token redundancy at the top and a monolithic single-file structure that could offload detailed check tables to reference files.

Suggestions

Trim the redundant opening paragraph and the 'Adapted from' attribution blockquote; the description already conveys the purpose and the body need not repeat it.

Move the detailed Phase 3-6 severity check tables into a reference file (e.g. references/checks.md) and keep SKILL.md as a concise overview linking one level deep.

Consider adding a brief validation/feedback note for the freshness re-run loop (e.g. re-audit after running the emitted translate commands) to make the recovery cycle explicit.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with dense, useful check tables, but the opening paragraph restates the description ('Audits a directory... Catches international content issues before they hurt rankings') and the 'Adapted from claude-blog-multilingual' attribution blockquote adds token overhead without aiding execution.	2 / 3
Actionability	Provides concrete runnable commands ('Run: /blog translate en/ai-trends-2026.md --to de', 'html.escape(value, quote=True)'), specific severities per check, and copy-paste-ready report and coverage-matrix templates.	3 / 3
Workflow Clarity	Seven phases are clearly sequenced (Discovery through Report) with explicit validation/sanitization checkpoints - rejecting symlinked or outside-root directories in Phase 1 and escaping HTML plus rejecting bad report paths in Phase 7 - and a dedicated Error Handling table.	3 / 3
Progressive Disclosure	Sections are well-organized with clear headings and no nested references, but the entire audit - including the detailed Phase 3-6 check tables - lives inline in a single ~190-line SKILL.md with no one-level-deep reference split for a leaner overview.	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.

A strong, third-person description that names concrete capabilities and provides explicit, natural-language trigger guidance including a non-English variant. It answers both what and when without vague padding.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions - 'Builds a translation coverage matrix, flags stale translations, validates hreflang and schema, and emits a prioritized report with runnable fix commands' - across completeness, consistency, hreflang, meta-tag parity, and freshness.	3 / 3
Completeness	Clearly answers both what (audit/coverage matrix/hreflang/schema/report) and when via an explicit 'Use when user says...' clause with concrete triggers.	3 / 3
Trigger Term Quality	Covers natural terms users would say - 'locale audit', 'check translations', 'multilingual audit', 'translation check', 'hreflang check' - plus a German variant ('Uebersetzungen pruefen').	3 / 3
Distinctiveness Conflict Risk	Niche is clearly multilingual blog content auditing with distinct triggers (hreflang, translation coverage); unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: AgriciDaniel/claude-blog
Path: brain/.raw/sources/claude-blog-skill/skills/blog-locale-audit/SKILL.md
Commit: aec971a

Reviewed: about 13 hours ago

Table of Contents

Discovery Implementation Validation

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.