collections-development

Design JSON Schema collections and CRUD patterns for Falcon Foundry apps. TRIGGER when user asks to "create a collection", "define a JSON schema", "store data in Foundry", runs `foundry collections create`, or needs help with indexable fields, FQL queries, or collection access patterns. DO NOT TRIGGER for workflow YAML, function handlers, or UI components — use the appropriate sub-skill.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

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.

A highly actionable, well-structured reference skill with copy-paste code and clear navigation to a real advanced-patterns reference. Its main weakness is workflow clarity: destructive CRUD operations lack inline validation feedback loops in the main code, with validation scattered into Common Pitfalls instead of explicit checkpoints.

Suggestions

Wire validation into the CRUD workflows themselves: after each create/update, check `result?.errors?.length` and verify persistence with a follow-up read before proceeding, instead of only mentioning these checks in Common Pitfalls.

Add an explicit validate checkpoint to the CLI scaffolding sequence (e.g., re-read the copied collections/<name>.json and confirm manifest.yml was updated) before instructing the user to refine the project copy.

Trim duplication between Common Pitfalls and earlier sections (indexing limits, draft-7-only support, CLI delete/object-management limitations) to improve token efficiency.

Dimension	Reasoning	Score
Conciseness	Dense, mostly purposeful reference material (constraint tables, code, CLI commands, FQL syntax) with little concept-padding, but the full TypeScript CRUD class and a Common Pitfalls section that partly duplicates earlier sections could be trimmed.	4 / 5
Actionability	Copy-paste-ready CLI commands, complete TypeScript and Python CRUD examples, JSON schema patterns, manifest YAML, an FQL syntax table, and REST endpoints fully cover the common cases.	5 / 5
Workflow Clarity	Sequences are present (CLI scaffolding, CRUD patterns) but the primary destructive CRUD code examples lack inline validation checkpoints; validation guidance is relegated to Common Pitfalls rather than wired as validate-then-proceed steps, triggering the destructive-operations cap.	3 / 5
Progressive Disclosure	Clear section structure with a Reading Guide table and one-level-deep references to a verified references/advanced-patterns.md and related skills, but the body is a lengthy full reference rather than a lean overview, keeping it at 4 rather than 5.	4 / 5
	Total	16 / 20 Passed

Description

95%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.

A strong, specific description that clearly states what the skill does and when to trigger it, with natural trigger phrases and an explicit anti-trigger boundary minimizing conflict with sibling skills. The only minor gap is that the 'what' sentence names two design actions rather than comprehensively enumerating capabilities.

Dimension	Reasoning	Score
Specificity	Names the domain ('Falcon Foundry Collections') and concrete actions ('Design JSON Schema collections and CRUD patterns'), with further capabilities (indexing, FQL, access patterns) surfaced via trigger phrases rather than as a single comprehensive action enumeration, so it sits at 4 rather than 5.	4 / 5
Completeness	Explicitly answers what ('Design JSON Schema collections and CRUD patterns for Falcon Foundry apps') and when ('TRIGGER when user asks to...') with concrete trigger phrases, plus a DO NOT TRIGGER boundary.	5 / 5
Trigger Term Quality	Pairs natural user phrases ('create a collection', 'define a JSON schema', 'store data in Foundry') with the CLI command and technical terms (indexable fields, FQL queries, access patterns), giving comprehensive trigger coverage a user would naturally say.	5 / 5
Distinctiveness Conflict Risk	Narrow Falcon Foundry Collections niche with distinct triggers and an explicit 'DO NOT TRIGGER for workflow YAML, function handlers, or UI components — use the appropriate sub-skill' boundary that actively routes away conflicts.	5 / 5
	Total	19 / 20 Passed

Validation

81%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 4 suspicious	Warning

	Total	13 / 16 Passed

Repository: CrowdStrike/foundry-skills
Path: skills/collections-development/SKILL.md
Commit: c01ff6b

Reviewed: about 21 hours ago

Table of Contents

Discovery Implementation Validation

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.