convex
Umbrella skill for all Convex development patterns. Routes to specific skills like convex-functions, convex-realtime, convex-agents, etc.
64
53%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/convex/SKILL.mdQuality
Discovery
22%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 description fails to explain what concrete actions the skill performs, instead describing its meta-role as a router. It lacks explicit trigger guidance and natural user keywords, making it difficult for Claude to know when to select this skill versus the specific Convex skills it references.
Suggestions
Add a 'Use when...' clause specifying when this umbrella skill should be selected over specific Convex skills (e.g., 'Use when the user mentions Convex without specifying a particular feature area')
Include natural trigger terms users would say like 'Convex backend', 'Convex database', 'real-time app', 'serverless functions'
Describe concrete actions this skill performs beyond routing, such as 'Guides Convex project setup, determines appropriate patterns, and coordinates between specialized Convex skills'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'umbrella skill' and 'development patterns' without listing any concrete actions. It only mentions routing to other skills rather than describing what this skill actually does. | 1 / 3 |
Completeness | The 'what' is weak (just says it 'routes' to other skills) and there is no 'when' clause or explicit trigger guidance. Missing any 'Use when...' statement entirely. | 1 / 3 |
Trigger Term Quality | Contains 'Convex' as a relevant keyword and mentions specific skill names (convex-functions, convex-realtime, convex-agents), but lacks natural user terms like 'database', 'backend', 'real-time sync', or common Convex use cases users would mention. | 2 / 3 |
Distinctiveness Conflict Risk | The 'Convex' domain is specific, but 'umbrella skill' and 'development patterns' are generic. Could conflict with the specific skills it mentions routing to, creating ambiguity about when to use this vs. the specialized skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted index skill that efficiently routes developers to specific Convex skills. It excels at conciseness and progressive disclosure by serving purely as a navigation hub. The actionability score reflects that this is intentionally a routing skill rather than an implementation guide, which is appropriate for its purpose.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean index skill with no unnecessary explanation. Every line serves navigation purposes, using efficient table format to convey skill routing information. | 3 / 3 |
Actionability | Provides clear routing to specific skills with 'Use When' guidance, but as an index skill it contains no executable code or concrete implementation details itself. The Quick Start section gives a reasonable workflow but remains at the routing level. | 2 / 3 |
Workflow Clarity | For an index/routing skill, the workflow is appropriately clear: the Quick Start section provides a sensible 4-step sequence for approaching Convex development, and the tables clearly indicate when to use each sub-skill. | 3 / 3 |
Progressive Disclosure | Excellent progressive disclosure - this is purely an overview that routes to one-level-deep specific skills. Well-organized into logical categories (Core, Data, Advanced, Security, Guidelines) with clear navigation via skill commands. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
62%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 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 |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_examples | No examples detected (no code fences and no 'Example' wording) | Warning |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
Total | 10 / 16 Passed | |
- Repository
- waynesutton/convexskills
- Commit
8ef49c9
- 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.