New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Logseq I18n

by logseq in logseq/logseq

Logseq i18n workflow for adding, renaming, reviewing, or editing translation keys and user-facing strings.

AGPL-3.0Auto-check passedFrontend & Design

Install Logseq I18n

skills CLI
$ npx skills add logseq/logseq --skill logseq-i18n -a claude-code

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

GitHub CLI
$ gh skill install logseq/logseq logseq-i18n --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/logseq/logseq.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/logseq-i18n .claude/skills/logseq-i18n && 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
logseq-i18n
GitHub stars
45k
Token cost
~1.7k tokens
SKILL.md length
811 words
Files
1
Skills in repo
12
Repo updated
First seen
Licence
AGPL-3.0

At a glance

Logseq i18n workflow for adding, renaming, reviewing, or editing translation keys and user-facing strings.

  • Works in 3 steps: docs/i18n-key-naming.md for key… → .i18n-lint.toml for lint scope, covered… → src/main/frontend/context/i18n.cljs for…
  • : writing UI code with hardcoded text
  • SKILL.md covers When This Skill Applies, Read These First, Scope Rules and Use These Helpers, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Logseq I18n is an agent skill from logseq/logseq. Logseq i18n workflow for adding, renaming, reviewing, or editing translation keys and user-facing strings. Use when: writing UI code with hardcoded text, adding new user-facing strings, editing translation dict files, reviewing i18n compliance, working with notification/show!, adding translatable UI attributes, or any task involving src/resources/dicts/. Also use when the user mentions i18n, translation, localization, or hardcoded strings.

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Frontend & Design, covering Internationalization and Translation. The repository describes itself as: A privacy-first, open-source platform for knowledge management and collaboration. Download link: http://github.com/logseq/logseq/releases. roadmap: https://logseq.io/p/NX4mcggEV. The licence is AGPL-3.0.

When your agent uses it

  • : writing UI code with hardcoded text
  • Adding new user-facing strings
  • Editing translation dict files
  • Reviewing i18n compliance

Example prompts

  • “/logseq-i18n”

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. docs/i18n-key-naming.md for key ownership, reuse, and naming
  2. .i18n-lint.toml for lint scope, covered helpers/attributes, exclusions,
  3. src/main/frontend/context/i18n.cljs for the translation helper APIs

What it can do on your machine

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

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).

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

  • Network

    No URLs in SKILL.md.

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

  • Credentials

    Names no API keys, tokens, secrets or passwords.

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

Context cost

Logseq I18n loads about 1.7k tokens when it runs. Until then it costs about 114 tokens; SKILL.md has 811 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~114
When it runs · the whole SKILL.md, loaded when a task matches
~1.7k

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 passed

The automated check found no risky patterns in SKILL.md.

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 logseq/logseq at commit 22a29b3, republished under its AGPL-3.0 licence (© logseq). 811 words, ~1,679 tokens.

