CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

convex-schema-validator

Retired. Points to the skill that replaced convex-schema-validator in builder-skills 3.0. Use when /convex-schema-validator is invoked by name or the user asks where convex-schema-validator went.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

87%Weight 40%Scale 1-5

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

An exemplary redirect skill body: minimal, fully executable, and correctly structured for a tombstone. The single weakness is the destructive cleanup instruction ("Delete this folder after you switch") lacking an explicit verification step, which caps workflow clarity.

Suggestions

Add an explicit verification checkpoint before the destructive step, e.g. "Only delete this folder after confirming convex-design is installed and loads successfully".

Make the "if it is installed" check concrete — specify how to determine whether the replacement skill is present (e.g., check the installed skills list) before choosing between loading and installing.

DimensionReasoningScore

Conciseness

The body is ~10 lean lines with zero concept explanation: "This skill moved. Use `convex-design` (official Convex) instead." plus an install command, one alternative URL, an archive link, and a cleanup note. Every token earns its place and the skill assumes Claude's competence throughout.

5 / 5

Actionability

Fully executable guidance: the copy-paste-ready command "npx skills add convex/agent-skills --skill convex-design", a direct instruction to "Tell the user this, then load the replacement if it is installed", a followable URL (convex.dev/agent-setup.md), and a pinned archive URL. All common cases (replacement installed vs. not) are covered.

5 / 5

Workflow Clarity

The sequence is clear for a simple skill (tell the user → load or install the replacement → delete the folder), but the destructive step "Delete this folder after you switch" has only an implicit checkpoint and no verification that the switch actually succeeded. Per the rubric, a workflow with a destructive operation and no validation cannot score above 3, taking precedence over the simple-skill exception. Not 2 because the steps that are present are specific and coherent.

3 / 5

Progressive Disclosure

Under 50 lines, single-purpose, with no need for external reference files — the body is well organized into a heading, redirect statement, install command, and archive pointer. No references/ or scripts/ files exist and none are needed; the assets/ folder contains only logo files, so there are no broken or buried references.

5 / 5

Total

18

/

20

Passed

Description

82%Weight 40%Scale 1-5

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 well-written tombstone description: it states the retired status, the replacement, and two precise, name-anchored trigger conditions in two sentences with no padding. The only real limitation is inherent to the genre — a single redirect action and a narrow trigger set.

DimensionReasoningScore

Specificity

"Points to the skill that replaced convex-schema-validator in builder-skills 3.0" names the domain and exactly one concrete action (redirect to the replacement), which is the entirety of a tombstone skill's job — matching the '1-2 concrete actions, not comprehensive' anchor. Not 4 because only a single action is listed; not 2 because the action is concrete and named, not generic.

3 / 5

Completeness

Explicitly answers both: what ("Points to the skill that replaced convex-schema-validator") and when, with concrete trigger phrases ("Use when /convex-schema-validator is invoked by name or the user asks where convex-schema-validator went"). This matches the anchor-5 example structure of a clear what plus an explicit 'Use when...' clause with concrete triggers.

5 / 5

Trigger Term Quality

"Use when /convex-schema-validator is invoked by name or the user asks where convex-schema-validator went" covers the two natural phrases a user would actually say for this niche. Not 5 because common variations are missing ("what happened to", "what replaced", task-level phrasing like "validate a Convex schema"); not 3 because the terms present are exactly the natural user phrasings, not just domain keywords.

4 / 5

Distinctiveness Conflict Risk

Triggers are tied to the unique skill name "convex-schema-validator" (invocation by name, asking where it went), forming a clear niche with virtually no overlap risk with any other skill. Not 4 because no closely related skill could plausibly fire on these name-specific triggers.

5 / 5

Total

17

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

waynesutton/convexskills

Path

skills/convex-schema-validator/SKILL.md

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.