verbatra
- 3 skills
- 0 followers
- 14 hours ago last updated
- ▌ Verbatra CLI · verbatraDrive the verbatra i18n CLI from a shell or CI. Use when locale files are out of sync, a key exists in the source locale but is missing in de/es/fr, a translation needs re-running after the source text changed, translation drift has to gate a pull request, strings have to be handed to a human translator and imported back, or a project needs verbatra set up. Also use when deciding whether a command costs money before running it, when branching on a verbatra exit code, or when reading verbatra.lock.json. Covers every command the verbatra binary registers, the supported formats and providers, and the JSON envelope.
- ▌ Verbatra MCP Tools · verbatraOperate a verbatra i18n project through the verbatra stdio MCP server, the one a verbatra mcp process serves over stdio. Use when an MCP client is connected to a verbatra server and translation status has to be read, a key is missing or stale in a target locale, a translation has to be corrected or re-run, a glossary term has to be added, or the review queue and token usage of the last run have to be reported. Also use when a provider-spending tool appears to be absent from the tool list. Covers every registered tool, the spend boundary that keeps some of them off the default list, and what each result means.
- ▌ Verbatra Studio Agent Tools · verbatraOperate a verbatra i18n project from an open Verbatra Studio dashboard tab through its WebMCP browser tools. Use when a browser agent is driving the Studio dashboard and translation status has to be read, a key is missing or stale in a target locale, translation values have to be scanned in bulk, who last changed a locale file has to be found, or a translation has to be corrected in place. Also use when the Studio tools are absent from the tab, or a provider-spending tool is missing from the set. Covers the whole tool set, the two gates that decide which tools register, and the traps specific to driving a browser tab.