Agent skill · uniswap
permissioned-pools-configurator
Interactively collect and validate the parameters for a Uniswap v4 Permissioned Pool setup - chain, underlying token, allowlist checker, adapter owner, verification deposit, the four wrapper registrations, hook, and pool pricing - and emit the JSON config the deployer skill consumes. Use when the user says "configure a permissioned pool", "permissioned pool config", "adapter parameters", "permissioned pool setup parameters", "PermissionsAdapter configuration", or asks to set up parameters for a permissioned pool before deploying. Covers contract mechanics only - does not constitute legal, financial, investment, tax, or compliance advice, and is not a compliance review.
What it needs
About 12k tokens when loaded.
What this skill does
Permissioned Pools Configurator Interactive bulk-form configurator for a Uniswap v4 Permissioned Pool. Collects every parameter the setup journey needs, validates each one, and displays a single JSON configuration object that the permissioned-pools-deployer skill consumes to run the on-chain sequence. For the contract mechanics behind any of these parameters, see permissioned-pools-issuer. Runtime Compatibility: This skill uses AskUserQuestion to collect parameters in batches. If AskUserQuestion is not available in your runtime, collect the same parameters through natural language conversation instead, in the same batch groupings and with the same validation after each group. Scope and Disclaimer This is a configuration tool, not deployment guidance and not a compliance review. ✅ It collects and validates the inputs a permissioned-pool setup needs and produces a JSON document. It does not call any contract, does not broadcast anything, and holds no signing keys. ✅ Treat this as contract mechanics only. This skill does not constitute legal, financial, investment, or tax advice, and it is not a compliance review of your token, your allowlist, your KYC or AML program, or your configuration. It covers what each parameter means and what breaks if it is wrong. ✅ It never invents a contract address. Addresses you supply are recorded as given; addresses you do not yet have — whether because they still need to be looked up against the deploy guide's table or because the issuer has not decided on them yet — are stored as the literal string "RESOLVE", never guessed or recalled from memory. ✅ Review the emitted configuration yourself, and re-resolve every address it marks for resolution, before handing it to a deployment flow. ✅ Read the repo's usage guidelines. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills uniswap/permissioned-pools-configurator