Agent skill · writing content · jeremylongshore
lokalise-data-handling
Implement Lokalise translation data handling, PII management, and compliance
Why this skill is useful
Provides specific patterns and code examples for handling translation data and compliance in Lokalise that the AI wouldn't reliably generate on its own.
What it needs
Requires @lokalise/node-api installed locally. Requires lokalise account access. About 6k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Lokalise Data Handling Overview Lokalise manages translation data through keys, translations, snapshots, and branches. This skill covers the translation data lifecycle (create, update, export), key metadata management (tags, descriptions, screenshots), translation snapshots for versioning, branch-based translation isolation, export format handling (JSON flat/nested, XLIFF, PO), character encoding (UTF-8 BOM handling), and plural form support across locales. Prerequisites @lokalise/node-api SDK installed (npm install @lokalise/node-api) API token with read/write access to the target project Understanding of i18n key naming conventions for your project lokalise2 CLI for bulk file operations (optional) Instructions 1. Understand the Translation Data Lifecycle Translation data in Lokalise follows this flow: Create keys (with platforms, tags, descriptions) -> Add base translations (source language) -> Translate (manually or via integrations) -> Review (proofread flag) -> Export (download to codebase). Create keys with metadata that helps translators: 2. Manage Key Metadata Tags, descriptions, and screenshots help translators understand context. Keep metadata current: 3. Use Snapshots for Translation Versioning Snapshots capture the entire project state at a point in time. Create them before bulk changes: Snapshots are immutable. Restoring creates a new project — it does not overwrite the current one. 4. Use Branches for Translation Isolation Branches let you work on translations for a feature without affecting production strings: 5. Handle Export Formats Lokalise supports multiple export formats. Choose based on your stack: 6. Handle Character Encoding All Lokalise exports use UTF-8. Watch for these encoding issues: When uploading files, always specify UTF-8 encoding. Lokalise auto-detects encoding but explicit is safer: 7. Handle Plural Forms Lokalise uses CLDR plural rules. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/lokalise-data-handling