Agent skill

Lokalise Upgrade Migration

by jeremylongshore in jeremylongshore/tons-of-skills-marketplace

Analyze, plan, and execute Lokalise SDK upgrades with breaking change detection.

MITAuto-check: notesData & Analytics

Install Lokalise Upgrade Migration

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill lokalise-upgrade-migration -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace lokalise-upgrade-migration --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/lokalise-upgrade-migration .claude/skills/lokalise-upgrade-migration && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
lokalise-upgrade-migration
GitHub stars
2.8k
Token cost
~2.2k tokens
SKILL.md length
444 words
Files
2 (incl. references)
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Analyze, plan, and execute Lokalise SDK upgrades with breaking change detection.

  • Works in 7 steps: Assess Current Version and Target → Review Breaking Changes by Version → Migrate Imports (v8 CJS to v9 ESM) → …
  • Upgrading Lokalise SDK versions
  • SKILL.md covers Current State, Overview, Prerequisites and Instructions, plus 5 more sections
  • Calls npm, node and git; reaches github.com and api.github.com; needs LOKALISE_API_TOKEN

What it does

Lokalise Upgrade Migration is an agent skill from jeremylongshore/tons-of-skills-marketplace. Analyze, plan, and execute Lokalise SDK upgrades with breaking change detection. Use when upgrading Lokalise SDK versions, detecting deprecations, or migrating to new API versions. Trigger with phrases like "upgrade lokalise", "lokalise migration", "lokalise breaking changes", "update lokalise SDK", "analyze lokalise version".

Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/implementation-guide.md`). Compatibility notes: Designed for Claude Code

It sits in Data & Analytics, covering Anomaly detection. It works with npm, TypeScript and Node.js. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

  • Upgrading Lokalise SDK versions
  • Detecting deprecations
  • Migrating to new API versions
  • With phrases like upgrade lokalise

Example prompts

  • “upgrade lokalise”
  • “lokalise migration”
  • “lokalise breaking changes”
  • “/lokalise-upgrade-migration”

Requirements

  • Node.js
  • A credential in LOKALISE_API_TOKEN
  • Compatibility (from SKILL.md): Designed for Claude Code
  • Pre-approved tools (allowed-tools): Read, Write, Edit, Bash(npm:*), Bash(npx:*), Bash(git:*), Bash(node:*), Bash(grep:*), Grep

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. Assess Current Version and Target
  2. Review Breaking Changes by Version
  3. Migrate Imports (v8 CJS to v9 ESM)
  4. Update Pagination Code (v6/v7 to v9)
  5. Update Error Handling
  6. Install and Verify
  7. Verify API Compatibility

What it can do on your machine

Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Edit
    • Bash(npm:*)
    • Bash(npx:*)
    • Bash(git:*)
    • Bash(node:*)
    • Bash(grep:*)
    • Grep

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npm
    • node
    • git
    • curl
    • npx
    • brew

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • github.com
    • api.github.com

    Also links to:

    • lokalise.github.io
    • developers.lokalise.com
    • nodejs.org

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • LOKALISE_API_TOKEN

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Designed for Claude Code

    From compatibility in the SKILL.md frontmatter.

Context cost

Lokalise Upgrade Migration loads about 2.2k tokens when it runs, and up to ~3.5k if it reads all its reference files. Until then it costs about 89 tokens; SKILL.md has 444 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~89
When it runs · the whole SKILL.md, loaded when a task matches
~2.2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteRuns commands with sudoSKILL.md:251
    sudo mv lokalise2 /usr/local/bin/

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 444 words, ~2,239 tokens.

Download SKILL.mdSave it as .claude/skills/lokalise-upgrade-migration/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
lokalise-upgrade-migration
description
Analyze, plan, and execute Lokalise SDK upgrades with breaking change detection. Use when upgrading Lokalise SDK versions, detecting deprecations, or migrating to new API versions. Trigger with phrases like "upgrade lokalise", "lokalise migration", "lokalise breaking changes", "update lokalise SDK", "analyze lokalise version".
allowed-tools
Read, Write, Edit, Bash(npm:*), Bash(npx:*), Bash(git:*), Bash(node:*), Bash(grep:*), Grep
compatibility
Designed for Claude Code
version
1.14.0
license
MIT
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
saas, lokalise, api, migration

Lokalise Upgrade Migration

Current State

!npm list @lokalise/node-api 2>/dev/null | grep lokalise || echo 'SDK not installed' !lokalise2 --version 2>/dev/null || echo 'CLI not installed' !node --version 2>/dev/null || echo 'Node.js not available' !cat package.json 2>/dev/null | grep -E '"type"|"module"' || echo 'No package.json type field'

Overview

Upgrade the @lokalise/node-api SDK between major versions with full breaking change detection, automated code transformation, and verification. The most significant migration is v8 (CommonJS) to v9+ (ESM-only), which requires changes to imports, module configuration, and potentially your build pipeline.

Prerequisites

  • Existing project using @lokalise/node-api (any version 6.x through 9.x)
  • Node.js 18+ for SDK v9 (Node.js 14+ for v8 and below)
  • Git repository with clean working tree (for safe rollback)
  • Test suite that exercises Lokalise API calls

Instructions

Step 1: Assess Current Version and Target
bash
set -euo pipefail
echo "=== Current SDK Version ==="
CURRENT=$(npm list @lokalise/node-api --json 2>/dev/null | node -e "
  const d = JSON.parse(require('fs').readFileSync(0,'utf8'));
  const v = d.dependencies?.['@lokalise/node-api']?.version || 'not found';
  console.log(v);
")
echo "Installed: ${CURRENT}"

echo -e "\n=== Latest Available ==="
LATEST=$(npm view @lokalise/node-api version)
echo "Latest: ${LATEST}"

echo -e "\n=== All Major Versions ==="
npm view @lokalise/node-api versions --json | node -e "
  const versions = JSON.parse(require('fs').readFileSync(0,'utf8'));
  const majors = {};
  versions.forEach(v => { const m = v.split('.')[0]; majors[m] = v; });
  Object.entries(majors).forEach(([m, v]) => console.log('  v' + m + '.x latest: ' + v));
"
Step 2: Review Breaking Changes by Version
VersionNode.jsModule SystemKey Breaking Changes
9.x18+ESM onlyrequire() removed, import only. Pagination returns typed cursors. ApiError export path changed.
8.x14+CJS + ESMLast version supporting require(). Constructor accepts apiKey (not token).
7.x14+CJSCursor pagination introduced. list() methods return paginated objects.
6.x12+CJSTypeScript rewrite. Method signatures changed from callbacks to promises.
Step 3: Migrate Imports (v8 CJS to v9 ESM)

This is the most impactful change. Every require() call must become an import.

Find all Lokalise imports in your codebase:

bash
set -euo pipefail
grep -rn "require.*lokalise\|from.*lokalise" --include="*.ts" --include="*.js" --include="*.mjs" . || echo "No imports found"

Transform patterns:

typescript
// BEFORE (v8 CommonJS)
const { LokaliseApi } = require('@lokalise/node-api');
const lok = new LokaliseApi({ apiKey: process.env.LOKALISE_API_TOKEN });

// AFTER (v9 ESM)
import { LokaliseApi } from '@lokalise/node-api';
const lok = new LokaliseApi({ apiKey: process.env.LOKALISE_API_TOKEN });

Update package.json for ESM:

json
{
  "type": "module"
}

Update tsconfig.json if using TypeScript:

json
{
  "compilerOptions": {
    "module": "ES2022",
    "moduleResolution": "bundler",
    "target": "ES2022"
  }
}
Step 4: Update Pagination Code (v6/v7 to v9)
typescript
// BEFORE (v6 offset pagination)
const keys = await lok.keys().list({
  project_id: projectId,
  page: 2,
  limit: 100,
});

// AFTER (v9 cursor pagination — preferred for large datasets)
const keys = await lok.keys().list({
  project_id: projectId,
  limit: 500,
  pagination: 'cursor',
  cursor: previousCursor,
});
// Access next cursor: keys.nextCursor
// Check for more: keys.hasNextCursor()
Step 5: Update Error Handling
typescript
// BEFORE (v8)
const { ApiError } = require('@lokalise/node-api');
try {
  await lok.projects().get(projectId);
} catch (e) {
  if (e instanceof ApiError) {
    console.error(e.message, e.code);
  }
}

// AFTER (v9 — ApiError import path unchanged, but must use import)
import { ApiError } from '@lokalise/node-api';
try {
  await lok.projects().get(projectId);
} catch (e) {
  if (e instanceof ApiError) {
    console.error(e.message, e.code);
  }
}
Step 6: Install and Verify
bash
set -euo pipefail
# Create a safety branch
git checkout -b upgrade/lokalise-sdk-v9

# Install the target version
npm install @lokalise/node-api@latest

# Run TypeScript compilation check
npx tsc --noEmit 2>&1 | head -40 || true

# Run tests
npm test
Step 7: Verify API Compatibility
typescript
// Quick smoke test after upgrade
import { LokaliseApi } from '@lokalise/node-api';

const lok = new LokaliseApi({ apiKey: process.env.LOKALISE_API_TOKEN! });

// Test basic operations still work
const projects = await lok.projects().list({ limit: 1 });
console.log('API connection OK:', projects.items[0]?.name ?? 'no projects');

const keys = await lok.keys().list({
  project_id: projects.items[0].project_id,
  limit: 5,
  pagination: 'cursor',
});
console.log('Cursor pagination OK:', keys.items.length, 'keys fetched');
Show full SKILL.md (190 more words)Show less

Output

  • Updated @lokalise/node-api to target version
  • All require() calls converted to ESM import (if upgrading to v9)
  • package.json and tsconfig.json updated for ESM compatibility
  • Pagination code migrated to cursor-based pattern
  • Tests passing against the new SDK version
  • Git branch with all changes for review

Error Handling

IssueCauseSolution
ERR_REQUIRE_ESMUsing require() with v9 SDKConvert to import syntax and set "type": "module" in package.json
SyntaxError: Cannot use importNode.js file not recognized as ESMRename .js to .mjs or add "type": "module"
TypeError: lok.keys is not a functionAPI changed between major versionsCheck SDK changelog for renamed methods
ERR_UNKNOWN_FILE_EXTENSION .tsTypeScript not configured for ESMUse tsx runner or configure ts-node with "esm": true
Tests fail after upgradeBreaking API changesCheck test against the version-specific migration notes above

Examples

Rollback Procedure
bash
set -euo pipefail
# If the upgrade causes issues, revert immediately
git stash  # Save any work in progress
npm install @lokalise/node-api@8  # Last CJS version
git checkout HEAD -- tsconfig.json package.json
npm test
echo "Rolled back to v8. Investigate failures before retrying."
CLI Upgrade (Separate from SDK)
bash
set -euo pipefail
# macOS
brew upgrade lokalise2

# Linux — download latest release binary
LATEST_CLI=$(curl -s https://api.github.com/repos/lokalise/lokalise-cli-2-go/releases/latest | grep -oP '"tag_name": "\K[^"]+')
curl -sL "https://github.com/lokalise/lokalise-cli-2-go/releases/download/${LATEST_CLI}/lokalise2_linux_x86_64.tar.gz" | tar xz
sudo mv lokalise2 /usr/local/bin/

# Verify
lokalise2 --version
Check for Deprecated API Usage
bash
set -euo pipefail
# Patterns that indicate outdated SDK usage
echo "=== Deprecated Patterns ==="
grep -rn "\.page\s*:" --include="*.ts" --include="*.js" . && echo "^ Offset pagination — migrate to cursor" || echo "No offset pagination found"
grep -rn "require.*lokalise" --include="*.ts" --include="*.js" . && echo "^ CommonJS require — migrate to ESM import" || echo "No CJS requires found"
grep -rn "new LokaliseApi.*token:" --include="*.ts" --include="*.js" . && echo "^ Old constructor — use apiKey instead of token" || echo "No old constructor pattern found"

Resources

Next Steps

  • For CI pipeline changes needed after ESM migration, see lokalise-ci-integration.
  • For performance improvements with the new cursor pagination, see lokalise-performance-tuning.
  • Run lokalise-debug-bundle if the upgrade causes unexpected API errors.

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in skills/.curated/lokalise-upgrade-migration of jeremylongshore/tons-of-skills-marketplace.

  • SKILL.md
  • references/implementation-guide.md

Open the folder on GitHubat commit cfae287

Compare with similar skills

Lokalise Upgrade Migration next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Lokalise Upgrade Migration compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Lokalise Upgrade Migration this skilljeremylongshore/tons-of-skills-marketplace2.8k—~2.2kAutomated safety check: NotesMIT
Bungalfrevn/apollo237—~2kAutomated safety check: NotesMIT
Spotpatchhuanglvjing/spotpatch134—~998Automated safety check: PassMIT
Swpm Code Reviewdeinsoftware/swpm125—~1.1kAutomated safety check: PassMIT
Bunbastani-inc/atomic856—~2.8kAutomated safety check: PassCustom licence
NodeHsienW/chat-gun143—~1.6kAutomated safety check: PassCustom licence

Similar skills

  • Bun

    galfrevn/apollo

    A skill your agent uses when building, running, testing, or bundling JavaScript/TypeScript applications.

    237 GitHub stars~2k tokensUpdated 1 mo ago
    Testing & QAAuto-check: notes
  • Spotpatch

    huanglvjing/spotpatch

    为 React 项目建立从浏览器页面元素到精确 JSX/TSX 源码、结构化上下文与可审阅修改的 SpotPatch 工作流。用户提到 SpotPatch、截图沟通前端修改、页面元素定位源码、Vite 或 Next.js 接入、组件数据链路、结构化 Prompt、AI 补丁审阅、安装检查或故障排查时使用此技能。

    134 GitHub stars~998 tokensUpdated 13 days ago
    Frontend & DesignAuto-check passed
  • Swpm Code Review

    deinsoftware/swpm

    Automated code review bash script for SWPM. An agent skill from deinsoftware/swpm.

    125 GitHub stars~1.1k tokensUpdated 4 mo ago
    DevelopmentAuto-check passed
  • Bun

    bastani-inc/atomic

    A skill your agent uses when building, testing, and deploying JavaScript/TypeScript applications.

    856 GitHub stars~2.8k tokensUpdated today
    Testing & QAAuto-check passed
  • Node

    HsienW/chat-gun

    Provides domain-specific best practices for Node.js development with TypeScript, covering type stripping, async patterns, error handling, streams, modules, testing, performance, caching, logging…

    143 GitHub stars~1.6k tokensUpdated today
    Testing & QAAuto-check passed
  • Pre Commit

    wellwelwel/poku

    Run the mandatory pre-commit checks for the poku repository before staging a commit.

    1.2k GitHub stars~728 tokensUpdated 3 mo ago
    Testing & QAAuto-check passed

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo
  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes
  • Adapting Transfer Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated today
    Auto-check passed
  • Analyzing Database Indexes

    jeremylongshore/tons-of-skills-marketplace

    Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2k tokensUpdated today
    Auto-check passed

Questions about Lokalise Upgrade Migration

What does Lokalise Upgrade Migration do?

Analyze, plan, and execute Lokalise SDK upgrades with breaking change detection. Lokalise Upgrade Migration is an agent skill from jeremylongshore/tons-of-skills-marketplace. Analyze, plan, and execute Lokalise SDK upgrades with breaking change detection.

When should I use Lokalise Upgrade Migration?

Lokalise Upgrade Migration fits situations like: upgrading Lokalise SDK versions; detecting deprecations; migrating to new API versions; with phrases like upgrade lokalise.

How do I install Lokalise Upgrade Migration in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill lokalise-upgrade-migration -a claude-code`. Or copy the skill folder (skills/.curated/lokalise-upgrade-migration in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/lokalise-upgrade-migration in your project. Claude Code loads it when a task matches its description.

How do I install Lokalise Upgrade Migration in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill lokalise-upgrade-migration -a codex`. Or copy the skill folder (skills/.curated/lokalise-upgrade-migration in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/lokalise-upgrade-migration in your project. Codex loads it when a task matches its description.

Can I use Lokalise Upgrade Migration in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill lokalise-upgrade-migration -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/lokalise-upgrade-migration, .gemini/skills/lokalise-upgrade-migration, .github/skills/lokalise-upgrade-migration and .opencode/skills/lokalise-upgrade-migration in your project.

What does Lokalise Upgrade Migration need to run?

Going by SKILL.md and its folder, Lokalise Upgrade Migration needs the command-line tools its instructions call (npm, node, git, curl, npx and brew) and credentials named LOKALISE_API_TOKEN. Our summary lists: Node.js; A credential in LOKALISE_API_TOKEN. Its frontmatter pre-approves these tools: Read, Write, Edit, Bash(npm:*), Bash(npx:*), Bash(git:*), Bash(node:*), Bash(grep:*), Grep. Compatibility (from SKILL.md): Designed for Claude Code.

Does Lokalise Upgrade Migration access the network?

SKILL.md names 5 domains. In commands or code: github.com and api.github.com; the agent is likely to contact these when it follows the instructions. As links in the text: lokalise.github.io, developers.lokalise.com and nodejs.org. This is read from the text; nothing was executed.

Is Lokalise Upgrade Migration safe to install?

Our automated static check of SKILL.md found notes only (runs commands with sudo), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Lokalise Upgrade Migration use?

Lokalise Upgrade Migration is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Lokalise Upgrade Migration use?

About 2.2k tokens (SKILL.md is roughly 9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.3k tokens, read only when the agent opens those files.

What are the alternatives to Lokalise Upgrade Migration?

Skills that share tags, products or a category with Lokalise Upgrade Migration: Bun (galfrevn/apollo, 237 stars), Spotpatch (huanglvjing/spotpatch, 134 stars), Swpm Code Review (deinsoftware/swpm, 125 stars) and Bun (bastani-inc/atomic, 856 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Lokalise Upgrade Migration?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.