Agent skill

Vero Source Verus

by sunblaze-ucb in sunblaze-ucb/vero

Load BEFORE translating Verus source (Rust with verus!. An agent skill from sunblaze-ucb/vero.

Apache-2.0Auto-check: notesWriting & Content

Install Vero Source Verus

skills CLI
$ npx skills add sunblaze-ucb/vero --skill vero-source-verus -a claude-code

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

GitHub CLI
$ gh skill install sunblaze-ucb/vero vero-source-verus --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/sunblaze-ucb/vero.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/vero-source-verus .claude/skills/vero-source-verus && 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/

Facts

Skill name
vero-source-verus
GitHub stars
107
Token cost
~1.8k tokens
SKILL.md length
565 words
Files
1
Skills in repo
16
Repo updated
First seen
Licence
Apache-2.0

At a glance

Load BEFORE translating Verus source (Rust with verus!. An agent skill from sunblaze-ucb/vero.

  • Tasks that involve Translation
  • SKILL.md covers When to use, Output-shape recap…, Verus fn modes → Lean… and Type mapping, plus 6 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Vero Source Verus is an agent skill from sunblaze-ucb/vero. Load BEFORE translating Verus source (Rust with verus! macro) to Lean 4. Provides Verus-specific classification rules (spec/proof/exec fn modes), type mappings (Seq/Map/Set vs List/AssocList), and patterns for mapping Verus constructs into the ratified bundle paradigm (Impl/ + Spec/ + Bundle + Harness). Pair with vero-discover, vero-plan, vero-translate, and vero-verus-pitfalls.

Its SKILL.md is about 1.8k 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. It works with Rust. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Translation

Example prompts

  • “/vero-source-verus”

Requirements

  • Pre-approved tools (allowed-tools): Read, Write, Edit, Bash, Grep, Glob

What it can do on your machine

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

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Edit
    • Bash
    • Grep
    • Glob

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are rust, json and lean).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    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

Vero Source Verus loads about 1.8k tokens when it runs. Until then it costs about 100 tokens; SKILL.md has 565 words of instructions outside code blocks.

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

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.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Read, Write, Edit, Bash, Grep, Glob

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 sunblaze-ucb/vero at commit 0a7325d, republished under its Apache-2.0 licence (© sunblaze-ucb). 565 words, ~1,819 tokens.

Download SKILL.mdSave it as .claude/skills/vero-source-verus/SKILL.md (or your agent's skills folder).
name
vero-source-verus
description
Load BEFORE translating Verus source (Rust with verus! macro) to Lean 4. Provides Verus-specific classification rules (spec/proof/exec fn modes), type mappings (Seq/Map/Set vs List/AssocList), and patterns for mapping Verus constructs into the ratified bundle paradigm (Impl/ + Spec/ + Bundle + Harness). Pair with vero-discover, vero-plan, vero-translate, and vero-verus-pitfalls.
allowed-tools
Read, Write, Edit, Bash, Grep, Glob

VCG Source: Verus → Lean 4

Verus-specific classification and translation patterns for the ratified curation paradigm. The shape of the emitted Lean is pinned by reference/BankLedger/ + .claude/skills/vero-translate/SKILL.md — this skill teaches the language mapping.

Worked upstream exemplar: reference/BankLedger-source-verus/ translates 1:1 into reference/BankLedger/. Cite it when the mapping is non-obvious.

When to use

  • Classifying items in a Verus source (with vero-discover).
  • Writing the translation plan (with vero-plan).
  • Emitting Lean from Verus (with vero-translate).

Output-shape recap (non-negotiable)

Per source module, translate emits:

  • <Project>/Impl/<Module>.lean — types + abbrev <Fn>Sig per API + def Bank.<fn> : Bank.<Fn>Sig := <translated reference impl> in code / code_aux markers. !curation @review v1 annotations.
  • <Project>/Spec/<Module>.lean — def spec_<…> (impl : RepoImpl) : Prop := … only. Frozen, no markers.
  • Bundle.lean, Harness.lean, Test.lean — shared, once per benchmark.

See .claude/skills/vero-translate/SKILL.md for file templates.

Verus fn modes → Lean classification

Verus declares every fn as exec, spec, or proof.

VerusLean artifactMarkers?
exec fn (an API)def Bank.<fn> : Bank.<FnSig> := <translated reference impl> in ImplYes — code / code_aux
exec fn (helper, not an API)Full body in ImplNo
spec fn (vocabulary)def <name> : <type> := … in Impl or Spec helpers; full bodyNo
proof fn / lemma (property worth tracking)spec_<name> entry → def spec_<name> in SpecNo (Spec frozen)
proof fn (pure proof helper)Drop from plan — becomes proof_aux downstream—
#[verifier::external_body]opaque in Impl; axiomatizeNo
axiom macroaxiom <name> : <type> near the related opaqueNo
#[test]#guard in Test.leanNo

Classify by role. A spec fn describing an invariant → vocabulary, no markers. A proof fn capturing a postcondition → spec_* entry.

Type mapping

VerusLean 4
u64 / u32 / u8Nat (usually)
i64 / i32Int
boolBool
StringString
Vec<T>List T
Seq<T> (spec-only)List T
Map<K, V> (spec-only)List (K × V) with uniqueness spec
Set<T> (spec-only)List T with uniqueness spec
Option<T>Option T
Result<T, E>Except E T
(T, U)T × U
struct Foo { x: u64 }structure Foo where x : Nat
enum Foo { A, B(u64) }inductive Foo where | A | B (_ : Nat)

u64 → Nat policy. Verus forces overflow bounds via requires/ensures; Lean's Nat has no overflow. Prefer Nat and elide overflow conditions — #guard tests still pin observable behavior. Note the divergence in the plan if the curator wants explicit overflow specs.

Show full SKILL.md (210 more words)Show less

Vec<T> vs Seq<T> and the @ view

In Verus, v@ lifts Vec<T> to Seq<T> for spec reasoning:

rust
fn push(v: &mut Vec<T>, x: T)
    ensures v@ == old(v)@.push(x)

In Lean, both become List T. The @ view has no direct analogue — drop it and operate on the List directly.

plan.json:

json
{
  "name": "spec_push_appends",
  "nl_description": "push extends the list with the new element at the end.",
  "lean_form": "∀ (v : List T) (x : T), impl.bankLedger.push v x = v ++ [x]",
  "apis_referenced": ["push"],
  "curator_intended_truth": "prove"
}

API translation pattern

Verus:

rust
pub fn create_account(id: AccountId, ledger: Ledger) -> (r: Ledger)
    requires /* … */
    ensures  /* post */
{ … }

plan.json:

json
{
  "upstream_name": "create_account",
  "lean_name": "createAccount",
  "sig_abbrev": "CreateAccountSig",
  "lean_type": "AccountId → Ledger → Ledger",
  "opaque": false,
  "nl_description": "Add a new account with the given id to the ledger."
}

Emitted Impl:

lean
namespace Bank
abbrev CreateAccountSig := AccountId → Ledger → Ledger
end Bank

-- !benchmark @start code_aux def=createAccount
-- !benchmark @end code_aux def=createAccount

-- !curation @review v1 [ ] createAccount — Impl/Account, code, reference impl
def Bank.createAccount : Bank.CreateAccountSig :=
-- !benchmark @start code def=createAccount
  -- translated Verus exec body, not `sorry`
  ...
-- !benchmark @end code def=createAccount
Partial functions
  • Type-enforced: use dependent argument or Option.
  • Caller-error explicit: Option <return> or Except Err <return>.
  • Pick consistently within a benchmark.

Spec translation pattern

proof fn stating a property
rust
proof fn deposit_preserves_sum(id: AccountId, amt: u64, l: Ledger)
    ensures sum(deposit(id, amt, l)) == sum(l) + amt
{ … }

plan.json:

json
{
  "name": "spec_deposit_preserves_sum",
  "nl_description": "Depositing `amt` adds exactly `amt` to the total.",
  "lean_form": "∀ (id : AccountId) (amt : Balance) (l : Ledger), impl.bankLedger.totalAssets (impl.bankLedger.deposit id amt l) = impl.bankLedger.totalAssets l + amt",
  "apis_referenced": ["deposit", "totalAssets"],
  "curator_intended_truth": "prove"
}

Emitted Spec:

lean
/-- Depositing `amt` adds exactly `amt` to the total. -/
def spec_deposit_preserves_sum (impl : RepoImpl) : Prop :=
  ∀ (id : AccountId) (amt : Balance) (l : Ledger),
    impl.bankLedger.totalAssets (impl.bankLedger.deposit id amt l) =
      impl.bankLedger.totalAssets l + amt
lemma_* proof helper

Many auxiliary lemmas per API under Verus — in the new paradigm they don't become separate benchmark artifacts. Drop from plan.json. The LLM may introduce similar helpers in proof_aux slots downstream.

external_body and opaque functions

rust
#[verifier::external_body]
pub fn now() -> u64 { … }

Translate to:

lean
opaque Bank.now : Unit → Nat

-- If Verus guarantees a postcondition:
axiom Bank.now_positive : ∀ u, Bank.now u > 0

Mark opaque: true in plan.json. No code markers for opaque functions.

Common pitfalls (see vero-verus-pitfalls)

  • &mut + old(x)@ has no Lean analogue; specs become value-passing f x = ….
  • Verus assume clauses are red flags; surface as !curation @review.
  • decreases clauses are proof hints; use them only when Lean needs termination help for the translated Impl body.
  • Trait-method calls may dispatch dynamically; Lean pins to concrete impls via canonical in Harness.

Load vero-verus-pitfalls before translating any non-trivial item.

Pair with

  • vero-plan — consumes Verus classifications.
  • vero-translate — emits Lean per the templates.
  • vero-verus-pitfalls — Verus→Lean corner cases.
  • vero-lean-pitfalls — universal Lean traps.

© 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

Files

Just SKILL.md in .claude/skills/vero-source-verus of sunblaze-ucb/vero.

Open the folder on GitHubat commit 0a7325d

Compare with similar skills

Vero Source Verus 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.

Vero Source Verus compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Vero Source Verus this skillsunblaze-ucb/vero107—~1.8kAutomated safety check: NotesApache-2.0
Update TranslationsRaicuparta/rai-pal734—~839Automated safety check: PassGPL-3.0
Zig Cinteropmohitmishra786/low-level-dev-skills253—~1.5kAutomated safety check: PassMIT
Code TranslationArabelaTso/Skills-4-SE253—~3.1kAutomated safety check: PassApache-2.0
Add UI Stringopenfootmanager/openfootmanager1.1k—~2.6kAutomated safety check: PassGPL-3.0
Translate It Doc En Zhmxsm/rocketmq-rust1.5k—~1.2kAutomated safety check: PassApache-2.0

Similar skills

  • Update Translations

    Raicuparta/rai-pal

    A skill your agent uses when asked to update translations, localize strings, add new languages, fix missing translation keys, or sync language files in this project.

    734 GitHub stars~839 tokensUpdated 3 days ago
    Writing & ContentAuto-check passed
  • Zig Cinterop

    mohitmishra786/low-level-dev-skills

    Zig C interoperability skill. An agent skill from mohitmishra786/low-level-dev-skills.

    253 GitHub stars~1.5k tokensUpdated 3 mo ago
    Writing & ContentAuto-check passed
  • Code Translation

    ArabelaTso/Skills-4-SE

    Convert code between programming languages while preserving functionality and semantics.

    253 GitHub stars~3.1k tokensUpdated 1 mo ago
    Writing & ContentAuto-check passed
  • Add UI String

    openfootmanager/openfootmanager

    Add or change any text a player can see, in every locale the game ships in.

    1.1k GitHub stars~2.6k tokensUpdated 2 days ago
    Testing & QAAuto-check passed
  • Translate It Doc En Zh

    mxsm/rocketmq-rust

    Translate English IT and software engineering documents into professional, accurate Chinese.

    1.5k GitHub stars~1.2k tokensUpdated today
    DevelopmentAuto-check passed
  • 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.

    26k GitHub stars~1.1k tokensUpdated yesterday
    Writing & ContentAuto-check passed

More from sunblaze-ucb/vero

All 16 skills in this repo
  • Vero Discover

    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.

    107 GitHub stars~3.9k tokensUpdated 1 mo ago
    Auto-check: notes
  • Vero Translate

    sunblaze-ucb/vero

    A skill your agent uses when translating selected verified items from Dafny/Verus/Coq into a compilable Lean 4 benchmark.

    107 GitHub stars~4.9k tokensUpdated 1 mo ago
    Auto-check: notes
  • Vero Coq Pitfalls

    sunblaze-ucb/vero

    Load BEFORE translating any Coq item to Lean 4 to avoid known Coq→Lean pitfalls.

    107 GitHub stars~1.5k tokensUpdated 1 mo ago
    Auto-check: notes
  • Vero Dafny Pitfalls

    sunblaze-ucb/vero

    Load BEFORE translating any Dafny item to Lean 4 to avoid known Dafny→Lean pitfalls.

    107 GitHub stars~1.2k tokensUpdated 1 mo ago
    Auto-check: notes
  • Vero Lean Pitfalls

    sunblaze-ucb/vero

    Load BEFORE writing any Lean 4 translation to avoid common Lean pitfalls (universes, coercions, type-class resolution, notation).

    107 GitHub stars~1.4k tokensUpdated 1 mo ago
    Auto-check: notes
  • Vero Plan

    sunblaze-ucb/vero

    Use after vero-select to write a detailed translation plan as .vero/plan.json — the authoritative contract the TRANSLATE stage executes.

    107 GitHub stars~3.6k tokensUpdated 1 mo ago
    Auto-check: notes

Works with

Questions about Vero Source Verus

What does Vero Source Verus do?

Load BEFORE translating Verus source (Rust with verus!. An agent skill from sunblaze-ucb/vero. Vero Source Verus is an agent skill from sunblaze-ucb/vero. Load BEFORE translating Verus source (Rust with verus!

When should I use Vero Source Verus?

Vero Source Verus fits situations like: tasks that involve Translation.

How do I install Vero Source Verus in Claude Code?

Run `npx skills add sunblaze-ucb/vero --skill vero-source-verus -a claude-code`. Or copy the skill folder (.claude/skills/vero-source-verus in sunblaze-ucb/vero) into .claude/skills/vero-source-verus in your project. Claude Code loads it when a task matches its description.

How do I install Vero Source Verus in Codex?

Run `npx skills add sunblaze-ucb/vero --skill vero-source-verus -a codex`. Or copy the skill folder (.claude/skills/vero-source-verus in sunblaze-ucb/vero) into .agents/skills/vero-source-verus in your project. Codex loads it when a task matches its description.

Can I use Vero Source Verus 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 sunblaze-ucb/vero --skill vero-source-verus -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-verus, .gemini/skills/vero-source-verus, .github/skills/vero-source-verus and .opencode/skills/vero-source-verus in your project.

What does Vero Source Verus need to run?

SKILL.md names no scripts, command-line tools or credentials: Vero Source Verus is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Write, Edit, Bash, Grep, Glob.

Does Vero Source Verus 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 Vero Source Verus safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Vero Source Verus use?

Vero Source Verus 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.

How many tokens does Vero Source Verus use?

About 1.8k tokens (SKILL.md is roughly 7.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 Vero Source Verus?

Skills that share tags, products or a category with Vero Source Verus: Update Translations (Raicuparta/rai-pal, 734 stars), Zig Cinterop (mohitmishra786/low-level-dev-skills, 253 stars), Code Translation (ArabelaTso/Skills-4-SE, 253 stars) and Add UI String (openfootmanager/openfootmanager, 1.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Vero Source Verus?

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.