Agent skill · software engineering · jeremylongshore
lokalise-deploy-integration
Deploy Lokalise integrations to Vercel, Netlify, and Cloud Run platforms.
Why this skill is useful
Adds an executable script for downloading translations from Lokalise and integrates it into CI/CD workflows for deployment.
What it needs
Requires curl, unzip 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 Deploy Integration Overview Translations must be downloaded fresh during CI/CD builds to ensure production always ships the latest reviewed content. This skill covers downloading translations as a build step, GitHub Actions workflows for translation sync, Vercel and Netlify build plugin integration, OTA (over-the-air) updates for mobile apps via Lokalise's iOS and Android SDKs, and environment-specific translation bundles. Prerequisites Lokalise API token with download permissions (read-only token recommended for CI) LOKALISEAPITOKEN and LOKALISEPROJECTID stored as CI secrets curl and unzip available in CI environment (standard on GitHub Actions runners) For OTA: Lokalise OTA SDK token (separate from API token, generated in Lokalise dashboard) Instructions 1. Download Translations in the Build Step Add a pre-build script that pulls translations from Lokalise before your framework compiles: Wire it into package.json: 2. GitHub Actions Workflow Full workflow that downloads translations, builds, and deploys: To trigger builds when translations change, set up a Lokalise webhook that fires a GitHub repositorydispatch: 3. Vercel Build Integration For Vercel, translations download during the build phase. Configure the token as an environment variable: In vercel.json, ensure the build command runs the translation download: For ISR/SSR apps that need translations at runtime (not just build time), cache translations in a KV store or download on cold start: 4. Netlify Build Integration Netlify uses build plugins or the prebuild command. The simplest approach uses netlify.toml: Set secrets via Netlify CLI: For a custom Netlify Build Plugin that integrates more deeply: 5. OTA Updates for Mobile (iOS/Android) Over-the-air updates let you push translation changes without an app store release. Lokalise provides native SDKs for this. iOS (Swift): Android (Kotlin): Both SDKs fall back to the bundled translations if OTA download fails, so the app always has working strings. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/lokalise-deploy-integration--b85c98