Markdown Article Formatter
JimLiu/baoyu-skills
Reformats plain text or Markdown articles with frontmatter, a title, a summary, headings, bold, lists and code blocks, and saves a separate formatted copy.
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.
$ npx skills add sunblaze-ucb/vero --skill vero-discover -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install sunblaze-ucb/vero vero-discover --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-discover .claude/skills/vero-discover && 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-discover" agent skill from https://github.com/sunblaze-ucb/vero/tree/main/.claude/skills/vero-discover into .claude/skills/vero-discover/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vero-discover", 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-discoverType 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-discover -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install sunblaze-ucb/vero vero-discover --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-discover .agents/skills/vero-discover && 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-discover" agent skill from https://github.com/sunblaze-ucb/vero/tree/main/.claude/skills/vero-discover into .agents/skills/vero-discover/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vero-discover", 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-discover -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install sunblaze-ucb/vero vero-discover --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-discover .cursor/skills/vero-discover && 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-discover" agent skill from https://github.com/sunblaze-ucb/vero/tree/main/.claude/skills/vero-discover into .cursor/skills/vero-discover/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vero-discover", 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-discover--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-discover -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install sunblaze-ucb/vero vero-discover --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-discover .gemini/skills/vero-discover && 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-discover" agent skill from https://github.com/sunblaze-ucb/vero/tree/main/.claude/skills/vero-discover into .gemini/skills/vero-discover/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vero-discover", 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-discoverInstalls 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-discover -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-discover .github/skills/vero-discover && 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-discover" agent skill from https://github.com/sunblaze-ucb/vero/tree/main/.claude/skills/vero-discover into .github/skills/vero-discover/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vero-discover", 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-discover -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-discover --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-discover .opencode/skills/vero-discover && 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-discover" agent skill from https://github.com/sunblaze-ucb/vero/tree/main/.claude/skills/vero-discover into .opencode/skills/vero-discover/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vero-discover", 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-discoverA 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.
Vero Discover is an agent skill from sunblaze-ucb/vero. Use when scanning a verified source repo (Dafny, Verus, or Coq) to classify every item and produce per-file discovery markdown for human curation. Produces curation/discovery/.md, curation/api.md, and curation/discoveryreport.json.
Its SKILL.md is about 3.9k 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 Documents & Office, covering Markdown. The licence is Apache-2.0.
4 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 these tools, so the agent can use them without asking each time:
ReadWriteBashGrepGlobAgentFrom allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown and json).
From the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
github.comFrom 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 Discover loads about 3.9k tokens when it runs. Until then it costs about 62 tokens; SKILL.md has 1,279 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 noted patterns worth knowing about, such as sudo or a known installer.
allowed-tools: Read, Write, Bash, Grep, Glob, AgentAutomated 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). 1,279 words, ~3,861 tokens.
.claude/skills/vero-discover/SKILL.md (or your agent's skills folder).Scan a verified source repository, classify every item (type, function, predicate, theorem, test, boundary), and produce per-file discovery markdown for human review plus a machine-readable JSON report.
Detect the source language from file extensions:
| Extension | Language | Notes |
|---|---|---|
.dfy | Dafny | |
.rs | Verus | Confirm by checking for verus! macro blocks |
.v | Coq | |
.vy | Coq (Vernacular) | Less common |
For Rust files, grep for verus! or use vstd:: to confirm Verus.
Plain Rust files without Verus annotations should be classified as
skip (not verified code).
Classify every top-level item into exactly one category:
| Category | Description | Lean mapping |
|---|---|---|
type | Data type, struct, enum, record | inductive or structure |
spec-fn | Ghost/specification function | def (body given) |
exec-fn | Executable function (API) | def with translated reference body inside a code marker |
predicate | Boolean/propositional predicate | def ... : Bool or def ... : Prop |
theorem | Lemma, theorem, proof function | def spec_* (impl : RepoImpl) : Prop |
axiom | Axiom, assumed property, external_body property | axiom |
test | Test function, assertion block | #guard block |
skip | Non-verified boilerplate, build config, imports | (not translated) |
Dafny:
datatype / class / newtype / type → typefunction (ghost) → spec-fnfunction method → exec-fnmethod → exec-fnpredicate → predicatelemma → theorem{:axiom} annotation → axiommethod Main() with assertions → testVerus:
struct / enum (including rspec! wrappers) → typespec fn / open spec fn / closed spec fn → spec-fnfn with ensures → exec-fnproof fn → theorem#[verifier::external_body] → axiom (mark as boundary)#[test] / assert! blocks → testCoq:
Inductive / Record / Structure / Class → typeDefinition / Fixpoint / Function → spec-fnLemma / Theorem / Fact / Corollary / Remark → theoremAxiom / Parameter / Conjecture → axiomExample / Goal → testInstance → spec-fn (with typeclass annotation)For each item, classify its visibility:
| Visibility | Meaning | Heuristic |
|---|---|---|
public | Exported, part of module API | pub, no underscore prefix, used by other modules |
internal | Used internally, not exported | Not pub, but used by other items in the project |
private | Helper, underscore-prefixed | _ prefix, or only used locally within one function |
Public APIs are higher-value benchmark tasks because they define the module's contract.
For each theorem/lemma, classify its spec quality:
| Kind | Description | Example |
|---|---|---|
functional | Describes functional behavior (input→output relationship) | push_pop_roundtrip |
characterizing | Independent mathematical property | sameDN_refl, size_nonneg |
helper | Facilitates loop invariant or SMT proof only | Internal induction step lemma |
tautological | Restates the implementation | f_returns_what_it_returns |
Functional and characterizing specs are high-value benchmark tasks. Helper and tautological specs are lower-value (may still be included).
For each item, record its dependencies:
reveal, Verus proof fn calls)Dependencies determine translation order: items with no dependencies are Layer 0; items depending only on Layer 0 are Layer 1; etc.
Every item is classified into one of four categories. The category determines how the item lands in the Lean benchmark:
| Category | What it becomes | Role |
|---|---|---|
| API | sig abbrev + reference implementation in !benchmark code marker + Bundle field + wired into canonical | Implementation obligation — pre-agent generation hides the curated body with sorry before the LLM writes its solution |
| API helper | (by default) nothing — the LLM invents it locally inside code_aux. Curator may opt-in: fully-defined def in Impl/ with no marker, not in Bundle | A tool API implementations share; curator-given only when the curator wants to hand it to the LLM |
| Spec | def spec_<name> (impl : RepoImpl) : Prop in Spec/<Module>.lean | Proof obligation — the LLM must prove (or refute) this downstream |
| Spec helper | Fully-defined function / predicate in Impl/ (or framework file), no marker, not in Bundle | Vocabulary referenced by bare name inside spec bodies; must be curated or the Spec file won't typecheck |
Plus the supporting roles that aren't in the four-way split: type (always curator-given, no marker), test (becomes #guard in Test.lean), skip (not translated).
The source language doesn't tell you. Dafny function method, Verus spec fn / fn, Coq Definition can each land in any of the four categories — the syntactic keyword is a weak hint, not the answer. Use these heuristics instead, in priority order:
impl.<…>) in any spec body? Yes → spec helper, it must be curator-given.ensures clauses on the function? Yes → author expected the body to be pinned by a spec → API. No ensures, only called from other proofs → spec helper.When two heuristics conflict, note it in the per-item discovery markdown as a suggestion that the curator review.
Predicates, types, and facts stated as theorems always land as spec helpers (predicates) / types / specs respectively. A predicate can't be an API obligation unless it is intentionally selected as executable code.
Produce one file per source file at curation/discovery/{source_path}.md.
Replace path separators with -- (e.g., src/policy/chrome.rs → src--policy--chrome.rs.md).
Every item line carries the suggested category (the curator overrides during review). Format: - [ ] category=<api|api_helper|spec|spec_helper|type|test|skip> <item>.
# discovery: {source_path}
Source: `{source_path}` ({N} lines)
Language: {Dafny | Verus | Coq}
Module: {module_name}
## Types
- [ ] category=type `TypeName` — {kind}, {N constructors/fields} — maps to: `{inductive|structure|abbrev}`
- Visibility: {public|internal|private}
- Dependencies: {list or "none"}
- Notes: {considerations, deriving suggestions}
## Functions
- [ ] category={api|api_helper|spec_helper} `funcName(args)` → {ReturnType} — maps to: `def`
- Visibility: {public|internal|private}
- Dependencies: [{list}]
- Reason: {one line — which heuristics drove the category suggestion}
- Notes: {annotations, ensures clauses, requires clauses}
## Predicates
- [ ] category=spec_helper `predName(args)` — maps to: `def ... : {Bool|Prop}`
- Visibility: {public|internal|private}
- Dependencies: [{list}]
- Notes: {what it checks}
## Theorems / Lemmas
- [ ] category={spec|spec_helper|skip} `theoremName` — maps to: `def spec_<…> (impl : RepoImpl) : Prop`
- Visibility: {public|internal|private}
- Dependencies: [{list}]
- Hypothesis: {preconditions / requires}
- Conclusion: {postcondition / ensures}
- Reason: {one line — why this category}
## Tests
- [ ] category=test `testName` — maps to: `#guard` block
- Values: {input/output pairs or assertion checks}
## External Boundaries
- [ ] category=api_helper `boundaryName` — maps to: `opaque`
- Properties proved in source: {list → become axioms in Lean}
## Notes
[Human adds review notes here]vero-select review.skip items are omitted entirely (don't clutter the review).TODO, FIXME, assume, or admit in the source.curation/discovery_report.jsonAfter producing the markdown files, also write a JSON report at
curation/discovery_report.json with this structure. The key field is
suggested_category — one of the four benchmark categories plus the
supporting roles (type, test, skip).
{
"source_language": "dafny",
"source_dir": "/path/to/source",
"commit_hash": "abc123",
"repo_url": "https://github.com/...",
"items": [
{
"name": "Stack",
"qualified_name": "Stack",
"suggested_category": "type",
"visibility": "public",
"source_file": "Stack.dfy",
"source_line": 3,
"signature_summary": "datatype Stack<T> = Empty | Cons(top: T, rest: Stack<T>)",
"dependencies": [],
"reason": "datatype declaration; always curator-given",
"notes": "Generic binary stack, 2 constructors"
},
{
"name": "push",
"qualified_name": "push",
"suggested_category": "api",
"visibility": "public",
"source_file": "Stack.dfy",
"source_line": 8,
"signature_summary": "function method push<T>(s: Stack<T>, v: T) : Stack<T>",
"dependencies": ["Stack"],
"reason": "user-facing library entry; has ensures clauses in source",
"notes": ""
},
{
"name": "toSeq",
"qualified_name": "toSeq",
"suggested_category": "spec_helper",
"visibility": "internal",
"source_file": "Stack.dfy",
"source_line": 22,
"signature_summary": "ghost function toSeq<T>(s: Stack<T>) : seq<T>",
"dependencies": ["Stack"],
"reason": "ghost function used only in ensures clauses of other fns; referenced by bare name in specs",
"notes": ""
},
{
"name": "push_pop_roundtrip",
"qualified_name": "push_pop_roundtrip",
"suggested_category": "spec",
"visibility": "public",
"source_file": "StackSpec.dfy",
"source_line": 5,
"signature_summary": "lemma push_pop_roundtrip<T>(s: Stack<T>, v: T) ensures pop(push(s, v)) == s",
"dependencies": ["Stack", "push", "pop"],
"reason": "characterizing lemma about push/pop; becomes def spec_* proof obligation",
"notes": "Round-trip property"
}
],
"file_summaries": {
"Stack.dfy": {"lines": 50, "types": 1, "functions": 5, "theorems": 0},
"StackSpec.dfy": {"lines": 40, "types": 0, "functions": 0, "theorems": 4}
}
}The suggested_category is the agent's best call per the heuristic rubric; the curator overrides it in vero-select review. The reason field (one sentence) is mandatory and must cite at least one heuristic — it's how the curator audits the suggestion.
This JSON is consumed by vero-select and vero-plan; both expect the four-category vocabulary.
curation/api.mdAfter producing per-file discovery markdowns, assemble curation/api.md:
# API Catalog: {project_name}
Source: {repo_url} ({commit_hash})
Language: {language}
Total lines: {N}
## Architecture
{ASCII dependency graph of modules}
## Summary
| File | Types | Spec Fns | Exec Fns | Predicates | Theorems | Axioms | Tests |
|------|------:|--------:|---------:|----------:|---------:|-------:|------:|
| ... | ... | ... | ... | ... | ... | ... | ... |
| **Total** | **N** | **N** | **N** | **N** | **N** | **N** | **N** |
## Per-File Catalogs
[Links to each curation/discovery/{path}.md]For repos with more than ~20 source files, use parallel sub-agents:
curation/api.mdEach sub-agent receives:
Do not read all source files up front and then write all markdowns at the end. A "read 19 files, think, then Write 19 times" flow is what causes multi-minute thinking stalls and loses everything on interrupt. Instead, close each file's loop before opening the next one:
1. Detect language (scan extensions + grep for markers)
2. List all source files (exclude tests/, build/, vendor/)
3. FOR EACH source file, one at a time (NOT in parallel):
a. Read the source file
b. Classify its top-level items (category, visibility, spec_kind,
body_disposition)
c. Extract dependencies
d. Write curation/discovery/<path>.md IMMEDIATELY — do not batch
writes across files
e. If discovery_report.json exists, Edit to append this file's
items; otherwise Write it fresh with just these items. Either
way the JSON stays valid after each file so the run is
restartable.
4. After the per-file loop, assemble curation/api.md with the summary
table (this is a small synthesis pass, one Write).
5. Report: total items found, items per category.Idempotency. If curation/discovery/<path>.md already exists and
the source file's mtime is older than the markdown, skip the Read +
Write pair unless --force. Do NOT blindly re-read all 19
already-analyzed files because of the Write guard — that's wasted
turns.
Check-in rule. Before each file's Write, announce in one
sentence: "Now processing src/foo.dfy — 3 types, 5 fns." Keeps
progress observable.
Batch size. If you must batch (for Agent sub-agents), group at most 5 files per sub-agent. Never dispatch a single 19-file batch.
curation/
├── discovery/
│ ├── src--module1.dfy.md
│ ├── src--module2.dfy.md
│ └── ...
├── api.md
└── discovery_report.json© 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-discover of sunblaze-ucb/vero.
Open the folder on GitHubat commit 0a7325d
Vero Discover 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 Discover this skillsunblaze-ucb/vero | 107 | — | ~3.9k | Automated safety check: Notes | Apache-2.0 | |
| Markdown Article FormatterJimLiu/baoyu-skills | 27k | 6 repos | ~3.5k | Automated safety check: Pass | MIT | |
| MarkitdownImCa0/just-laws | 781 | 14 repos | ~3.2k | Automated safety check: Notes | MIT | |
| Obsidian MarkdownAtmosphere/atmosphere | 3.8k | 20 repos | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Crosspostingwasp-lang/wasp | 19k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Gzh Designisjiamu/gzh-design-skill | 4k | — | ~2.2k | Automated safety check: Pass | AGPL-3.0 |
JimLiu/baoyu-skills
Reformats plain text or Markdown articles with frontmatter, a title, a summary, headings, bold, lists and code blocks, and saves a separate formatted copy.
ImCa0/just-laws
Convert files and office documents to Markdown. An agent skill from ImCa0/just-laws.
Atmosphere/atmosphere
Create and edit Obsidian Flavored Markdown with wikilinks, embeds, callouts, properties, and other Obsidian-specific syntax.
wasp-lang/wasp
Crosspost Wasp blog articles (MDX) to DEV.to and Medium. An agent skill from wasp-lang/wasp.
isjiamu/gzh-design-skill
微信公众号文章排版引擎,将 Markdown 转换为可直接粘贴到公众号编辑器的 HTML。主题风格从 references/theme-index.md 注册的自定义主题库中选取,自动章节编号、关键词下划线标记、引言卡片、目录导航、代码块、图片/GIF、作者签名。支持 Markdown / Word(.docx) / PDF / 纯文本输入(非 Markdown…
supabase/supabase
Review Supabase docs changes locally in your supabase/supabase checkout — either an open PR (triage, classify, verify) or your own branch before opening a PR (local self-review).
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.
sunblaze-ucb/vero
Load BEFORE translating any Python item to Lean 4 to avoid known Python→Lean pitfalls.
Categories
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. Vero Discover is an agent skill from sunblaze-ucb/vero. Use when scanning a verified source repo (Dafny, Verus, or Coq) to classify every item and produce per-file discovery markdown for human curation.
Vero Discover fits situations like: scanning a verified source repo (Dafny; coq) to classify every item and produce per-file discovery markdown for human curation.
Run `npx skills add sunblaze-ucb/vero --skill vero-discover -a claude-code`. Or copy the skill folder (.claude/skills/vero-discover in sunblaze-ucb/vero) into .claude/skills/vero-discover in your project. Claude Code loads it when a task matches its description.
Run `npx skills add sunblaze-ucb/vero --skill vero-discover -a codex`. Or copy the skill folder (.claude/skills/vero-discover in sunblaze-ucb/vero) into .agents/skills/vero-discover 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-discover -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-discover, .gemini/skills/vero-discover, .github/skills/vero-discover and .opencode/skills/vero-discover in your project.
SKILL.md names no scripts, command-line tools or credentials: Vero Discover is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Write, Bash, Grep, Glob, Agent.
SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
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.
Vero Discover 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 3.9k tokens (SKILL.md is roughly 15k 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 Discover: Markdown Article Formatter (JimLiu/baoyu-skills, 27k stars), Markitdown (ImCa0/just-laws, 781 stars), Obsidian Markdown (Atmosphere/atmosphere, 3.8k stars) and Crossposting (wasp-lang/wasp, 19k 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.