CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

convex-functions

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

Quality

89%

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

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

This is an exemplary retired-pointer skill body: minimal, fully actionable, and correctly sequenced for its single purpose of redirecting users to the replacement skill. The two minor deductions are the unverified 'delete this folder' cleanup instruction and the orphaned, unreferenced logo assets in the bundle.

DimensionReasoningScore

Conciseness

The body is 18 lines with zero padding: every sentence carries new instructions (the redirect, the install command, the alternative setup URL, the archive link, the cleanup note). It fully assumes Claude's competence and matches the 'lean and efficient; every token earns its place' anchor.

5 / 5

Actionability

The guidance is fully executable: a copy-paste install command ("npx skills add convex/agent-skills --skill convex-design"), a direct URL to follow ("read and follow https://www.convex.dev/agent-setup.md"), and an unambiguous conditional instruction ("Tell the user this, then load the replacement if it is installed"). This matches the copy-paste-ready anchor 5; there are no pseudocode or missing-detail gaps.

5 / 5

Workflow Clarity

For a simple single-purpose skill the sequence is clear: inform the user, load the replacement if installed, otherwise install it (with a one-step alternative). It falls short of anchor 5 because the destructive cleanup instruction "Delete this folder after you switch" has no verification checkpoint (e.g., confirming convex-design loads successfully before deleting), though the archived GitHub copy makes it low-risk and recoverable, so the strict destructive-operation cap of 3 does not fully apply.

4 / 5

Progressive Disclosure

The short body is well organized with clearly signaled one-level-deep external links (the agent-setup URL and the GitHub archive), which suits a sub-50-line skill. However, the bundle's assets/ directory (large-logo.png, small-logo.svg) is present but never referenced in the body, a minor organization gap that keeps it at anchor 4 rather than 5.

4 / 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.

A well-crafted description for a retired-pointer skill: it states exactly what the skill now does (redirect to the replacement) and gives precise, natural trigger conditions that keep it from firing on unrelated Convex work. The only weakness is specificity — it describes a single redirect action without naming the replacement skill (convex-design) or its install path.

Suggestions

Name the replacement skill directly in the description (e.g., "Points to convex-design, which replaced convex-functions in builder-skills 3.0") so the 'what' is concrete rather than a generic pointer.

Add one or two natural trigger variants such as "convex functions" or "the old Convex skill" to broaden keyword coverage for users who don't type the exact slug.

DimensionReasoningScore

Specificity

"Points to the skill that replaced convex-functions in builder-skills 3.0" names one concrete action (redirecting to the replacement), but lists no further actions and never names the replacement skill itself. It matches anchor 3 (domain plus 1-2 concrete actions, not comprehensive) rather than 4, which requires several specific actions.

3 / 5

Completeness

The 'what' is explicit ("Retired. Points to the skill that replaced convex-functions in builder-skills 3.0") and the 'when' is explicit with concrete trigger phrases ("Use when /convex-functions is invoked by name or the user asks where convex-functions went"). This clearly matches the anchor-5 example pattern of both what and when stated with concrete triggers, and is more explicit than the anchor-4 'when could be more specific' case.

5 / 5

Trigger Term Quality

Natural trigger phrases like "/convex-functions is invoked by name" and "the user asks where convex-functions went" cover the realistic invocation cases well. A few natural variants are missing (e.g., "convex functions", "old Convex skill"), so it sits at anchor 4 rather than the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

Triggers are scoped to the exact retired skill name ("convex-functions") in both slash-command and 'where did it go' phrasings, giving it a clear niche with minimal overlap with any other skill. It is not the broad, generic case of anchors 1-3 and matches anchor 5.

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-functions/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.