votex-status
Skill3 starsChanged 50 days agoMITView on GitHub
Fetch current or historical Votex/The Vault vote-buy status, including target epoch, USDC bids, bid share, acquired veV when published, and on-chain IncreaseVoteBuy fallback transactions. Use for Vault/Votex epoch and allocation questions.
In this repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- doublezero-statusSkill
- inventorySkill
- jito-bam-boostSkill
- jitosol-stewardSkill
- marinade-bond-sweepSkill
- onboardingSkill
- sfdp-checkSkill
- upgrade-agave-primarySkill
- upgrade-agaveSkill
- upgrade-mainnetSkill
- upgrade-testnetSkill
- validator-performanceSkill
- validator-revenueSkill
- votex-roi-simSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
Read installed bundle and configuration before running commands.
- Distinctive: line 17
Run from the resolved bundle root:
- Very specific: line 27
Use VotaFi tribeca-stats first.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Votex Status
Read installed bundle and configuration before running commands. Resolve paths from this loaded SKILL.md, not the session working directory.
Apply RPC setup and selection; repair missing URLs through onboarding, then resume the requested task. No RPC credential is bundled.
Run from the resolved bundle root:
bun src/skills/votex-status/scripts/votex_status.ts <epoch|current>Options: --epoch-only, --json, --no-names, and --max-pages N. Unknown, duplicate or incomplete options are usage errors (exit 2).
For current, read the Vault gaugemeister; the active vote-buy target is currentRewardsEpoch + 1. Do not infer it from wall time.
Use VotaFi tribeca-stats first. On HTTP 404, scan the epoch window for matching on-chain IncreaseVoteBuy transactions. The fallback reports bids/share but cannot calculate acquired veV. No stats and no transactions is a valid zero-bid state.
Totals are USDC only. A Vault vote buy in another mint, or a published vote buy without a mint, fails the report in both the published-stats and on-chain paths; it is never summed as USDC or silently skipped.
Report source type, UTC/local epoch window, total bids, sorted rows, and whether veV is unavailable.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.