Conciseness

The body is lean and assumes Claude's competence — no concept explanations, no restated Postgres knowledge, every bullet is a directive. It misses 5 because the 'When to trigger' section substantially duplicates the frontmatter description's trigger list, and 'Keep the skill focused on orchestration and verification, not duplicating the full runbook' is maintainer-facing rather than agent guidance — minor tokens that could be trimmed. It is above 3 because there is no unnecessary explanation, only these small redundancies.

Actionability

Guidance is concrete in its delegation — it names the exact canonical scope (proxy setup, URL rewriting, pg_dump/pg_restore, extension precreation, restore verification) and the specific file 'docker-compose.restore-test.yaml' with a clear precondition for its use. But the body contains no executable commands at all, and its sole source of executable steps is a reference outside the bundle at '../../../docs/recipes/fly-mpg-backup-restore.md', a relative path that does not resolve from the skill's directory. It is above 2 (more than high-level hints — precise file names and scope rules) but below 4 (nothing in the body is directly executable, and the primary pointer is fragile).

Workflow Clarity

The 'Treat the recipe as canonical for' bullet implies a real phase sequence (proxy setup → URL rewriting → pg_dump/pg_restore → extension precreation → restore verification → restored-db app startup), and 'Use docker-compose.restore-test.yaml only after the recipe has created the restored database container' gives one explicit ordering constraint. However, the body provides no explicit validation checkpoints or error-recovery loops of its own, and the rubric caps workflow clarity at 3 for destructive/batch database operations without validation steps in the skill itself. It is above 2 because an ordered phase list plus one sequencing rule is present, but the cap and the fully deferred verification keep it from 4.

Progressive Disclosure

Sections are well organized, and the single reference is one level deep and clearly signaled ('Use the human-facing recipe as the source of truth for the exact commands and restore procedure'). However, there are no bundle files at all — no references/, scripts/, or assets/ — and the one detailed material the skill depends on lives outside the skill bundle at a relative path ('../../../docs/recipes/fly-mpg-backup-restore.md') that does not resolve from the skill's location, making navigation fragile and the skill non-self-contained. This is more than a minor organization gap (ruling out 4) but the reference is clearly signaled and nothing inlined belongs elsewhere (ruling out 2).

Specificity

The description names several concrete operations — 'Fly Managed Postgres backups', 'Fly MPG proxy access', 'pg_dump or pg_restore from a proxied production database', 'testing app/backfill behavior on a restored local copy of prod' — which are specific tools and actions, not vague abstractions. It falls short of 5 because everything is framed as trigger conditions rather than an explicit statement of what the skill does, leaving minor gaps in capability coverage.

Completeness

The 'when' is explicit and strong ('Use when working with... or when testing app/backfill behavior on a restored local copy of prod'), and the enumerated trigger operations convey the 'what' — backing up, restoring, dumping/restoring via the proxy — reasonably concretely. It sits between anchor 4 and 5: the when has concrete trigger phrases, but the what is only carried implicitly inside the when-clauses with no standalone capability statement, which keeps it below 5. It is above 3 because both what and when are effectively communicated, not just one.

Trigger Term Quality

Natural user phrasing is well covered: 'backups', 'pg_dump', 'pg_restore', 'restore', 'backfill', 'restored local copy of prod', 'proxy', plus both the full name 'Fly Managed Postgres' and the abbreviation 'Fly MPG'. A few natural variations are missing (e.g. 'database dump', 'restore production data locally', 'snapshot'), so it is good but not comprehensive enough for 5, and clearly above the partial-coverage anchor at 3.

Distinctiveness Conflict Risk

This is a clear niche — Fly.io Managed Postgres backup/restore through the MPG proxy — with distinct triggers (MPG, proxied production database, restored local copy of prod) that virtually no other skill would claim. Conflict risk is minimal, matching the top anchor.