Translator Api

This handles browser Translator API integration for on-device translation in JavaScript or TypeScript web apps. It walks you through capability checks, session lifecycle, model download UX, streaming output, and permissions policy wiring. The procedures are thorough: you get guarded session templates, abort handling, quota measurement, and fallback patterns for unsupported language pairs or blocked contexts. It won't help with cloud translation SDKs or server-side pipelines. If you're adding translation to a frontend and want to use the built-in browser API instead of shipping to a service, this gives you the full integration checklist and keeps you out of the common traps around secure contexts and iframe delegation.

skills.sh installs: 151
GitHub stars: 31
last updated: Jun 3, 2026

View on GitHub

Install

$ npx -y skills add webmaxru/agent-skills --skill translator-api --agent claude-code

Installs into .claude/skills of the current project.

Files

Translator API

Procedures

Step 1: Identify the browser integration surface

Inspect the workspace for browser entry points, text-input flows, localization UI, and any existing AI abstraction layer.
Execute node scripts/find-translator-targets.mjs . to inventory likely frontend files and existing Translator API markers when a Node runtime is available.
If a Node runtime is unavailable, inspect the nearest package.json, HTML entry point, and framework bootstrap files manually to identify the browser app boundary.
If the workspace contains multiple frontend apps, prefer the app that contains the active route, translation UI, or user-requested feature surface.
If the inventory still leaves multiple plausible frontend targets, stop and ask which app should receive the Translator API integration.
If the project is not a browser web app, stop and explain that this skill does not apply.

SKILL.md on GitHub