Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →jeremylongshore/lokalise-data-handling
Implement Lokalise translation data handling, PII management, and compliance patterns.
Passed 19 of 22 test cases with the skill, and 11 of 22 without it.
and 7 more in the full report
8 fixed11 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
Write a `lokalise2` CLI command to upload `./locales/en.json` as language `en` with placeholder conversion enabled so variable tags get converted to standard placeholders.
| Checked | Without skill | With skill |
|---|---|---|
| Invokes lokalise2 file upload with --file ./locales/en.json. | Passed | Passed |
| Passes --convert-placeholders true to enable variable placeholder conversion. | Missed | Passed |
The instructions your model reads when the skill loads.
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.
@lokalise/node-api SDK installed (npm install @lokalise/node-api)lokalise2 CLI for bulk file operations (optional)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:
import { LokaliseApi } from "@lokalise/node-api";
const lokalise = new LokaliseApi({ apiKey: process.env.LOKALISE_API_TOKEN! });
// Create keys with rich metadata
await lokalise.keys().create({
project_id: projectId,
keys: [
{
key_name: {
ios: "welcome.title",
android: "welcome_title",
web: "welcome.title",
other: "welcome.title",
},
description: "Main heading on the welcome screen shown after signup",
platforms: ["web", "ios", "android"],
tags: ["onboarding", "v2.1"],
base_translations: [
test cases passed, vs 11 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.