Creator · AgriciDaniel
Last updated · Sep 2, 2026
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 translatio
Creator · AgriciDaniel
Last updated · Sep 2, 2026
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 translatio
Creator · AgriciDaniel
Last updated · Sep 2, 2026
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 translatio
Creator · AgriciDaniel
Last updated · Sep 2, 2026
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 translatio
Sandbox only
Install targets
Codex install prompt
Install the "blog-localize" agent skill from https://github.com/AgriciDaniel/claude-blog/tree/main/brain/.raw/sources/claude-blog-skill/skills/blog-localize. Read its SKILL.md or equivalent instructions first, install only the files needed for this workspace, and summarize any required setup before using it. Skill purpose: 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". After the install attempt, report the result to https://www.openagentskill.com/api/agent/outcome with POST JSON {"event_id":"install_<unique-id>","skill_slug":"agricidaniel-blog-localize","task":"Install blog-localize","agent":"codex","outcome":"success","install_used":true}. Replace event_id with a unique value and outcome with success or failed. Report success only after the skill is installed and a minimal verification passes.Supply asset profile
Deep research, source comparison, literature review, RAG, knowledge search, and reports.
Scenario
Research agents
I need my agent to research a topic, compare sources, and produce a concise report.
Agent fit
Claude Code + CLI + Codex
Codex, Claude Code, Cursor, CLI, or custom agents.
Install
Ready
npx skills add AgriciDaniel/claude-blog --skill blog-localize
Maintenance
fresh
9d since push
Risk
Risky
Permission surface may require sandboxing
GitHub quality
2.0K
80/100 Quality · 82/100 Trust
Coverage tags
Review notes
Permission surface may require sandboxing · Financial research output is not financial advice; require human review before any live investment decision
Agent adoption scorecard
These scores combine public repository metadata, OpenAgentSkill review signals, maintenance freshness, and install readiness. They are a shortlist signal, not a replacement for human review.
Quality
StrongSolid option that is likely worth shortlisting for production workflows.
Trust
Sandbox onlyUseful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
Audit
RiskyA machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
OpenAgentSkill Trust Score v5
Run only in a sandbox and compare close alternatives before using it for real work.
Stars
2.0K GitHub stars
Repo activity
2.0K stars, 333 forks
Maintenance
9d since push
License
MIT
Install
npx skills add AgriciDaniel/claude-blog --skill blog-localize
Install safety
Agent-readable metadata
Use this block or the embedded JSON to decide whether an agent should install this skill, choose an alternative, or ask for human review first.
Suited tasks
Suited agents
Install decision
Trust and risk
Outcome loop
Install command
npx skills add AgriciDaniel/claude-blog --skill blog-localizeDo not use when
Alternative
1.9K Stars
npx skills add yanliudesign/mono-color-skill --skill mono-color
Alternative
61.0K Stars
npx skills add mvanhorn/last30days-skill -g
Alternative
38.4K Stars
npx skills add Imbad0202/academic-research-skills
Alternative
28.0K Stars
npx skills add assafelovic/gpt-researcher
Agent safety v2
This skill should not be selected by an agent without explicit human security review.
Do not auto-install. Inspect the source, dependencies, and permission surface first.
high
Skill metadata references terminal, CLI, shell, subprocess, or command execution workflows.
medium
Skill may drive a browser or interact with web pages.
medium
Skill likely fetches remote pages, APIs, repositories, or external services.
medium
Skill may read or write project files, documents, generated artifacts, or local workspace state.
Agent resolve plan
The Resolve API returns the selected skill, alternatives, safety policy, audit notes, install target, and copy-paste prompt an agent can follow without scraping this page.
Open JSON
/api/agent/resolve?task=Use%20blog-localize%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Resolve text
/api/agent/resolve?task=Use%20blog-localize%20for%20an%20agent%20workflow&agent=codex&max_risk=medium&format=text
Install handoff
/api/skills/agricidaniel-blog-localize/install
Agent should check
Copy prompt
Task: Use blog-localize in this workspace.
Resolve first: https://www.openagentskill.com/api/agent/resolve?task=Use%20blog-localize%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Review install handoff: https://www.openagentskill.com/api/skills/agricidaniel-blog-localize/install
Install command: npx skills add AgriciDaniel/claude-blog --skill blog-localize
Before running it, summarize audit warnings, required permissions, and the fallback skill if install is risky.Agent handoff
Use the public install endpoint to fetch the command, safety checklist, target prompts, and canonical links for this skill.
Install handoff
/api/skills/agricidaniel-blog-localize/install
LLM text format
/api/skills/agricidaniel-blog-localize/install?format=text
Find alternatives
/api/skills/search?q=blog-localize&limit=3
Agent prompt
Use blog-localize for this task. Review https://www.openagentskill.com/api/skills/agricidaniel-blog-localize/install, then install with: npx skills add AgriciDaniel/claude-blog --skill blog-localizeRegistry metadata
This page exposes the same decision, trust, audit, use-case, and install signals through the Registry API, so agents can rank this skill without scraping the UI.
Manifest
/api/registry/manifest/agricidaniel-blog-localize
LLM text
/api/registry/manifest/agricidaniel-blog-localize?format=text
Install alias
/api/registry/install/agricidaniel-blog-localize
Recommend
/api/registry/recommend?task=Use%20blog-localize%20in%20an%20agent%20workflow&limit=3
Agent fit
Research agents
Use-case tags
Platforms
Claude Code
Audit report
A machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
Agent decision cockpit
Use this as a leading candidate, then validate the README and install path in your own agent stack.
Role in stack
Primary pick
Primary fit
Research agents
Trust label
Production-ready
Install path
Command ready
Use when
Evidence
review first
Implementation path
Trust profile
Useful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
GitHub adoption
PASS2.0K GitHub stars
Stars/forks activity
PASS2.0K stars, 333 forks; issue activity unavailable in current metadata
Recent maintenance
PASS9d since push
License clarity
PASSMIT
Good signals
Review before install
Recommended action
Run only in a sandbox and compare close alternatives before using it for real work.
Quality profile
Solid option that is likely worth shortlisting for production workflows.
Workflow fit
Investigate faster
I need my agent to research a topic, compare sources, and produce a concise report.
Manage repositories
I need my agent to triage GitHub issues, review pull requests, and summarize repository changes.
Publish consistently
I need my agent to turn research and product updates into useful content drafts.
Workflow fit
Find, compare, and synthesize
A workflow for agents that gather sources, compare claims, summarize long material, and draft useful research briefs.
Turn skills into distribution
A workflow for turning newly indexed skills into SEO briefs, social drafts, comparison pages, and reusable publishing workflows.
Inspect, patch, and verify code
A workflow for software agents that inspect repositories, review pull requests, generate tests, and turn findings into shippable patches.
Alternative shortlist
Similar skills that may fit this task.
Generate original one-ink or controlled two-ink editorial images from any theme, sentence, article idea, object, or reference photo. Always use this skill when the user asks for 单色海报、双色印刷、单色调视觉、蓝色/绿色孔版印刷、risograph、网点照片、复古或当代编辑排版、zine poster, monochrome editorial poster, duotone print, or asks to use the mono-color style. It uses an adaptive white, gray, or pale-beige substrate, no more than two printing inks, active negative space, terse human language, and strong serif/grotesk/mono typography without making retro styling the default or copying a source composition, wording, logo, or artwork. Produce both the final generation prompt and the generated raster image unless the user explicitly asks for prompt only.
Research the last 30 days across Reddit, X, YouTube, Hacker News, Polymarket, GitHub, and the web, then synthesize a grounded brief for an AI agent.
Academic Research Skills for Claude Code: research → write → review → revise → finalize
Run autonomous deep research over web and local sources
--- name: blog-localize description: > 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". user-invokable: true argument-hint: "<file> --locale <locale-code>" license: MIT compatibility: Standalone within claude-blog. Invoked by blog-multilingual. metadata: author: AgriciDaniel version: "1.11.0" category: blog ---
# Blog Localize, Cultural Deep-Adaptation
Takes a translated blog post and performs cultural adaptation so the result feels like it was written for the target market, not translated into it. This is the layer above `blog-translate`: it replaces examples, adjusts tone, swaps references, and localizes the entire reading experience.
> Adapted from `claude-blog-multilingual` by Chris Mueller (Pro Hub Challenge, > March 2026). Original: https://github.com/Chriss54/multilingual-int
## Key References
- `../blog-translate/references/cultural-adaptation.md`, the shared cultural profiles file with substitution tables for DACH, Francophone, Hispanic, Japanese, and a custom template. Do not duplicate this file.
## When to Use
- Right after `blog-translate` produces a base translation. - When existing translated content reads like "translated from English". - When targeting a specific market, not just a language. - When content needs local statistics, examples, and brand references.
## Workflow
### Phase 1: Locale Understanding
1. Parse the locale code with the shared multilingual locale rules used by `blog-translate`, `blog-multilingual`, and `blog-locale-audit`: ISO 639-1 language in lowercase, optional ISO 15924 script in title case, optional ISO 3166-1 Alpha-2 region in uppercase. Accept full codes (`de-DE`, `fr-CA`, `es-MX`, `pt-BR`, `zh-Hant`) and unambiguous plain language codes (`de`, `fr`). Require a region or explicit neutral mode for ambiguous language-only targets such as `es`, `pt`, and `zh`. 2. Load the cultural profile from `../blog-translate/references/cultural-adaptation.md`. - If the locale has a profile, use it. - If not, follow the "Custom-locale template" section in that reference to build a minimal profile inline. 3. Read the translated post only after resolving it inside the project root/current working directory. Reject symlinked paths, traversal outside the root, files over 10 MB, and binary files. Then identify adaptation targets.
### Phase 2: Cultural Audit
Scan for elements that signal foreign origin:
| Element | What to look for | |---------|------------------| | Brand examples | US or UK brands with no relevance locally | | Statistics sources | US-only studies and surveys | | CTAs | American-style aggressive calls-to-action | | Idioms | Literally translated English expressions | | Legal references | Foreign laws (CCPA, FTC) where local law applies (DSGVO, RGPD) | | Cultural references | Foreign holidays, events, customs | | Currency and pricing | USD without conversion or context | | Tone | Too casual or too formal for the target market | | Address form | Inconsistent Sie/du, tu/vous, formal/informal |
Output an audit report listing every target with severity (critical, recommended, optional).
### Phase 3: Adaptation
#### 3a. Example Substitution
Swap foreign examples for local equivalents:
- Use WebSearch to find local case studies, brands, or scenarios. - Replace inline, preserving the same argument and structure. - Record source URL, access date, and rationale for every non-obvious local replacement. - If no local equivalent exists, keep the original but add local context ("In the German market, the equivalent dynamic is X").
#### 3b. Statistics Localization
- Use primary or high-quality local sources for replacement statistics: national statistics offices, regulators, official industry bodies, academic datasets, or named research reports with methodology. - Do not rely on generic WebSearch snippets as evidence. Fetch the cited page, verify the figure and context, and record the source URL and date. - Fetch cited pages only after SSRF checks: allow `https` URLs only; reject `javascript:`, `data:`, `file:`, localhost, loopback, private, link-local, multicast, and reserved IPs after DNS resolution; disable redirects or validate the final URL with the same checks; cap redirects, response size, and request time; log the final URL and access date. - If local data exists with comparable methodology, swap the source and the figure together. Keep one named source per claim. - If local data is related but uses a different methodology or timeframe, do not silently swap it. Keep the original claim scoped, or rewrite the claim to match the local source. - If not, keep the original stat but mark its geographic scope ("In the US, ..."). - Never strip source attribution.
#### 3c. CTA Adaptation
Rewrite calls-to-action per the cultural profile:
- Adjust aggressiveness level (DACH and JA prefer informational, US prefers imperative). - Use culturally appropriate action verbs. - Adapt urgency framing.
#### 3d. Tone Calibration
- Match formality per profile (DACH defaults to Sie for B2B, du for B2C lifestyle; FR defaults to vous; JA shifts register sharply by audience). - Ensure consistent formal or informal address throughout the entire document. - Match local content-style conventions.
#### 3e. Legal and Regulatory Context
- Map legal references by issue and jurisdiction. Keep the original law when the claim is specifically about US compliance. Only substitute when the local law addresses the same issue, such as CCPA to DSGVO in DE, RGPD in FR, LGPD in BR, LFPDPPP in MX, Ley 1581 in CO, or Ley 25.326 in AR. - Add local compliance notes where they help the reader. - Remove irrelevant foreign regulatory references.
#### 3f. Brand Example Swaps (Quick Map)
Profiles in `../blog-translate/references/cultural-adaptation.md` provide substitution tables. Common examples:
| Source (US) | DACH | FR | ES (Spain) | LATAM | JA | |-------------|------|----|----|-------|----| | Walmart | MediaMarkt | Carrefour | El Corte Inglés | Walmart MX | Aeon | | Target | Saturn | Auchan | Hipercor | Liverpool | Ito-Yokado | | FTC | Bundeskartellamt | DGCCRF | CNMC | PROFECO (MX) | JFTC | | CCPA | DSGVO | RGPD | RGPD | LFPDPPP (MX), Ley 1581 (CO), Ley 25.326 (AR), LGPD (BR) | APPI |
### Phase 4: Quality Verification
- All critical adaptation targets addressed. - Tone is consistent throughout. - No remaining foreign-origin markers. - Statistics have valid sources (original or localized). - CTAs match cultural expectations. - Formal or informal address is consistent end to end. - Content still supports the same argument as the original. - SEO elements remain optimized beyond keyword placement: localized title and meta, heading intent, slug, alt text, internal-link anchors, same-language canonical, hreflang compatibility, and schema `inLanguage`. - Word count is within the expected ratio for the language pair.
### Phase 5: Save and Report
1. Save the localized version. Default: write a reviewed copy as `{slug}-localized.{ext}`. Only overwrite the translated file when the user asks for overwrite; before overwriting, create a timestamped backup and show a diff summary. Resolve every output path inside the project root and reject traversal, symlinked paths, or writes outside that root.
2. Present the summary:
``` ## Localization complete: [Title]
### Target locale: [locale-code] ([locale-name])
### Adaptations made | Type | Count | Examples | |------|-------|----------| | Brand examples | [N] | Walmart -> MediaMarkt | | Statistics | [N] | US survey -> DACH survey | | CTAs | [N] | "Buy now" -> "Jetzt entdecken" | | Tone adjustments | [N] | Casual -> Sie | | Legal references | [N] | CCPA -> DSGVO | | Cultural references | [N] | Thanksgiving -> Weihnachtsgeschaeft |
### Cultural fit score - Naturalness: [1-10] - Market relevance: [1-10] - Tone match: [1-10] - Overall: [N]/30
### Remaining recommendations - [Optional adaptations not applied] ```
## Error Handling
| Scenario | Action | |----------|--------| | No cultural profile for the locale | Build a minimal profile from the custom-locale template, proceed | | File is not in the expected language | Warn the user, offer to translate first | | No local statistics available | Keep the original stat with a geographic-scope note | | Locale code ambiguous (e.g., `pt`) | Ask: "Did you mean `pt-BR` (Brazil) or `pt-PT` (Portugal)?" |
## Cross-References
- Pre-step (translation): `/blog translate <file> --to <code>` - QA across language versions: `/blog locale-audit <directory>` - One-command pipeline: `/blog multilingual <topic> --languages <codes>`
Source provenance
Decision snapshot
2,016 GitHub stars
Audit
Install and adoption review
Agent-proven evidence
Outcome reports after resolve, review, install, and one narrow run.
No agent outcome data yet. The first agent run can report success, setup needs, risk blocks, failure, or not-relevant through /api/agent/outcome.
Install
Free and open source. Review the report before installing into production agents.
Growth loop
Scenario-led draft for blog-localize, ready for a manual X post.
blog-localize: Cultural adaptation for translated content. Run AFTER blog-translate completes. Adjusts brand... 2.0K stars https://www.openagentskill.com/skills/agricidaniel-blog-localize?ref=x
Listing + install path for blog-localize: https://www.openagentskill.com/skills/agricidaniel-blog-localize?ref=x Install: npx skills add AgriciDaniel/claude-blog --skill blog-localize
Listing source
This listing was indexed from public sources and is not marked official until a maintainer claim is approved.
Attribution links to the public repository or creator profile. Creators can claim the listing to update ownership signals.
Claim this skillOwner claim
This Registry indexed listing is attributed to AgriciDaniel but is not marked official yet. Claim it to add a verified owner signal and make future launch, install, and audit updates easier to trust.
Creator backlink kit
Show the canonical listing, current trust and audit signals, and real Agent-Proven evidence where developers evaluate the repository.
[](https://www.openagentskill.com/skills/agricidaniel-blog-localize?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/agricidaniel-blog-localize?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/agricidaniel-blog-localize/audit)
[](https://www.openagentskill.com/skills/agricidaniel-blog-localize?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)AgriciDaniel
@agricidaniel
Share whether this skill looks useful for your agent workflow. Aggregated feedback improves rankings over time.
Sandbox only
mono-color
Generate original one-ink or controlled two-ink editorial images from any theme, sentence, article idea, object, or reference photo. Always use this skill when the user asks for 单色海报、双色印刷、单色调视觉、蓝色/绿色孔版印刷、risograph、网点照片、复古或当代编辑排版、zine poster, monochrome editorial poster, duotone print, or asks to use the mono-color style. It uses an adaptive white, gray, or pale-beige substrate, no more than two printing inks, active negative space, terse human language, and strong serif/grotesk/mono typography without making retro styling the default or copying a source composition, wording, logo, or artwork. Produce both the final generation prompt and the generated raster image unless the user explicitly asks for prompt only.
1.9K StarsLast30days Skill
Research the last 30 days across Reddit, X, YouTube, Hacker News, Polymarket, GitHub, and the web, then synthesize a grounded brief for an AI agent.
61.0K StarsAcademic Research Skills
Academic Research Skills for Claude Code: research → write → review → revise → finalize
38.4K StarsGPT Researcher
Run autonomous deep research over web and local sources
28.0K StarsSandbox only
Install targets
Codex install prompt
Install the "blog-localize" agent skill from https://github.com/AgriciDaniel/claude-blog/tree/main/brain/.raw/sources/claude-blog-skill/skills/blog-localize. Read its SKILL.md or equivalent instructions first, install only the files needed for this workspace, and summarize any required setup before using it. Skill purpose: 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". After the install attempt, report the result to https://www.openagentskill.com/api/agent/outcome with POST JSON {"event_id":"install_<unique-id>","skill_slug":"agricidaniel-blog-localize","task":"Install blog-localize","agent":"codex","outcome":"success","install_used":true}. Replace event_id with a unique value and outcome with success or failed. Report success only after the skill is installed and a minimal verification passes.Supply asset profile
Deep research, source comparison, literature review, RAG, knowledge search, and reports.
Scenario
Research agents
I need my agent to research a topic, compare sources, and produce a concise report.
Agent fit
Claude Code + CLI + Codex
Codex, Claude Code, Cursor, CLI, or custom agents.
Install
Ready
npx skills add AgriciDaniel/claude-blog --skill blog-localize
Maintenance
fresh
9d since push
Risk
Risky
Permission surface may require sandboxing
GitHub quality
2.0K
80/100 Quality · 82/100 Trust
Coverage tags
Review notes
Permission surface may require sandboxing · Financial research output is not financial advice; require human review before any live investment decision
Agent adoption scorecard
These scores combine public repository metadata, OpenAgentSkill review signals, maintenance freshness, and install readiness. They are a shortlist signal, not a replacement for human review.
Quality
StrongSolid option that is likely worth shortlisting for production workflows.
Trust
Sandbox onlyUseful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
Audit
RiskyA machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
OpenAgentSkill Trust Score v5
Run only in a sandbox and compare close alternatives before using it for real work.
Stars
2.0K GitHub stars
Repo activity
2.0K stars, 333 forks
Maintenance
9d since push
License
MIT
Install
npx skills add AgriciDaniel/claude-blog --skill blog-localize
Install safety
Agent-readable metadata
Use this block or the embedded JSON to decide whether an agent should install this skill, choose an alternative, or ask for human review first.
Suited tasks
Suited agents
Install decision
Trust and risk
Outcome loop
Install command
npx skills add AgriciDaniel/claude-blog --skill blog-localizeDo not use when
Alternative
1.9K Stars
npx skills add yanliudesign/mono-color-skill --skill mono-color
Alternative
61.0K Stars
npx skills add mvanhorn/last30days-skill -g
Alternative
38.4K Stars
npx skills add Imbad0202/academic-research-skills
Alternative
28.0K Stars
npx skills add assafelovic/gpt-researcher
Agent safety v2
This skill should not be selected by an agent without explicit human security review.
Do not auto-install. Inspect the source, dependencies, and permission surface first.
high
Skill metadata references terminal, CLI, shell, subprocess, or command execution workflows.
medium
Skill may drive a browser or interact with web pages.
medium
Skill likely fetches remote pages, APIs, repositories, or external services.
medium
Skill may read or write project files, documents, generated artifacts, or local workspace state.
Agent resolve plan
The Resolve API returns the selected skill, alternatives, safety policy, audit notes, install target, and copy-paste prompt an agent can follow without scraping this page.
Open JSON
/api/agent/resolve?task=Use%20blog-localize%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Resolve text
/api/agent/resolve?task=Use%20blog-localize%20for%20an%20agent%20workflow&agent=codex&max_risk=medium&format=text
Install handoff
/api/skills/agricidaniel-blog-localize/install
Agent should check
Copy prompt
Task: Use blog-localize in this workspace.
Resolve first: https://www.openagentskill.com/api/agent/resolve?task=Use%20blog-localize%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Review install handoff: https://www.openagentskill.com/api/skills/agricidaniel-blog-localize/install
Install command: npx skills add AgriciDaniel/claude-blog --skill blog-localize
Before running it, summarize audit warnings, required permissions, and the fallback skill if install is risky.Agent handoff
Use the public install endpoint to fetch the command, safety checklist, target prompts, and canonical links for this skill.
Install handoff
/api/skills/agricidaniel-blog-localize/install
LLM text format
/api/skills/agricidaniel-blog-localize/install?format=text
Find alternatives
/api/skills/search?q=blog-localize&limit=3
Agent prompt
Use blog-localize for this task. Review https://www.openagentskill.com/api/skills/agricidaniel-blog-localize/install, then install with: npx skills add AgriciDaniel/claude-blog --skill blog-localizeRegistry metadata
This page exposes the same decision, trust, audit, use-case, and install signals through the Registry API, so agents can rank this skill without scraping the UI.
Manifest
/api/registry/manifest/agricidaniel-blog-localize
LLM text
/api/registry/manifest/agricidaniel-blog-localize?format=text
Install alias
/api/registry/install/agricidaniel-blog-localize
Recommend
/api/registry/recommend?task=Use%20blog-localize%20in%20an%20agent%20workflow&limit=3
Agent fit
Research agents
Use-case tags
Platforms
Claude Code
Audit report
A machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
Agent decision cockpit
Use this as a leading candidate, then validate the README and install path in your own agent stack.
Role in stack
Primary pick
Primary fit
Research agents
Trust label
Production-ready
Install path
Command ready
Use when
Evidence
review first
Implementation path
Trust profile
Useful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
GitHub adoption
PASS2.0K GitHub stars
Stars/forks activity
PASS2.0K stars, 333 forks; issue activity unavailable in current metadata
Recent maintenance
PASS9d since push
License clarity
PASSMIT
Good signals
Review before install
Recommended action
Run only in a sandbox and compare close alternatives before using it for real work.
Quality profile
Solid option that is likely worth shortlisting for production workflows.
Workflow fit
Investigate faster
I need my agent to research a topic, compare sources, and produce a concise report.
Manage repositories
I need my agent to triage GitHub issues, review pull requests, and summarize repository changes.
Publish consistently
I need my agent to turn research and product updates into useful content drafts.
Workflow fit
Find, compare, and synthesize
A workflow for agents that gather sources, compare claims, summarize long material, and draft useful research briefs.
Turn skills into distribution
A workflow for turning newly indexed skills into SEO briefs, social drafts, comparison pages, and reusable publishing workflows.
Inspect, patch, and verify code
A workflow for software agents that inspect repositories, review pull requests, generate tests, and turn findings into shippable patches.
Alternative shortlist
Similar skills that may fit this task.
Generate original one-ink or controlled two-ink editorial images from any theme, sentence, article idea, object, or reference photo. Always use this skill when the user asks for 单色海报、双色印刷、单色调视觉、蓝色/绿色孔版印刷、risograph、网点照片、复古或当代编辑排版、zine poster, monochrome editorial poster, duotone print, or asks to use the mono-color style. It uses an adaptive white, gray, or pale-beige substrate, no more than two printing inks, active negative space, terse human language, and strong serif/grotesk/mono typography without making retro styling the default or copying a source composition, wording, logo, or artwork. Produce both the final generation prompt and the generated raster image unless the user explicitly asks for prompt only.
Research the last 30 days across Reddit, X, YouTube, Hacker News, Polymarket, GitHub, and the web, then synthesize a grounded brief for an AI agent.
Academic Research Skills for Claude Code: research → write → review → revise → finalize
Run autonomous deep research over web and local sources
--- name: blog-localize description: > 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". user-invokable: true argument-hint: "<file> --locale <locale-code>" license: MIT compatibility: Standalone within claude-blog. Invoked by blog-multilingual. metadata: author: AgriciDaniel version: "1.11.0" category: blog ---
# Blog Localize, Cultural Deep-Adaptation
Takes a translated blog post and performs cultural adaptation so the result feels like it was written for the target market, not translated into it. This is the layer above `blog-translate`: it replaces examples, adjusts tone, swaps references, and localizes the entire reading experience.
> Adapted from `claude-blog-multilingual` by Chris Mueller (Pro Hub Challenge, > March 2026). Original: https://github.com/Chriss54/multilingual-int
## Key References
- `../blog-translate/references/cultural-adaptation.md`, the shared cultural profiles file with substitution tables for DACH, Francophone, Hispanic, Japanese, and a custom template. Do not duplicate this file.
## When to Use
- Right after `blog-translate` produces a base translation. - When existing translated content reads like "translated from English". - When targeting a specific market, not just a language. - When content needs local statistics, examples, and brand references.
## Workflow
### Phase 1: Locale Understanding
1. Parse the locale code with the shared multilingual locale rules used by `blog-translate`, `blog-multilingual`, and `blog-locale-audit`: ISO 639-1 language in lowercase, optional ISO 15924 script in title case, optional ISO 3166-1 Alpha-2 region in uppercase. Accept full codes (`de-DE`, `fr-CA`, `es-MX`, `pt-BR`, `zh-Hant`) and unambiguous plain language codes (`de`, `fr`). Require a region or explicit neutral mode for ambiguous language-only targets such as `es`, `pt`, and `zh`. 2. Load the cultural profile from `../blog-translate/references/cultural-adaptation.md`. - If the locale has a profile, use it. - If not, follow the "Custom-locale template" section in that reference to build a minimal profile inline. 3. Read the translated post only after resolving it inside the project root/current working directory. Reject symlinked paths, traversal outside the root, files over 10 MB, and binary files. Then identify adaptation targets.
### Phase 2: Cultural Audit
Scan for elements that signal foreign origin:
| Element | What to look for | |---------|------------------| | Brand examples | US or UK brands with no relevance locally | | Statistics sources | US-only studies and surveys | | CTAs | American-style aggressive calls-to-action | | Idioms | Literally translated English expressions | | Legal references | Foreign laws (CCPA, FTC) where local law applies (DSGVO, RGPD) | | Cultural references | Foreign holidays, events, customs | | Currency and pricing | USD without conversion or context | | Tone | Too casual or too formal for the target market | | Address form | Inconsistent Sie/du, tu/vous, formal/informal |
Output an audit report listing every target with severity (critical, recommended, optional).
### Phase 3: Adaptation
#### 3a. Example Substitution
Swap foreign examples for local equivalents:
- Use WebSearch to find local case studies, brands, or scenarios. - Replace inline, preserving the same argument and structure. - Record source URL, access date, and rationale for every non-obvious local replacement. - If no local equivalent exists, keep the original but add local context ("In the German market, the equivalent dynamic is X").
#### 3b. Statistics Localization
- Use primary or high-quality local sources for replacement statistics: national statistics offices, regulators, official industry bodies, academic datasets, or named research reports with methodology. - Do not rely on generic WebSearch snippets as evidence. Fetch the cited page, verify the figure and context, and record the source URL and date. - Fetch cited pages only after SSRF checks: allow `https` URLs only; reject `javascript:`, `data:`, `file:`, localhost, loopback, private, link-local, multicast, and reserved IPs after DNS resolution; disable redirects or validate the final URL with the same checks; cap redirects, response size, and request time; log the final URL and access date. - If local data exists with comparable methodology, swap the source and the figure together. Keep one named source per claim. - If local data is related but uses a different methodology or timeframe, do not silently swap it. Keep the original claim scoped, or rewrite the claim to match the local source. - If not, keep the original stat but mark its geographic scope ("In the US, ..."). - Never strip source attribution.
#### 3c. CTA Adaptation
Rewrite calls-to-action per the cultural profile:
- Adjust aggressiveness level (DACH and JA prefer informational, US prefers imperative). - Use culturally appropriate action verbs. - Adapt urgency framing.
#### 3d. Tone Calibration
- Match formality per profile (DACH defaults to Sie for B2B, du for B2C lifestyle; FR defaults to vous; JA shifts register sharply by audience). - Ensure consistent formal or informal address throughout the entire document. - Match local content-style conventions.
#### 3e. Legal and Regulatory Context
- Map legal references by issue and jurisdiction. Keep the original law when the claim is specifically about US compliance. Only substitute when the local law addresses the same issue, such as CCPA to DSGVO in DE, RGPD in FR, LGPD in BR, LFPDPPP in MX, Ley 1581 in CO, or Ley 25.326 in AR. - Add local compliance notes where they help the reader. - Remove irrelevant foreign regulatory references.
#### 3f. Brand Example Swaps (Quick Map)
Profiles in `../blog-translate/references/cultural-adaptation.md` provide substitution tables. Common examples:
| Source (US) | DACH | FR | ES (Spain) | LATAM | JA | |-------------|------|----|----|-------|----| | Walmart | MediaMarkt | Carrefour | El Corte Inglés | Walmart MX | Aeon | | Target | Saturn | Auchan | Hipercor | Liverpool | Ito-Yokado | | FTC | Bundeskartellamt | DGCCRF | CNMC | PROFECO (MX) | JFTC | | CCPA | DSGVO | RGPD | RGPD | LFPDPPP (MX), Ley 1581 (CO), Ley 25.326 (AR), LGPD (BR) | APPI |
### Phase 4: Quality Verification
- All critical adaptation targets addressed. - Tone is consistent throughout. - No remaining foreign-origin markers. - Statistics have valid sources (original or localized). - CTAs match cultural expectations. - Formal or informal address is consistent end to end. - Content still supports the same argument as the original. - SEO elements remain optimized beyond keyword placement: localized title and meta, heading intent, slug, alt text, internal-link anchors, same-language canonical, hreflang compatibility, and schema `inLanguage`. - Word count is within the expected ratio for the language pair.
### Phase 5: Save and Report
1. Save the localized version. Default: write a reviewed copy as `{slug}-localized.{ext}`. Only overwrite the translated file when the user asks for overwrite; before overwriting, create a timestamped backup and show a diff summary. Resolve every output path inside the project root and reject traversal, symlinked paths, or writes outside that root.
2. Present the summary:
``` ## Localization complete: [Title]
### Target locale: [locale-code] ([locale-name])
### Adaptations made | Type | Count | Examples | |------|-------|----------| | Brand examples | [N] | Walmart -> MediaMarkt | | Statistics | [N] | US survey -> DACH survey | | CTAs | [N] | "Buy now" -> "Jetzt entdecken" | | Tone adjustments | [N] | Casual -> Sie | | Legal references | [N] | CCPA -> DSGVO | | Cultural references | [N] | Thanksgiving -> Weihnachtsgeschaeft |
### Cultural fit score - Naturalness: [1-10] - Market relevance: [1-10] - Tone match: [1-10] - Overall: [N]/30
### Remaining recommendations - [Optional adaptations not applied] ```
## Error Handling
| Scenario | Action | |----------|--------| | No cultural profile for the locale | Build a minimal profile from the custom-locale template, proceed | | File is not in the expected language | Warn the user, offer to translate first | | No local statistics available | Keep the original stat with a geographic-scope note | | Locale code ambiguous (e.g., `pt`) | Ask: "Did you mean `pt-BR` (Brazil) or `pt-PT` (Portugal)?" |
## Cross-References
- Pre-step (translation): `/blog translate <file> --to <code>` - QA across language versions: `/blog locale-audit <directory>` - One-command pipeline: `/blog multilingual <topic> --languages <codes>`
Source provenance
Decision snapshot
2,016 GitHub stars
Audit
Install and adoption review
Agent-proven evidence
Outcome reports after resolve, review, install, and one narrow run.
No agent outcome data yet. The first agent run can report success, setup needs, risk blocks, failure, or not-relevant through /api/agent/outcome.
Install
Free and open source. Review the report before installing into production agents.
Growth loop
Scenario-led draft for blog-localize, ready for a manual X post.
blog-localize: Cultural adaptation for translated content. Run AFTER blog-translate completes. Adjusts brand... 2.0K stars https://www.openagentskill.com/skills/agricidaniel-blog-localize?ref=x
Listing + install path for blog-localize: https://www.openagentskill.com/skills/agricidaniel-blog-localize?ref=x Install: npx skills add AgriciDaniel/claude-blog --skill blog-localize
Listing source
This listing was indexed from public sources and is not marked official until a maintainer claim is approved.
Attribution links to the public repository or creator profile. Creators can claim the listing to update ownership signals.
Claim this skillOwner claim
This Registry indexed listing is attributed to AgriciDaniel but is not marked official yet. Claim it to add a verified owner signal and make future launch, install, and audit updates easier to trust.
Creator backlink kit
Show the canonical listing, current trust and audit signals, and real Agent-Proven evidence where developers evaluate the repository.
[](https://www.openagentskill.com/skills/agricidaniel-blog-localize?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/agricidaniel-blog-localize?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/agricidaniel-blog-localize/audit)
[](https://www.openagentskill.com/skills/agricidaniel-blog-localize?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)AgriciDaniel
@agricidaniel
Share whether this skill looks useful for your agent workflow. Aggregated feedback improves rankings over time.
Sandbox only
mono-color
Generate original one-ink or controlled two-ink editorial images from any theme, sentence, article idea, object, or reference photo. Always use this skill when the user asks for 单色海报、双色印刷、单色调视觉、蓝色/绿色孔版印刷、risograph、网点照片、复古或当代编辑排版、zine poster, monochrome editorial poster, duotone print, or asks to use the mono-color style. It uses an adaptive white, gray, or pale-beige substrate, no more than two printing inks, active negative space, terse human language, and strong serif/grotesk/mono typography without making retro styling the default or copying a source composition, wording, logo, or artwork. Produce both the final generation prompt and the generated raster image unless the user explicitly asks for prompt only.
1.9K StarsLast30days Skill
Research the last 30 days across Reddit, X, YouTube, Hacker News, Polymarket, GitHub, and the web, then synthesize a grounded brief for an AI agent.
61.0K StarsAcademic Research Skills
Academic Research Skills for Claude Code: research → write → review → revise → finalize
38.4K StarsGPT Researcher
Run autonomous deep research over web and local sources
28.0K StarsSandbox only
Install targets
Codex install prompt
Install the "blog-localize" agent skill from https://github.com/AgriciDaniel/claude-blog/tree/main/brain/.raw/sources/claude-blog-skill/skills/blog-localize. Read its SKILL.md or equivalent instructions first, install only the files needed for this workspace, and summarize any required setup before using it. Skill purpose: 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". After the install attempt, report the result to https://www.openagentskill.com/api/agent/outcome with POST JSON {"event_id":"install_<unique-id>","skill_slug":"agricidaniel-blog-localize","task":"Install blog-localize","agent":"codex","outcome":"success","install_used":true}. Replace event_id with a unique value and outcome with success or failed. Report success only after the skill is installed and a minimal verification passes.Supply asset profile
Deep research, source comparison, literature review, RAG, knowledge search, and reports.
Scenario
Research agents
I need my agent to research a topic, compare sources, and produce a concise report.
Agent fit
Claude Code + CLI + Codex
Codex, Claude Code, Cursor, CLI, or custom agents.
Install
Ready
npx skills add AgriciDaniel/claude-blog --skill blog-localize
Maintenance
fresh
9d since push
Risk
Risky
Permission surface may require sandboxing
GitHub quality
2.0K
80/100 Quality · 82/100 Trust
Coverage tags
Review notes
Permission surface may require sandboxing · Financial research output is not financial advice; require human review before any live investment decision
Agent adoption scorecard
These scores combine public repository metadata, OpenAgentSkill review signals, maintenance freshness, and install readiness. They are a shortlist signal, not a replacement for human review.
Quality
StrongSolid option that is likely worth shortlisting for production workflows.
Trust
Sandbox onlyUseful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
Audit
RiskyA machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
OpenAgentSkill Trust Score v5
Run only in a sandbox and compare close alternatives before using it for real work.
Stars
2.0K GitHub stars
Repo activity
2.0K stars, 333 forks
Maintenance
9d since push
License
MIT
Install
npx skills add AgriciDaniel/claude-blog --skill blog-localize
Install safety
Agent-readable metadata
Use this block or the embedded JSON to decide whether an agent should install this skill, choose an alternative, or ask for human review first.
Suited tasks
Suited agents
Install decision
Trust and risk
Outcome loop
Install command
npx skills add AgriciDaniel/claude-blog --skill blog-localizeDo not use when
Alternative
1.9K Stars
npx skills add yanliudesign/mono-color-skill --skill mono-color
Alternative
61.0K Stars
npx skills add mvanhorn/last30days-skill -g
Alternative
38.4K Stars
npx skills add Imbad0202/academic-research-skills
Alternative
28.0K Stars
npx skills add assafelovic/gpt-researcher
Agent safety v2
This skill should not be selected by an agent without explicit human security review.
Do not auto-install. Inspect the source, dependencies, and permission surface first.
high
Skill metadata references terminal, CLI, shell, subprocess, or command execution workflows.
medium
Skill may drive a browser or interact with web pages.
medium
Skill likely fetches remote pages, APIs, repositories, or external services.
medium
Skill may read or write project files, documents, generated artifacts, or local workspace state.
Agent resolve plan
The Resolve API returns the selected skill, alternatives, safety policy, audit notes, install target, and copy-paste prompt an agent can follow without scraping this page.
Open JSON
/api/agent/resolve?task=Use%20blog-localize%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Resolve text
/api/agent/resolve?task=Use%20blog-localize%20for%20an%20agent%20workflow&agent=codex&max_risk=medium&format=text
Install handoff
/api/skills/agricidaniel-blog-localize/install
Agent should check
Copy prompt
Task: Use blog-localize in this workspace.
Resolve first: https://www.openagentskill.com/api/agent/resolve?task=Use%20blog-localize%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Review install handoff: https://www.openagentskill.com/api/skills/agricidaniel-blog-localize/install
Install command: npx skills add AgriciDaniel/claude-blog --skill blog-localize
Before running it, summarize audit warnings, required permissions, and the fallback skill if install is risky.Agent handoff
Use the public install endpoint to fetch the command, safety checklist, target prompts, and canonical links for this skill.
Install handoff
/api/skills/agricidaniel-blog-localize/install
LLM text format
/api/skills/agricidaniel-blog-localize/install?format=text
Find alternatives
/api/skills/search?q=blog-localize&limit=3
Agent prompt
Use blog-localize for this task. Review https://www.openagentskill.com/api/skills/agricidaniel-blog-localize/install, then install with: npx skills add AgriciDaniel/claude-blog --skill blog-localizeRegistry metadata
This page exposes the same decision, trust, audit, use-case, and install signals through the Registry API, so agents can rank this skill without scraping the UI.
Manifest
/api/registry/manifest/agricidaniel-blog-localize
LLM text
/api/registry/manifest/agricidaniel-blog-localize?format=text
Install alias
/api/registry/install/agricidaniel-blog-localize
Recommend
/api/registry/recommend?task=Use%20blog-localize%20in%20an%20agent%20workflow&limit=3
Agent fit
Research agents
Use-case tags
Platforms
Claude Code
Audit report
A machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
Agent decision cockpit
Use this as a leading candidate, then validate the README and install path in your own agent stack.
Role in stack
Primary pick
Primary fit
Research agents
Trust label
Production-ready
Install path
Command ready
Use when
Evidence
review first
Implementation path
Trust profile
Useful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
GitHub adoption
PASS2.0K GitHub stars
Stars/forks activity
PASS2.0K stars, 333 forks; issue activity unavailable in current metadata
Recent maintenance
PASS9d since push
License clarity
PASSMIT
Good signals
Review before install
Recommended action
Run only in a sandbox and compare close alternatives before using it for real work.
Quality profile
Solid option that is likely worth shortlisting for production workflows.
Workflow fit
Investigate faster
I need my agent to research a topic, compare sources, and produce a concise report.
Manage repositories
I need my agent to triage GitHub issues, review pull requests, and summarize repository changes.
Publish consistently
I need my agent to turn research and product updates into useful content drafts.
Workflow fit
Find, compare, and synthesize
A workflow for agents that gather sources, compare claims, summarize long material, and draft useful research briefs.
Turn skills into distribution
A workflow for turning newly indexed skills into SEO briefs, social drafts, comparison pages, and reusable publishing workflows.
Inspect, patch, and verify code
A workflow for software agents that inspect repositories, review pull requests, generate tests, and turn findings into shippable patches.
Alternative shortlist
Similar skills that may fit this task.
Generate original one-ink or controlled two-ink editorial images from any theme, sentence, article idea, object, or reference photo. Always use this skill when the user asks for 单色海报、双色印刷、单色调视觉、蓝色/绿色孔版印刷、risograph、网点照片、复古或当代编辑排版、zine poster, monochrome editorial poster, duotone print, or asks to use the mono-color style. It uses an adaptive white, gray, or pale-beige substrate, no more than two printing inks, active negative space, terse human language, and strong serif/grotesk/mono typography without making retro styling the default or copying a source composition, wording, logo, or artwork. Produce both the final generation prompt and the generated raster image unless the user explicitly asks for prompt only.
Research the last 30 days across Reddit, X, YouTube, Hacker News, Polymarket, GitHub, and the web, then synthesize a grounded brief for an AI agent.
Academic Research Skills for Claude Code: research → write → review → revise → finalize
Run autonomous deep research over web and local sources
--- name: blog-localize description: > 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". user-invokable: true argument-hint: "<file> --locale <locale-code>" license: MIT compatibility: Standalone within claude-blog. Invoked by blog-multilingual. metadata: author: AgriciDaniel version: "1.11.0" category: blog ---
# Blog Localize, Cultural Deep-Adaptation
Takes a translated blog post and performs cultural adaptation so the result feels like it was written for the target market, not translated into it. This is the layer above `blog-translate`: it replaces examples, adjusts tone, swaps references, and localizes the entire reading experience.
> Adapted from `claude-blog-multilingual` by Chris Mueller (Pro Hub Challenge, > March 2026). Original: https://github.com/Chriss54/multilingual-int
## Key References
- `../blog-translate/references/cultural-adaptation.md`, the shared cultural profiles file with substitution tables for DACH, Francophone, Hispanic, Japanese, and a custom template. Do not duplicate this file.
## When to Use
- Right after `blog-translate` produces a base translation. - When existing translated content reads like "translated from English". - When targeting a specific market, not just a language. - When content needs local statistics, examples, and brand references.
## Workflow
### Phase 1: Locale Understanding
1. Parse the locale code with the shared multilingual locale rules used by `blog-translate`, `blog-multilingual`, and `blog-locale-audit`: ISO 639-1 language in lowercase, optional ISO 15924 script in title case, optional ISO 3166-1 Alpha-2 region in uppercase. Accept full codes (`de-DE`, `fr-CA`, `es-MX`, `pt-BR`, `zh-Hant`) and unambiguous plain language codes (`de`, `fr`). Require a region or explicit neutral mode for ambiguous language-only targets such as `es`, `pt`, and `zh`. 2. Load the cultural profile from `../blog-translate/references/cultural-adaptation.md`. - If the locale has a profile, use it. - If not, follow the "Custom-locale template" section in that reference to build a minimal profile inline. 3. Read the translated post only after resolving it inside the project root/current working directory. Reject symlinked paths, traversal outside the root, files over 10 MB, and binary files. Then identify adaptation targets.
### Phase 2: Cultural Audit
Scan for elements that signal foreign origin:
| Element | What to look for | |---------|------------------| | Brand examples | US or UK brands with no relevance locally | | Statistics sources | US-only studies and surveys | | CTAs | American-style aggressive calls-to-action | | Idioms | Literally translated English expressions | | Legal references | Foreign laws (CCPA, FTC) where local law applies (DSGVO, RGPD) | | Cultural references | Foreign holidays, events, customs | | Currency and pricing | USD without conversion or context | | Tone | Too casual or too formal for the target market | | Address form | Inconsistent Sie/du, tu/vous, formal/informal |
Output an audit report listing every target with severity (critical, recommended, optional).
### Phase 3: Adaptation
#### 3a. Example Substitution
Swap foreign examples for local equivalents:
- Use WebSearch to find local case studies, brands, or scenarios. - Replace inline, preserving the same argument and structure. - Record source URL, access date, and rationale for every non-obvious local replacement. - If no local equivalent exists, keep the original but add local context ("In the German market, the equivalent dynamic is X").
#### 3b. Statistics Localization
- Use primary or high-quality local sources for replacement statistics: national statistics offices, regulators, official industry bodies, academic datasets, or named research reports with methodology. - Do not rely on generic WebSearch snippets as evidence. Fetch the cited page, verify the figure and context, and record the source URL and date. - Fetch cited pages only after SSRF checks: allow `https` URLs only; reject `javascript:`, `data:`, `file:`, localhost, loopback, private, link-local, multicast, and reserved IPs after DNS resolution; disable redirects or validate the final URL with the same checks; cap redirects, response size, and request time; log the final URL and access date. - If local data exists with comparable methodology, swap the source and the figure together. Keep one named source per claim. - If local data is related but uses a different methodology or timeframe, do not silently swap it. Keep the original claim scoped, or rewrite the claim to match the local source. - If not, keep the original stat but mark its geographic scope ("In the US, ..."). - Never strip source attribution.
#### 3c. CTA Adaptation
Rewrite calls-to-action per the cultural profile:
- Adjust aggressiveness level (DACH and JA prefer informational, US prefers imperative). - Use culturally appropriate action verbs. - Adapt urgency framing.
#### 3d. Tone Calibration
- Match formality per profile (DACH defaults to Sie for B2B, du for B2C lifestyle; FR defaults to vous; JA shifts register sharply by audience). - Ensure consistent formal or informal address throughout the entire document. - Match local content-style conventions.
#### 3e. Legal and Regulatory Context
- Map legal references by issue and jurisdiction. Keep the original law when the claim is specifically about US compliance. Only substitute when the local law addresses the same issue, such as CCPA to DSGVO in DE, RGPD in FR, LGPD in BR, LFPDPPP in MX, Ley 1581 in CO, or Ley 25.326 in AR. - Add local compliance notes where they help the reader. - Remove irrelevant foreign regulatory references.
#### 3f. Brand Example Swaps (Quick Map)
Profiles in `../blog-translate/references/cultural-adaptation.md` provide substitution tables. Common examples:
| Source (US) | DACH | FR | ES (Spain) | LATAM | JA | |-------------|------|----|----|-------|----| | Walmart | MediaMarkt | Carrefour | El Corte Inglés | Walmart MX | Aeon | | Target | Saturn | Auchan | Hipercor | Liverpool | Ito-Yokado | | FTC | Bundeskartellamt | DGCCRF | CNMC | PROFECO (MX) | JFTC | | CCPA | DSGVO | RGPD | RGPD | LFPDPPP (MX), Ley 1581 (CO), Ley 25.326 (AR), LGPD (BR) | APPI |
### Phase 4: Quality Verification
- All critical adaptation targets addressed. - Tone is consistent throughout. - No remaining foreign-origin markers. - Statistics have valid sources (original or localized). - CTAs match cultural expectations. - Formal or informal address is consistent end to end. - Content still supports the same argument as the original. - SEO elements remain optimized beyond keyword placement: localized title and meta, heading intent, slug, alt text, internal-link anchors, same-language canonical, hreflang compatibility, and schema `inLanguage`. - Word count is within the expected ratio for the language pair.
### Phase 5: Save and Report
1. Save the localized version. Default: write a reviewed copy as `{slug}-localized.{ext}`. Only overwrite the translated file when the user asks for overwrite; before overwriting, create a timestamped backup and show a diff summary. Resolve every output path inside the project root and reject traversal, symlinked paths, or writes outside that root.
2. Present the summary:
``` ## Localization complete: [Title]
### Target locale: [locale-code] ([locale-name])
### Adaptations made | Type | Count | Examples | |------|-------|----------| | Brand examples | [N] | Walmart -> MediaMarkt | | Statistics | [N] | US survey -> DACH survey | | CTAs | [N] | "Buy now" -> "Jetzt entdecken" | | Tone adjustments | [N] | Casual -> Sie | | Legal references | [N] | CCPA -> DSGVO | | Cultural references | [N] | Thanksgiving -> Weihnachtsgeschaeft |
### Cultural fit score - Naturalness: [1-10] - Market relevance: [1-10] - Tone match: [1-10] - Overall: [N]/30
### Remaining recommendations - [Optional adaptations not applied] ```
## Error Handling
| Scenario | Action | |----------|--------| | No cultural profile for the locale | Build a minimal profile from the custom-locale template, proceed | | File is not in the expected language | Warn the user, offer to translate first | | No local statistics available | Keep the original stat with a geographic-scope note | | Locale code ambiguous (e.g., `pt`) | Ask: "Did you mean `pt-BR` (Brazil) or `pt-PT` (Portugal)?" |
## Cross-References
- Pre-step (translation): `/blog translate <file> --to <code>` - QA across language versions: `/blog locale-audit <directory>` - One-command pipeline: `/blog multilingual <topic> --languages <codes>`
Source provenance
Decision snapshot
2,016 GitHub stars
Audit
Install and adoption review
Agent-proven evidence
Outcome reports after resolve, review, install, and one narrow run.
No agent outcome data yet. The first agent run can report success, setup needs, risk blocks, failure, or not-relevant through /api/agent/outcome.
Install
Free and open source. Review the report before installing into production agents.
Growth loop
Scenario-led draft for blog-localize, ready for a manual X post.
blog-localize: Cultural adaptation for translated content. Run AFTER blog-translate completes. Adjusts brand... 2.0K stars https://www.openagentskill.com/skills/agricidaniel-blog-localize?ref=x
Listing + install path for blog-localize: https://www.openagentskill.com/skills/agricidaniel-blog-localize?ref=x Install: npx skills add AgriciDaniel/claude-blog --skill blog-localize
Listing source
This listing was indexed from public sources and is not marked official until a maintainer claim is approved.
Attribution links to the public repository or creator profile. Creators can claim the listing to update ownership signals.
Claim this skillOwner claim
This Registry indexed listing is attributed to AgriciDaniel but is not marked official yet. Claim it to add a verified owner signal and make future launch, install, and audit updates easier to trust.
Creator backlink kit
Show the canonical listing, current trust and audit signals, and real Agent-Proven evidence where developers evaluate the repository.
[](https://www.openagentskill.com/skills/agricidaniel-blog-localize?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/agricidaniel-blog-localize?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/agricidaniel-blog-localize/audit)
[](https://www.openagentskill.com/skills/agricidaniel-blog-localize?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)AgriciDaniel
@agricidaniel
Share whether this skill looks useful for your agent workflow. Aggregated feedback improves rankings over time.
Sandbox only
mono-color
Generate original one-ink or controlled two-ink editorial images from any theme, sentence, article idea, object, or reference photo. Always use this skill when the user asks for 单色海报、双色印刷、单色调视觉、蓝色/绿色孔版印刷、risograph、网点照片、复古或当代编辑排版、zine poster, monochrome editorial poster, duotone print, or asks to use the mono-color style. It uses an adaptive white, gray, or pale-beige substrate, no more than two printing inks, active negative space, terse human language, and strong serif/grotesk/mono typography without making retro styling the default or copying a source composition, wording, logo, or artwork. Produce both the final generation prompt and the generated raster image unless the user explicitly asks for prompt only.
1.9K StarsLast30days Skill
Research the last 30 days across Reddit, X, YouTube, Hacker News, Polymarket, GitHub, and the web, then synthesize a grounded brief for an AI agent.
61.0K StarsAcademic Research Skills
Academic Research Skills for Claude Code: research → write → review → revise → finalize
38.4K StarsGPT Researcher
Run autonomous deep research over web and local sources
28.0K StarsSandbox only
Install targets
Codex install prompt
Install the "blog-localize" agent skill from https://github.com/AgriciDaniel/claude-blog/tree/main/brain/.raw/sources/claude-blog-skill/skills/blog-localize. Read its SKILL.md or equivalent instructions first, install only the files needed for this workspace, and summarize any required setup before using it. Skill purpose: 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". After the install attempt, report the result to https://www.openagentskill.com/api/agent/outcome with POST JSON {"event_id":"install_<unique-id>","skill_slug":"agricidaniel-blog-localize","task":"Install blog-localize","agent":"codex","outcome":"success","install_used":true}. Replace event_id with a unique value and outcome with success or failed. Report success only after the skill is installed and a minimal verification passes.Supply asset profile
Deep research, source comparison, literature review, RAG, knowledge search, and reports.
Scenario
Research agents
I need my agent to research a topic, compare sources, and produce a concise report.
Agent fit
Claude Code + CLI + Codex
Codex, Claude Code, Cursor, CLI, or custom agents.
Install
Ready
npx skills add AgriciDaniel/claude-blog --skill blog-localize
Maintenance
fresh
9d since push
Risk
Risky
Permission surface may require sandboxing
GitHub quality
2.0K
80/100 Quality · 82/100 Trust
Coverage tags
Review notes
Permission surface may require sandboxing · Financial research output is not financial advice; require human review before any live investment decision
Agent adoption scorecard
These scores combine public repository metadata, OpenAgentSkill review signals, maintenance freshness, and install readiness. They are a shortlist signal, not a replacement for human review.
Quality
StrongSolid option that is likely worth shortlisting for production workflows.
Trust
Sandbox onlyUseful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
Audit
RiskyA machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
OpenAgentSkill Trust Score v5
Run only in a sandbox and compare close alternatives before using it for real work.
Stars
2.0K GitHub stars
Repo activity
2.0K stars, 333 forks
Maintenance
9d since push
License
MIT
Install
npx skills add AgriciDaniel/claude-blog --skill blog-localize
Install safety
Agent-readable metadata
Use this block or the embedded JSON to decide whether an agent should install this skill, choose an alternative, or ask for human review first.
Suited tasks
Suited agents
Install decision
Trust and risk
Outcome loop
Install command
npx skills add AgriciDaniel/claude-blog --skill blog-localizeDo not use when
Alternative
1.9K Stars
npx skills add yanliudesign/mono-color-skill --skill mono-color
Alternative
61.0K Stars
npx skills add mvanhorn/last30days-skill -g
Alternative
38.4K Stars
npx skills add Imbad0202/academic-research-skills
Alternative
28.0K Stars
npx skills add assafelovic/gpt-researcher
Agent safety v2
This skill should not be selected by an agent without explicit human security review.
Do not auto-install. Inspect the source, dependencies, and permission surface first.
high
Skill metadata references terminal, CLI, shell, subprocess, or command execution workflows.
medium
Skill may drive a browser or interact with web pages.
medium
Skill likely fetches remote pages, APIs, repositories, or external services.
medium
Skill may read or write project files, documents, generated artifacts, or local workspace state.
Agent resolve plan
The Resolve API returns the selected skill, alternatives, safety policy, audit notes, install target, and copy-paste prompt an agent can follow without scraping this page.
Open JSON
/api/agent/resolve?task=Use%20blog-localize%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Resolve text
/api/agent/resolve?task=Use%20blog-localize%20for%20an%20agent%20workflow&agent=codex&max_risk=medium&format=text
Install handoff
/api/skills/agricidaniel-blog-localize/install
Agent should check
Copy prompt
Task: Use blog-localize in this workspace.
Resolve first: https://www.openagentskill.com/api/agent/resolve?task=Use%20blog-localize%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Review install handoff: https://www.openagentskill.com/api/skills/agricidaniel-blog-localize/install
Install command: npx skills add AgriciDaniel/claude-blog --skill blog-localize
Before running it, summarize audit warnings, required permissions, and the fallback skill if install is risky.Agent handoff
Use the public install endpoint to fetch the command, safety checklist, target prompts, and canonical links for this skill.
Install handoff
/api/skills/agricidaniel-blog-localize/install
LLM text format
/api/skills/agricidaniel-blog-localize/install?format=text
Find alternatives
/api/skills/search?q=blog-localize&limit=3
Agent prompt
Use blog-localize for this task. Review https://www.openagentskill.com/api/skills/agricidaniel-blog-localize/install, then install with: npx skills add AgriciDaniel/claude-blog --skill blog-localizeRegistry metadata
This page exposes the same decision, trust, audit, use-case, and install signals through the Registry API, so agents can rank this skill without scraping the UI.
Manifest
/api/registry/manifest/agricidaniel-blog-localize
LLM text
/api/registry/manifest/agricidaniel-blog-localize?format=text
Install alias
/api/registry/install/agricidaniel-blog-localize
Recommend
/api/registry/recommend?task=Use%20blog-localize%20in%20an%20agent%20workflow&limit=3
Agent fit
Research agents
Use-case tags
Platforms
Claude Code
Audit report
A machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
Agent decision cockpit
Use this as a leading candidate, then validate the README and install path in your own agent stack.
Role in stack
Primary pick
Primary fit
Research agents
Trust label
Production-ready
Install path
Command ready
Use when
Evidence
review first
Implementation path
Trust profile
Useful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
GitHub adoption
PASS2.0K GitHub stars
Stars/forks activity
PASS2.0K stars, 333 forks; issue activity unavailable in current metadata
Recent maintenance
PASS9d since push
License clarity
PASSMIT
Good signals
Review before install
Recommended action
Run only in a sandbox and compare close alternatives before using it for real work.
Quality profile
Solid option that is likely worth shortlisting for production workflows.
Workflow fit
Investigate faster
I need my agent to research a topic, compare sources, and produce a concise report.
Manage repositories
I need my agent to triage GitHub issues, review pull requests, and summarize repository changes.
Publish consistently
I need my agent to turn research and product updates into useful content drafts.
Workflow fit
Find, compare, and synthesize
A workflow for agents that gather sources, compare claims, summarize long material, and draft useful research briefs.
Turn skills into distribution
A workflow for turning newly indexed skills into SEO briefs, social drafts, comparison pages, and reusable publishing workflows.
Inspect, patch, and verify code
A workflow for software agents that inspect repositories, review pull requests, generate tests, and turn findings into shippable patches.
Alternative shortlist
Similar skills that may fit this task.
Generate original one-ink or controlled two-ink editorial images from any theme, sentence, article idea, object, or reference photo. Always use this skill when the user asks for 单色海报、双色印刷、单色调视觉、蓝色/绿色孔版印刷、risograph、网点照片、复古或当代编辑排版、zine poster, monochrome editorial poster, duotone print, or asks to use the mono-color style. It uses an adaptive white, gray, or pale-beige substrate, no more than two printing inks, active negative space, terse human language, and strong serif/grotesk/mono typography without making retro styling the default or copying a source composition, wording, logo, or artwork. Produce both the final generation prompt and the generated raster image unless the user explicitly asks for prompt only.
Research the last 30 days across Reddit, X, YouTube, Hacker News, Polymarket, GitHub, and the web, then synthesize a grounded brief for an AI agent.
Academic Research Skills for Claude Code: research → write → review → revise → finalize
Run autonomous deep research over web and local sources
--- name: blog-localize description: > 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". user-invokable: true argument-hint: "<file> --locale <locale-code>" license: MIT compatibility: Standalone within claude-blog. Invoked by blog-multilingual. metadata: author: AgriciDaniel version: "1.11.0" category: blog ---
# Blog Localize, Cultural Deep-Adaptation
Takes a translated blog post and performs cultural adaptation so the result feels like it was written for the target market, not translated into it. This is the layer above `blog-translate`: it replaces examples, adjusts tone, swaps references, and localizes the entire reading experience.
> Adapted from `claude-blog-multilingual` by Chris Mueller (Pro Hub Challenge, > March 2026). Original: https://github.com/Chriss54/multilingual-int
## Key References
- `../blog-translate/references/cultural-adaptation.md`, the shared cultural profiles file with substitution tables for DACH, Francophone, Hispanic, Japanese, and a custom template. Do not duplicate this file.
## When to Use
- Right after `blog-translate` produces a base translation. - When existing translated content reads like "translated from English". - When targeting a specific market, not just a language. - When content needs local statistics, examples, and brand references.
## Workflow
### Phase 1: Locale Understanding
1. Parse the locale code with the shared multilingual locale rules used by `blog-translate`, `blog-multilingual`, and `blog-locale-audit`: ISO 639-1 language in lowercase, optional ISO 15924 script in title case, optional ISO 3166-1 Alpha-2 region in uppercase. Accept full codes (`de-DE`, `fr-CA`, `es-MX`, `pt-BR`, `zh-Hant`) and unambiguous plain language codes (`de`, `fr`). Require a region or explicit neutral mode for ambiguous language-only targets such as `es`, `pt`, and `zh`. 2. Load the cultural profile from `../blog-translate/references/cultural-adaptation.md`. - If the locale has a profile, use it. - If not, follow the "Custom-locale template" section in that reference to build a minimal profile inline. 3. Read the translated post only after resolving it inside the project root/current working directory. Reject symlinked paths, traversal outside the root, files over 10 MB, and binary files. Then identify adaptation targets.
### Phase 2: Cultural Audit
Scan for elements that signal foreign origin:
| Element | What to look for | |---------|------------------| | Brand examples | US or UK brands with no relevance locally | | Statistics sources | US-only studies and surveys | | CTAs | American-style aggressive calls-to-action | | Idioms | Literally translated English expressions | | Legal references | Foreign laws (CCPA, FTC) where local law applies (DSGVO, RGPD) | | Cultural references | Foreign holidays, events, customs | | Currency and pricing | USD without conversion or context | | Tone | Too casual or too formal for the target market | | Address form | Inconsistent Sie/du, tu/vous, formal/informal |
Output an audit report listing every target with severity (critical, recommended, optional).
### Phase 3: Adaptation
#### 3a. Example Substitution
Swap foreign examples for local equivalents:
- Use WebSearch to find local case studies, brands, or scenarios. - Replace inline, preserving the same argument and structure. - Record source URL, access date, and rationale for every non-obvious local replacement. - If no local equivalent exists, keep the original but add local context ("In the German market, the equivalent dynamic is X").
#### 3b. Statistics Localization
- Use primary or high-quality local sources for replacement statistics: national statistics offices, regulators, official industry bodies, academic datasets, or named research reports with methodology. - Do not rely on generic WebSearch snippets as evidence. Fetch the cited page, verify the figure and context, and record the source URL and date. - Fetch cited pages only after SSRF checks: allow `https` URLs only; reject `javascript:`, `data:`, `file:`, localhost, loopback, private, link-local, multicast, and reserved IPs after DNS resolution; disable redirects or validate the final URL with the same checks; cap redirects, response size, and request time; log the final URL and access date. - If local data exists with comparable methodology, swap the source and the figure together. Keep one named source per claim. - If local data is related but uses a different methodology or timeframe, do not silently swap it. Keep the original claim scoped, or rewrite the claim to match the local source. - If not, keep the original stat but mark its geographic scope ("In the US, ..."). - Never strip source attribution.
#### 3c. CTA Adaptation
Rewrite calls-to-action per the cultural profile:
- Adjust aggressiveness level (DACH and JA prefer informational, US prefers imperative). - Use culturally appropriate action verbs. - Adapt urgency framing.
#### 3d. Tone Calibration
- Match formality per profile (DACH defaults to Sie for B2B, du for B2C lifestyle; FR defaults to vous; JA shifts register sharply by audience). - Ensure consistent formal or informal address throughout the entire document. - Match local content-style conventions.
#### 3e. Legal and Regulatory Context
- Map legal references by issue and jurisdiction. Keep the original law when the claim is specifically about US compliance. Only substitute when the local law addresses the same issue, such as CCPA to DSGVO in DE, RGPD in FR, LGPD in BR, LFPDPPP in MX, Ley 1581 in CO, or Ley 25.326 in AR. - Add local compliance notes where they help the reader. - Remove irrelevant foreign regulatory references.
#### 3f. Brand Example Swaps (Quick Map)
Profiles in `../blog-translate/references/cultural-adaptation.md` provide substitution tables. Common examples:
| Source (US) | DACH | FR | ES (Spain) | LATAM | JA | |-------------|------|----|----|-------|----| | Walmart | MediaMarkt | Carrefour | El Corte Inglés | Walmart MX | Aeon | | Target | Saturn | Auchan | Hipercor | Liverpool | Ito-Yokado | | FTC | Bundeskartellamt | DGCCRF | CNMC | PROFECO (MX) | JFTC | | CCPA | DSGVO | RGPD | RGPD | LFPDPPP (MX), Ley 1581 (CO), Ley 25.326 (AR), LGPD (BR) | APPI |
### Phase 4: Quality Verification
- All critical adaptation targets addressed. - Tone is consistent throughout. - No remaining foreign-origin markers. - Statistics have valid sources (original or localized). - CTAs match cultural expectations. - Formal or informal address is consistent end to end. - Content still supports the same argument as the original. - SEO elements remain optimized beyond keyword placement: localized title and meta, heading intent, slug, alt text, internal-link anchors, same-language canonical, hreflang compatibility, and schema `inLanguage`. - Word count is within the expected ratio for the language pair.
### Phase 5: Save and Report
1. Save the localized version. Default: write a reviewed copy as `{slug}-localized.{ext}`. Only overwrite the translated file when the user asks for overwrite; before overwriting, create a timestamped backup and show a diff summary. Resolve every output path inside the project root and reject traversal, symlinked paths, or writes outside that root.
2. Present the summary:
``` ## Localization complete: [Title]
### Target locale: [locale-code] ([locale-name])
### Adaptations made | Type | Count | Examples | |------|-------|----------| | Brand examples | [N] | Walmart -> MediaMarkt | | Statistics | [N] | US survey -> DACH survey | | CTAs | [N] | "Buy now" -> "Jetzt entdecken" | | Tone adjustments | [N] | Casual -> Sie | | Legal references | [N] | CCPA -> DSGVO | | Cultural references | [N] | Thanksgiving -> Weihnachtsgeschaeft |
### Cultural fit score - Naturalness: [1-10] - Market relevance: [1-10] - Tone match: [1-10] - Overall: [N]/30
### Remaining recommendations - [Optional adaptations not applied] ```
## Error Handling
| Scenario | Action | |----------|--------| | No cultural profile for the locale | Build a minimal profile from the custom-locale template, proceed | | File is not in the expected language | Warn the user, offer to translate first | | No local statistics available | Keep the original stat with a geographic-scope note | | Locale code ambiguous (e.g., `pt`) | Ask: "Did you mean `pt-BR` (Brazil) or `pt-PT` (Portugal)?" |
## Cross-References
- Pre-step (translation): `/blog translate <file> --to <code>` - QA across language versions: `/blog locale-audit <directory>` - One-command pipeline: `/blog multilingual <topic> --languages <codes>`
Source provenance
Decision snapshot
2,016 GitHub stars
Audit
Install and adoption review
Agent-proven evidence
Outcome reports after resolve, review, install, and one narrow run.
No agent outcome data yet. The first agent run can report success, setup needs, risk blocks, failure, or not-relevant through /api/agent/outcome.
Install
Free and open source. Review the report before installing into production agents.
Growth loop
Scenario-led draft for blog-localize, ready for a manual X post.
blog-localize: Cultural adaptation for translated content. Run AFTER blog-translate completes. Adjusts brand... 2.0K stars https://www.openagentskill.com/skills/agricidaniel-blog-localize?ref=x
Listing + install path for blog-localize: https://www.openagentskill.com/skills/agricidaniel-blog-localize?ref=x Install: npx skills add AgriciDaniel/claude-blog --skill blog-localize
Listing source
This listing was indexed from public sources and is not marked official until a maintainer claim is approved.
Attribution links to the public repository or creator profile. Creators can claim the listing to update ownership signals.
Claim this skillOwner claim
This Registry indexed listing is attributed to AgriciDaniel but is not marked official yet. Claim it to add a verified owner signal and make future launch, install, and audit updates easier to trust.
Creator backlink kit
Show the canonical listing, current trust and audit signals, and real Agent-Proven evidence where developers evaluate the repository.
[](https://www.openagentskill.com/skills/agricidaniel-blog-localize?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/agricidaniel-blog-localize?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/agricidaniel-blog-localize/audit)
[](https://www.openagentskill.com/skills/agricidaniel-blog-localize?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)AgriciDaniel
@agricidaniel
Share whether this skill looks useful for your agent workflow. Aggregated feedback improves rankings over time.
Sandbox only
mono-color
Generate original one-ink or controlled two-ink editorial images from any theme, sentence, article idea, object, or reference photo. Always use this skill when the user asks for 单色海报、双色印刷、单色调视觉、蓝色/绿色孔版印刷、risograph、网点照片、复古或当代编辑排版、zine poster, monochrome editorial poster, duotone print, or asks to use the mono-color style. It uses an adaptive white, gray, or pale-beige substrate, no more than two printing inks, active negative space, terse human language, and strong serif/grotesk/mono typography without making retro styling the default or copying a source composition, wording, logo, or artwork. Produce both the final generation prompt and the generated raster image unless the user explicitly asks for prompt only.
1.9K StarsLast30days Skill
Research the last 30 days across Reddit, X, YouTube, Hacker News, Polymarket, GitHub, and the web, then synthesize a grounded brief for an AI agent.
61.0K StarsAcademic Research Skills
Academic Research Skills for Claude Code: research → write → review → revise → finalize
38.4K StarsGPT Researcher
Run autonomous deep research over web and local sources
28.0K StarsPermission surface
shell or command execution, filesystem or document access
Agent outcomes
No agent outcome data yet
Docs
Strong README/SKILL.md context
Risk summary
Install readiness
Permission surface
shell or command execution, filesystem or document access
Agent outcomes
No agent outcome data yet
Docs
Strong README/SKILL.md context
Risk summary
Install readiness
Permission surface
shell or command execution, filesystem or document access
Agent outcomes
No agent outcome data yet
Docs
Strong README/SKILL.md context
Risk summary
Install readiness
Permission surface
shell or command execution, filesystem or document access
Agent outcomes
No agent outcome data yet
Docs
Strong README/SKILL.md context
Risk summary
Install readiness