CtrlK
BlogDocsLog inGet started
Tessl Logo

blog-translate

Translate existing blog posts into one or more target languages with SEO-optimized localization. Produces native-quality translations that preserve markdown structure, frontmatter, schema JSON-LD, image and chart embeds, and evidence-backed explanations. Localizes keywords, meta tags, numbers, dates, currencies, and quote styles per locale. Flags machine-translation artifacts for review. Run BEFORE blog-localize: this handles language conversion; localize handles cultural adaptation after translation completes. Use when user says "translate blog", "blog translate", "uebersetzen", "traduire", "traducir", "translate post", "blog auf Deutsch", "blog en espanol".

76

Quality

96%

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

92%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 a strong, highly actionable instruction skill: a sequenced 7-phase workflow with real validation checkpoints and feedback loops, concrete specifics, and clean one-level-deep references to verified bundle files. The only weakness is mild redundancy and marketing flavor in the opening paragraph that restates the description.

Suggestions

Trim the intro paragraph (lines 27-30): it restates the frontmatter description and uses promotional phrasing ('publication-ready', 'culturally correct') that adds little actionable value.

Consider shortening or moving the provenance blockquote (lines 32-33) to a comment or footer so the body opens directly with operational content.

DimensionReasoningScore

Conciseness

Largely efficient and operational with no padding about concepts Claude already knows, but the opening paragraph ('Unlike generic translation, this skill produces SEO-optimized, publication-ready content with localized keywords, meta tags, and culturally correct formatting') restates the description with mild marketing flavor. Fits the score-4 anchor (efficient, minor trimmable instances); not 5 because of that redundant, slightly promotional intro, and not 3 because the bulk of the body is tight, specific operational guidance.

4 / 5

Actionability

Highly concrete and specific guidance throughout: exact hreflang codes, ISO normalization rules (639-1 lowercase / 15924 title case / 3166-1 Alpha-2 uppercase), explicit reject criteria (symlinks, >10 MB, binary, traversal), length adjustments (DE +30%, FR +15%, JA -20%), exact output paths, and a copy-paste-ready delivery template. As an instruction skill this matches the score-5 anchor (specific guidance covering common cases); not 4 because details are complete rather than having minor gaps.

5 / 5

Workflow Clarity

A clearly sequenced 7-phase workflow with explicit validation: Phase 5 'Verify structural integrity' checklist (H2/H3 counts, images with alt, SVG labels, FAQ count, evidence-backed explanations) and a Phase 6 feedback loop (scan for artifacts -> flag inline -> 'translator agent should re-pass any flagged passage before delivery'). Matches the score-5 anchor (explicit validation steps, feedback loops, checklists); the batch-operation cap at 3 does not apply because validation is present.

5 / 5

Progressive Disclosure

Clear overview organized into well-labeled sections (Key References, Workflow, Error Handling, Cross-References) with well-signaled one-level-deep references to real files ('references/translation-rules.md', 'references/cultural-adaptation.md', both confirmed present) introduced under 'Load on demand' with descriptions. Matches the score-5 anchor (clear overview, well-signaled one-level-deep references, easy navigation); no nested or buried references.

5 / 5

Total

19

/

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 excellent: it concretely states capabilities, provides comprehensive natural trigger terms (including multilingual synonyms), answers both 'what' and 'when' explicitly, and explicitly disambiguates from the related blog-localize skill. No substantive weaknesses to address.

DimensionReasoningScore

Specificity

Lists multiple concrete actions with comprehensive coverage: 'Translate existing blog posts', 'preserve markdown structure, frontmatter, schema JSON-LD, image and chart embeds', 'Localizes keywords, meta tags, numbers, dates, currencies, and quote styles', 'Flags machine-translation artifacts'. Fits the score-5 anchor (multiple specific concrete actions, comprehensive coverage); it is not 4 because coverage is broad rather than having only minor gaps.

5 / 5

Completeness

Explicitly answers both what ('Translate existing blog posts into one or more target languages with SEO-optimized localization...') and when ('Use when user says "translate blog"...') with concrete trigger phrases. Matches the score-5 example exactly; not 4 because the 'when' is explicit and concrete rather than merely adequate.

5 / 5

Trigger Term Quality

Comprehensive natural trigger coverage including synonyms and multilingual equivalents: 'translate blog', 'blog translate', 'uebersetzen', 'traduire', 'traducir', 'translate post', 'blog auf Deutsch', 'blog en espanol'. Matches the score-5 anchor; not 4 because common variations and multilingual synonyms are all present.

5 / 5

Distinctiveness Conflict Risk

Clear niche with distinct multilingual triggers and explicit disambiguation from a sibling skill ('Run BEFORE blog-localize: this handles language conversion; localize handles cultural adaptation'). Minimal conflict risk; not 4 because it actively distinguishes itself rather than having only minor overlap risk.

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.

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