Skip to content
TrustedSkillsbeta
Back to all skills

Readme I18N

Checked
u9401066·vlatest·writing·Apache-2.0

This skill translates README files into multiple languages (I18N), making your documentation accessible to a global audience and improving collaboration.

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add u9401066/med-paper-assistant --skill readme-i18n -a claude-code
  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

u9401066

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned u9401066/med-paper-assistant at 7e1eab0b05.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Scanned
1 file, 48 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The readme-i18n skill translates README files into multiple languages. It can handle various markdown formats and output translated versions in plain text or markdown. This allows for broader accessibility and understanding of project documentation across different linguistic communities.

When to use it

  • You need to translate a software project's README file into Spanish for a new user base.
  • Your open-source project aims to reach an international audience, requiring translations in French, German, and Japanese.
  • A medical paper assistant needs to provide documentation in multiple languages for researchers globally.
  • You want to make your internal technical documentation accessible to non-English speaking team members.

Key capabilities

  • README file translation
  • Multiple language support
  • Markdown format handling
  • Plain text output option
  • Markdown output option

Example prompts

  • "Translate this README file into French: [paste README content]"
  • "Can you translate the following markdown to German? [paste README content]"
  • "Please provide a plain text translation of this README in Spanish. [paste README content]"

Tips & gotchas

The quality of the translation depends on the underlying language model; review and editing by native speakers is recommended for critical documentation. Ensure the input README file is properly formatted markdown to avoid parsing errors.