agentleFS
clearsmogclearsmog/claude-skills/translate/SKILL.md

translate

Skill2 starsChanged 9 months agoMITView on GitHub

Multi-format document translation. Supports Typst ↔ Quarto. For Beamer translations, configure at project level.

48 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use faq, summarize and 10 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.
  • AnthropicSkill

    faq

    Turn repeat questions into a pinned FAQ. Use when a champion keeps answering the same questions.

    Also in 3 projects that use this

  • 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

  • AnthropicSkill

    analyze

    Answer data questions -- from quick lookups to full analyses. Use when looking up a single metric, investigating what's driving a trend or drop, comparing segments over time, or preparing a formal data report for stakeholders.

    Also in 4 projects that use this

  • sunnyclinches44Skill

    explain

    Explains code using real-world analogies and ASCII diagrams

    Also in 5 projects that use this

  • VercelSkill

    publish

    Publish a single demo to v0 and optionally create Typefully drafts. Use when the user says "publish", "publish to v0", or "create typefully draft" for a demo.

    Also in 3 projects that use this

  • +2 more from anthropics

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 40 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If no target specified, infer from project context

    line 34
  2. Very specific:

    Run /qa on the translated file to verify quality.

    line 91

“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

Multi-Format Translation Workflow

Translate documents between supported formats.

The source file is authoritative: leave it unchanged, and make the target match it rather than improve on it.


Supported Translations

FromToMethod
.typ (Typst).qmd (Quarto)Component mapping
.qmd (Quarto).typ (Typst)CSS classes to components

Note: For Beamer (.tex) translations, configure at project level. Projects with Beamer support should have their own translate skill with environment mapping tables.

Format Detection

Parse $ARGUMENTS:

  • First argument: source file path
  • Second argument (optional): target format (.qmd, .typ)
  • If no target specified, infer from project context

Typst → Quarto

Component Mapping

Typst (qk)Quarto CSS
#keypoint[...]::: {.keybox}\n...\n:::
#insight[...]::: {.highlightbox}\n...\n:::
#tip[...]::: {.methodbox}\n...\n:::
#note[...]::: {.softbox}\n...\n:::
#warning[...]::: {.keybox}\n**Warning:** ...\n:::
#trap[...]::: {.keybox}\n**Common mistake:** ...\n:::

Citation Mapping

  • @key → @key (same in Quarto)

Math Mapping

  • $...$ (Typst inline) → $...$ (Quarto inline)
  • $ ... $ (Typst display) → $$...$$ (Quarto display)

Quarto → Typst

Component Mapping

Quarto CSSTypst (qk)
::: {.keybox}#keypoint[...]
::: {.highlightbox}#insight[...]
::: {.methodbox}#tip[...]
::: {.resultbox}#keypoint[...]
::: {.quotebox}#quote(attribution: "...")[...]
::: {.softbox}#note[...]

Math Mapping

  • $...$ → $...$
  • $$...$$ → $ ... $ (display)

Quality Standards (All Translations)

  1. Content parity — every idea from source must appear in target
  2. Environment parity — every box/callout must use the corresponding target element
  3. Notation consistency — same symbols as source
  4. No content loss — never summarize or condense
  5. All citations verified — every reference resolves
  6. All images referenced — every figure path valid
  7. Compile successfully — target must build without errors

Post-Translation

Run /qa on the translated file to verify quality.

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.