Skillhub Onchain

Skill Hub on-chain publish

When to use

• Publishing a new agent skill to the public hub
• Verifying a skill's bundle hash / Merkle leaf
• Linking Cheshire Terminal UI to live catalog data
• Reading the redacted public submission ledger (safe for GitHub)

Origins

Pipeline

upload SKILL.md → scanner (CRITICAL blocks) → Solana fee + memo → Irys/Arweave package → Solana memo anchor

1. Open https://skills.x402.wtf/publish (or run npm run relay:upload in Solizardking/skills)
2. Drop SKILL.md (+ optional helpers)
3. Scan — fix CRITICAL findings
4. Connect Phantom / Solflare and pay the publish fee
5. Relay confirms the payment signature on RPC, then packages + anchors

Public APIs (no secrets)

# Full catalog
curl -sS https://skills.x402.wtf/api/skills.json | head

# Redacted community submissions (GitHub-safe ledger)
curl -sS https://skills.x402.wtf/api/submissions.json

# On-chain summary + catalog anchor receipt pointers
curl -sS https://skills.x402.wtf/api/onchain.json

# Per-skill source
curl -sS https://skills.x402.wtf/api/skills/solana-common-errors/SKILL.md | head

Cheshire wiring

Cheshire proxies the live hub:

curl -sS https://cheshireterminal.ai/api/skills | jq '.sources, .count'
# SKILLS_LIVE_BASE_URL defaults to https://skills.x402.wtf

Env (Cheshire deploy):

Security

• Private job stores live under onchain/submissions/ (gitignored)
• Public ledger (onchain/public-ledger.json → /api/submissions.json) is redacted:
  • no private keys / keypairs / mnemonics
  • no blocked skill file bodies
  • only hashes, risk, wallets, payment + explorer links
• Never commit SOLANA_KEYPAIR, .env, or merchant private keys

Install this skill

npx skills add Solizardking/cheshire-terminal --path skills-store/skillhub-onchain

Related skills

• solana-common-errors — Anchor/GLIBC/build-sbf troubleshooting
• cheshire-api — Cheshire REST + MCP discovery