Aholo Viewer Docs
manycoretech/aholo-viewer
Guides writing and maintaining Aholo Viewer documentation: README, AGENTS.md, architecture notes, bilingual manual pages and AI collaboration guides.
Sync Japanese README translations with English source. An agent skill from aws-samples/sample-amazon-bedrock-agentcore-onboarding.
Install Sync Ja
$ npx skills add aws-samples/sample-amazon-bedrock-agentcore-onboarding --skill sync-ja -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install aws-samples/sample-amazon-bedrock-agentcore-onboarding sync-ja --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/aws-samples/sample-amazon-bedrock-agentcore-onboarding.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/sync-ja .claude/skills/sync-ja && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "sync-ja" agent skill from https://github.com/aws-samples/sample-amazon-bedrock-agentcore-onboarding/tree/main/.claude/skills/sync-ja into .claude/skills/sync-ja/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sync-ja", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/aws-samples/sample-amazon-bedrock-agentcore-onboarding/tree/main/.claude/skills/sync-jaType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add aws-samples/sample-amazon-bedrock-agentcore-onboarding --skill sync-ja -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install aws-samples/sample-amazon-bedrock-agentcore-onboarding sync-ja --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aws-samples/sample-amazon-bedrock-agentcore-onboarding.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/sync-ja .agents/skills/sync-ja && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "sync-ja" agent skill from https://github.com/aws-samples/sample-amazon-bedrock-agentcore-onboarding/tree/main/.claude/skills/sync-ja into .agents/skills/sync-ja/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sync-ja", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add aws-samples/sample-amazon-bedrock-agentcore-onboarding --skill sync-ja -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install aws-samples/sample-amazon-bedrock-agentcore-onboarding sync-ja --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aws-samples/sample-amazon-bedrock-agentcore-onboarding.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/sync-ja .cursor/skills/sync-ja && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "sync-ja" agent skill from https://github.com/aws-samples/sample-amazon-bedrock-agentcore-onboarding/tree/main/.claude/skills/sync-ja into .cursor/skills/sync-ja/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sync-ja", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/aws-samples/sample-amazon-bedrock-agentcore-onboarding.git --path .claude/skills/sync-ja--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add aws-samples/sample-amazon-bedrock-agentcore-onboarding --skill sync-ja -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install aws-samples/sample-amazon-bedrock-agentcore-onboarding sync-ja --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aws-samples/sample-amazon-bedrock-agentcore-onboarding.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/sync-ja .gemini/skills/sync-ja && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "sync-ja" agent skill from https://github.com/aws-samples/sample-amazon-bedrock-agentcore-onboarding/tree/main/.claude/skills/sync-ja into .gemini/skills/sync-ja/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sync-ja", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install aws-samples/sample-amazon-bedrock-agentcore-onboarding sync-jaInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add aws-samples/sample-amazon-bedrock-agentcore-onboarding --skill sync-ja -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/aws-samples/sample-amazon-bedrock-agentcore-onboarding.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/sync-ja .github/skills/sync-ja && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "sync-ja" agent skill from https://github.com/aws-samples/sample-amazon-bedrock-agentcore-onboarding/tree/main/.claude/skills/sync-ja into .github/skills/sync-ja/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sync-ja", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add aws-samples/sample-amazon-bedrock-agentcore-onboarding --skill sync-ja -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install aws-samples/sample-amazon-bedrock-agentcore-onboarding sync-ja --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aws-samples/sample-amazon-bedrock-agentcore-onboarding.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/sync-ja .opencode/skills/sync-ja && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "sync-ja" agent skill from https://github.com/aws-samples/sample-amazon-bedrock-agentcore-onboarding/tree/main/.claude/skills/sync-ja into .opencode/skills/sync-ja/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sync-ja", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
sync-ja- GitHub stars
- 133
- Token cost
- ~1.5k tokens
- SKILL.md length
- 696 words
- Files
- 1
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- MIT-0
At a glance
Sync Japanese README translations with English source. An agent skill from aws-samples/sample-amazon-bedrock-agentcore-onboarding.
- Works in 5 steps: Identify target files → Analyze drift for each pair → Apply two-pass translation → …
- English READMEs change and Japanese versions need updating
- SKILL.md covers Usage, Arguments, Translation Quality Rules and Steps, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Sync Ja is an agent skill from aws-samples/sample-amazon-bedrock-agentcore-onboarding, published by the product's own GitHub organization. Sync Japanese README translations with English source. Use when English READMEs change and Japanese versions need updating, or when improving Japanese translation fluency.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Writing & Content, covering Translation and Technical documentation. It works with Amazon Web Services. The licence is MIT-0.
When your agent uses it
- English READMEs change and Japanese versions need updating
- Improving Japanese translation fluency
Example prompts
- “/sync-ja”
Requirements
- Pre-approved tools (allowed-tools): Read, Write, Edit, Glob, Grep, Task, AskUserQuestion
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 376ee7c. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadWriteEditGlobGrepTaskAskUserQuestion
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Sync Ja loads about 1.5k tokens when it runs. Until then it costs about 45 tokens; SKILL.md has 696 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from aws-samples/sample-amazon-bedrock-agentcore-onboarding at commit 376ee7c, republished under its MIT-0 licence (© aws-samples). 696 words, ~1,501 tokens.
Download SKILL.mdSave it as
.claude/skills/sync-ja/SKILL.md (or your agent's skills folder).- name
- sync-ja
- description
- Sync Japanese README translations with English source. Use when English READMEs change and Japanese versions need updating, or when improving Japanese translation fluency.
- allowed-tools
- Read, Write, Edit, Glob, Grep, Task, AskUserQuestion
Sync Japanese README
Synchronize README_ja.md files with their English README.md counterparts, producing natural, native-speaker-quality Japanese — not literal translation.
Usage
/sync-ja— Auto-detect all out-of-sync README_ja.md files and update them/sync-ja 09_browser_use— Sync a specific module's README_ja.md/sync-ja 06_identity 07_gateway— Sync multiple specific modules/sync-ja --check— Report which files are out of sync without modifying them
Arguments
$ARGUMENTS contains optional module directory names and flags.
Parse $ARGUMENTS for:
- Positional: directory name(s) (optional, e.g.
09_browser_use) - --check: Dry-run mode — only report drift, don't edit
If no directories specified, scan all numbered directories ([0-9]*_*/) for README.md + README_ja.md pairs.
Translation Quality Rules
The Two-Pass Method
Pass 1 — Translate for meaning: Convert the English content into Japanese, focusing on accurately conveying the meaning of each section.
Pass 2 — Rewrite for fluency: Read the Pass 1 output as a native Japanese reader would. Rewrite sentences that sound like translated text (翻訳調) into natural Japanese that reads as if originally written by a native speaker.
Fluency Guidelines
- Avoid translationese (翻訳調):
- BAD:
このステップでは、エージェントのランタイムへのデプロイを行います(stiff, literal) - GOOD:
このステップでは、エージェントをランタイムにデプロイします(natural)
- BAD:
- Use appropriate sentence endings: Mix
です/ますfor explanations with conciseする/できるfor instructions - Keep sentences short: Japanese readers prefer shorter sentences. Split long compound sentences
- Natural word order: Japanese has different information flow — restructure sentences rather than mirroring English order
- Appropriate particles: Use natural particle choices (は/が/を/に/で) — don't force English preposition mappings
- Omit unnecessary subjects: Japanese often omits obvious subjects — don't add 「あなたは」or「これは」where context is clear
What to Keep in English
- AWS service names (Amazon Bedrock, AgentCore, CloudWatch, etc.)
- API names, SDK method names, CLI commands
- Code blocks (entire content)
- Mermaid diagrams (entire content)
- File paths and filenames
- Technical terms that are commonly used in English in Japanese tech writing (e.g., runtime, deploy, endpoint)
Established Term Mappings
| English | Japanese |
|---|---|
| Process Overview | プロセス概要 |
| Prerequisites | 前提条件 |
| How to use | 使用方法 |
| File Structure | ファイル構成 |
| Step N: | ステップN: |
| Key Implementation Pattern | 主要な実装パターン |
| Usage Example | 使用例 |
| References | 参考資料 |
| Next Steps | 次のステップ |
| Troubleshooting | トラブルシューティング |
| Architecture | アーキテクチャ |
| Clean up | クリーンアップ |
| Overview | 概要 |
Steps
1. Identify target files
If specific directories given in $ARGUMENTS, use those. Otherwise, find all pairs:
Glob: [0-9]*_*/README.md
Glob: [0-9]*_*/README_ja.mdFor --check mode, compare heading structure between EN and JA and report differences, then stop.
2. Analyze drift for each pair
For each README.md + README_ja.md pair:
- Read both files
- Compare heading structure (count and names of
#,##,###headings) - Identify:
- Sections in EN missing from JA (need translation)
- Sections in JA not in EN (stale, need removal)
- Sections where EN content has substantially changed (need update)
Show full SKILL.md (289 more words)Show less
3. Apply two-pass translation
For each file that needs updating:
Pass 1: Edit README_ja.md to match the English structure and content. Focus on meaning accuracy.
Pass 2: Re-read the edited README_ja.md and rewrite any sentences that sound unnatural. Ask yourself: "Would a native Japanese technical writer write it this way?" If not, rephrase.
Key rules during editing:
- Preserve heading levels exactly — same
#depth as English - Preserve mermaid diagrams and code blocks verbatim
- Preserve all links — update link text to Japanese but keep URLs
- Match section order with English README
4. Self-review checklist
Before finishing each file, verify:
- All EN headings have corresponding JA headings at the same level
- No stale JA sections that don't exist in EN
- Code blocks and mermaid diagrams are identical to EN
- No translationese — reads naturally in Japanese
- Technical terms kept in English where appropriate
- Links work (relative paths unchanged)
5. Summary
Print a summary:
- Files updated (with brief description of what changed)
- Files already in sync (skipped)
- Any sections that need manual review (e.g., heavily rewritten content)
Examples of Good vs Bad Translation
Example 1: Instruction text
- EN:
In this step, you will deploy the agent to the AgentCore runtime. - BAD:
このステップでは、あなたはエージェントをAgentCoreランタイムにデプロイすることになります。 - GOOD:
このステップでは、エージェントをAgentCoreランタイムにデプロイします。
Example 2: Feature description
- EN:
AgentCore Browser provides persistent browser sessions that your agent can use to interact with web applications. - BAD:
AgentCore Browserは、あなたのエージェントがWebアプリケーションと対話するために使用できる永続的なブラウザセッションを提供します。 - GOOD:
AgentCore Browserは、Webアプリケーションを操作するための永続的なブラウザセッションを提供します。エージェントはこのセッションを使ってWebページの閲覧や入力を行えます。
Example 3: Benefit list
- EN:
- Eliminates the need for hardcoded credentials - BAD:
- ハードコードされた認証情報の必要性を排除します - GOOD:
- 認証情報のハードコードが不要になります
Important Notes
- Never overwrite README_ja.md without reading it first — it may have manual refinements
- If a README_ja.md doesn't exist yet, create it from scratch using the two-pass method
- When in doubt about a translation choice, prefer clarity over literal accuracy
- The top-level project README_ja.md follows the same rules
© aws-samples, MIT-0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .claude/skills/sync-ja of aws-samples/sample-amazon-bedrock-agentcore-onboarding.
Open the folder on GitHubat commit 376ee7c
Compare with similar skills
Sync Ja next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Sync Ja this skillaws-samples/sample-amazon-bedrock-agentcore-onboarding | 133 | — | ~1.5k | Automated safety check: Pass | MIT-0 | |
| Aholo Viewer Docsmanycoretech/aholo-viewer | 1.1k | — | ~341 | Automated safety check: Pass | MIT | |
| Moonbit Docs Maintainermoonbitlang/moonbit-docs | 2.4k | — | ~1.1k | Automated safety check: Pass | Custom licence | |
| Dsh Web Documentationzhu1090093659/dsh-web | 8.4k | — | ~479 | Automated safety check: Pass | Apache-2.0 | |
| Translate It Doc En Zhmxsm/rocketmq-rust | 1.5k | — | ~1.2k | Automated safety check: Pass | Apache-2.0 | |
| Awesome Swift macOS Apps Docsjaywcjlove/awesome-swift-macos-apps | 1.7k | — | ~1.3k | Automated safety check: Pass | CC0-1.0 |
Similar skills
Moonbit Docs Maintainer
moonbitlang/moonbit-docs
A skill your agent uses when maintaining the moonbitlang/moonbit-docs repository, including Sphinx docs under next/, MoonBit examples under next/sources/, error-code documentation, gettext…
Dsh Web Documentation
zhu1090093659/dsh-web
A skill your agent uses when adding or editing dsh-web README files, docs, AGENTS.md instructions, user-facing configuration text, or bilingual documentation pairs.
Translate It Doc En Zh
mxsm/rocketmq-rust
Translate English IT and software engineering documents into professional, accurate Chinese.
Awesome Swift macOS Apps Docs
jaywcjlove/awesome-swift-macos-apps
Maintains app entries in the awesome-swift-macos-apps lists, keeping README.md and README.zh.md in step with one-sentence descriptions and correct category placement.
Bilingual Jsdoc
MichealWayne/fe-tools
Write or update bilingual (Chinese + English) JSDoc for exported functions in fe-tools.
More from aws-samples/sample-amazon-bedrock-agentcore-onboarding
- Official
Clean Workshop
aws-samples/sample-amazon-bedrock-agentcore-onboarding
Clean up AWS resources created by the AgentCore workshop. An agent skill from aws-samples/sample-amazon-bedrock-agentcore-onboarding.
- Official
Run Workshop
aws-samples/sample-amazon-bedrock-agentcore-onboarding
Run the AgentCore workshop steps sequentially to test the full attendee experience.
- Official
Scaffold Workshop
aws-samples/sample-amazon-bedrock-agentcore-onboarding
Scaffold and draft a new AgentCore workshop. An agent skill from aws-samples/sample-amazon-bedrock-agentcore-onboarding.
Related
Works with
Categories
Questions about Sync Ja
What does Sync Ja do?
Sync Japanese README translations with English source. An agent skill from aws-samples/sample-amazon-bedrock-agentcore-onboarding. Sync Ja is an agent skill from aws-samples/sample-amazon-bedrock-agentcore-onboarding, published by the product's own GitHub organization. Sync Japanese README translations with English source.
When should I use Sync Ja?
Sync Ja fits situations like: english READMEs change and Japanese versions need updating; improving Japanese translation fluency.
How do I install Sync Ja in Claude Code?
Run `npx skills add aws-samples/sample-amazon-bedrock-agentcore-onboarding --skill sync-ja -a claude-code`. Or copy the skill folder (.claude/skills/sync-ja in aws-samples/sample-amazon-bedrock-agentcore-onboarding) into .claude/skills/sync-ja in your project. Claude Code loads it when a task matches its description.
How do I install Sync Ja in Codex?
Run `npx skills add aws-samples/sample-amazon-bedrock-agentcore-onboarding --skill sync-ja -a codex`. Or copy the skill folder (.claude/skills/sync-ja in aws-samples/sample-amazon-bedrock-agentcore-onboarding) into .agents/skills/sync-ja in your project. Codex loads it when a task matches its description.
Can I use Sync Ja in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add aws-samples/sample-amazon-bedrock-agentcore-onboarding --skill sync-ja -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sync-ja, .gemini/skills/sync-ja, .github/skills/sync-ja and .opencode/skills/sync-ja in your project.
What does Sync Ja need to run?
SKILL.md names no scripts, command-line tools or credentials: Sync Ja is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Write, Edit, Glob, Grep, Task, AskUserQuestion.
Does Sync Ja access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Sync Ja safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Sync Ja use?
Sync Ja is published under the MIT-0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Sync Ja use?
About 1.5k tokens (SKILL.md is roughly 6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Sync Ja?
Skills that share tags, products or a category with Sync Ja: Aholo Viewer Docs (manycoretech/aholo-viewer, 1.1k stars), Moonbit Docs Maintainer (moonbitlang/moonbit-docs, 2.4k stars), Dsh Web Documentation (zhu1090093659/dsh-web, 8.4k stars) and Translate It Doc En Zh (mxsm/rocketmq-rust, 1.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Sync Ja?
aws-samples (a GitHub organization, an official publisher) maintains it in aws-samples/sample-amazon-bedrock-agentcore-onboarding, which has 133 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 1, 2026.
Source: aws-samples/sample-amazon-bedrock-agentcore-onboarding on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.