What is next-intl-workflows-and-tooling?

A guide for setting up and maintaining translations in Next.js applications with next-intl, a library for displaying text in different languages. It covers type checking, message loading, validation, translation services, and experimental extraction tools.

Use it when configuring next-intl, migrating or upgrading it, checking translations, connecting Crowdin, or using message extraction and precompilation.

It helps prevent missing translations, incorrect setup, weak type checking, and localization workflows that are difficult to maintain.

next-intl-workflows-and-tooling — Skill for Claude Code and Codex by a

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add andrewsrigom/agent-skills --skill next-intl-workflows-and-tooling

Clone the repo

git clone --depth 1 https://github.com/andrewsrigom/agent-skills

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/andrewsrigom/agent-skills/next-intl-workflows-and-tooling/github.svg)](https://agentmods.dev/skills/andrewsrigom/agent-skills/next-intl-workflows-and-tooling)

Your own site

<a href="https://agentmods.dev/skills/andrewsrigom/agent-skills/next-intl-workflows-and-tooling"><img src="https://agentmods.dev/badge/skills/andrewsrigom/agent-skills/next-intl-workflows-and-tooling/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/andrewsrigom/agent-skills/next-intl-workflows-and-tooling"><img src="https://agentmods.dev/badge/skills/andrewsrigom/agent-skills/next-intl-workflows-and-tooling.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 71 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 848 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00071	$0.00848
Opus 5	$0.00036	$0.00424
Sonnet 5	$0.00014	$0.00170
Haiku 4.5	$0.00007	$0.00085

Measured 11d ago against content hash b9981e8fc9dc, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

next-intl-workflows-and-tooling scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

next-intl/next-intl-workflows-and-tooling/SKILL.md · 86 lines

How it starts

The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Next Intl Workflows and Tooling

Use this skill when the task is about durable setup, typing, validation, translation operations, or experimental tooling.

Scope

createNextIntlPlugin and request-config discovery
TypeScript augmentation
plugin experimental options like createMessagesDeclaration, extract, messages, srcPath, and precompile
message loading strategy decisions
missing-message handling
validation and localization operations
useExtracted, getExtracted, and extraction-related tradeoffs

Routing cues

plugin setup, AppConfig, typed locales/messages/formats, Crowdin, extraction, validation -> use this skill
routing rules, pathnames, domains, locale switchers -> use next-intl-routing-and-navigation
message authoring, ICU, rich text, formatter APIs -> use next-intl-messages-and-formatting
getRequestConfig, metadata, error files, tests -> use next-intl-server-runtime

Default path

Read references/plugin-types-and-loading.md first.
If the task touches translation operations or extraction, read references/localization-ops-and-extraction.md.
Treat plugin setup and AppConfig augmentation as baseline correctness work, not optional polish.
Choose the simplest message-loading model that preserves type safety and operational clarity.

When to deviate

Use extraction tooling only when the repo’s translation workflow genuinely benefits from it.
Enable precompile only when the performance gain is worth the tradeoffs.
Keep repo-local message files unless an external translation system is clearly justified.

Guardrails

Keep createNextIntlPlugin() in sync with the real requestConfig path.
Prefer typed Locale, Messages, and Formats augmentation.
createMessagesDeclaration needs a representative messages file and TypeScript support for arbitrary extensions.
Keep repo-local message files as the default message source unless an external system is clearly justified.
Use onError and getMessageFallback deliberately instead of tolerating silent missing-message behavior.
Configure extract together with messages and srcPath, not in isolation.
Treat precompile as a performance optimization with tradeoffs. It is incompatible with t.raw.
Do not assume createMessagesDeclaration is needed when useExtracted is the chosen workflow.
Treat useExtracted as experimental and note its translator-context tradeoffs.

Read the full file on GitHub · 86 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

11d ago First seen · 86 lines · 71 tokens per session scan A b9981e8fc9dc

Subscribe to this mod's changes

next-intl-workflows-and-tooling is a skill published in the GitHub repository andrewsrigom/agent-skills (2 stars, last pushed 5mo ago), licensed MIT. It adds 71 tokens to every session and 848 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Frontend Localization

harden

Improve interface resilience through better error handling, i18n support, text overflow handling, and edge case management. Makes interfaces robust and production-ready. Use when the user asks to harden, make production-ready, handle edge cases, add error states, or fix overflow and i18n issues.

fengshao1227/ccg-workflow · 62 tokens

localization-toolkit

This skill should be used when setting up, auditing, or enforcing internationalization/localization in UI codebases (React/TS, i18next or similar, JSON locales), including installing/configuring the i18n framework, replacing hard-coded strings, ensuring en-US/zh-CN coverage, mapping error codes to localized messages…

zebbern/claude-code-guide · 82 tokens

json-ui

CRITICAL: Use for json-ui component rendering and development. Triggers on: json-ui, json render, component catalog, report render, HTML report, I18nString, i18n, bilingual, language switch, dual language, PaperHeader, AuthorList, Abstract, MetricsGrid, Section, Highlight, Zod schema, catalog.ts, cli.ts…

actionbook/actionbook · 118 tokens

experience-ui-bundle-localize

MUST activate to localize / internationalize a uiBundles//src/ project (React or Angular): extract hardcoded user-facing strings into Custom Labels, wire a runtime i18n library over the Platform SDK backend, add labels for another language, or troubleshoot label rendering across locales. Triggers: user-facing string…

forcedotcom/sf-skills · 225 tokens

ss-motion

Apply a named StyleSeed motion to a component — either one of the 5 personality seeds (Spring/Silk/Snap/Float/Pulse × entrance/exit/hover/press/layout) or a distinctive keyword move from the motion library (toggle-flip, toggle-curtain, reveal-blur, pop-in, shimmer, …). Translates vibe words into framer-motion code…

bitjaru/styleseed · 85 tokens

extract-source-sample

Given the path to a finished content-goose ad-run folder, extract everything that defines that ad — recipe shot list, VO script, characters, voices, world, atom-skills, master mp4 — and emit a source-sample.json in the exact shape the upload-ad-sample skill writes to the Goose Ads library. Also links every character…

gooseworks-ai/goose-skills · 160 tokens