Convex Verify
Prove a Convex feature works — seed, drive as multiple identities, assert positive AND negative cases
- What
- Prove a Convex feature works — seed, drive as multiple identities, assert positive AND negative cases
- Cost
- Free
- Needs
- a Convex project (see the repo README for setup); convex-test + vitest dev deps with vitest.config.ts edge-runtime config
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — the most rigorous guide of the 12: "a green typecheck proves the code parses, not that a non-owner is refused". The loop the whole field is missing — seed → drive → assert, run in-process with convex-test so no deployment is needed: seed the caller's rows AND a second user's rows, drive the feature as three identities (owner, other authenticated user, unauthenticated) with `t.withIdentity`, assert the positive case AND the NEGATIVE ones (the wrong caller is actually refused; a list query returns only the caller's rows). A failing negative assertion is a real authz hole found before ship — emitted as a bus finding, and the fix goes in the function (convex-authz), never by weakening the test. Distinct from `get-convex-convex-reviewer` (lot 32): reviewer = STATIC audit of written code in 3 passes; verify = EXECUTION proof. Complementary with convex-test (this lot): test = WRITE the tests; verify = PROVE the feature. By @get-convex, listed here with credit to its creator. Honest caveats: requires a Convex project and the convex-test + vitest dev deps with the edge-runtime config (free tier exists); never weakens an assertion to make it green. Skill Harbor never reviews the code, review it yourself before use.
Version:
Quick answer
Convex Verify is a free Muse skill, the most rigorous Convex guide: a green typecheck proves the code parses, not that a non-owner is refused. Its seed, drive and assert loop runs in-process with convex-test, with no deployment: seed both users' rows, drive the feature as owner, other user and unauthenticated, and assert positive and negative cases.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 2cfe645Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: a Convex project (see the repo README for setup); convex-test + vitest dev deps with vitest.config.ts edge-runtime config Install "Convex Verify" for me. Give my agent the seed → drive → assert workflow for proving my Convex features work: seed both the caller's and a second user's rows, drive the function as owner / other user / unauthenticated with t.withIdentity, assert positive AND negative behavior (wrong caller refused, data-scope enforced), never weaken an assertion to make it pass, emit bus findings for failures Repository: https://raw.githubusercontent.com/get-convex/agent-skills/2cfe645c87f971242cfc8ef3eb53662cbec26a53/skills/convex-verify/SKILL.md Pinned version: install the code at commit 2cfe645c87f971242cfc8ef3eb53662cbec26a53 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file for the get-convex-agent-skills-convex-verify skill from the repository into a temporary folder 2. Safety check: review the SKILL.md for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md into the agent's skills directory, in a folder named "get-convex-agent-skills-convex-verify". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. add convex-test + vitest dev deps, set the edge-runtime config, name the feature to prove). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. Never ask me to paste secrets in chat — credentials go through the secure vault or environment variables. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 2cfe645 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.