Conciseness

Nearly all content is earned, non-generic platform knowledge (limits tables, draft-7-only rule, upsert semantics, paging-by-start-key) with no tutorials on concepts Claude already knows, but there is duplication: collection name/description constraints and the workflow_integration YAML each appear in both a dedicated section and Common Pitfalls, and the 60-line TypeScript IncidentCollection class could be trimmed. Fits anchor 4 (efficient with minor trimming possible) rather than 5 or 3.

Actionability

Copy-paste-ready throughout: complete `foundry collections create` commands with flags, exact REST endpoints, two full valid JSON schemas, working TypeScript and falconpy Python snippets, an FQL syntax table, and manifest YAML blocks. Covers the common cases and includes error-path specifics (404 vs 429, result.errors messages); matches the anchor-5 example.

Workflow Clarity

Validation checkpoints exist — "Check the description against this table before running `collections create`", "Always check `result?.errors?.length` after write operations", "Verify persistence with a follow-up read or list call" — so the destructive/batch cap of 3 does not apply. However, there is no explicit end-to-end sequence (create → wire manifest → implement access → verify); the steps and checkpoints are scattered across reference sections rather than ordered, fitting anchor 4 rather than 5.

Progressive Disclosure

Section organization is good and the Reading Guide table clearly signals `references/advanced-patterns.md` (verified present, one level deep), but the body also points to `use-cases/collections.md` and `use-cases/lookup-table-enrichment.md` which do not exist in the bundle — broken navigation paths. Combined with substantial content inlined in SKILL.md (~390 lines including a full CRUD class that belongs in a reference), this sits between anchors 3 and 4, and the dead references are more than a minor gap.

Specificity

"Design JSON Schema collections and CRUD patterns" plus trigger-side enumeration of "indexable fields, FQL queries, or collection access patterns" names several concrete actions in a well-defined domain, but the what-clause itself covers only two, leaving minor gaps (e.g., API/SDK object access, agent-tool exposure are absent). Fits anchor 4 rather than 5 because the capability list is not comprehensive, and above 3 because more than 1-2 specific actions are stated.

Completeness

Explicitly answers both questions: "what" in the opening sentence and "when" via "TRIGGER when user asks to ... or needs help with ..." with concrete trigger phrases, plus a negative boundary. Matches the anchor-5 example structure exactly; a missing or weak trigger clause would cap it at 3, which is not the case.

Trigger Term Quality

Covers natural user phrasings ("create a collection", "define a JSON schema", "store data in Foundry"), the exact CLI invocation `foundry collections create`, and domain terms (FQL queries, indexable fields), so keyword coverage is comprehensive with synonyms and the verbatim command. Not 4: no clearly missing natural term for this domain — the phrases map directly onto how a user would express the need.

Distinctiveness Conflict Risk

The niche is narrow (Falcon Foundry collections) and the "DO NOT TRIGGER for workflow YAML, function handlers, or UI components — use the appropriate sub-skill" clause explicitly disambiguates against the sibling skills most likely to collide. Minimal conflict risk; anchor 5 fits.