Download SKILL.mdSave it as .claude/skills/logseq-i18n/SKILL.md (or your agent's skills folder).
name
logseq-i18n
description
Logseq i18n workflow for adding, renaming, reviewing, or editing translation keys and user-facing strings. Use when: writing UI code with hardcoded text, adding new user-facing strings, editing translation dict files, reviewing i18n compliance, working with notification/show!, adding translatable UI attributes, or any task involving src/resources/dicts/. Also use when the user mentions i18n, translation, localization, or hardcoded strings.

Logseq i18n Skill

When This Skill Applies

  • Adding or editing user-facing strings in shipped UI
  • Replacing hardcoded UI text with translations
  • Adding, renaming, deduplicating, or removing keys in src/resources/dicts/
  • Reviewing code for i18n compliance
  • Editing notification/show! calls or translatable UI attributes
  • Updating i18n tooling, docs, or lint configuration

Read These First

  1. docs/i18n-key-naming.md for key ownership, reuse, and naming
  2. .i18n-lint.toml for lint scope, covered helpers/attributes, exclusions, and allowlists
  3. src/main/frontend/context/i18n.cljs for the translation helper APIs

Use docs/contributing-to-translations.md only when the task is specifically about locale contribution workflow.

Scope Rules

  • .i18n-lint.toml is the source of truth for which files and APIs are checked for hardcoded UI text.
  • Inside that scope, all shipped user-facing UI text must be internationalized.
  • Console output does not need i18n. Keep out-of-scope developer-only (Dev) labels inline in code/config, not in translation dictionaries.
  • If you introduce a new UI helper, alert API, translatable attribute, UI namespace, or shipped surface, update .i18n-lint.toml so lint coverage stays accurate.

Use These Helpers

All translation helpers live in frontend.context.i18n.

HelperUse for
tStandard translation with preferred locale
ttTry multiple keys and return the first existing translation
t-enForce English text when UI output also needs English console/debug output
interpolate-rich-text / interpolate-rich-text-nodeReplace placeholders with rich-text or hiccup fragments
interpolate-sentenceKeep a full sentence in one key while inserting placeholders and inline links
replace-newlines-with-brRender translated newline characters as [:br] nodes
locale-join-rich-text / locale-join-rich-text-nodeJoin rich fragments with locale-aware separators
locale-format-number / locale-format-date / locale-format-timeLocale-aware formatting for dynamic values before translation

Do not introduce parallel i18n helpers elsewhere unless the change also updates the shared i18n API deliberately.

Core Rules

Rule 1: No hardcoded shipped UI text

If the text is user-facing and in .i18n-lint.toml scope, hardcoded literals in buttons, labels, placeholders, tooltips, dialogs, notifications, empty states, and similar UI are a bug.

Rule 2: Reuse keys by meaning, not by English text

Search src/resources/dicts/en.edn first. Reuse a key only when both match:

  • semantic owner
  • textual role

If the English text matches but the meaning differs, create a new key and follow docs/i18n-key-naming.md.

Rule 3: English source lives in en.edn
  • Add new English source text to src/resources/dicts/en.edn.
  • When introducing a new key for the first time, you must also add the Simplified Chinese (zh-CN) translation in the same change. English and zh-CN are the two required locales for any new key.
  • Add other non-English entries only when you are also providing actual translations.
  • When renaming or removing keys, update affected locale files so stale keys do not remain behind.
  • Do not copy English into non-English locale files just to fill gaps. Tongue falls back to :en.
Rule 4: Keep complete sentences together
  • Prefer one translation entry per complete sentence or message.
  • Do not split rich text or linked text across multiple keys.
  • Use interpolate-sentence or interpolate-rich-text* when markup and word order must stay together.
Rule 5: Prefer placeholders for plain dynamic text

Use placeholder strings like {1} and {2} for plain dynamic text. Format arguments in the caller before passing them to t.

Show full SKILL.md (311 more words)Show less
Rule 6: Function-valued translations are restricted

Use function values only when:

  • the locale needs real logic such as conditional/plural behavior, or
  • the translation must return hiccup rich text

When function values are necessary, only these are allowed inside the function body:

  • str
  • when
  • if
  • =
Rule 7: Locale details matter
  • Preserve emoji and icon glyphs from en.edn exactly.
  • Use punctuation natural to the locale.
  • Pluralization is locale-specific. Do not force English singular/plural logic onto every language.

Workflow

When adding or changing user-facing text:

  1. Use .i18n-lint.toml to confirm the text is in i18n scope.
  2. Search src/resources/dicts/en.edn for an exact semantic match.
  3. If no exact match exists, name the key with docs/i18n-key-naming.md.
  4. If the naming guide still does not yield one clear key, stop and ask for human guidance instead of guessing.
  5. Add or update the English source text in en.edn.
  6. Replace the literal with the appropriate helper from frontend.context.i18n.
  7. Add/update locale translations only where actual translations are being supplied.
  8. If you introduced a new linted helper/attribute/surface, update .i18n-lint.toml.

Validation

After changing keys:

bash
bb lang:validate-translations

After changing shipped UI text:

bash
bb lang:lint-hardcoded --git-changed

After editing dictionary files:

bash
bb lang:format-dicts

bb lang:format-dicts is the canonical repo formatter for dictionary key ordering and namespace spacing.

Common Mistakes

MistakeFix
Hardcoded UI string in a linted UI surfaceMove it into en.edn and use a helper from frontend.context.i18n
Reusing a key only because the English text matchesReuse only on exact semantic owner + role match
Copying English into non-English locale filesLeave the key missing unless you are adding a real translation
Using (fn ...) for plain placeholder textUse "..." with {1}, {2}, ...
Splitting one sentence across multiple keysKeep a single translation entry and interpolate into it
Adding a new linted helper but not updating .i18n-lint.tomlExtend the TOML config in the same change
Editing dict files without running bb lang:format-dictsRun the formatter before finishing

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

Files

Just SKILL.md in .agents/skills/logseq-i18n of logseq/logseq.

Open the folder on GitHubat commit 22a29b3

Compare with similar skills

Logseq I18n 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.

Logseq I18n compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Logseq I18n this skilllogseq/logseq45k—~1.7kAutomated safety check: PassAGPL-3.0
Chatbox i18n Translatorchatboxai/chatbox42k—~508Automated safety check: PassGPL-3.0
Internationalization Workflow with i18niOfficeAI/AionUi33k1 repos~1.9kAutomated safety check: PassApache-2.0
Enforce Rules For I18nmoeru-ai/airi50k—~1.5kAutomated safety check: PassMIT
Claude Desktop Chinese Localizationjavaht/claude-desktop-zh-cn7.5k—~1.6kAutomated safety check: PassMIT
Translation ReviewDevolutions/UniGetUI26k—~1.3kAutomated safety check: PassMIT

Similar skills

  • Chatbox i18n Translator

    chatboxai/chatbox

    Translates new or changed i18n keys from a Chatbox Pro diff, staged changes or a commit range, writing the locale JSON files directly with a built-in glossary.

    42k GitHub stars~508 tokensUpdated 13 days ago
    Frontend & DesignAuto-check passed

  • Internationalization Workflow with i18n

    iOfficeAI/AionUi

    Standards for keeping all user-facing text translatable: read the i18n config first, use namespaced keys, reuse shared strings and follow the key naming rules.

    33k GitHub starsUsed in 1 repo~1.9k tokens
    Frontend & DesignAuto-check passed

  • Enforce Rules For I18n

    moeru-ai/airi

    Review pending AIRI translations on Crowdin in a batch, then sync them into the repository.

    50k GitHub stars~1.5k tokensUpdated today
    Frontend & DesignAuto-check passed

  • Claude Desktop Chinese Localization

    javaht/claude-desktop-zh-cn

    Adds missing Simplified and Traditional Chinese translations to the Claude Desktop Chinese patch across three layers, then checks how many mappings actually hit.

    7.5k GitHub stars~1.6k tokensUpdated 2 days ago
    Frontend & DesignAuto-check passed

  • Translation Review

    Devolutions/UniGetUI

    Reviews UniGetUI .json language files for localization quality, detects parity issues, English-equal entries, wrong-script content, and cross-language outliers, then generates a dataset for…

    26k GitHub stars~1.3k tokensUpdated today
    Frontend & DesignAuto-check passed

  • Frontend I18n

    langflow-ai/langflow

    Add, change, or review user-facing text in the Langflow frontend using the i18n system (i18next / react-i18next).

    156k GitHub stars~1k tokensUpdated today
    Frontend & DesignAuto-check passed

More from logseq/logseq

All 12 skills in this repo

  • Logseq Review Workflow Eval

    logseq/logseq

    Compare two revisions of the Logseq logseq-review-workflow skill by running the same review prompt against isolated before and after skill snapshots, collecting both outputs, and producing a…

    45k GitHub stars~1k tokensUpdated today
    Auto-check passed

  • Esm Cjs Risk Scan

    logseq/logseq

    Scan Logseq ClojureScript Node/Electron targets for npm module loading risks, especially ESM-only packages that may fail when loaded through js/require or shadow-cljs require-based shims.

    45k GitHub stars~3.3k tokensUpdated today
    Auto-check passed

  • Logseq Plugin SDK

    logseq/logseq

    Build, debug, or review Logseq plugins with the @logseq/libs SDK (TypeScript/JavaScript, iframe/shadow sandboxed).

    45k GitHub stars~2.3k tokensUpdated today
    Auto-check passed

  • Logseq CLI

    logseq/logseq

    Operate the current Logseq command-line interface to inspect or modify graphs, pages, blocks, tasks, tags, and properties; run Datascript queries; show page/block trees; manage graphs; and manage…

    45k GitHub stars~1.9k tokensUpdated today
    Auto-check passed

  • Logseq Dependency Upgrade

    logseq/logseq

    Audit, plan, and refresh dependency upgrades for the Logseq repository by scanning every non-gitignored package.json, deps.edn, bb.edn and nbb.edn manifest, checking latest upstream versions…

    45k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Logseq Answer Machine

    logseq/logseq

    Answer user questions about the Logseq repository by researching source code, docs, tests, runtime behavior, and local tools.

    45k GitHub stars~1.2k tokensUpdated today
    Auto-check: warnings

Categories

Questions about Logseq I18n

What does Logseq I18n do?

Logseq i18n workflow for adding, renaming, reviewing, or editing translation keys and user-facing strings. Logseq I18n is an agent skill from logseq/logseq. Logseq i18n workflow for adding, renaming, reviewing, or editing translation keys and user-facing strings.

When should I use Logseq I18n?

Logseq I18n fits situations like: : writing UI code with hardcoded text; adding new user-facing strings; editing translation dict files; reviewing i18n compliance.

How do I install Logseq I18n in Claude Code?

Run `npx skills add logseq/logseq --skill logseq-i18n -a claude-code`. Or copy the skill folder (.agents/skills/logseq-i18n in logseq/logseq) into .claude/skills/logseq-i18n in your project. Claude Code loads it when a task matches its description.

How do I install Logseq I18n in Codex?

Run `npx skills add logseq/logseq --skill logseq-i18n -a codex`. Or copy the skill folder (.agents/skills/logseq-i18n in logseq/logseq) into .agents/skills/logseq-i18n in your project. Codex loads it when a task matches its description.

Can I use Logseq I18n 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 logseq/logseq --skill logseq-i18n -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/logseq-i18n, .gemini/skills/logseq-i18n, .github/skills/logseq-i18n and .opencode/skills/logseq-i18n in your project.

What does Logseq I18n need to run?

SKILL.md names no scripts, command-line tools or credentials: Logseq I18n is instructions for the agent only.

Does Logseq I18n access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Logseq I18n safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Logseq I18n use?

Logseq I18n is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Logseq I18n use?

About 1.7k tokens (SKILL.md is roughly 6.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Logseq I18n?

Skills that share tags, products or a category with Logseq I18n: Chatbox i18n Translator (chatboxai/chatbox, 42k stars), Internationalization Workflow with i18n (iOfficeAI/AionUi, 33k stars), Enforce Rules For I18n (moeru-ai/airi, 50k stars) and Claude Desktop Chinese Localization (javaht/claude-desktop-zh-cn, 7.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Logseq I18n?

logseq (a GitHub organization) maintains it in logseq/logseq, which has 45,158 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on October 7, 2026.

Source: logseq/logseq on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.