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

inventory

Skill3 starsChanged 49 days agoMITView on GitHub

Discover, verify, and maintain Solana validator host and instance facts, including roles, paths, signer roles, and failover relationships. Use when adding servers or refreshing host layout; chain profiles, RPC configuration, and SFDP identity-pair setup belong to onboarding.

6 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 5 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 5

    Distinctive

    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. Very specific:

    Read installed bundle and configuration before running commands.

    line 13
  2. Distinctive:

    Read the shared inventory only when the task depends on host layout.

    line 21
  3. Distinctive:

    Verify relevant facts through user confirmation or read-only SSH/RPC checks before changing them.

    line 22
  4. Distinctive:

    Ask only for facts that cannot be discovered safely.

    line 23
  5. Distinctive:

    Update current facts and the check timestamp.

    line 24
  6. Distinctive:

    Treat unknown or stale facts as blockers for destructive operations.

    line 25
  7. Very specific:

    When updating Markdown, preserve created and set last_updated in frontmatter.

    line 40

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “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

Validator Inventory

Read installed bundle and configuration before running commands. Resolve paths from this loaded SKILL.md, not the session working directory.

Own host and signer facts for both new and existing instances. Read host and signer inventory for discovery and verification. Use the operator-selected VALIDATOR_OPS_HOST_INVENTORY or ~/.config/validator-ops/hosts.md. Never default to a private fleet bundled in an existing checkout. Reuse an explicitly selected inventory after checking relevance and freshness.

For missing or outdated chain profiles, RPC references, or SFDP identity-pair configuration, use onboarding. Host observations, chain profiles and local signer roles are separate evidence; none establishes the others or grants execution authorization.

Workflow

  1. Read the shared inventory only when the task depends on host layout.
  2. Verify relevant facts through user confirmation or read-only SSH/RPC checks before changing them.
  3. Ask only for facts that cannot be discovered safely.
  4. Update current facts and the check timestamp; remove superseded detail instead of accumulating history.
  5. Treat unknown or stale facts as blockers for destructive operations.

Keep

  • Active aliases and roles.
  • Cluster, client/version, identity, vote account, RPC, config, ledger, accounts, key paths, and service/screen.
  • Failover relationships and safety constraints.
  • A short note for unreachable or retired aliases when it prevents misuse.

Omit

  • Private keys, seeds, passwords, API keys, SSH keys, and tokens.
  • Full command logs, migration narratives, old hardware snapshots, and per-refresh changelogs.
  • Superseded values already recoverable from Git history.

When updating Markdown, preserve created and set last_updated in frontmatter. Report UTC and local check time.

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.