Skills i18n-localization
๐Ÿ“ฆ

i18n-localization

Content revision r2 Safe โš™๏ธ External commands

Audit and Improve Application Localization

Hardcoded text and incomplete locale files create inconsistent multilingual experiences. This skill reviews localization structure, detects common gaps, and recommends practical i18n patterns.

Supports: Claude Codex Code(CC)
๐Ÿ“Š 75 Adequate

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "i18n-localization" from https://skillstore.io/skills/sickn33-i18n-localization.md and its manifest at https://skillstore.io/api/skills/sickn33-i18n-localization/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Test it

Using "i18n-localization". Review the checkout interface for hardcoded text.

Expected outcome:

  • CheckoutPage.tsx contains three likely hardcoded labels.
  • Move each label into the checkout namespace.
  • Use stable keys for the title, submit action, and delivery message.

Using "i18n-localization". Compare English, Turkish, and Arabic locale files.

Expected outcome:

  • Turkish is missing two authentication keys.
  • Arabic has one extra checkout key.
  • Review Arabic screens in RTL mode after aligning the key sets.

Using "i18n-localization". Recommend safer date and number localization.

Expected outcome:

Use locale-aware formatters for dates, currencies, and counts. Define fallback locales and test representative values for every supported region.

Security Audit

Safe
v5 โ€ข 7/24/2026 Open versioned report

All 13 static findings are false positives after source review. The high findings confuse Python dictionary keys with certificate files. The medium findings identify Markdown fences and inline command documentation, not executable Ruby or shell backticks.

2
Files scanned
407
Lines analyzed
0
Review items
0
False positives ignored
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History โ†’
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/sickn33-i18n-localization/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/sickn33-i18n-localization/security.svg)](https://skillstore.io/skills/sickn33-i18n-localization?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/sickn33-i18n-localization?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-i18n-localization/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/sickn33-i18n-localization.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA ยท BibTeX ยท CFF)

APA citation

sickn33. (2026). i18n-localization security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-i18n-localization/audits/5

BibTeX citation

@techreport{sickn33-sickn33-i18n-localization-2026, author = {sickn33}, title = {i18n-localization security audit report (audit version 5)}, institution = {Skillstore}, year = {2026}, number = {5}, url = {https://skillstore.io/skills/sickn33-i18n-localization/audits/5}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "i18n-localization security audit report (audit version 5)" version: "unspecified" type: report authors: - name: "sickn33" date-released: "2026-07-24" url: "https://skillstore.io/skills/sickn33-i18n-localization/audits/5" identifiers: - type: other value: "skillstore:sickn33-i18n-localization:audit:5" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High
45
Architecture
85
Maintainability
87
Content
69
Community
83
Spec Compliance

What You Can Build

Prepare a Web Application

Review components, locale files, formatting, and RTL behavior before a multilingual release.

Check Translation Coverage

Compare locale key sets and identify missing or extra entries across supported languages.

Establish i18n Standards

Define translation namespaces, fallback rules, formatting patterns, and release checks for a product team.

Try These Prompts

Find Hardcoded Text
Review [project path] for hardcoded user-facing text and list each likely issue with its file and recommended translation key.
Compare Locale Keys
Compare locale files under [locale path], using [base locale] as the reference, and summarize missing or extra keys by language.
Review Locale Behavior
Assess pluralization, date and number formatting, fallback behavior, and RTL support for [framework] and [supported locales].
Plan an i18n Migration
Design a phased migration for [application], covering key structure, framework integration, locale resources, automated checks, fallback policy, and RTL testing.

Best Practices

  • Use stable translation keys grouped by feature namespace.
  • Apply locale-aware plural, date, number, and currency formatting.
  • Test fallback locales, long text, and RTL layouts before release.

Avoid

  • Do not concatenate translated fragments into complete sentences.
  • Do not assume every language uses the same text length or direction.
  • Do not treat automated key checks as linguistic quality review.

Frequently Asked Questions

Which frameworks does this skill cover?
It includes patterns for React, Next.js, Vue, Python gettext, and generic locale file structures.
Can it find hardcoded strings automatically?
Yes. The included checker uses regular expressions for common React, Vue, and Python patterns.
Does it compare translation completeness?
Yes. It compares flattened keys across JSON locale files grouped by language directory.
Does it translate content?
No. It supports localization structure and review, but professional translators should verify language quality.
Can it validate RTL layouts?
It recommends logical CSS properties and RTL checks, but visual validation still requires application testing.
Will the checker modify project files?
No. The included script reads matching files and prints findings without writing changes.

Developer Details

Author

sickn33

License

MIT

Skillstore revision

r2

Version notice

The author did not declare a version.

Ref

88a8e9a07f4c54ab105c1c41b6267c287146b07b

Maintenance freshness

7/26/2026

Usage

6 downloads ยท 108 views

File structure

๐Ÿ“ scripts/

๐Ÿ“„ i18n_checker.py

๐Ÿ“„ SKILL.md

More from sickn33

View all
View all