How do I install the Convex Suggest skill?

Run npx skillmds@latest add openclaw/convex-suggest in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Convex Suggest safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Convex Suggest?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Convex Suggest free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Convex Suggest?

OpenClaw (@openclaw) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Convex Suggest by openclaw — Agent Skill

Name: Convex Suggest
Rating: 4.666666666666667 (3 reviews)
Author: OpenClaw

Convex Suggest

Suggest the matching Convex component when the user hand-rolls a pattern it already solves (crons, sharded-counter, rate-limiter, storage, search, presence, workflow, RAG, prosemirror-sync). Passive — suggest after the task, never interrupt. Never install without consent.

OpenClaw Updated Sep 9, 2026 9.1k repo stars

File contents

Proactively suggest the right Convex component

When you see code or intent that duplicates what a Convex component already does, surface a targeted suggestion: ONE component, WHY (anchored in the user's own code or ask), and a concrete install hint. Never install without explicit consent. Never suggest more than one component at a time unless the user asks.

Workflow

Observe the codeSnippets and userAsk passively — never block the current task to suggest.
Match against the detector rules (see generators/suggest-detector.mjs): email/SMTP → resend; push notifications → expo-push; setInterval/cron → @convex-dev/crons; shared counter increments → @convex-dev/sharded-counter; .collect().length scans → @convex-dev/aggregate; multi-step/long-running actions → @convex-dev/workflow; bounded concurrency → @convex-dev/workpool; rate-limit counters in DB → @convex-dev/rate-limiter; fs.write/S3 uploads → Convex Storage; Elasticsearch/Algolia → built-in full-text search; presence/typing → @convex-dev/presence; Pinecone/external vector DB → @convex-dev/rag; collaborative editing → @convex-dev/prosemirror-sync.
After finishing the current task, offer ONE suggestion: name the component, quote the specific code or phrase that triggered it, explain why the component fits better.
If the user says yes: run /add <component> or follow the installHint from the detector.
If the user says no or ignores it: drop it. Do not repeat the same suggestion.

Rules

Passive — never interrupt the current task; surface the suggestion AFTER completing what the user asked.
One at a time — pick the highest-priority match; do not dump a list of five components.
Cite WHY from the user's own code or ask — 'I noticed you wrote post.likes + 1 in a mutation that many users call concurrently; that causes OCC conflicts at scale.'
Never install without explicit consent — suggest, explain, wait for a yes.
Do not suggest a component the user has already installed.
Do not fire on generic coding questions unrelated to Convex (sorting arrays, writing CSS, etc.).

---name: convex-suggestdescription: Suggest the matching Convex component when the user hand-rolls a pattern it already solves (crons, sharded-counter, rate-limiter, storage, search, presence, workflow, RAG, prosemirror-sync). Passive — suggest after the task, never interrupt. Never install without consent.---  # Proactively suggest the right Convex component When you see code or intent that duplicates what a Convex component already does, surface a targeted suggestion: ONE component, WHY (anchored in the user's own code or ask), and a concrete install hint. Never install without explicit consent. Never suggest more than one component at a time unless the user asks. ## Workflow 1. Observe the codeSnippets and userAsk passively — never block the current task to suggest. 2. Match against the detector rules (see generators/suggest-detector.mjs): email/SMTP → resend; push notifications → expo-push; setInterval/cron → @convex-dev/crons; shared counter increments → @convex-dev/sharded-counter; .collect().length scans → @convex-dev/aggregate; multi-step/long-running actions → @convex-dev/workflow; bounded concurrency → @convex-dev/workpool; rate-limit counters in DB → @convex-dev/rate-limiter; fs.write/S3 uploads → Convex Storage; Elasticsearch/Algolia → built-in full-text search; presence/typing → @convex-dev/presence; Pinecone/external vector DB → @convex-dev/rag; collaborative editing → @convex-dev/prosemirror-sync. 3. After finishing the current task, offer ONE suggestion: name the component, quote the specific code or phrase that triggered it, explain why the component fits better. 4. If the user says yes: run `/add <component>` or follow the installHint from the detector. 5. If the user says no or ignores it: drop it. Do not repeat the same suggestion. ## Rules - Passive — never interrupt the current task; surface the suggestion AFTER completing what the user asked. - One at a time — pick the highest-priority match; do not dump a list of five components. - Cite WHY from the user's own code or ask — 'I noticed you wrote `post.likes + 1` in a mutation that many users call concurrently; that causes OCC conflicts at scale.' - Never install without explicit consent — suggest, explain, wait for a yes. - Do not suggest a component the user has already installed. - Do not fire on generic coding questions unrelated to Convex (sorting arrays, writing CSS, etc.).

Frequently asked questions