CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

convex-file-storage

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

Quality

80%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/convex-file-storage/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

76%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 tombstone body is a model of token efficiency and gives a concrete install command plus clear redirect instructions. Its main flaws are a vague "load the replacement if installed" step and a destructive cleanup instruction ("Delete this folder") with no verification checkpoint, plus orphaned asset files in the bundle.

Suggestions

Add a verification checkpoint before the destructive step, e.g., "Only after confirming convex-design loads successfully, delete this folder."

Specify how to load the replacement when it is already installed (e.g., the expected skill path or invocation) so the "load" step is executable.

Remove or reference the unused assets/large-logo.png and assets/small-logo.svg so the bundle contains only files the skill actually uses.

DimensionReasoningScore

Conciseness

The body is 12 lean lines — "This skill moved. Use `convex-design` (official Convex) instead" — with zero padding and no explanation of concepts Claude already knows; every token earns its place.

5 / 5

Actionability

It provides a copy-paste-ready command ("npx skills add convex/agent-skills --skill convex-design") and a followable URL, but "load the replacement if it is installed" omits how to locate or load it, a minor gap that fits the 'mostly executable with minor gaps' anchor rather than fully copy-paste-ready level 5.

4 / 5

Workflow Clarity

The redirect sequence (tell the user, then load or install the replacement) is clear, but "Delete this folder after you switch" is a destructive step with no verification checkpoint (e.g., confirm the replacement is installed and working first), so the destructive-operation cap holds workflow clarity at 3.

3 / 5

Progressive Disclosure

For an under-50-line single-purpose skill the body is well organized with a clear heading and one-level-deep external links, but the bundle's assets (large-logo.png, small-logo.svg) are orphaned — referenced nowhere in the body — a minor organization gap that keeps it below the top anchor.

4 / 5

Total

16

/

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.

This is a well-formed tombstone description: it is unambiguous about the skill's retired status, names its replacement, and gives explicit, narrowly-scoped trigger conditions that minimize conflict risk. Its weaknesses are thin coverage of the original skill's subject matter and missing natural keyword variants, which slightly limit specificity and trigger reach.

Suggestions

Briefly state the original skill's domain (e.g., "was for file storage/upload in Convex") so users searching by capability words, not just the skill name, can find it.

Add one or two natural trigger variants such as "Convex file storage" or "storing files in Convex" to broaden keyword coverage.

DimensionReasoningScore

Specificity

"Points to the skill that replaced convex-file-storage in builder-skills 3.0" names the domain and one concrete action (redirecting to the replacement), but says nothing about the original skill's capabilities, matching the '1-2 concrete actions, not comprehensive' anchor rather than the broader coverage of level 4.

3 / 5

Completeness

It explicitly answers both "what" ("Retired. Points to the skill that replaced convex-file-storage") and "when" with concrete trigger phrases ("Use when /convex-file-storage is invoked by name or the user asks where convex-file-storage went"), matching the top anchor; the "when" clause is already maximally explicit so the level-4 anchor ("could be more explicit") does not fit.

5 / 5

Trigger Term Quality

"Use when /convex-file-storage is invoked by name or the user asks where convex-file-storage went" provides relevant, natural triggers for this niche, but misses common variations a user might say (e.g., "Convex file storage", "file uploads in Convex"), fitting the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

Triggers are scoped to the exact skill name and questions about its disappearance — a clear niche with distinct triggers and minimal risk of firing for the wrong skill.

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-file-storage/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.