CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

convex-agents

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

Quality

90%

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

93%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 minimal redirect skill: lean, fully actionable, with exact commands and URLs for both the replacement-install and already-installed paths. The only meaningful gap is that the destructive cleanup instruction ("Delete this folder after you switch") relies on an implicit rather than explicit validation of the switch.

DimensionReasoningScore

Conciseness

The body is roughly ten lines where every sentence instructs ("Use `convex-agent` (official Convex) instead. Tell the user this, then load the replacement if it is installed.") with zero padding or explanation of concepts Claude already knows. The pinned old-content URL is properly framed as a deprecated pointer, so the time-sensitivity penalty does not apply — matching the 'every token earns its place' anchor.

5 / 5

Actionability

The guidance is fully executable: an exact install command ("npx skills add convex/agent-skills --skill convex-agent"), a one-step setup URL ("read and follow https://www.convex.dev/agent-setup.md"), the replacement's exact name, and explicit behavioral instructions for both the installed and not-installed cases. This matches the 'copy-paste ready commands covering the common cases' anchor.

5 / 5

Workflow Clarity

The sequence is clear for a single-purpose redirect skill: tell the user it moved, load or install the replacement, then "Delete this folder after you switch". It scores 4 rather than 5 because the destructive delete step is gated only by the implicit "after you switch" condition — a checkpoint is present but never made explicit (no instruction on how to confirm the switch succeeded), which is a minor validation gap.

4 / 5

Progressive Disclosure

The skill is under 50 lines with no content that belongs in separate files, so per the simple-skill guidance well-organized sections suffice; the two external links (install docs, old-content archive) are one level deep and clearly labeled. The bundled assets (large-logo.png, small-logo.svg) are branding files, not content references, so they create no navigation burden.

5 / 5

Total

19

/

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-constructed retirement-notice description: it states the skill's single purpose plainly, includes an explicit 'Use when' clause with concrete triggers, and is highly distinguishable from other skills. Its only limitation is inherent to its nature — a redirect has few capabilities to enumerate, capping specificity at mid-range.

Suggestions

Name the replacement explicitly in the description (e.g., "Points to `convex-agent`, the skill that replaced convex-agents in builder-skills 3.0") to raise specificity and help users who know the successor's name.

Add an unhyphenated natural variant such as "Convex agents" to the trigger clause so users typing the name without the hyphen still match.

DimensionReasoningScore

Specificity

"Points to the skill that replaced convex-agents in builder-skills 3.0" names the domain and one concrete action (redirecting to the replacement), but offers no further capabilities to enumerate — matching the '1-2 concrete actions, not comprehensive' anchor. It is not a 4 because there are not several specific actions listed, and not a 2 because 'Points to the skill that replaced' is a concrete, unambiguous action rather than generic filler.

3 / 5

Completeness

It explicitly answers 'what' ("Retired. Points to the skill that replaced convex-agents") and 'when' with a concrete trigger clause ("Use when /convex-agents is invoked by name or the user asks where convex-agents went"), matching the anchor requiring both what and when with concrete trigger phrases. A 4 would require the 'when' to be less explicit, but here both trigger conditions are spelled out.

5 / 5

Trigger Term Quality

The description includes the exact invocation trigger "/convex-agents is invoked by name" and the natural user phrase "asks where convex-agents went", giving good coverage of how a user would actually reference this skill. It falls short of 5 because common variations like the unhyphenated "Convex agents" or "Convex agent skills" are absent, while exceeding 3 since both the slash-command form and a colloquial question form are covered.

4 / 5

Distinctiveness Conflict Risk

The triggers are pinned to the exact retired skill name ("/convex-agents... invoked by name", "where convex-agents went"), creating a clear niche with minimal risk of firing for unrelated skills. It is not a 4 because the scope is so narrow — only the legacy name — that overlap even with closely related skills is unlikely.

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