convex-database
Convex reactive database patterns, schema design, real-time queries, mutations, actions, and deployment best practices. Use when designing Convex schemas, writing queries/mutations, or managing the Convex backend.
100
100%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
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.
This is a strong skill description that clearly identifies the Convex backend framework as its domain, lists specific capabilities (schema design, queries, mutations, actions, deployment), and includes an explicit 'Use when' clause with natural trigger terms. It uses proper third-person voice and is concise without being vague.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'reactive database patterns', 'schema design', 'real-time queries', 'mutations', 'actions', and 'deployment best practices'. These are concrete, identifiable capabilities within the Convex ecosystem. | 3 / 3 |
Completeness | Clearly answers both 'what' (reactive database patterns, schema design, real-time queries, mutations, actions, deployment best practices) and 'when' (explicit 'Use when designing Convex schemas, writing queries/mutations, or managing the Convex backend'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Convex', 'schema', 'queries', 'mutations', 'actions', 'real-time', 'backend', 'deployment'. These cover the main terms a developer working with Convex would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | The repeated use of 'Convex' as a specific technology creates a clear niche. It's unlikely to conflict with generic database skills or other backend framework skills due to the distinct Convex branding and terminology like 'mutations', 'actions', and 'reactive database'. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill that efficiently communicates Convex-specific patterns, constraints, and workflows. The critical development rules section is particularly strong, providing non-obvious guardrails that prevent common mistakes. The executable code examples and deployment workflow with validation checkpoints make this immediately actionable.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It avoids explaining what Convex is or how databases work generally. Every section delivers specific, non-obvious rules and patterns that Claude wouldn't inherently know (e.g., index naming conventions, no .filter(), no ctx.db in actions). No wasted tokens. | 3 / 3 |
Actionability | Provides fully executable TypeScript code examples for schema definition, queries, and mutations. Commands like `npx convex deploy` and `npx convex dev` are specific and copy-paste ready. The critical rules section gives precise, concrete constraints rather than vague guidance. | 3 / 3 |
Workflow Clarity | The 'Quick Workflow' section provides a clear 4-step sequence with explicit validation checkpoints (dev server confirmation, unit testing, health check), a feedback loop for error recovery (rollback via import, fix, re-deploy, re-check), and clear sequencing of schema change through deployment. | 3 / 3 |
Progressive Disclosure | The skill opens with a clear reference to project-specific configuration in a separate file (database-config.md), keeps the main content as a well-structured overview with distinct sections (Critical Rules, Schema Patterns, Real-Time, Deployment, Workflow), and avoids monolithic walls of text or deeply nested references. | 3 / 3 |
Total | 12 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- monkilabs/opencastle
- Commit
f5c8508
- 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.