agentleFS
ai-search-guruai-search-guru/getcito-worlds-first-open-source-aio-aeo-or-geo-tool/skills/translate/SKILL.md

translate

Skill432 starsChanged 12 days agoMITView on GitHub

Translates a page into the user's markets, keeps rules and sources.

49 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use summarize, calendar and 5 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • mitsuhikoSkill

    summarize

    Fetch a URL or convert a local file (PDF/DOCX/HTML/etc.) into Markdown using `uvx markitdown`, optionally it can summarize

    Also in 8 projects that use this

  • jacobraskSkill

    calendar

    Interact with Apple Calendar via AppleScript. Use when the user asks to check calendar, view events, create events, manage schedule, find free time, or list calendars. Triggers include "my calendar", "my schedule", "calendar events", "create event", "add to calendar", "what's on my calendar", "free time", "available slots", "upcoming events", "today's events". Requires macOS with Calendar.app.

    Also in 3 projects that use this

  • sunnyclinches44Skill

    explain

    Explains code using real-world analogies and ASCII diagrams

    Also in 5 projects that use this

  • AnthropicSkill

    weather

    The optional standing status report ("the weather"): compile open incidents, build health, merge-queue stats, and deploy lag into one always-current report page, and post to the channel only when a defined event fires. Use when the weather routine fires, or when someone asks to run/update the weather report.

    Also in 3 projects that use this

  • MicrosoftSkill

    web-search

    Also in 3 projects that use this

  • Microsoft AzureSkill

    release-notes

    Author and update release notes for Azure App Configuration libraries and providers. USE FOR: write release notes, add release note entry, update release notes, draft release notes, new version release notes, format release notes. DO NOT USE FOR: generating changelogs from git history, writing internal engineering notes.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 40 edited versions we read keep these.

  • 7

    Distinctive

    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:

    If the draft or the languages are unclear, ask which ones.

    line 17
  2. Distinctive:

    Keep the structure: the same headings, lists, tables, FAQ and schema, translated.

    line 27
  3. Distinctive:

    Keep every fact, figure, date, name, product name and source exactly as the original has them.

    line 28
  4. Distinctive:

    Keep links as they are, unless the person gives the addresses of the translated pages.

    line 29
  5. Distinctive:

    Don't add, drop or change facts, claims or figures: translate only.

    line 38
  6. Distinctive:

    Don't add local prices, offers or examples the original doesn't have.

    line 39
  7. Distinctive:

    Never publish a translation yourself: the app decides whether a page goes live, and asks the person unless an Admin allowed this agent to …

    line 40

“Common” is measured: kept by at least 6 in 10 of the 40 edited versions of this file we could read. “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

Translate a page

Translate an existing draft into the languages of the brand's markets. Only the language changes: the facts, structure, sources and rules stay as they are.

When to use

  • "Translate /pricing to German and French", "Make a Turkish version of this draft."
  • If the draft or the languages are unclear, ask which ones; offer the languages of the brand's tracked regions.

What to read

  1. get_draft for the draft: its passages, its sources, and which passages AI quotes (locked).
  2. list_brands when the person names no language: the brand's region, for the language to offer first.

Steps

  1. Translate the draft passage by passage, into natural language for that market, not word for word.
  2. Keep the structure: the same headings, lists, tables, FAQ and schema, translated.
  3. Keep every fact, figure, date, name, product name and source exactly as the original has them. Units and date formats follow the market; the values don't change.
  4. Keep links as they are, unless the person gives the addresses of the translated pages.
  5. Save each language as its own draft with create_draft, the title in that language; the app asks the person first when it should.

Output

For each language: the translated page, and a short list of what to check, such as terms that have no settled translation, or a passage that may need a local example.

Don't

  • Don't add, drop or change facts, claims or figures: translate only.
  • Don't add local prices, offers or examples the original doesn't have.
  • Never publish a translation yourself: the app decides whether a page goes live, and asks the person unless an Admin allowed this agent to go live on its own.

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.