Translation Diff Export
Devolutions/UniGetUI
Compares UniGetUI JSON locale files against English, identifies untranslated or source-changed keys, and generates patch, reference, and handoff files for a target language.
Load BEFORE curating an existing Lean 4 source repo into the benchmark format.
$ npx skills add sunblaze-ucb/vero --skill vero-source-lean -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install sunblaze-ucb/vero vero-source-lean --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/sunblaze-ucb/vero.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/vero-source-lean .claude/skills/vero-source-lean && rm -rf skills-srcUse ~/.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/
Install the "vero-source-lean" agent skill from https://github.com/sunblaze-ucb/vero/tree/main/.claude/skills/vero-source-lean into .claude/skills/vero-source-lean/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vero-source-lean", 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 install https://github.com/sunblaze-ucb/vero/tree/main/.claude/skills/vero-source-leanType 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.
$ npx skills add sunblaze-ucb/vero --skill vero-source-lean -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install sunblaze-ucb/vero vero-source-lean --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sunblaze-ucb/vero.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/vero-source-lean .agents/skills/vero-source-lean && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "vero-source-lean" agent skill from https://github.com/sunblaze-ucb/vero/tree/main/.claude/skills/vero-source-lean into .agents/skills/vero-source-lean/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vero-source-lean", 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.
$ npx skills add sunblaze-ucb/vero --skill vero-source-lean -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install sunblaze-ucb/vero vero-source-lean --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sunblaze-ucb/vero.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/vero-source-lean .cursor/skills/vero-source-lean && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "vero-source-lean" agent skill from https://github.com/sunblaze-ucb/vero/tree/main/.claude/skills/vero-source-lean into .cursor/skills/vero-source-lean/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vero-source-lean", 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 https://github.com/sunblaze-ucb/vero.git --path .claude/skills/vero-source-lean--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add sunblaze-ucb/vero --skill vero-source-lean -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install sunblaze-ucb/vero vero-source-lean --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sunblaze-ucb/vero.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/vero-source-lean .gemini/skills/vero-source-lean && rm -rf skills-srcUse ~/.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/
Install the "vero-source-lean" agent skill from https://github.com/sunblaze-ucb/vero/tree/main/.claude/skills/vero-source-lean into .gemini/skills/vero-source-lean/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vero-source-lean", 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.
$ gh skill install sunblaze-ucb/vero vero-source-leanInstalls 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).
$ npx skills add sunblaze-ucb/vero --skill vero-source-lean -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/sunblaze-ucb/vero.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/vero-source-lean .github/skills/vero-source-lean && rm -rf skills-srcUse ~/.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/
Install the "vero-source-lean" agent skill from https://github.com/sunblaze-ucb/vero/tree/main/.claude/skills/vero-source-lean into .github/skills/vero-source-lean/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vero-source-lean", 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.
$ npx skills add sunblaze-ucb/vero --skill vero-source-lean -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install sunblaze-ucb/vero vero-source-lean --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sunblaze-ucb/vero.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/vero-source-lean .opencode/skills/vero-source-lean && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "vero-source-lean" agent skill from https://github.com/sunblaze-ucb/vero/tree/main/.claude/skills/vero-source-lean into .opencode/skills/vero-source-lean/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vero-source-lean", 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.
vero-source-leanLoad BEFORE curating an existing Lean 4 source repo into the benchmark format.
Vero Source Lean is an agent skill from sunblaze-ucb/vero. Load BEFORE curating an existing Lean 4 source repo into the benchmark format. Lean→Lean is mostly extraction, not translation — the source defs become the canonical Impl, the source theorems become the spec obligations. Pair with vero-discover, vero-plan, vero-translate, vero-spec-write, and vero-lean-pitfalls.
Its SKILL.md is about 2k 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 Writing & Content, covering Translation. The licence is Apache-2.0.
3 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 0a7325d. It shows what the files ask for, not the result of running them.
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.
No scripts in the folder and no shell commands in SKILL.md (its code samples are lean).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Vero Source Lean loads about 2k tokens when it runs. Until then it costs about 83 tokens; SKILL.md has 929 words of instructions outside code blocks.
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.
The automated check found no risky patterns in SKILL.md.
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.
The full file from sunblaze-ucb/vero at commit 0a7325d, republished under its Apache-2.0 licence (© sunblaze-ucb). 929 words, ~2,000 tokens.
.claude/skills/vero-source-lean/SKILL.md (or your agent's skills folder).Lean source is the special case: the upstream is already in the target language. The curation work is not translation but extraction + reshaping to fit the ratified benchmark paradigm.
Reference the canonical shape at reference/BankLedger/. The end product looks identical to a benchmark curated from Dafny / Verus / Coq — the difference is the path to get there.
Given a Lean 4 source repo (no lakefile.toml at the curation-output path, just .lean files), produce a benchmark Lean project with:
Impl/<Module>.lean): the source's executable defs become def <Project>.<name> : <Sig> := <body> wrapped in !benchmark code def=<name> markers. The body is the real Lean source body — pre-agent-gen will replace it with sorry before the LLM sees the benchmark.Spec/<Module>.lean): the source's theorems / lemmas become def spec_<name> (impl : RepoImpl) : Prop := <statement> definitions. The theorems themselves are dropped — proofs live in Proof/ (materialized later for gen).Because Lean→Lean is extraction, every selected theorem/spec must keep source traceability. Emit or preserve a source map that records the source declaration, target Lean spec/API, and whether the item was extracted, compressed, trusted/opaque, or intentionally skipped. Do not assume one source file maps to exactly one benchmark file.
| Source construct | Output classification |
|---|---|
def f : T := body (top-level executable) | API (kind=api) — body becomes code marker interior |
def _f / private def f / nested def inside a non-API | API helper (kind=api_helper) |
theorem t : P x := proof | Spec candidate — P x is the spec body |
lemma t : P x := proof | Spec candidate (same as theorem) |
def P : T → Prop := … (predicate) | Spec helper (spec_helpers[]) — used in spec bodies |
structure Foo where ... | Type — preserved verbatim |
inductive Foo := ... | Type |
abbrev FooSig := T → U | Sig abbrev — passed through as-is |
instance : Hashable Foo := … | Type-class instance — preserved in global_aux if unrelated to spec bodies |
axiom A : P | Trusted axiom — added to manifest.json::trusted_axioms |
opaque f : T → U | Opaque — preserved in global_aux |
import … | Import — preserved at file head |
#guard … / example … | Test → Test.lean |
#eval … (debug) | Skip; flag with @review human |
The single hard part. A typical Lean theorem looks like:
theorem ledger_create_zero (ledger : Ledger) (id : AccountId) :
¬ accountExists id ledger →
getBalance id (createAccount id ledger) = some 0 := by
intro h
…The benchmark spec is the proposition shape, not the proof. Strip the proof (:= by …) and reshape into a RepoImpl parameter:
def spec_ledger_create_zero (impl : RepoImpl) : Prop :=
∀ (ledger : Ledger) (id : AccountId),
¬ impl.bankLedger.accountExists id ledger →
impl.bankLedger.getBalance id (impl.bankLedger.createAccount id ledger) = some 0Rules:
impl.<repo_impl_field>.<fn>. The source uses bare names (createAccount); the spec uses bundle-qualified names (impl.bankLedger.createAccount).: becomes Prop (it already was).∀-quantified at the spec level (the source theorem's parameters become explicit ∀ in the spec body).def isWellFormed : Ledger → Prop), preserve that predicate as a spec_helper_* in the same Spec/<Module>.lean file. Reference it from the spec body.<module>_<intent> map to specs spec_<module>_<intent>.createAccountZeroBalance) map to snake_case (spec_create_account_zero_balance).createAccount_zero_balance), preserve and just prefix spec_.For each module:
<source>/<Module>.lean.<Project>/Impl/<Module>.lean:global_aux and outside-marker contextabbrev <Name>Sig := <type> for each APIdef <Project>.<name> : <Project>.<Name>Sig := <original-body> inside code marker paircode_aux marker pair (empty, room for the LLM to add internal helpers)select.json):def spec_<name> (impl : RepoImpl) : Prop := <body> in <Project>/Spec/<Module>.leanimpl.<repo_impl_field>.<fn>manifest.json::packages[].modules[]:apis[] lists the executables; each entry { name, sig, type, kind: "api" }specs[] lists the spec names (bare strings)spec_helpers[] lists predicate helpers if anyBundle.lean + Harness.lean + Test.lean standard (one bundle field per API; canonical wires through to <Project>.<api>; #guards from source #guard/example).Lean→Lean curation is honest extraction of what the upstream source already proves — it must NOT synthesize new specs. The lean_spec workflow therefore deliberately omits the spec_write stage; the only specs in the curated benchmark are the ones the translate stage extracts from existing source theorem / lemma / example declarations.
If a curator wants additional specs, they should extend the upstream source repo with new theorems first (so the new specs are anchored in real, type-checked claims about the API), then re-run curation. Do not edit the curated benchmark to add specs that don't exist upstream.
Do not turn a source theorem into a benchmark obligation if the extracted
spec_* ignores RepoImpl, concludes True, or only proves a library
helper fact unrelated to the implementation. Classify those as
spec_helper / source context unless there is an explicit human
decision to keep a theorem-only obligation.
lake build succeeds.apis[] entry has its abbrev <Sig> + def <Project>.<name> in the right Impl file.specs[] entry exists as def spec_<name> (impl : RepoImpl) : Prop := … in the right Spec file.Spec/<Module>.lean files have NO theorem / lemma / example declarations (the validator's spec_shape check enforces this).axiom declarations are listed in manifest.json::trusted_axioms..vero/source_map.json,
.vero/discover.json, or another validator-readable artifact.Spec/. They're not benchmark obligations; they're proofs that the source was correct.instance blocks for DecidableEq unless they're already in the source — the validator's anti-cheat instance check (gen/eval side) rejects suspicious additions.def spec_helper_x (executable predicate, used in specs) with def spec_x (proof obligation). They live in the same Spec file but their manifest classification differs.© sunblaze-ucb, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .claude/skills/vero-source-lean of sunblaze-ucb/vero.
Open the folder on GitHubat commit 0a7325d
Vero Source Lean 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Vero Source Lean this skillsunblaze-ucb/vero | 107 | — | ~2k | Automated safety check: Pass | Apache-2.0 | |
| Translation Diff ExportDevolutions/UniGetUI | 26k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Sync Translationssymfony/symfony | 31k | — | ~1.9k | Automated safety check: Pass | MIT | |
| Translation Diff ImportDevolutions/UniGetUI | 26k | — | ~750 | Automated safety check: Pass | MIT | |
| Translation Diff TranslateDevolutions/UniGetUI | 26k | — | ~934 | Automated safety check: Pass | MIT | |
| Generate Translationspayloadcms/payload | 45k | — | ~1.1k | Automated safety check: Pass | MIT |
Devolutions/UniGetUI
Compares UniGetUI JSON locale files against English, identifies untranslated or source-changed keys, and generates patch, reference, and handoff files for a target language.
symfony/symfony
Synchronize translation catalogs across maintained Symfony branches: find messages that newer branches added to the English catalogs but that are still missing from the oldest maintained branch…
Devolutions/UniGetUI
Merges translated key-value pairs from a UniGetUI JSON localization patch back into the full language file and validates the merged result.
Devolutions/UniGetUI
Translates a sparse UniGetUI JSON language patch, writes completed entries into the working copy, preserves placeholders and terminology, and prepares the patch for merge-back.
payloadcms/payload
A skill your agent uses when new translation keys are added to packages to generate new translations strings
Narcooo/inkos
Drives long-form fiction, scripts, storyboards, interactive films and long-document translation through InkOS, with every change made by a typed action.
sunblaze-ucb/vero
A skill your agent uses when scanning a verified source repo (Dafny, Verus, or Coq) to classify every item and produce per-file discovery markdown for human curation.
sunblaze-ucb/vero
A skill your agent uses when translating selected verified items from Dafny/Verus/Coq into a compilable Lean 4 benchmark.
sunblaze-ucb/vero
Load BEFORE translating any Coq item to Lean 4 to avoid known Coq→Lean pitfalls.
sunblaze-ucb/vero
Load BEFORE translating any Dafny item to Lean 4 to avoid known Dafny→Lean pitfalls.
sunblaze-ucb/vero
Load BEFORE writing any Lean 4 translation to avoid common Lean pitfalls (universes, coercions, type-class resolution, notation).
sunblaze-ucb/vero
Use after vero-select to write a detailed translation plan as .vero/plan.json — the authoritative contract the TRANSLATE stage executes.
Categories
Load BEFORE curating an existing Lean 4 source repo into the benchmark format. Vero Source Lean is an agent skill from sunblaze-ucb/vero. Load BEFORE curating an existing Lean 4 source repo into the benchmark format.
Vero Source Lean fits situations like: tasks that involve Translation.
Run `npx skills add sunblaze-ucb/vero --skill vero-source-lean -a claude-code`. Or copy the skill folder (.claude/skills/vero-source-lean in sunblaze-ucb/vero) into .claude/skills/vero-source-lean in your project. Claude Code loads it when a task matches its description.
Run `npx skills add sunblaze-ucb/vero --skill vero-source-lean -a codex`. Or copy the skill folder (.claude/skills/vero-source-lean in sunblaze-ucb/vero) into .agents/skills/vero-source-lean in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sunblaze-ucb/vero --skill vero-source-lean -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/vero-source-lean, .gemini/skills/vero-source-lean, .github/skills/vero-source-lean and .opencode/skills/vero-source-lean in your project.
SKILL.md names no scripts, command-line tools or credentials: Vero Source Lean is instructions for the agent only.
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.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Vero Source Lean is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2k tokens (SKILL.md is roughly 8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Vero Source Lean: Translation Diff Export (Devolutions/UniGetUI, 26k stars), Sync Translations (symfony/symfony, 31k stars), Translation Diff Import (Devolutions/UniGetUI, 26k stars) and Translation Diff Translate (Devolutions/UniGetUI, 26k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
sunblaze-ucb (a GitHub organization) maintains it in sunblaze-ucb/vero, which has 107 GitHub stars. The repository holds 16 skills in this directory. The repository was last updated on August 17, 2026.
Source: sunblaze-ucb/vero on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.