Convex-Dev/convex / .claude/skills/deploy
deploy
VerifiedDeploy an actor (smart contract) to the Convex network. Use when the user wants to create a new on-chain actor with exported functions.
Deploy a Convex Actor
Actors are autonomous on-chain programs with their own address, state, and callable functions.
See the convex-lisp skill for CVM conventions and error codes. Deploying is a
transaction, so it needs a key the user has supplied — see transact.
Actor Structure
A typical actor deployment:
(deploy
'(do
;; Internal state (private to the actor)
(def counter 0)
;; Callable functions: mark each with ^:callable so it can be
;; invoked from outside the actor via (call ...)
(defn ^:callable increment []
(set! counter (+ counter 1))
counter)
(defn ^:callable get-count []
counter)))
Key Rules
deployreturns the new actor's address (e.g.#12345)- Only functions tagged with
^:callablemetadata can be called from outside (there is noexportform). The equivalent map form is^{:callable true} - Use
set!to update an existingdeffrom inside a function; plaindefs declared in the actor body are private state - Actors have their own
*address*and*balance* - Use
(set-controller #ADDR)inside the actor to set who can upgrade it deployalso accepts a vector of code forms, which is how library builders are composed into one actor:(deploy [(@convex.fungible/build-token {…}) (@convex.fungible/add-mint {…})])
After Deployment
- Note the returned address for the user
- Optionally register a CNS name:
(*registry*/create 'my.actor.name #NEW-ADDR)— needs control of the parent namespace; see thecnsskill - Test by calling a
^:callablefunction:(call #NEW-ADDR (get-count))
Workflow
- Help the user design the actor based on
$ARGUMENTS - Write the Convex Lisp source
- Deploy using
transactwith the(deploy ...)expression - Verify the deployment with a test query
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 117k | Updated | Claude CodeCodex | Verified | Install |