convex-check-updates
Skill4 starsChanged 54 days agoMITView on GitHub
Check the current app's pinned Convex components against recommended versions and upgrade them behind a build gate.
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 3 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Run curl -fsSL https://graceful-tiger-715.convex.site/check-updates.mjs -o /tmp/cu.mjs && node /tmp/cu.mjs from the project root.
- Very specific: line 15
If COMPONENTS_UP_TO_DATE: tell the user.
- Very specific: line 16
If COMPONENTS_STALE=<n>: list each stale entry (component name, installed → current, summary, breaking flag) and ask the user before …
- Distinctive: line 18
If any gate command fails: revert (git checkout -- .
- Distinctive: line 24
Never upgrade without an explicit user yes — not even a minor version.
- Distinctive: line 27
Do not auto-republish a live *.convex.app site after upgrading without user confirmation.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
<!-- GENERATED from convex-agents content/capabilities/check-updates.json — do not edit by hand. -->check-updates
Detect stale Convex components in the current app against the anteater registry and, with explicit user consent, upgrade them one at a time behind a build gate (typecheck + next build). Each upgrade is gated and smoke-tested before the next.
Workflow
- Run
curl -fsSL https://graceful-tiger-715.convex.site/check-updates.mjs -o /tmp/cu.mjs && node /tmp/cu.mjsfrom the project root. - If COMPONENTS_UP_TO_DATE: tell the user; done.
- If COMPONENTS_STALE=
<n>: list each stale entry (component name, installed → current, summary, breaking flag) and ask the user before touching anything. - On yes: install the new ref, apply each migration.steps change (delegate convex/ edits to convex-expert), run every migration.gate command.
- If any gate command fails: revert (git checkout -- . or reinstall old ref) and report; never leave the app half-migrated.
- Give the user the smoke check (migration.smoke) to run after each successful upgrade.
- Repeat for each stale component, one at a time.
Rules
- Never upgrade without an explicit user yes — not even a minor version.
- Gate each component individually before moving to the next.
- breaking:true upgrades require a snapshot (commit or branch) before applying.
- Do not auto-republish a live *.convex.app site after upgrading without user confirmation.
Trending
Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data
Other versions3 projects use a version of this.
Word for word · 3
- openclaw/clawhub★ 9.5k100% same
- moltbot/molthub★ 9.5k100% same
- clawdbot/clawdhub★ 9.5k100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository59 other files it gives its agents.
- AGENTS.mdAGENTS.md
- codebase-designSkill
- code-reviewSkill
- convex-acquire-domainSkill
- convex-addSkill
- convex-advisorSkill
- convex-agentSkill
- convex-authSkill
- convex-authzSkill
- convex-backupSkill
- convex-billingSkill
- convex-costSkill
- convex-create-componentSkill
- convex-cronsSkill
- convex-deploy-guardSkill
- convex-designSkill
- convex-docsSkill
- convex-domainsSkill
- convex-envSkill
- convex-expertSkill
- convex-explain-appSkill
- convex-improve-convex-pluginSkill
- convex-insightsSkill
- convex-launch-readinessSkill
- convex-migrate-rehearseSkill
- convex-migrateSkill
- convex-monitorSkill
- convex-optimizeSkill
- convex-quickstartSkill
- convex-reviewerSkill
- convex-seedSkill
- convex-self-healSkill
- convex-sentinelSkill
- convex-shipSkill
- convexSkill
- convex-suggestSkill
- convex-testSkill
- convex-verifySkill
- diagnosing-bugsSkill
- domain-modelingSkill
- grillingSkill
- grill-meSkill
- grill-with-docsSkill
- handoffSkill
- implementSkill
- improve-codebase-architectureSkill
- prototypeSkill
- releaseSkill
- researchSkill
- resolving-merge-conflictsSkill
- setup-afk-codingSkill
- setup-matt-pocock-skillsSkill
- tddSkill
- teachSkill
- to-specSkill
- to-ticketsSkill
- triageSkill
- wayfinderSkill
- writing-for-agentsSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.