Use this skill to scaffold a new human-language locale for the kit's skills/agents/CLAUDE.md. Mirrors every existing SKILL.md.hbs into a SKILL.md.<locale>.hbs stub so a translator (or LLM) can edit copy without touching machine-readable frontmatter. Default locale codes — vi, ja, fr, es, de — but accepts any 2-5 char code.
Scanned 6/5/2026
Install via CLI
openskills install tuanle96/agent-harness-kit---
name: i18n-add-locale
description: Use this skill to scaffold a new human-language locale for the kit's skills/agents/CLAUDE.md. Mirrors every existing SKILL.md.hbs into a SKILL.md.<locale>.hbs stub so a translator (or LLM) can edit copy without touching machine-readable frontmatter. Default locale codes — vi, ja, fr, es, de — but accepts any 2-5 char code.
allowed-tools: Read, Write, Bash(node .harness/scripts/locale-scaffold.mjs:*)
suggested-turns: 4
---
## When to invoke
- Adding a new human language to the kit (or a fork's downstream).
- After upstream adds a new English skill — re-running this skill scaffolds
the locale stubs for the new file, leaving translated files untouched.
## Steps
1. **Pick a locale.** Two-to-five char ISO code (vi, ja, fr-CA, etc.).
2. **Dry-run the scan.**
```
node .claude/skills/i18n-add-locale/scripts/locale-scaffold.mjs \
--locale <code> --dry-run
```
Lists every SKILL.md / SKILL.md.hbs that lacks a `.<locale>.hbs` sibling.
3. **Materialize stubs.**
```
node .claude/skills/i18n-add-locale/scripts/locale-scaffold.mjs \
--locale <code>
```
For each missing sibling, copies the English master and prepends a
`<!-- LOCALE_TODO: translate body --> ` banner so the translator can grep
for pending work.
4. **Register the locale.** Edit `src/core/render-templates.mjs` and add the
code to `SUPPORTED_HUMAN_LANGS`. The renderer picks the variant via
`--locale <code>` or `HARNESS_LOCALE` env.
5. **Verify rendering** by running `agent-harness-kit init --locale <code>`
in a scratch dir and grepping the output for `LOCALE_TODO` (must be
zero before publishing).
## Output contract
```
locale: <code>
scaffolded: <N>
already-present: <M>
register-in: src/core/render-templates.mjs (SUPPORTED_HUMAN_LANGS)
```
## Anti-patterns
- Don't translate the YAML frontmatter — the renderer + Claude Code parse
it as machine-readable. Translate only the body markdown.
- Don't drop the master `.hbs` file. The locale stub *augments*; the
renderer falls back to the master when the locale variant is missing.
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.