agentleFS
roborun-xyzroborun-xyz/sol-validator-skills/skills/jitosol-steward/SKILL.md

jitosol-steward

Skill3 starsChanged 51 days agoMITView on GitHub

Check current JitoSOL Steward validator ranking, algorithmic delegation fraction, active/transient stake, instant unstake and scoring cycle on Solana mainnet. Use for JitoSOL rank or delegation-set comparisons, not ordinary Jito MEV or BAM rewards.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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
  1. Distinctive:

    Read installed bundle and configuration before running commands.

    line 13
  2. Distinctive:

    Run this read-only check from the bundle root:

    line 15
  3. Very specific:

    Use --vote-account PUBKEY for an explicit vote account or --validator PUBKEY for vote/identity resolution.

    line 21
  4. Very specific:

    Add --pool-summary to compare all positive algorithmic target fractions against 1 / current member count and show the five largest actual …

    line 23

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

JitoSOL Steward

Read installed bundle and configuration before running commands. Resolve paths from this loaded skill, not the session working directory. Install dependencies with bun install --frozen-lockfile from the resolved bundle root when node_modules is absent.

Run this read-only check from the bundle root:

bun src/skills/jitosol-steward/scripts/check.ts --profile my-validator --format markdown

Use --vote-account PUBKEY for an explicit vote account or --validator PUBKEY for vote/identity resolution. --config PATH and --rpc URL follow the shared RPC precedence. Resolve missing profile/RPC setup through onboarding, then resume. SSH and signers are unnecessary.

Add --pool-summary to compare all positive algorithmic target fractions against 1 / current member count and show the five largest actual active-stake balances. Use --format json for complete addresses, exact lamports and comparable records.

Report UTC and local check times, finalized snapshot slot, current/state epoch, Overall Rank and scored count, score, delegation numerator/denominator, active/transient stake, stake-list update epoch, instant-unstake flag and next cycle epoch. Overall Rank is the 1-based position in the on-chain descending score index across all scored validators, including zero scores; tied scores retain on-chain order. It is not the rank among only eligible or delegated validators. Newly added validators and incomplete scoring cycles have an unavailable rank, never rank zero. A validator absent from the list is not_in_pool, not a failed chain query.

Keep algorithmic target fractions separate from actual stake. Nonmembers have numerator zero (some unused denominators may be zero). Directed stake, deposits, and rebalance timing can make actual stake differ from algorithmic targets; this helper does not decode directed stake and cannot attribute excess balances to it. SPL list balances are observations at lastUpdateEpoch, not direct stake-account queries. Rank and next cycle do not guarantee future stake or admission.

The helper checks mainnet genesis and live vote/identity, then verifies the config/state owners and Anchor discriminators, derived state PDA, SPL pool/list owners and links, V2 size, index uniqueness/order and positive fractions. Config/state/list/pool are read together at finalized commitment. Unsupported layouts or failed checks stop the query; do not replace missing data with zero or bypass validation.

Decoder source

Layout and ranking semantics were reviewed against Jito's Steward V2 state, accounts and timing reference. The SPL list uses a 9-byte header and 73-byte entries; the pool validator-list pubkey begins at byte 98 per the SPL StakePool struct. The timing reference's pool offsets disagree with that struct and the validated live account; use the helper's checked links rather than copying those pool offsets.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.