lokalise-cost-tuning
Optimize Lokalise costs through plan selection, usage monitoring, and efficiency. Use when analyzing Lokalise billing, reducing costs, or implementing usage monitoring and budget alerts. Trigger with phrases like "lokalise cost", "lokalise billing", "reduce lokalise costs", "lokalise pricing", "lokalise budget".
What this skill does
# Lokalise Cost Tuning
## Overview
Optimize Lokalise localization spending across plan tiers, contributor seats, Translation Memory (TM) leverage, machine translation (MT) triage, and dead key cleanup. Lokalise pricing is per-seat subscription (Essential ~$120/user/month, Pro ~$290/user/month) with optional pay-per-use for MT and AI features.
## Prerequisites
- Lokalise Admin role for billing and usage visibility
- `LOKALISE_API_TOKEN` with read access to project statistics
- Understanding of translation workflow (human, MT, or hybrid)
- `curl` and `jq` for API queries
## Instructions
### Step 1: Audit Current Usage
```bash
set -euo pipefail
echo "=== Lokalise Usage Audit ==="
# Get all projects with statistics
PROJECTS=$(curl -sf "https://api.lokalise.com/api2/projects?limit=100&include_statistics=1" \
-H "X-Api-Token: ${LOKALISE_API_TOKEN}")
echo "$PROJECTS" | jq -r '.projects[] | [.name, .statistics.keys_total, (.statistics.languages // [] | length), .statistics.progress_total] | @tsv' \
| column -t -s $'\t' -N "Project,Keys,Languages,Progress%"
# Totals
TOTAL_KEYS=$(echo "$PROJECTS" | jq '[.projects[].statistics.keys_total] | add')
TOTAL_LANGS=$(echo "$PROJECTS" | jq '[.projects[] | (.statistics.languages // [] | length)] | max')
PROJECT_COUNT=$(echo "$PROJECTS" | jq '.projects | length')
echo ""
echo "Totals: ${PROJECT_COUNT} projects, ${TOTAL_KEYS} keys, up to ${TOTAL_LANGS} languages"
echo ""
# Contributor count (seats = cost driver)
TEAMS=$(curl -sf "https://api.lokalise.com/api2/teams" \
-H "X-Api-Token: ${LOKALISE_API_TOKEN}")
echo "$TEAMS" | jq -r '.teams[] | "Team: \(.name) — \(.users_count) users (seats)"'
```
### Step 2: Reduce Per-Seat Costs
Seats are the largest cost driver. Strategies to minimize:
```typescript
import { LokaliseApi } from "@lokalise/node-api";
const lok = new LokaliseApi({ apiKey: process.env.LOKALISE_API_TOKEN! });
// Audit: Find inactive contributors (no activity in 90 days)
async function findInactiveContributors(projectId: string): Promise<void> {
const contributors = await lok.contributors().list({
project_id: projectId,
limit: 500,
});
console.log("=== Contributor Activity Audit ===");
for (const c of contributors.items) {
const langs = c.languages
.map((l: { lang_iso: string }) => l.lang_iso)
.join(", ");
console.log(
`${c.fullname} <${c.email}> — ` +
`admin: ${c.is_admin}, reviewer: ${c.is_reviewer}, ` +
`languages: [${langs}]`
);
}
console.log(`\nTotal contributors: ${contributors.items.length}`);
console.log(
"Review: Remove freelancers between tasks. " +
"Use contributor groups for batch management."
);
}
// Strategy: Use task-based access for freelance translators
// - Add freelancers when a translation task opens
// - Remove them when the task closes
// - This avoids paying for idle seats
// Cost example: 10 individual seats = ~$1,200/month
// 3 permanent + task-based freelancers = ~$360/month
```
### Step 3: Maximize Translation Memory (TM) Hits
TM matches reduce human translation volume. Keys with 100% TM match cost zero for translation.
```typescript
// Strategy: Translate similar projects sequentially to build TM
// Don't translate 3 apps in parallel — do one first, seed the TM,
// then the others get 30-50% free matches on shared strings
// Enable automations on upload to apply TM automatically
const uploadResult = await lok.files().upload(projectId, {
data: base64FileData,
filename: "en.json",
lang_iso: "en",
use_automations: true, // Apply TM + MT suggestions
replace_modified: true,
detect_icu_plurals: true,
});
// Check TM coverage after upload
const languages = await lok.languages().list({ project_id: projectId, limit: 50 });
for (const lang of languages.items) {
console.log(
`${lang.lang_iso}: ${lang.statistics?.progress ?? 0}% translated, ` +
`${lang.statistics?.words_to_do ?? "?"} words remaining`
);
}
```
### Step 4: Machine Translation Triage
Pre-translate low-risk content with MT. Reserve human translation for critical strings.
```bash
set -euo pipefail
# Identify untranslated key volume per language
curl -sf "https://api.lokalise.com/api2/projects/${LOKALISE_PROJECT_ID}/languages" \
-H "X-Api-Token: ${LOKALISE_API_TOKEN}" \
| jq '.languages[] | {
locale: .lang_iso,
progress: .statistics.progress,
words_to_do: .statistics.words_to_do
}'
```
**MT triage matrix — decide by key prefix:**
| Key Prefix | Content Type | Translation Method | Cost Impact |
|-----------|-------------|-------------------|-------------|
| `tooltip.*`, `help.*` | Tooltips, help text | Machine Translation | Low risk, high volume savings |
| `log.*`, `debug.*` | Log messages | MT or skip | These rarely face users |
| `ui.label.*`, `nav.*` | UI labels, navigation | Human | Medium risk, must be natural |
| `marketing.*`, `cta.*` | Marketing copy, CTAs | Human (senior) | High risk, brand-critical |
| `legal.*`, `tos.*` | Legal text | Human + legal review | Compliance-critical |
### Step 5: Clean Up Dead Keys
Orphaned keys waste per-word costs and clutter the project.
```typescript
import { readFileSync } from "fs";
async function findOrphanedKeys(
projectId: string,
sourceCodeDir: string
): Promise<string[]> {
// Get all keys from Lokalise
const allKeys: string[] = [];
let cursor: string | undefined;
do {
const page = await lok.keys().list({
project_id: projectId,
limit: 500,
...(cursor ? { cursor } : {}),
});
for (const k of page.items) {
allKeys.push(k.key_name.web ?? k.key_name.other ?? "");
}
cursor = page.hasNextCursor() ? page.nextCursor() : undefined;
} while (cursor);
console.log(`Lokalise keys: ${allKeys.length}`);
// Compare against source code references
// (simplified — adjust grep pattern for your i18n framework)
const { execSync } = await import("child_process");
const sourceRefs = execSync(
`grep -roh "t(['\"][^'\"]*['\"])" ${sourceCodeDir} 2>/dev/null || true`,
{ encoding: "utf-8" }
)
.split("\n")
.map((line) => line.replace(/^t\(['"]/, "").replace(/['"]\)$/, ""))
.filter(Boolean);
const sourceKeySet = new Set(sourceRefs);
const orphaned = allKeys.filter((k) => !sourceKeySet.has(k));
console.log(`Source code references: ${sourceKeySet.size}`);
console.log(`Orphaned keys: ${orphaned.length}`);
return orphaned;
}
// Archive orphaned keys to stop paying for their translations
async function archiveKeys(projectId: string, keyNames: string[]): Promise<void> {
// Look up key IDs
for (const name of keyNames.slice(0, 50)) {
const result = await lok.keys().list({
project_id: projectId,
filter_keys: name,
limit: 1,
});
if (result.items.length > 0) {
await lok.keys().update(result.items[0].key_id, {
project_id: projectId,
is_archived: true,
});
}
await new Promise((r) => setTimeout(r, 170)); // Rate limit
}
}
```
### Step 6: Monitor Monthly Spend
```bash
set -euo pipefail
echo "=== Monthly Cost Estimate ==="
# Count total seats across teams
SEAT_COUNT=$(curl -sf "https://api.lokalise.com/api2/teams" \
-H "X-Api-Token: ${LOKALISE_API_TOKEN}" \
| jq '[.teams[].users_count] | add')
# Estimate based on plan tier (adjust rate for your plan)
RATE_PER_SEAT=120 # Essential plan — adjust to 290 for Pro
MONTHLY_COST=$((SEAT_COUNT * RATE_PER_SEAT))
echo "Active seats: ${SEAT_COUNT}"
echo "Estimated monthly cost: \$${MONTHLY_COST} (at \$${RATE_PER_SEAT}/seat)"
echo ""
echo "Cost reduction levers:"
echo " 1. Remove inactive contributors (task-based access)"
echo " 2. Use contributor groups instead of individual invites"
echo " 3. Pre-translate with MT to reduce human translation volume"
echo " 4. Archive orphaned keys to reduce per-word charges"
echo " 5. Translate similar projects sequentially to maximize TM"
```
## Output
- Usage audit report: projects, keys, languRelated in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.