i18n (Internationalization) guideline skills for nextjs web development

Internationalization (i18n) guide for Next.js / Node.js web applications using the App Router. Covers translation file structure, locale routing, SEO metadat...

This guide appears coherent and safe for implementing i18n in a Next.js App Router project. Before applying it: 1) Ensure your project matches the App Router structure the guide assumes (src/app/[lang], server vs client components). 2) If you set NEXT_PUBLIC_APP_URL in env, confirm it's the correct public base URL; the examples fall back to a literal default if the env var is missing. 3) Watch out for XSS: structured-data examples use JSON.stringify (safe), but avoid placing untrusted HTML into dangerouslySetInnerHTML or translation strings that may contain markup. 4) The guide recommends never using machine translation for production copy — follow your org's localization and review processes. If you need the skill to perform any automated actions (editing files, running scripts), require an explicit install or code-based tool instead of following the prose directly.

Type: OpenClaw Skill Name: web-i18n-nextjs Version: 1.0.0 The skill bundle is primarily documentation and code examples for Next.js i18n. It is classified as 'suspicious' due to potential XSS vulnerabilities arising from the use of `dangerouslySetInnerHTML` for JSON-LD structured data (in `references/structured-data.md`) and basic string `.replace()` for template variable substitution (in `references/translation-files.md`). While these patterns are common, they can be exploited if the data being rendered or substituted (e.g., from dictionaries, CMS, or user input) is not properly sanitized, allowing for script injection. There is no evidence of intentional malicious behavior, data exfiltration, or prompt injection against the agent; the identified issues are vulnerabilities rather than malware.