convex-database
Convex reactive database patterns, schema design, real-time queries, mutations, actions, authentication, migrations, performance optimization, and component creation. Use when designing Convex schemas, writing queries/mutations, managing the Convex backend, setting up auth, migrating data, optimizing performance, or building Convex components.
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 technology domain, lists comprehensive specific capabilities, and includes an explicit 'Use when...' clause with natural trigger terms. The description is well-structured, concise, and would allow Claude to confidently select this skill when a user is working with Convex, while avoiding false triggers for other database or backend technologies.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and concepts: schema design, real-time queries, mutations, actions, authentication, migrations, performance optimization, and component creation. These are all distinct, concrete capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (reactive database patterns, schema design, queries, mutations, actions, auth, migrations, optimization, components) and 'when' with an explicit 'Use when...' clause listing specific trigger scenarios. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Convex', 'schema', 'queries', 'mutations', 'auth', 'migrations', 'performance', 'real-time', 'backend', 'components'. These cover the natural vocabulary a developer working with Convex would use. | 3 / 3 |
Distinctiveness Conflict Risk | The repeated use of 'Convex' as a specific technology creates a clear niche. Terms like 'Convex schemas', 'Convex backend', and 'Convex components' are highly distinctive and unlikely to conflict with generic database or backend skills. | 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 an excellent skill file that efficiently covers Convex database patterns with high information density. The critical development rules section is particularly strong, providing specific, non-obvious constraints that Claude wouldn't know by default. The combination of a topic routing table, concrete code examples, clear workflow steps with validation checkpoints, and well-organized references makes this a model skill file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient throughout. It avoids explaining what Convex is or how databases work, instead jumping straight into actionable rules and patterns. Every section earns its place with specific, non-obvious guidance (e.g., '.filter() is equivalent to JS filtering', 'skip no-op writes'). | 3 / 3 |
Actionability | Provides fully executable TypeScript code examples for schema definition, queries, mutations, and auth patterns. The critical rules are specific and concrete (e.g., exact import paths, naming conventions for indexes, specific commands like `npx convex dev`). Copy-paste ready examples throughout. | 3 / 3 |
Workflow Clarity | The 'Quick Workflow' section provides a clear 5-step sequence with explicit validation checkpoints, a rollback procedure for failures, and a dedicated validation checkpoints table. The migration workflow correctly references the detailed guide and includes a health check command with error handling. | 3 / 3 |
Progressive Disclosure | Excellent topic routing table at the top with one-level-deep references to specific files (migrations, performance, auth, components, quickstart). The SKILL.md serves as a clear overview with essential rules and patterns inline, while appropriately deferring detailed topics to reference files. Also links to project-specific config. | 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
18c6f2c
- 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.