CtrlK
BlogDocsLog inGet started
Tessl Logo

blog-localize

Cultural adaptation for translated content. Run AFTER blog-translate completes. Adjusts brand examples, CTAs, legal references, and formality for the target market (German, French, Japanese, Spanish, etc.). Deep cultural adaptation of translated blog posts. Goes beyond translation to swap brand examples, adapt CTAs, substitute legal references, localize statistic sources where possible, and adjust formality (Sie/du, tu/vous, formal/informal). Built-in profiles for DACH, Francophone, Hispanic, and Japanese markets, plus a custom-locale template. Makes content feel locally authored, not translated. Use when user says "localize blog", "blog localize", "cultural adaptation", "adapt for Germany", "adapt for France", "lokalisieren", "localiser", "adaptar".

73

Quality

91%

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

The canonical home for this skill is blog-localize in AgriciDaniel/claude-blog

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 thorough, actionable five-phase workflow with strong concrete guidance and validation for destructive steps. Main gaps are minor verbosity from inlined reference-style content and the absence of an explicit retry loop.

Suggestions

Move the brand-swap quick-map table and the report summary template into a reference file under ./references/ and link to them, tightening the SKILL.md body and improving progressive disclosure.

Add an explicit validate-fix-retry loop in Phase 4 (e.g., 'if a verification check fails, return to the relevant Phase 3 step, re-apply, and re-verify') rather than relying on the separate error-handling table.

Trim the SSRF rule enumeration to a concise checklist or move the full policy into a reference, keeping only the enforceable constraints inline.

DimensionReasoningScore

Conciseness

Largely efficient and assumes Claude's competence (no basic explanations of what localization is), but the inline quick-map table, SSRF rule list, and full summary template could be trimmed or deferred to keep the body leaner.

4 / 5

Actionability

Highly concrete guidance throughout — specific locale-parsing rules, file paths, an SSRF checklist, a substitution table, an output filename pattern, and a copy-paste-ready summary template cover the common cases.

5 / 5

Workflow Clarity

A clearly sequenced five-phase workflow with a Phase-4 verification checklist and backup-before-overwrite validation, but it lacks an explicit validate-fix-retry loop embedded within the phases (recovery is only implicit via the error-handling table).

4 / 5

Progressive Disclosure

Well-sectioned with a clearly signaled one-level-deep reference to cultural-adaptation.md, but several blocks (quick-map table, summary template) are inlined that could live in separate reference files; no local bundle files exist to offload them.

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

The description is comprehensive and well-structured, clearly stating concrete capabilities and providing explicit, multilingual trigger phrases. It cleanly distinguishes itself from the sibling blog-translate skill.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'swap brand examples, adapt CTAs, substitute legal references, localize statistic sources... and adjust formality' — giving comprehensive coverage rather than vague abstraction.

5 / 5

Completeness

Explicitly answers both what ('Deep cultural adaptation... swap brand examples, adapt CTAs, substitute legal references') and when ('Use when user says...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Provides natural trigger phrases users would say, including English variants ('localize blog', 'blog localize', 'cultural adaptation') and multilingual synonyms ('lokalisieren', 'localiser', 'adaptar').

5 / 5

Distinctiveness Conflict Risk

Carves a clear niche as the layer above blog-translate ('Run AFTER blog-translate completes') with distinct localize-vs-translate triggers, minimizing overlap with related skills.

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.