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 citation capsules. 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".

73

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

85%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-sequenced, highly actionable workflow with strong validation and feedback loops. Its main weakness is progressive disclosure: the body points to two reference files that are not present in the bundle, so the on-demand detail it promises is unavailable.

Suggestions

Add the referenced bundle files (references/translation-rules.md and references/cultural-adaptation.md) so the 'Load on demand' pointers resolve; missing reference files break the progressive-disclosure navigation the skill relies on.

Trim the opening paragraph that restates the frontmatter description, and tighten the Phase 2 translatable-surface list, to push conciseness from efficient to lean.

Make the 'Key References' entries clickable links (e.g. [translation-rules.md](references/translation-rules.md)) and note which phase consumes each file, so the reference routing is explicit rather than implied.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence (no explaining of what markdown/JSON-LD/SVG are), but the opening paragraph restates the description and a few lists could be tightened, fitting 'efficient; minor instances of over-explanation that could be trimmed' rather than the fully lean 5.

4 / 5

Actionability

Concrete, copy-paste-ready guidance throughout — exact frontmatter block, hreflang code list, per-locale length adjustments (DE +30%, FR +15%, JA -20%), slug constraints, output path structure, and a full delivery template — covering the common cases.

5 / 5

Workflow Clarity

Seven clearly sequenced phases with explicit validation checkpoints and a feedback loop: Phase 6 scans for artifacts and requires the translator agent to 're-pass any flagged passage before delivery', Phase 5 verifies structural integrity, and the error-handling table defines retry behavior.

5 / 5

Progressive Disclosure

References are well-signaled and one level deep under 'Key References / Load on demand', but the referenced files (references/translation-rules.md, references/cultural-adaptation.md) do not exist in the bundle, so the signaled references do not actually resolve — structure is present but navigation is broken.

3 / 5

Total

17

/

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.

A strong, concrete description that clearly states capabilities, provides comprehensive multilingual trigger phrases, and explicitly disambiguates the skill from closely related sibling skills. It answers both 'what' and 'when' without relying on vague language.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Translate existing blog posts', 'preserve markdown structure, frontmatter, schema JSON-LD, image and chart embeds, and citation capsules', 'Localizes keywords, meta tags, numbers, dates, currencies, and quote styles', 'Flags machine-translation artifacts' — with comprehensive coverage and no vague fluff.

5 / 5

Completeness

Explicitly answers both 'what' (SEO-optimized translation preserving structure and localizing per locale) and 'when' ('Use when user says...') with concrete trigger phrases, plus boundary guidance ('Run BEFORE blog-localize').

5 / 5

Trigger Term Quality

Comprehensive natural trigger coverage including multilingual synonyms users actually say — 'translate blog', 'uebersetzen', 'traduire', 'traducir', 'blog auf Deutsch', 'blog en espanol' — matching the anchor's expectation of synonyms and variations.

5 / 5

Distinctiveness Conflict Risk

Clear niche (language conversion only) with explicit disambiguation from sibling skills — 'Run BEFORE blog-localize: this handles language conversion; localize handles cultural adaptation' — and distinct multilingual triggers minimizing conflict risk.

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.

Validation14 / 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: 4 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.