Agent skill · software engineering · jeremylongshore
lokalise-core-workflow-a
Execute Lokalise primary workflow: Upload source files and manage translation
Why this skill is useful
Adds executable scripts for uploading translation files and managing keys in Lokalise that are not in public documentation.
What it needs
Requires @lokalise/node-api, lokalise2 installed locally. Requires lokalise account access. About 5k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Lokalise Core Workflow A Overview Primary workflow covering the "source to Lokalise" direction: upload translation files, create and update keys programmatically, tag keys for organization, and perform bulk operations. Both SDK and CLI approaches shown for every operation. Prerequisites Lokalise API token exported as LOKALISEAPITOKEN Lokalise project ID exported as LOKALISEPROJECTID @lokalise/node-api installed for SDK examples lokalise2 CLI installed for CLI examples Source translation file(s) in a supported format (JSON, XLIFF, PO, YAML, etc.) Instructions 1. Upload source translation files. File upload is async: the API returns a process object that must be polled until completion. SDK — Base64 encode and upload: SDK — Poll upload process until complete: CLI — Upload with polling: 1. Create keys programmatically when keys come from code scanning, CMS exports, or CI pipelines rather than file uploads. SDK — Create keys with initial translations: SDK — Update existing keys: 1. Tag keys for organization. Tags let you filter keys in the Lokalise UI and API — useful for release tracking, feature flags, and workflow status. SDK — Add tags to existing keys (bulk): SDK — Filter keys by tag: 1. Perform bulk key operations for large-scale changes. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/lokalise-core-workflow-a