CtrlK
BlogDocsLog inGet started
Tessl Logo

convex-quickstart

Get a barebones Convex + web template running from a one-sentence idea.

64

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/convex-quickstart/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

96%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a model of token-efficient, actionable instruction: concrete commands, an explicit verification feedback loop, a degradation path, and high-signal Convex gotchas with no padding. The only structural improvement is offloading the capability-level Convex API rules into a reference file so the quickstart stays purely about standing up the template.

DimensionReasoningScore

Conciseness

Lean and imperative throughout — no padding, no explanations of concepts Claude already knows; every rule is a non-obvious Convex-specific constraint (e.g. ".withIndex(...) callbacks only have eq/gt/gte/lt/lte — there is no .range(...) method") that earns its tokens.

5 / 5

Actionability

Fully executable guidance: a concrete recipe invocation with arguments ("Run recipe `quickstart-recipe@^2` with {idea, template}"), and copy-paste commands including `npx tsc --noEmit`, `npx convex whoami`, `npx convex dev --once`, and `CONVEX_AGENT_MODE=anonymous npx convex dev --once` with the exact condition governing each.

5 / 5

Workflow Clarity

Clear three-step sequence (run recipe → open dev URL → confirm before building features) with a confirmation checkpoint, a re-run guard ("Never re-run the recipe if it already reported success"), and an explicit SELF-VERIFY feedback loop — verify, fix every reported error, only then finish — plus a defined degradation path when the scaffold cannot run.

5 / 5

Progressive Disclosure

The body is short (~24 lines) and well organized into Workflow and Rules sections, but four dense paragraphs of general Convex API rules (data access/imports, reserved names, HTTP routes, runQuery references) are inlined in the quickstart that could be split into a one-level-deep reference file; no references are signaled, which keeps this just below the clear overview with well-signaled references anchor.

4 / 5

Total

19

/

20

Passed

Description

53%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description communicates a clear, narrow purpose in third person with a concrete domain, but it answers only 'what' — not 'when'. Adding an explicit trigger clause and natural synonyms (scaffold, set up a Convex project, Next.js) would materially raise completeness and trigger-term quality.

Suggestions

Add an explicit 'when' clause, e.g. "Use when the user wants to scaffold or set up a new Convex project, Convex + Next.js app, or web template from an idea."

Include natural trigger synonyms users would actually say: "scaffold", "set up", "quickstart", "Next.js", "Convex project".

Optionally note the concrete deliverables (project created, deps installed, local backend + web dev server running) to lift specificity beyond a single action.

DimensionReasoningScore

Specificity

Names the domain ("Convex + web template") and one concrete action ("Get a barebones... template running"), but stops there — no scaffold/set up/install verbs beyond the single action, matching the '1-2 concrete actions, not comprehensive' anchor rather than the several-actions anchors at 4-5.

3 / 5

Completeness

The 'what' is clear (stand up a barebones Convex + web template locally), but there is no 'Use when...' clause or equivalent explicit trigger guidance, so completeness is capped at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

"Convex", "web template", and "one-sentence idea" are relevant keywords, but common natural phrasings a user would actually say ("set up a Convex project", "scaffold a Convex app", "Next.js", "quickstart") are missing — some relevant keywords, missing common variations or synonyms.

3 / 5

Distinctiveness Conflict Risk

"Convex" pins a clear niche with distinct triggers and minimal conflict risk, but the description could still overlap generic web-app or Next.js scaffolding skills since no explicit triggers disambiguate — mostly distinct with minor overlap risk.

4 / 5

Total

13

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
openclaw/clawhub
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.