agentleFS
Sign inStart free
surfmind-spacesurfmind-space/awesome-surfmind/skills/terminology-keeper/SKILL.md

terminology-keeper

Skill8 starsChanged 5 months agoMITView on GitHub

Builds and applies a consistent glossary for translation — extracting recurring domain terms, suggesting preferred translations, and flagging inconsistencies so terminology stays uniform across a page or document. Use when the user needs term consistency across translations or localization, mentions a glossary, terminology, or terminology database, or asks to translate domain material uniformly.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Keep translations consistent across a page, document, product copy, legal text, docs, or domain material by building a glossary of the …

    line 14
  2. Distinctive:

    When a term has competing translations in the source, pick one preferred form, normalize every occurrence to it, and note the alternates.

    line 21
  3. Distinctive:

    Use concise headings. Include these sections when they fit:

    line 26
  4. Distinctive:

    Do not over-translate brand or code terms.

    line 35
  5. Distinctive:

    When a term has multiple valid translations across subdomains (legal vs.

    line 36
  6. Distinctive:

    If the source is inconsistent and you cannot tell which translation is correct, surface it under terms needing confirmation instead of …

    line 37

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Terminology Keeper

Keep translations consistent across a page, document, product copy, legal text, docs, or domain material by building a glossary of the recurring domain terms and applying the same preferred translation throughout.

How To Work

  1. Extract recurring domain terms, acronyms, product names, and terms of art from the source.
  2. Build a glossary table: Source term | Preferred translation | Context | Notes.
  3. Apply the glossary consistently in the translated or rewritten output.
  4. When a term has competing translations in the source, pick one preferred form, normalize every occurrence to it, and note the alternates.
  5. Flag terms that need user or domain-expert confirmation.

Output Format

Use concise headings. Include these sections when they fit:

  • Glossary
  • Translated or revised text
  • Terms needing confirmation

Guardrails

  • Preserve important names, numbers, links, code, formatting, dates, currencies, and user constraints.
  • Do not over-translate brand or code terms; keep do-not-translate items verbatim.
  • When a term has multiple valid translations across subdomains (legal vs. medical vs. financial), choose by the document's domain and record the assumption rather than picking casually.
  • If the source is inconsistent and you cannot tell which translation is correct, surface it under terms needing confirmation instead of guessing.

Respond in the same language as the user's request unless the skill explicitly involves translation or localization.

Example

Source (EN → ES) mixes translations of the same term: "The Plaintiff filed the claim. Later, the claimant amended the same claim, and the demandante withdrew it."

Glossary

Source termPreferred translationContextNotes
claimdemandalegal filingnot reclamación in this context
Plaintiff / claimantdemandantethe party suingnormalize both source variants to one term

Translated text (es): "El demandante presentó la demanda. Más tarde, el demandante modificó la misma demanda y la retiró."

Terms needing confirmation: Source used "Plaintiff" and "claimant" interchangeably — confirm both refer to the same party before finalizing.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free