Install
$ agentstack add skill-sourav15mukherjee-skillforge-free-skills-i18n-helper ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
i18n/Localization Helper
Extract hardcoded strings, generate locale files, and validate translation completeness across languages.
Workflow
- Detect the i18n framework in use
``bash grep -E "i18next|react-intl|vue-i18n|next-intl|@formatjs" package.json 2>/dev/null ` Check for config files: i18n.ts, next.config.js with i18n key, src/locales/`. If no framework found, recommend one and help set it up.
- Discover existing locale files
``bash find . -maxdepth 4 \( -name "*.json" -o -name "*.yaml" \) -path "*/locale*" -o -path "*/i18n/*" -o -path "*/translations/*" | grep -v node_modules `` Parse each file, build key inventory per language. Note structure: flat vs nested keys.
- Scan source code for hardcoded strings
Find user-facing strings in JSX text, component props, toast/alert calls, page titles, form validation messages. Exclude: CSS classes, console.log, import paths, test strings, URLs.
- Generate translation keys
Naming convention: page.section.element `` "Welcome back" → common.welcomeBack "Submit" → common.buttons.submit "Email is required" → forms.validation.emailRequired ``
- Extract and update source code
Replace hardcoded strings with translation calls: ```tsx // Before Welcome back
// After (i18next) const { t } = useTranslation(); {t("common.welcomeBack")} ```
- Generate or update locale files
Create JSON/YAML for each language. Non-primary languages get placeholders: ``json { "common": { "welcomeBack": "[ES] Welcome back" } } ``
- Validate locale completeness
`` en.json: 142/142 keys (100%) es.json: 128/142 keys (90.1%) — 14 missing fr.json: 135/142 keys (95.1%) — 7 missing ``
- Find unused translation keys
Report keys in locale files never referenced in source code.
Rules
- Never modify non-primary locale files without user confirmation
- Preserve existing key structure and ordering
- Mark placeholder translations with
[TODO]or[LANG]prefix - Do not extract developer-facing strings (logs, error codes)
- Handle pluralization using the framework's syntax
- Handle interpolation:
"Hello, {{name}}"not string concatenation - Process one file at a time, show changes before applying
- Sort keys alphabetically within namespaces
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: sourav15mukherjee
- Source: sourav15mukherjee/skillforge-free-skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.