peg-poolslisted
Install: claude install-skill use-peg/peg-pools
# peg-pools
One prompt, two wallet signatures: the developer ends up owning a zero-fee `PegAsset` wrapper and a
`PegPool` (frozen peg-v8 `PegRevenuePool`) for one of ten tokenized stocks on Robinhood Chain (4663),
registered with Peg and visible on usepeg.trade under Community. Seeding liquidity is a separate
follow-up prompt (five more signatures). Every transaction is prepared by a script, verified against
pinned bytecode hashes, shown to the developer, and signed in their own browser wallet or their own
shell. The skill has no signer and wants none.
## How to run the scripts
Seven scripts live in `scripts/`. Invoke each one exactly in this form (the permission rule is
anchored on the quoted path prefix, so keep the double quotes and put the script name after the
closing quote):
```
node "${CLAUDE_PLUGIN_ROOT}/skills/peg-pools/scripts/"check-env.mjs
```
`${CLAUDE_PLUGIN_ROOT}` is the installed plugin directory (the one holding `.claude-plugin/` and
`skills/`). Claude Code substitutes it in this document and in the permission rule before you read
them, so the command above already carries the absolute path; if the literal variable ever appears,
put the plugin directory in its place yourself. Run scripts from the developer's project
root: they write only `.peg/<stock>/` (plans, receipts, records, `state.json`) and, at the end,
`peg-pool.json` plus a `.gitignore` line. Do not create or edit those files yourself; the scripts
re-verify every plan file at sign time and refus