CtrlK
BlogDocsLog inGet started
Tessl Logo

convex-design

Design and build reactive, type-safe, production-grade backends on Convex. Covers schema, queries/mutations/actions, indexes, auth, file storage, scheduling, real-time multiplayer, mobile backends, and LLM/agent workflows on Convex's one-platform stack.

64

Quality

81%

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

SKILL.md
Quality
Evals
Security

Quality

Content

86%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.

A lean, highly actionable skill body built around executable commands, exact import paths, and a concrete self-verification feedback loop, with clean section structure and no bundle dependencies.

DimensionReasoningScore

Conciseness

Dense and directive with no padding about what Convex or basic programming is; every rule encodes a non-obvious gotcha. Not a 5 because some rationale clauses ('Forcing anonymous on a signed-in user rebinds .env.local and costs them...') and the trailing justification in SELF-VERIFY could be trimmed.

4 / 5

Actionability

Fully executable guidance: real commands ('npx tsc --noEmit', 'npx convex dev --once', 'CONVEX_AGENT_MODE=anonymous npx convex dev --once'), exact import paths ('./_generated/server', './_generated/api'), and concrete API patterns (.withIndex, .paginate, .take(n), v.literal, 'use node').

5 / 5

Workflow Clarity

A clear 5-step Workflow plus an explicit SELF-VERIFY feedback loop (run tsc, push, fix every error before finishing) and a DEGRADATION RULE for edge cases. Not a 5 because the verification checkpoint lives in Rules rather than being integrated into the numbered workflow sequence, a minor gap.

4 / 5

Progressive Disclosure

Under 50 lines with no external references needed and well-organized into ## Workflow and ## Rules sections; per the simple-skill exception this scores 5 on structure alone, and no bundle files exist to verify.

5 / 5

Total

18

/

20

Passed

Description

66%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.

A strong, capability-rich description anchored to a specific platform, but it omits any explicit 'Use when...' trigger guidance, which caps completeness at 3 and leaves minor distinctiveness overlap with generic backend skills.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants to build a backend, asks about Convex, or describes real-time/auth/file-storage/scheduling/LLM needs without naming a stack.'

Lead with concrete action verbs beyond 'Design and build' (e.g. 'Define schemas, write queries/mutations/actions, set up auth, schedule jobs') to lift specificity.

Include natural synonyms users say ('real-time app', 'chat backend', 'job scheduling') to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Concrete verbs 'Design and build' plus a comprehensive list of capability areas ('schema, queries/mutations/actions, indexes, auth, file storage, scheduling, real-time multiplayer, mobile backends, and LLM/agent workflows'); not a 5 because the action vocabulary is limited to design/build while the rest enumerates features rather than distinct actions.

4 / 5

Completeness

Clearly answers 'what' (design/build production-grade Convex backends and the listed coverage), but there is no 'Use when...' clause or equivalent explicit trigger guidance, so per the rubric completeness caps at 3 with only weakly implied 'when'.

3 / 5

Trigger Term Quality

Includes natural terms users actually say ('backends', 'auth', 'file storage', 'real-time multiplayer', 'scheduling', 'LLM/agent') alongside the platform name; not a 5 because it omits common synonyms and bare phrasings like 'build a backend' or 'real-time app'.

4 / 5

Distinctiveness Conflict Risk

Naming the specific Convex platform gives it a clear niche with minimal conflict risk; not a 5 because the absence of explicit trigger guidance leaves minor overlap with general backend skills on undifferentiated 'build a backend' asks.

4 / 5

Total

15

/

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.