convex
Guidelines for developing with Convex backend-as-a-service platform, covering queries, mutations, actions, and real-time data patterns
62
52%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./convex/SKILL.mdQuality
Discovery
40%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 identifies a clear niche (Convex platform) and lists relevant technical concepts, making it distinctive. However, it lacks explicit trigger guidance ('Use when...') and the capabilities listed are technical jargon rather than concrete user-facing actions. The description would benefit from natural language triggers and clearer action statements.
Suggestions
Add a 'Use when...' clause with trigger terms like 'Convex project', 'Convex backend', 'Convex database', or 'building with Convex'
Replace abstract terms like 'queries, mutations, actions' with concrete actions like 'write database queries', 'create server functions', 'implement real-time subscriptions'
Include common user phrases like 'Convex app', 'reactive data', 'serverless backend' to improve trigger term coverage
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Convex backend-as-a-service) and lists some actions (queries, mutations, actions, real-time data patterns), but these are technical concepts rather than concrete user-facing actions like 'create database queries' or 'set up real-time subscriptions'. | 2 / 3 |
Completeness | Describes what (guidelines for Convex development covering specific patterns) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes 'Convex' and 'backend-as-a-service' which users might say, plus technical terms like 'queries, mutations, actions'. However, missing common variations like 'Convex database', 'Convex functions', 'reactive queries', or 'BaaS'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Convex' is a specific platform name that creates a clear niche. The combination of 'Convex backend-as-a-service' with specific patterns like 'queries, mutations, actions' makes it unlikely to conflict with other backend or database skills. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides excellent, actionable Convex code examples that are immediately usable, which is its primary strength. However, it's diluted by generic TypeScript/React guidance that Claude doesn't need, and lacks the workflow validation checkpoints that would help with complex operations. The document would benefit from trimming non-Convex content and adding explicit verification steps.
Suggestions
Remove or significantly reduce the 'General Development Specifications' section - Claude already knows TypeScript best practices, React patterns, and Tailwind/Shadcn usage
Add validation/verification steps to workflows, especially for schema migrations and deployment processes
Consider splitting into SKILL.md (quick start + core patterns) and separate reference files for HTTP routes, cron jobs, and file handling
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary general guidance (code style, UI framework integration, React patterns) that Claude already knows and isn't Convex-specific. The Convex-specific sections are reasonably efficient, but the document could be tightened by removing generic TypeScript/React advice. | 2 / 3 |
Actionability | Provides fully executable, copy-paste ready code examples for all major Convex patterns including queries, mutations, actions, schema definitions, HTTP routes, cron jobs, and file handling. Each example is complete and demonstrates real usage. | 3 / 3 |
Workflow Clarity | The file handling section shows a clear 3-step process, but other multi-step workflows lack explicit validation checkpoints. No feedback loops for error recovery are provided, and the best practices are listed without sequencing for when to apply them. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear section headers, but it's a monolithic document with no references to external files for advanced topics. The general development specifications section could be split out or removed entirely, as it's not Convex-specific. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
Total | 13 / 16 Passed | |
- Repository
- mindrally/skills
- Commit
47f47c1
- 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.