convex-backend

Convex backend development guidelines. Use when writing Convex functions, schemas, queries, mutations, actions, or any backend code in a Convex project. Triggers on tasks involving Convex database operations, real-time subscriptions, file storage, or serverless functions.

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

92%

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

A concise, highly actionable reference with strong code examples and clear organization. The main weakness is progressive disclosure: the body advertises a complete guide in AGENTS.md, but that file is absent from the bundle.

Suggestions

Add the referenced AGENTS.md to the bundle (or remove the "Full Compiled Document" section) so the only deeper-level reference is real.

If AGENTS.md is intentionally omitted, inline the few additional rules that matter most instead of pointing to a missing file.

Consider moving the verbose validators table into the referenced detail file to keep SKILL.md even leaner as an overview.

Dimension	Reasoning	Score
Conciseness	Lean and table/code-driven with no padding explaining what Convex or TypeScript are; every section earns its place.	3 / 3
Actionability	Executable, copy-paste-ready TypeScript (function registration, query-with-index) plus a complete validators table and concrete "Key Rules" directives.	3 / 3
Workflow Clarity	A single-purpose reference skill (not a multi-step process); per the simple-skills note its well-organized categories and unambiguous guidance warrant a 3.	3 / 3
Progressive Disclosure	Structure is present and it signals a deeper reference, but the referenced [AGENTS.md](AGENTS.md) does not exist and no bundle files are provided, so the one-level-deep navigation is broken.	2 / 3
	Total	11 / 12 Passed

Description

100%

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, specific description with concrete actions, natural trigger terms, and explicit what/when guidance in third person. It clearly occupies the Convex-backend niche with low conflict risk.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ("writing Convex functions, schemas, queries, mutations, actions", "database operations, real-time subscriptions, file storage, or serverless functions") rather than vague language.	3 / 3
Completeness	Explicitly answers both what ("Convex backend development guidelines") and when ("Use when...", "Triggers on...") with explicit triggers.	3 / 3
Trigger Term Quality	Good coverage of natural terms a user would say — "Convex functions", "schemas", "queries", "mutations", "actions", "real-time subscriptions", "file storage", "serverless functions" — matching the score-3 anchor.	3 / 3
Distinctiveness Conflict Risk	The Convex-specific niche and triggers make it clearly distinguishable and unlikely to fire for the wrong skill.	3 / 3
	Total	12 / 12 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: CloudAI-X/claude-workflow-v2
Path: skills/convex-backend/SKILL.md
Commit: 4c242af

Reviewed: about 16 hours ago

Table of Contents

Discovery Implementation Validation

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.