Conciseness

The body assumes Claude's competence throughout — no basic concepts are explained — but it could be tightened: the check-vs-typecheck point is explained twice in §6 ("the sync half writes ~690 files into the directory the dev server watches" and later "which regenerates ~690 files under `.svelte-kit/`"), and dated war-story passages ("That collision froze a whole session's worth of work before it was diagnosed") pad rules that could stand alone. This fits the 3 anchor (mostly efficient, some unnecessary explanation); it is above 2 because nearly all content is non-obvious project-specific knowledge, and below 4 because the duplication and narrative padding are more than minor.

Actionability

The guidance is fully executable and copy-paste ready: `node .claude/skills/retool-migration/extract.mjs "<export.json>" --queries`, the `getModeratorDb()` Kysely snippet, the `NAVIGATION` TypeScript block, `pnpm --filter ./apps/moderator run typecheck`, and concrete grep/sed recipes for endpoint discovery. Specific examples cover the common cases, matching the 5 anchor.

Workflow Clarity

A clearly sequenced §0–§7 workflow with explicit validation gates for batch/destructive operations: the coverage gate ("Diff that against your classification. Anything unaccounted for is a gap, not a judgement call"), five named review passes, typecheck/check commands, and "Read the WARNING lines, not just ERROR". Feedback loops (fix findings, re-run reviews, re-validate) are present throughout, matching the 5 anchor.

Progressive Disclosure

External references are clearly signaled and one level deep (CLAUDE.md, retool-db-cutover.md, report-queue-pattern.md), but the SKILL.md itself is a ~435-line monolith with reference-type material inlined — cutover history ("Since 2026-08-21 it points at the moderator database"), attribution/backfill naming policy, and dated audit anecdotes — that belongs in reference files. Additionally, the helper files the instructions depend on (`extract.mjs`, `retool-db.mjs`, `CLICKUP-SCOPE.md`, `MIGRATIONS.md`) are not present in the evaluated bundle (no references/, scripts/, or assets/ directories exist). This fits the 3 anchor (some structure, content that should be separate is inline); it is above 2 because sections are well-organized and links are clearly signaled, and below 4 because the missing bundle files and inlined reference material are more than minor organization gaps.

Specificity

The description lists multiple concrete actions — "Port a Retool app's functionality", "Decodes the export, inventories its queries, and builds the page with shadcn + Tailwind under the Retool nav group" — with the tech stack and destination named explicitly. It matches the 5 anchor (multiple specific concrete actions, comprehensive coverage); the 4 anchor's "minor gaps in coverage" does not apply since decode, inventory, build, and nav registration are all stated.

Completeness

The 'when' is explicit with concrete trigger phrases — "Use when given a Retool JSON export (or asked to migrate/replace a Retool moderation tool)" — and the 'what' is answered concretely by the surrounding sentences. It clearly matches the 5 anchor; the 4 anchor ("'when' could be more explicit") is worse than what is written.

Trigger Term Quality

Natural trigger terms include "Retool JSON export", "migrate/replace a Retool moderation tool", and "Port", covering the synonyms a user would plausibly say along with the artifact type. This matches the 5 anchor's comprehensive coverage including synonyms; it is not the 4 anchor because no common variation of the request is missing.

Distinctiveness Conflict Risk

It occupies a clear niche (Retool exports into apps/moderator) with distinct triggers that no similar skill would share; the one adjacent skill (moderator-page-migration) is disambiguated by the 'Retool export' trigger itself. Minimal conflict risk, matching the 5 anchor.