convex-create-component

Builds reusable Convex components with isolated tables and app-facing APIs. Use for new components, reusable backend modules, integrations, or component boundary work.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/convex-create-component/SKILL.md

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with executable code, concrete commands, a sequenced workflow with validation feedback loops, and a clean one-level-deep reference structure. The main weakness is mild redundancy between the skeleton and the Patterns section.

Suggestions

Collapse the duplicated app-wrapper example: keep it in the Component Skeleton and have the Client-facing API pattern reference it (or show only the contrasting Bad snippet) to tighten token use.

Shorten the inline returns-object validator in listUnread to the essential shape (e.g., `returns: v.array(v.any())` or a comment) since the index/query mechanics are the actual lesson.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and assumes competence, but the app-wrapper example appears both in the Component Skeleton and again (nearly identically) in the Client-facing API pattern, and the full returns-object validator in listUnread is heavier than needed to convey the point, fitting the score-2 anchor.	2 / 3
Actionability	It provides a complete, copy-paste-ready skeleton (convex.config.ts, schema.ts, lib.ts, app wiring), specific commands like `npx convex codegen --component-dir convex/components/<name>` and `npx convex dev`, and concrete Bad/Good code pairs, matching the score-3 anchor.	3 / 3
Workflow Clarity	A 10-step numbered workflow is followed by a dedicated ordered Validation section with a validate->fix->retry feedback loop ("fix codegen, type, or boundary issues before finishing") and a closing checklist, satisfying the score-3 anchor.	3 / 3
Progressive Disclosure	SKILL.md acts as a clear overview with a decision table pointing to one-level-deep, real reference files (local/packaged/hybrid-components.md) plus a separate advanced-patterns.md, all clearly signaled and verified to exist, matching the score-3 anchor.	3 / 3
	Total	11 / 12 Passed

Description

75%

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 is third-person, well-scoped to the Convex component niche, and cleanly answers both what and when with an explicit trigger clause. It is slightly thin on enumerated concrete actions and on natural trigger-term variations.

Suggestions

Add one or two more concrete actions (e.g., "defines isolated schemas, exposes typed query/mutation APIs, wires components into the app") to lift specificity toward the score-3 anchor.

Broaden the "Use for" clause with natural phrasings a user might actually say, such as "Use when creating a Convex component, packaging backend logic for reuse, or building a third-party integration that owns its own tables."

Dimension	Reasoning	Score
Specificity	"Builds reusable Convex components with isolated tables and app-facing APIs" names the domain and a couple of concrete properties, but it is essentially a single action with descriptors rather than a list of multiple specific actions, matching the score-2 anchor.	2 / 3
Completeness	It explicitly states both what it does ("Builds reusable Convex components with isolated tables and app-facing APIs") and when to use it via an explicit "Use for..." clause, satisfying the score-3 anchor.	3 / 3
Trigger Term Quality	The "Use for new components, reusable backend modules, integrations, or component boundary work" clause offers several relevant terms, but coverage of natural user phrasings is partial and missing common variations, fitting the score-2 anchor.	2 / 3
Distinctiveness Conflict Risk	The "Convex components" niche with isolated tables is a clear, scoped domain unlikely to trigger for unrelated skills, matching the score-3 anchor.	3 / 3
	Total	10 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: openclaw/clawhub
Path: .agents/skills/convex-create-component/SKILL.md
Commit: f92495f

Reviewed: about 21 hours ago

Table of Contents

Discovery Implementation Validation

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.