Skills

Skill 30 of 33

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…

1 minute · 329 words · 3 sections

Install

$ npx skills add convex/agent-skills --skill convex-suggest

$ npx skills add convex/agent-skills

The first command installs just this skill, by the name in its SKILL.md; the second installs the whole repository.

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.).

About this skill

Trigger

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.

The verbatim description from this skill’s front matter — the string an agent matches on to decide whether to load it.

Colophon for this issue

Colophon

How this issue was made

Source

github.com/convex/agent-skills, branch main, last pushed 29 October 2026.

Licence

Apache-2.0 — the text of every skill is reproduced unmodified, frontmatter included, under the upstream licence.

Discovery

33 skills found by walking the repository tree for SKILL.md, not by matching a directory convention. One layout observed: skills/*/SKILL.md.

Issue colours

Resolved from a curated brand profile — hue 80°, chroma 0.160. Two accent tones are generated per issue and each is proven against its own ground before it ships: a single accent that passes AA on both light and dark paper is arithmetically impossible.

Heading repairs

1 repair applied to this skill so the document has one h1 and no skipped levels:

Shifted “3 headings” from h1 to h2 so the skill title is the only h1.

Spec compliance

Every skill satisfies the Agent Skills specification’s frontmatter rules.

Images

Images inside a skill come from the upstream repository. Where the author gave no alternative text we mark the image decorative rather than inventing a description — a plausible caption we made up is worse than none for the reader who depends on it.

Signal

Install counts come from skills.sh. They measure downloads, not quality, and an unranked repository is not an unread one.

Agent surfaces

The whole issue is available as one markdown document at /convex/agent-skills.md, and each skill at its own .md URL.

Publication

Set by Skills Docs from the source repository. Body text is Literata at the reader’s chosen size and measure; code is Geist Mono. Nothing on this page was written by us except this paragraph.

Proactively suggest the right Convex component

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.

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.).