CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

convex-best-practices

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

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

83%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.

As a retirement stub, the content is near-ideal: extremely lean, fully executable, and crystal clear about what to tell the user and where the replacements live. The two blemishes are the unvalidated, ambiguous "delete this folder" instruction capping workflow clarity, and orphaned asset files in the bundle that serve no purpose.

Suggestions

Remove or tighten "Delete this folder after you switch": either drop it, or make it explicit who deletes, when, and only after verifying the replacement skills are installed and working.

Delete the unreferenced assets/large-logo.png and assets/small-logo.svg from the bundle, or reference them if they are intentionally retained.

DimensionReasoningScore

Conciseness

The body is a lean redirect: "This skill moved. Use `convex-reviewer`... and `convex-optimize`... instead. Tell the user this, then load the replacement if it is installed." Every sentence instructs; nothing explains concepts Claude already knows. This matches the top anchor — every token earns its place.

5 / 5

Actionability

The guidance is fully executable: a copy-paste install command (`npx skills add convex/agent-skills --skill convex-reviewer --skill convex-optimize`), a directive to read and follow a concrete URL (https://www.convex.dev/agent-setup.md), a link to the old content, and an unambiguous behavioral instruction (tell the user, then load the replacement if installed).

5 / 5

Workflow Clarity

The redirect sequence (tell the user it moved, load the replacement if installed, otherwise offer the install command) is clear, but the destructive instruction "Delete this folder after you switch" has an ambiguous actor and no validation checkpoint. Per the rubric, a workflow involving a destructive operation without validation/verification is capped at 3.

3 / 5

Progressive Disclosure

The body is under 50 lines, well organized for a single-purpose stub, and all outbound references (install command, agent-setup URL, old-content GitHub link) are clearly signaled and one level deep. It is not a 5 because the bundle ships two asset files (assets/large-logo.png, assets/small-logo.svg) that are never referenced in the body — a minor organization gap.

4 / 5

Total

17

/

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.

For a retirement/redirect stub, this description is exemplary: it is upfront about being retired, states its single purpose, and gives precise explicit trigger conditions that prevent it from firing for general Convex work. The only real limitation is the inherent one-action scope, which slightly limits specificity and leaves a few natural phrasing variants uncovered.

Suggestions

Name the replacement skills in the description (e.g., "Points to convex-reviewer and convex-optimize, which replaced it") to add specificity beyond the single "points to" action.

Add a natural phrasing variant such as "convex best practices" (without the slash) to the trigger clause so the redirect also fires when users type the name informally.

DimensionReasoningScore

Specificity

The description names its domain (a retired-skill redirect) and exactly one concrete action — "Points to the skill that replaced convex-best-practices" — which matches the anchor for naming a domain with 1-2 concrete actions. It is not a 4 because no additional specific actions are listed.

3 / 5

Completeness

It explicitly answers both questions: the what is "Retired. Points to the skill that replaced convex-best-practices in builder-skills 3.0" and the when is an explicit "Use when..." clause with concrete trigger phrases. This matches the top anchor exactly.

5 / 5

Trigger Term Quality

"Use when /convex-best-practices is invoked by name or the user asks where convex-best-practices went" supplies natural phrases users would actually say. It is not a 5 because common variations like "convex best practices" (without the slash) or "what happened to the convex skill" are not covered.

4 / 5

Distinctiveness Conflict Risk

It occupies a clear niche (redirect for one exact skill name) and triggers only on explicit invocation of "convex-best-practices" by name, so conflict with the replacement skills (convex-reviewer, convex-optimize) or any other skill is minimal.

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-best-practices/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.