Agent skill

Website I18n

Envilder website internationalization workflow. An agent skill from macalbert/envilder.

Install Website I18n

skills CLI

$ npx skills add macalbert/envilder --skill website-i18n -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install macalbert/envilder website-i18n --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/macalbert/envilder.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/website-i18n .claude/skills/website-i18n && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "website-i18n" agent skill from https://github.com/macalbert/envilder/tree/main/.github/skills/website-i18n into .claude/skills/website-i18n/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "website-i18n", 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

$skill-installer install https://github.com/macalbert/envilder/tree/main/.github/skills/website-i18n

Type 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.

skills CLI

$ npx skills add macalbert/envilder --skill website-i18n -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install macalbert/envilder website-i18n --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/macalbert/envilder.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/website-i18n .agents/skills/website-i18n && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "website-i18n" agent skill from https://github.com/macalbert/envilder/tree/main/.github/skills/website-i18n into .agents/skills/website-i18n/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "website-i18n", 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.

skills CLI

$ npx skills add macalbert/envilder --skill website-i18n -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install macalbert/envilder website-i18n --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/macalbert/envilder.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/website-i18n .cursor/skills/website-i18n && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "website-i18n" agent skill from https://github.com/macalbert/envilder/tree/main/.github/skills/website-i18n into .cursor/skills/website-i18n/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "website-i18n", 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

$ gemini skills install https://github.com/macalbert/envilder.git --path .github/skills/website-i18n

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add macalbert/envilder --skill website-i18n -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install macalbert/envilder website-i18n --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/macalbert/envilder.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/website-i18n .gemini/skills/website-i18n && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "website-i18n" agent skill from https://github.com/macalbert/envilder/tree/main/.github/skills/website-i18n into .gemini/skills/website-i18n/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "website-i18n", 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.

GitHub CLI

$ gh skill install macalbert/envilder website-i18n

Installs 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).

skills CLI

$ npx skills add macalbert/envilder --skill website-i18n -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/macalbert/envilder.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/website-i18n .github/skills/website-i18n && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "website-i18n" agent skill from https://github.com/macalbert/envilder/tree/main/.github/skills/website-i18n into .github/skills/website-i18n/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "website-i18n", 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.

skills CLI

$ npx skills add macalbert/envilder --skill website-i18n -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install macalbert/envilder website-i18n --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/macalbert/envilder.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/website-i18n .opencode/skills/website-i18n && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "website-i18n" agent skill from https://github.com/macalbert/envilder/tree/main/.github/skills/website-i18n into .opencode/skills/website-i18n/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "website-i18n", 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: website-i18n
GitHub stars: 138
Token cost: ~761 tokens
SKILL.md length: 284 words
Files: 1
Skills in repo: 30
Repo updated: Oct 5, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Envilder website internationalization workflow. An agent skill from macalbert/envilder.

Works in 4 steps: Define the type → Add strings to every locale file → Use in component → …
Reviewing translated strings
SKILL.md covers When to Use, File Locations, Adding New Translations:… and Terms That MUST NOT Be…, plus 2 more sections
Calls aws and tsc

What it does

Website I18n is an agent skill from macalbert/envilder. Envilder website internationalization workflow. Use when adding, editing, or reviewing translated strings, creating localized pages, or verifying i18n completeness. Covers the full lifecycle from type definition to locale files.

Its SKILL.md is about 760 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 Frontend & Design, covering Internationalization. It works with Astro and TypeScript. The repository describes itself as: One secret mapping for local dev, CI/CD, and runtime. Envilder resolves cloud secrets from your own vaults without SaaS middlemen, duplicated config, or .env drift. The licence is MIT.

When your agent uses it

Reviewing translated strings
Creating localized pages
Verifying i18n completeness

Example prompts

“/website-i18n”

Requirements

Node.js

Workflow steps

4 steps, taken from the step headings in SKILL.md.

Define the type
Add strings to every locale file
Use in component
Create localized pages

What it can do on your machine

Read from SKILL.md and the folder at commit b6a0327. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- aws
- tsc
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use aws, which can reach the network depending on how they are called.
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

Website I18n loads about 761 tokens when it runs. Until then it costs about 60 tokens; SKILL.md has 284 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~60
When it runs · the whole SKILL.md, loaded when a task matches: ~761

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: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

