Individual skill
submit-hook
Submit a deployed Uniswap v4 hook to the public univ4-hooks registry - format the listing, open a PR (issue fallback) so it lists on the hook marketplace.
skills/submit-hook/SKILL.md
Source commit 25575a6be3bfab41925964de55654056a2fe0c39
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 789
- Repository last updated
- Nov 7, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-agents Repository topic
- claude-code Repository topic
- agent-framework Repository topic
- agents Repository topic
- ai Repository topic
- anthropic Repository topic
- claude Repository topic
- harness Repository topic
- llm Repository topic
- automation Repository topic
- crypto Declared skill tag
- dev Declared skill tag
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 5,368 bytesSKILL.mdcore · 5,368 bytesSKILL.mdcore · 5,368 bytessubmit-univ4.pyruns · 7,758 bytes
Read excerpt
> **${var}** - a hook address (`0x...`) to submit. Empty means the most recent **live mainnet** deploy in `memory/state/hook-deploys.json`.
Today is ${today}. This skill takes a hook this instance already deployed and lists it on the public registry `aeonfun/univ4-hooks` (the source behind the aeon hook marketplace). It does the formatting the registry expects, then opens a PR. The flags and callbacks are decoded from the address by the registry, so this skill only supplies the address, the chain, and the human-readable listing.
The mechanics (clone, write the entry, regenerate the registry, open the PR, fall back to an issue when there is no push access) live in `skills/submit-hook/submit-univ4.py`, so all GitHub egress stays inside that helper.
## What lists, and what does not
- **Only live mainnet deploys.** A dry-run or a testnet deploy is never submitted (the registry lists real, verifiable hooks). Skip with `SUBMIT_HOOK_SKIP`.
- **Only registry-supported chains.** The registry's `chains.json` covers `ethereum base robinhood monad bnb arbitrum unichain`. A deploy on any other chain is skipped (`SUBMIT_HOOK_UNSUPPORTED_CHAIN`); note it and stop.
- **Idempotent.** The helper skips if the address (any chain) or the slug is already listed, so re-running is safe.
## Steps
