Agent skill · data analytics · jeremylongshore
lokalise-performance-tuning
Optimize Lokalise API performance with caching, pagination, and bulk
Why this skill is useful
Adds executable scripts for optimizing Lokalise API performance through caching and pagination techniques that aren't widely documented.
What it needs
Requires @lokalise/node-api installed locally. Requires lokalise account access. About 7k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Lokalise Performance Tuning Overview Optimize Lokalise API throughput for translation pipelines by implementing cursor pagination, local caching, batch key operations (500/request), request throttling under the 6 req/s rate limit, and selective language downloads. Prerequisites @lokalise/node-api SDK v9+ (ESM) or REST API access LOKALISEAPITOKEN environment variable set Understanding of project size (key count, language count) to calibrate batch sizes Optional: Redis or LRU cache library for persistent caching Instructions Step 1: Use Cursor Pagination for Large Datasets Cursor pagination is significantly faster than offset pagination for projects with 5K+ keys. Offset pagination degrades as page numbers increase because the server must skip rows; cursor pagination uses a pointer. Offset pagination comparison (avoid for large projects): Keys Offset (limit=100) Cursor (limit=500) Time saved ------ -------------------- -------------------- ----------- 1,000 10 requests 2 requests 80% 10,000 100 requests 20 requests 80% 50,000 500 requests (~84s) 100 requests (~17s) 80% Step 2: Cache Translation Downloads Locally Translation file downloads are the most expensive Lokalise operation. Cache them locally and use project lastactivity timestamps to invalidate. Step 3: Batch Key Operations Lokalise supports creating, updating, and deleting up to 500 keys per request. Always batch instead of making individual requests. Step 4: Implement Request Throttling A proper request queue prevents 429 Too Many Requests errors and makes your integration resilient under load. Step 5: Async File Operations with Webhooks File uploads and downloads are processed asynchronously by Lokalise. Instead of polling the process status endpoint, use webhooks to get notified when processing completes. If you must poll (no webhook endpoint available): Step 6: Selective Language Downloads (Delta Exports) Downloading all languages when you only need one wastes bandwidth and API time. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/lokalise-performance-tuning--a1efaf