CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

convex-security-check

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

1.00x
Quality

83%

Does it follow best practices?

Impact

100%

1.00x

Average score across 3 eval scenarios

SecuritybySnyk

Critical

Do not install without reviewing

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 redirect/tombstone skill this is an excellent example of economy: fully executable commands, precise links, and zero padding. The two weaknesses are the unvalidated destructive instruction to delete the folder and two orphaned logo assets in the bundle that serve no referenced purpose.

Suggestions

Add a validation step before the destructive delete, e.g. "Confirm sec-check loads successfully before deleting this folder", so the workflow is safe if the install fails.

Remove the unreferenced assets/large-logo.png and assets/small-logo.svg, or reference them somewhere, so the bundle matches the skill's actual content.

DimensionReasoningScore

Conciseness

Every line earns its place: what moved, what to use instead, copy-paste install commands, a one-step setup URL, and a link to the old content. There is no padding and no explanation of concepts Claude already knows, matching the 'lean and efficient' anchor.

5 / 5

Actionability

The guidance is fully executable: concrete install commands ("npx builder-skills add sec-check", "npx skills add convex/agent-skills --skill convex-authz"), exact URLs for setup and old content, and a clear directive ("Tell the user this, then load the replacement if it is installed"). It covers the common cases for a redirect skill, matching the copy-paste-ready anchor.

5 / 5

Workflow Clarity

The sequence is present and readable (tell the user, load or install the replacement, then "Delete this folder after you switch"), but the final delete step is destructive with no validation checkpoint — nothing confirms the replacement is installed and working before the folder is removed. Per the rubric guideline, a workflow with a destructive operation and no validation is capped at 3 even for a single-purpose skill.

3 / 5

Progressive Disclosure

The body is short, well-organized, and its external links (convex.dev agent setup, GitHub old-content link) are clearly signaled and one level deep. However, the bundle contains two asset files (large-logo.png, small-logo.svg) that are referenced nowhere in the body, a minor organization gap that keeps this just below the top anchor.

4 / 5

Total

17

/

20

Passed

Description

75%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-written tombstone description: it is unambiguous about its retired status, states exactly what it does (point to replacements), and gives explicit, concrete trigger conditions. The main limitation is narrow trigger vocabulary — only the exact hyphenated skill name, with no natural phrasing variations.

Suggestions

Add natural trigger variations such as "convex security check" (spaced) or "the old Convex security skill" so the description fires when users refer to the skill without the exact hyphenated name.

Name the replacement skills in the description itself (e.g., "Points to sec-check and convex-authz") so the redirect target is visible before the body is loaded.

DimensionReasoningScore

Specificity

"Points to the skill that replaced convex-security-check" names the domain and one concrete action (redirecting to the replacement), matching the anchor for 1-2 concrete actions without comprehensive coverage. It is not a 2 because the action is concrete rather than generic, and not a 4 because only a single capability is described.

3 / 5

Completeness

It explicitly answers both questions: what ("Retired. Points to the skill that replaced convex-security-check in builder-skills 3.0") and when ("Use when /convex-security-check is invoked by name or the user asks where convex-security-check went") with concrete trigger phrases. This matches the top anchor exactly; neither component is vague or implicit.

5 / 5

Trigger Term Quality

Triggers rely on the exact skill name ("/convex-security-check is invoked by name", "asks where convex-security-check went"), which are relevant keywords but miss natural variations and synonyms such as "convex security check" split into words or "the old Convex security skill". This fits the 'some relevant keywords but missing common variations' anchor rather than the good-coverage anchor.

3 / 5

Distinctiveness Conflict Risk

It occupies a clear niche — a tombstone for one specific retired skill name — and its triggers (invocation by exact name, asking where it went) are distinct from any other skill's triggers. Conflict risk is minimal, matching the top anchor.

5 / 5

Total

16

/

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-security-check/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.