More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Loc Sync — Keep Translations in Sync with Updates

    1

    Synchronize translations with updated source files using fingerprinting to catch stale and modified strings.

    $3

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Loc Sync — Keep Translations in Sync with Updates

    Loc Sync — Keep Translations in Sync with Updates

    Example session with this skill installed

    The upstream mod just updated to v1.5.0. Compare the new default.json with our v1.4.0 baseline and show me what needs re-translating for the German locale.

    • Read your context and instructions
    • Compiled the loc sync

    I have analyzed the changes between v1.4.0 and the current v1.5.0 source. The update contains 12 new strings and 5 stale strings where the English source text was modified.

    Sync Report: v1.5.0 Update

    KeyStatusSource Diff (v1.4.0 -> v1.5.0)Current Translation (DE)
    UI_MENU_STARTStale"Press [START] to play" -> "Press {0} to play"Drücken Sie [START] zum Spielen
    OPT_GFX_ULTRANewN/A (Added key)[Missing]
    MSG_SAVE_ERRStale"Error saving game" -> "Save failed: Disk full"Fehler beim Speichern
    NPC_GREET_01RemovedKey no longer exists in sourceHallo Reisender
    WP_SWORD_DESCStale"A sharp blade." -> "A rusty blade."Eine scharfe Klinge.

    Technical Summary

    • New Keys: 12 (Requires initial translation)
    • Stale Keys: 5 (Source changed, translation is now inaccurate)
    • Removed Keys: 3 (Obsolete, will be purged on merge)
    • Placeholders: Warning - UI_MENU_START now requires {0} but the German text is hardcoded.

    Next steps

    1. Run python3 scripts/locsync.py merge to remove the 3 obsolete keys.
    2. Run python3 scripts/loctx.py prepare --keys UI_MENU_START,MSG_SAVE_ERR,WP_SWORD_DESC to update stale translations.
    3. Use loc-qa to verify the new {0} placeholder renders correctly in the German UI.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Updating a translated app or game mod usually means hunting through thousands of lines for a handful of changed source strings. This skill automates the detection of new, removed, and stale keys by tracking source fingerprints. It prevents the "silent bug" where a source string changes its meaning or placeholders while the old translation remains, leading to inaccurate text or application crashes.

    What it does

    • Source tracking creates a baseline of source strings to detect future changes accurately.
    • Delta reporting generates word-level diffs showing exactly how source text evolved.
    • Stale detection flags translations that no longer match the modified source logic.
    • Key management identifies and removes obsolete keys while preserving file layout and comments.
    • Progress logging tracks translation coverage and history across multiple versions.

    How it works

    1. Establish baseline by running the baseline command against the current state or a specific git revision.
    2. Analyze updates using the diff command to compare the new source against the baseline or old files.
    3. Clean and prep by running merge to remove dead keys and todo to export specific keys for translation.
    4. Finalize update by recording the new state and generating a localized changelog.

    Frameworks & tools

    The skill operates via a Python CLI (locsync.py) and interacts with .l10n.json files and git repositories. It produces reports in HTML and Markdown formats and integrates with loc-translate and loc-qa workflows.

    Why this beats prompting it yourself

    Generic LLM prompts miss "stale" translations where the source changed but the key remained. This skill uses precise fingerprinting to ensure 100% of upstream changes are caught, even when placeholders or punctuation updates would otherwise go unnoticed.

    Use cases

    • Syncing a community game mod translation after a major patch.
    • Updating mobile app localizations when source placeholders change.
    • Generating a "What's New" changelog for a specific language release.
    • Auditing a translation for technical debt and obsolete keys.

    Known limitations

    Requires a structured .l10n.json format and a local Python environment. It does not perform the actual translation itself, which requires the companion loc-translate skill.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Game Development.

    Requires Python 3 environment. Works specifically with .l10n.json formats. Does not perform automated translation, only synchronization and diffing.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 21 days ago

    Permissions

    Terminal / Shell
    Read Files
    Write Files
    Listed21 days ago

    What's inside

    Frequently Asked Questions

    Unlike generic prompts that only look at text, this skill uses fingerprinting to detect when a source string has changed even if the key stays the same, preventing outdated or "stale" translations from remaining in your app.

    Loc Sync is a specialized utility for the Loc-Translate ecosystem; it identifies what needs to be translated and cleans up dead keys, while its companion skill, loc-translate, performs the actual AI-powered translation.

    The skill requires a Python environment and works specifically with .l10n.json files and Git repositories to track version history and source baselines.

    Yes, Loc Sync includes a 'clean and prep' function that automatically identifies and removes obsolete keys from your localization files while carefully preserving your existing file layout and comments.

    You will receive the locsync.py CLI tool, documentation for the command suite (baseline, diff, merge, and todo), and integration guides for connecting it to your existing translation and QA workflows.

    Absolutely. By running the 'diff' and 'progress' commands, Loc Sync generates HTML or Markdown reports that highlight exactly what changed between versions, making it perfect for creating localized 'What's New' logs.

    New in Game Development