gramiojs/documentation

translate-page

Translate a GramIO documentation page from English to Russian (or vice versa), preserving code blocks, twoslash annotations, and frontmatter.

First seen Apr 7, 2026

Installation

$ npx skills add gramiojs/documentation --skill translate-page

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from gramiojs/documentation.

npx skills add gramiojs/documentation

Browse all from gramiojs/documentation

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 7
Default branch main
Open issues 0
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Allowed toolsRead, Write, Edit, Glob
More metadata
internal
1

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,679 B
  • docs SUMMARY.md 163 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

Translate Documentation Page

You are translating a GramIO documentation page between English and Russian.

Arguments

The user provides [path] — e.g., docs/storages.md or docs/ru/guides/telegram-stars.md.

Steps

  1. Determine direction:

- If path starts with docs/ru/ → translating RU to EN, target is docs/{rest-of-path}. - Otherwise → translating EN to RU, target is docs/ru/{rest-of-path} (remove leading docs/).

  1. Read the source page completely.
  1. Read AGENTS.md for translation conventions.
  1. Translate the content with these rules:

- Translate all prose (headings, paragraphs, list items, table cells). - Do NOT translate code blocks — keep all code exactly as-is. - Do NOT modify // ^? twoslash annotations. - Do NOT translate frontmatter field names, only values (title, description content, keywords content). - Update image paths: EN uses /path/image.png, RU uses /ru/path/image.png. - Keep all links functional — internal links should use the correct locale prefix. - Preserve markdown formatting (bold, italic, code spans, blockquotes, admonitions). - Keep ::: code-group, ::: tip, ::: warning, ::: danger markers unchanged. - Keep badge HTML blocks unchanged.

  1. Write the translated page to the target path.
  1. Verify the target file exists and has the same structure as the source.