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

74

Quality

92%

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

85%

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

A well-structured, actionable localization workflow with strong sequencing and validation checkpoints. Its main weakness is token efficiency: a few sections, notably the SSRF guardrail paragraph and the swap table, could be tightened without losing clarity.

Suggestions

Tighten the Phase 3b SSRF paragraph into a compact checklist or shorter rule list so it earns its tokens more efficiently.

Consider moving the full brand/regulator swap table into the referenced cultural-adaptation.md and keeping only a brief pointer inline, reducing body length while preserving actionability.

Trim introductory prose in the opening paragraphs that restates the description ('This is the layer above blog-translate...') since the frontmatter already conveys positioning.

DimensionReasoningScore

Conciseness

Mostly efficient and assumes Claude's competence, but the SSRF guard paragraph and the brand-substitution table run long and could be tightened; a few sections carry detail that pads rather than instructs.

2 / 3

Actionability

Gives concrete, executable guidance — exact ISO locale parsing rules, named source categories, a specific brand/regulator swap table, and a copy-ready output summary template — rather than abstract direction.

3 / 3

Workflow Clarity

Five clearly sequenced phases with explicit validation checkpoints: a Phase 4 quality-verification checklist, SSRF checks before fetching, path-resolution rejection rules, and timestamped-backup-before-overwrite, providing clear feedback loops.

3 / 3

Progressive Disclosure

Well-organized into clear sections with a single one-level-deep, clearly signaled external reference (cultural-adaptation.md) explicitly marked 'Do not duplicate this file'; no deeply nested references and easy navigation.

3 / 3

Total

11

/

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, supplies explicit multilingual triggers, and clearly delineates when to invoke it. It avoids vagueness and over-claims while remaining concise.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'swap brand examples, adapt CTAs, substitute legal references, localize statistic sources where possible, and adjust formality' — matching the anchor for listing several specific concrete actions.

3 / 3

Completeness

Clearly answers both what (deep cultural adaptation of translated blog posts with named sub-tasks) and when via an explicit 'Use when user says...' clause, matching the top anchor.

3 / 3

Trigger Term Quality

Provides natural user phrasings across languages ('localize blog', 'blog localize', 'cultural adaptation', 'adapt for Germany', 'lokalisieren', 'localiser', 'adaptar'), giving good coverage of terms a user would actually say.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (post-translation cultural adaptation, distinct from blog-translate) with multilingual, market-specific triggers unlikely to fire for the wrong skill.

3 / 3

Total

12

/

12

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.