Conciseness

The body is very lean with no background on Convex or seeding concepts ("Populate tables via an internalMutation seed function (re-runnable) or `npx convex import`, matching the schema"), assuming Claude's competence. However, the Rules section duplicates the workflow — "Make seeding idempotent" restates step 3 verbatim and "Seed via internalMutation or convex import, matching validators" restates steps 1-2 — so a few tokens could be trimmed, keeping it below anchor 5.

Actionability

Real commands and mechanisms are named (`npx convex run`, `npx convex import`, internalMutation, "clear-then-insert or upsert"), but the primary path lacks executable detail: no example internalMutation seed function, no exact `npx convex run <functionName>` invocation syntax, and "Verify row counts" specifies no method (dashboard, count query, or CLI). Missing key details on the main path fits anchor 3 rather than anchor 4's mostly-executable guidance.

Workflow Clarity

A clear 4-step sequence distinguishes both paths ("For fixtures: write an internalMutation...", "For bulk import: shape the data to the schema and use `npx convex import`") and ends with an explicit validation checkpoint ("Verify row counts") plus a safety mechanism ("clear-then-insert or upsert so re-running is safe"), matching anchor 4. Not 5: there is no failure-handling feedback loop (what to do if counts are wrong) and the verification method is unspecified.

Progressive Disclosure

The skill is under 50 lines, single-purpose, and well organized into a summary line, Workflow, and Rules sections with no external references needed or referenced — and no bundle files (references/, scripts/, assets/) exist. Per the guideline for simple skills under 50 lines, well-organized sections alone merit a 5.

Specificity

"Seed or import data into the Convex database" names the domain ("the Convex database") and exactly two actions ("Seed", "import data"), matching the anchor for domain plus 1-2 concrete actions that are not comprehensive. Not 4: it does not list several specific actions (no populate, backfill, or fixture loading); not 2: two named actions exceed 'minimal or generic'.

Completeness

The description answers 'what' clearly ("Seed or import data into the Convex database") but contains no 'when' or trigger guidance whatsoever, which caps completeness at 3 per the judging guideline. Not 4: the 'when' is not weakly implied or explicit — it is entirely absent.

Trigger Term Quality

"Seed", "import data", and "Convex" are phrases a user would naturally say when needing this skill, but common variations and synonyms are absent (populate, load data, fixtures, sample data, backfill, .csv/.jsonl). This fits 'some relevant keywords but missing common variations', below anchor 4's 'good keyword coverage'.

Distinctiveness Conflict Risk

"the Convex database" scopes the skill to a specific platform and the seed/import niche is fairly distinct, leaving only minor overlap risk with closely related skills (other Convex data skills, generic import tooling). Not 5: it lacks explicit distinct trigger phrases that would fully separate it from neighboring skills.