Claude-skill-registry lokalise-install-auth

install

source · Clone the upstream repo

git clone https://github.com/majiayu000/claude-skill-registry

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/lokalise-install-auth" ~/.claude/skills/majiayu000-claude-skill-registry-lokalise-install-auth && rm -rf "$T"

manifest: skills/data/lokalise-install-auth/SKILL.md

Lokalise Install & Auth

Overview

Set up Lokalise SDK/CLI and configure API token authentication for translation management.

Prerequisites

Node.js 14+ (v18+ recommended for ESM support)
Package manager (npm, pnpm, or yarn)
Lokalise account with project access
API token from Lokalise profile settings

Instructions

Step 1: Install Node.js SDK

# Node.js SDK (ESM module, v9+)
npm install @lokalise/node-api

# For CommonJS projects, use v8
npm install @lokalise/node-api@8

Step 2: Install CLI Tool (Optional)

# macOS via Homebrew
brew tap lokalise/cli-2
brew install lokalise2

# Linux/Windows via direct download
# Visit: https://github.com/lokalise/lokalise-cli-2-go/releases

# Verify installation
lokalise2 --version

Step 3: Generate API Token

Log into Lokalise
Click profile avatar -> Profile Settings
Go to "API tokens" tab
Click "Generate new token"
Choose "Read and write" for full access
Copy the token immediately (shown only once)

Step 4: Configure Authentication

# Set environment variable
export LOKALISE_API_TOKEN="your-api-token"

# Or create .env file
echo 'LOKALISE_API_TOKEN=your-api-token' >> .env

# CLI configuration (creates ~/.lokalise2/config.yml)
lokalise2 --token "$LOKALISE_API_TOKEN" project list

Step 5: Verify Connection

import { LokaliseApi } from "@lokalise/node-api";

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

// Test connection by listing projects
const projects = await lokaliseApi.projects().list();
console.log(`Connected! Found ${projects.items.length} projects.`);

Output

Installed
```
@lokalise/node-api
```
package
Optional:
```
lokalise2
```
CLI installed
Environment variable or .env file with API token
Successful connection verification

Error Handling

Error	Cause	Solution
`401 Unauthorized`	Invalid or expired token	Generate new token in profile settings
`403 Forbidden`	Token lacks required permissions	Use read-write token, not read-only
`ERR_REQUIRE_ESM`	Using require() with SDK v9+	Use ESM imports or downgrade to v8
`ENOTFOUND api.lokalise.com`	Network blocked	Check firewall allows outbound HTTPS

Examples

TypeScript Setup (ESM)

import { LokaliseApi } from "@lokalise/node-api";

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

// List all projects
const projects = await lokaliseApi.projects().list();
projects.items.forEach(p => console.log(`${p.project_id}: ${p.name}`));

CommonJS Setup (SDK v8)

const { LokaliseApi } = require("@lokalise/node-api");

const lokaliseApi = new LokaliseApi({
  apiKey: process.env.LOKALISE_API_TOKEN,
});

lokaliseApi.projects().list().then(projects => {
  console.log(`Found ${projects.items.length} projects`);
});

CLI Configuration File

# ~/.lokalise2/config.yml
token: "your-api-token"
project_id: "123456789.abcdef"

OAuth2 Authentication (for apps)

import { LokaliseApiOAuth } from "@lokalise/node-api";

// Use token obtained via OAuth2 flow
const lokaliseApi = new LokaliseApiOAuth({
  apiKey: oauthAccessToken,
});

Resources

Next Steps

After successful auth, proceed to

lokalise-hello-world

for your first API call.