Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →jeremylongshore/lokalise-deploy-integration
Deploy Lokalise integrations to Vercel, Netlify, and Cloud Run platforms.
Passed 17 of 23 test cases with the skill, and 12 of 23 without it.
and 4 more in the full report
6 fixed11 passed either way5 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
We want to automatically execute our `./scripts/download-translations.sh` script whenever `npm run build` is executed in a Node.js project. Which script lifecycle hook in `package.json` should trigger the localization fetch prior to compiling Next.js?
| Checked | Without skill | With skill |
|---|---|---|
| Configures a prebuild entry in package.json executing ./scripts/download-translations.sh ./src/locales. | Missed | Passed |
The instructions your model reads when the skill loads.
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.
LOKALISE_API_TOKEN and LOKALISE_PROJECT_ID stored as CI secretscurl and unzip available in CI environment (standard on GitHub Actions runners)Add a pre-build script that pulls translations from Lokalise before your framework compiles:
#!/bin/bash
# scripts/download-translations.sh
set -euo pipefail
PROJECT_ID="${LOKALISE_PROJECT_ID:?Missing LOKALISE_PROJECT_ID}"
API_TOKEN="${LOKALISE_API_TOKEN:?Missing LOKALISE_API_TOKEN}"
DEST_DIR="${1:-./src/locales}"
echo "Downloading translations for project $PROJECT_ID..."
BUNDLE_URL=$(curl -sf -X POST \
"https://api.lokalise.com/api2/projects/${PROJECT_ID}/files/download" \
-H "X-Api-Token: ${API_TOKEN}" \
-H "Content-Type: application/json" \
-d "{
\"format\": \"json\",
\"original_filenames\": false,
\"bundle_structure\": \"%LANG_ISO%.json\",
\"export_empty_as\": \"base\",
\"json_unescaped_slashes\": true,
test cases passed, vs 12 / 23 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.