NoteMentions a .env fileSKILL.md:84

`.env`, `--map`, `--envfile`, `--exec`, `--provider`, `--push`, `CI/CD`, `IAM`,

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 macalbert/envilder at commit b6a0327, republished under its MIT licence (© macalbert). 284 words, ~761 tokens.

Download SKILL.mdSave it as .claude/skills/website-i18n/SKILL.md (or your agent's skills folder).

name: website-i18n
description: Envilder website internationalization workflow. Use when adding, editing, or reviewing translated strings, creating localized pages, or verifying i18n completeness. Covers the full lifecycle from type definition to locale files.

Website i18n

Every user-visible string on the Envilder website MUST go through the i18n system. Never hardcode text in components.

When to Use

Adding new user-visible text to any component or page
Creating a new page (must create locale variants)
Reviewing PRs that add/change website content
Checking i18n completeness after content changes

File Locations

What	Where
Translation types	`src/website/src/i18n/types.ts`
Locale files	`src/website/src/i18n/{en,ca,es}.ts` (one per locale)
i18n utilities	`src/website/src/i18n/utils.ts`
Astro i18n config	`src/website/astro.config.mjs` → `i18n.locales`
Pages (default locale)	`src/website/src/pages/*.astro`
Pages (other locales)	`src/website/src/pages/<locale>/*.astro`

Adding New Translations: 4-Step Workflow

1. Define the type

Add the new key structure in src/website/src/i18n/types.ts:

typescript

// In the Translations interface
section: {
  title: string;
  description: string;
};

2. Add strings to every locale file

Update all locale files in src/website/src/i18n/:

en.ts: English (source)
ca.ts: Catalan
es.ts: Spanish

TypeScript will error if any locale is missing a key defined in types.ts.

3. Use in component

Access translations via the useTranslations helper:

astro

---
import { useTranslations } from '../i18n/utils';
const { lang = 'en' } = Astro.props;
const t = useTranslations(lang);
---
<h2>{t.section.title}</h2>
<p>{t.section.description}</p>

4. Create localized pages

For new pages:

Default locale: src/website/src/pages/new-page.astro
Other locales: src/website/src/pages/<locale>/new-page.astro

Check astro.config.mjs → i18n.locales to discover all active locales.

Terms That MUST NOT Be Translated

Product names, CLI flags, code tokens, and acronyms stay in English:

envilder, AWS SSM, Azure Key Vault, GitHub Action, envilder.json, .env, --map, --envfile, --exec, --provider, --push, CI/CD, IAM, RBAC, CLI, API, JSON, YAML, Node.js, pnpm, npx

Constraints

Never hardcode user-visible text: always use i18n keys
Never hardcode version numbers: use __SDK_*_VERSION__ / __APP_VERSION__ globals from astro.config.mjs
All 3 locales must be updated simultaneously (TypeScript catches mismatches)
Preserve existing key structure: add new keys, don't rename existing ones without updating all references

Verification

After adding translations:

TypeScript compilation catches missing keys (tsc --noEmit or dev server)
Navigate to each locale in dev server to verify text renders
Optionally delegate to @i18n Reviewer for linguistic quality check

Files

Just SKILL.md in .github/skills/website-i18n of macalbert/envilder.

Open the folder on GitHubat commit b6a0327

Compare with similar skills

Website I18n 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.

Website I18n compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Website I18n this skillmacalbert/envilder	138	—	~761	Automated safety check: Notes	MIT	3 days ago
Create Docsvictorgarciaesgi/nuxt-typed-router	413	2 repos	~2.8k	Automated safety check: Pass	MIT	2 days ago
Building With Lobe UIlobehub/lobe-ui	2.2k	—	~2k	Automated safety check: Pass	MIT	today
Motion Dev Animations199-biotechnologies/motion-dev-animations-skill	105	1 repos	~2.8k	Automated safety check: Notes	MIT	6 mo ago
Instui Docsinstructure/instructure-ui	482	—	~498	Automated safety check: Pass	Custom licence	yesterday
Aholo Site Ownermanycoretech/aholo-viewer	1.1k	—	~530	Automated safety check: Pass	MIT	today

Similar skills

Create Docs
victorgarciaesgi/nuxt-typed-router
Create complete documentation sites for projects. An agent skill from victorgarciaesgi/nuxt-typed-router.
413 GitHub starsUsed in 2 repos~2.8k tokens
Frontend & DesignAuto-check passed
Building With Lobe UI
lobehub/lobe-ui
Build UI with the LobeHub design ecosystem — @lobehub/ui (plus its base-ui, chat, mobile, awesome, brand, mdx, i18n namespaces), @lobehub/icons, @lobehub/charts, @lobehub/fluent-emoji and…
2.2k GitHub stars~2k tokensUpdated today
Frontend & DesignAuto-check passed
Motion Dev Animations
199-biotechnologies/motion-dev-animations-skill
Creates 120fps GPU-accelerated animations with Motion.dev (Framer Motion successor) for React, Next.js, Svelte, and Astro projects.
105 GitHub starsUsed in 1 repo~2.8k tokens
Frontend & DesignAuto-check: notes
Instui Docs
instructure/instructure-ui
Look up authoritative Instructure UI (InstUI, @instructure/ui-) documentation — component APIs, props, theme variables, usage examples, and guides — by querying instructure.design's plaintext docs.
482 GitHub stars~498 tokensUpdated yesterday
Frontend & DesignAuto-check passed
Aholo Site Owner
manycoretech/aholo-viewer
Owns the Aholo Viewer Astro website shell and Playground integration, covering routes, layouts, i18n copy and scoped CSS, while leaving the renderer and example content to other skills.
1.1k GitHub stars~530 tokensUpdated today
Frontend & DesignAuto-check passed
Admin Template Project Initializer
southliu/south-admin-react
Removes the south-admin-react template's demo pages, components and menu entries, after a dry-run preview and your confirmation, and cleans up the matching imports.
580 GitHub stars~519 tokensUpdated 18 days ago
Frontend & DesignAuto-check passed

Questions about Website I18n

What does Website I18n do?

Envilder website internationalization workflow. An agent skill from macalbert/envilder. Website I18n is an agent skill from macalbert/envilder. Envilder website internationalization workflow.

When should I use Website I18n?

Website I18n fits situations like: reviewing translated strings; creating localized pages; verifying i18n completeness.

How do I install Website I18n in Claude Code?

Run `npx skills add macalbert/envilder --skill website-i18n -a claude-code`. Or copy the skill folder (.github/skills/website-i18n in macalbert/envilder) into .claude/skills/website-i18n in your project. Claude Code loads it when a task matches its description.

How do I install Website I18n in Codex?

Run `npx skills add macalbert/envilder --skill website-i18n -a codex`. Or copy the skill folder (.github/skills/website-i18n in macalbert/envilder) into .agents/skills/website-i18n in your project. Codex loads it when a task matches its description.

Can I use Website I18n 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 macalbert/envilder --skill website-i18n -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/website-i18n, .gemini/skills/website-i18n, .github/skills/website-i18n and .opencode/skills/website-i18n in your project.

What does Website I18n need to run?

Going by SKILL.md and its folder, Website I18n needs the command-line tools its instructions call (aws and tsc). Our summary lists: Node.js.

Does Website I18n 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 Website I18n safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Website I18n use?

Website I18n is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Website I18n use?

About 761 tokens (SKILL.md is roughly 3k 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 Website I18n?

Skills that share tags, products or a category with Website I18n: Create Docs (victorgarciaesgi/nuxt-typed-router, 413 stars), Building With Lobe UI (lobehub/lobe-ui, 2.2k stars), Motion Dev Animations (199-biotechnologies/motion-dev-animations-skill, 105 stars) and Instui Docs (instructure/instructure-ui, 482 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Website I18n?

macalbert (a GitHub user) maintains it in macalbert/envilder, which has 138 GitHub stars. The repository holds 30 skills in this directory. The repository was last updated on October 5, 2026.

Source: macalbert/envilder on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Website I18n

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Website i18n

When to Use

File Locations

Adding New Translations: 4-Step Workflow

1. Define the type

2. Add strings to every locale file

3. Use in component

4. Create localized pages

Terms That MUST NOT Be Translated

Constraints

Verification

Files

Compare with similar skills

Similar skills

More from macalbert/envilder

Related

Questions about Website I18n