convex-component-authoring
How to create, structure, and publish self-contained Convex components with proper isolation, exports, and dependency management
59
48%
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 ./skills/convex-component-authoring/SKILL.mdQuality
Discovery
32%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 specific technology domain (Convex) and lists relevant concepts, but lacks concrete actionable verbs and completely omits trigger guidance for when Claude should select this skill. The terminology is moderately specific to Convex but could benefit from more natural user-facing keywords and explicit usage scenarios.
Suggestions
Add a 'Use when...' clause with trigger terms like 'Convex component', 'publish Convex package', 'component isolation', or 'Convex library'
Replace abstract terms like 'proper isolation' with concrete actions such as 'configure component.config.ts', 'define public API exports', 'set up peer dependencies'
Include file type triggers users might mention: 'convex.config.ts', 'component entry point', 'Convex npm package'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Convex components) and lists some actions (create, structure, publish) with qualifiers (proper isolation, exports, dependency management), but these are somewhat abstract rather than concrete specific actions like 'configure package.json' or 'define component entry points'. | 2 / 3 |
Completeness | Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance. Per rubric guidelines, missing explicit trigger guidance should cap completeness at 2, and this has no 'when' component at all. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Convex components', 'exports', 'dependency management', but misses common variations users might say such as 'npm package', 'component library', 'convex plugin', or 'publish to npm'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Convex components' provides some specificity, but 'dependency management' and 'exports' are generic terms that could overlap with general JavaScript/npm packaging skills or other component-based frameworks. | 2 / 3 |
Total | 7 / 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 guidance with comprehensive, executable code examples for Convex component authoring. However, it's somewhat verbose with explanatory content that could be trimmed, and lacks explicit validation/verification steps in the workflow. The structure is good but could benefit from splitting detailed examples into separate files.
Suggestions
Add explicit validation checkpoints after each major step (e.g., 'Run `npx convex dev` to verify schema compiles correctly before proceeding')
Move the detailed Rate Limiter example to a separate EXAMPLES.md file and reference it from the main skill
Remove or condense the 'What Are Convex Components?' section - Claude understands these concepts
Add a troubleshooting section with common error messages and their solutions to support error recovery
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary explanations like 'What Are Convex Components?' section that explains basic concepts Claude likely knows. The extensive code examples are valuable but could be more condensed in places. | 2 / 3 |
Actionability | Provides fully executable, copy-paste ready code examples throughout. Every section includes concrete TypeScript code with proper imports, types, and complete implementations including a full rate limiter component example. | 3 / 3 |
Workflow Clarity | Steps are presented in a logical numbered sequence (1-5 for creating a component), but lacks explicit validation checkpoints. No verification steps between creating schema, functions, and publishing. Missing feedback loops for error recovery during component development. | 2 / 3 |
Progressive Disclosure | Content is well-structured with clear sections, but the document is quite long (~300 lines) with all content inline. The rate limiter example could be in a separate EXAMPLES.md file. References to external docs are present but the main content could benefit from better splitting. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 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 |
Total | 12 / 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.