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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable and densely packed with Foundry-specific, executable material, with a properly offloaded reference file. Its weaknesses are repetition across sections and a reference-manual structure where validation guidance is scattered rather than sequenced.

Suggestions

Deduplicate the indexable-fields guidance (currently in JSON Schema Requirements, Indexable Fields, FQL Search, and Common Pitfalls) into a single authoritative section to tighten conciseness.

Fold the write-validation checkpoints (check `result?.errors?.length`, verify with a follow-up read) into a numbered CRUD/write workflow so the feedback loop is explicit rather than buried in Common Pitfalls.

Move the full TypeScript/Python CRUD class listings and the API endpoint reference into references/advanced-patterns.md, keeping SKILL.md as a concise overview with one-level-deep pointers.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and Foundry-specific, but several facts are restated across sections — `x-cs-indexable` explained in four places, the draft-7-only and CLI-cannot-delete limits each repeated — so not every token earns its place.	2 / 3
Actionability	Provides copy-paste-ready CLI commands, full draft-7 JSON schemas, TypeScript and Python CRUD classes, concrete API endpoints, and an FQL syntax table — fully executable guidance.	3 / 3
Workflow Clarity	The CLI scaffolding has a short inline sequence and write-validation is called out, but validation checkpoints live scattered in "Common Pitfalls" rather than integrated into a single clearly sequenced workflow, leaving the feedback loop implicit.	2 / 3
Progressive Disclosure	There is a real one-level reference (references/advanced-patterns.md) signaled via a Reading Guide table, but ~330 lines of inline API/code reference (two-language CRUD, schemas, endpoints, FQL syntax) could be split out for a leaner overview.	2 / 3
	Total	9 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong: concrete capabilities, natural trigger phrases, an explicit when-to-use clause, and a clear negative-trigger boundary against sibling skills. It uses third-person imperative voice with no first/second-person padding.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "Design JSON Schema collections and CRUD patterns", "define a JSON schema", "indexable fields, FQL queries, or collection access patterns" — rather than vague language.	3 / 3
Completeness	Explicitly answers what ("Design JSON Schema collections and CRUD patterns for Falcon Foundry apps") and when ("TRIGGER when user asks to...") with an explicit trigger clause, so it is not capped at 2.	3 / 3
Trigger Term Quality	Natural phrases a user would say ("create a collection", "store data in Foundry") plus the literal CLI command `foundry collections create` and domain terms (FQL, indexable fields) give broad coverage.	3 / 3
Distinctiveness Conflict Risk	Narrow Falcon Foundry Collections niche with a "DO NOT TRIGGER for workflow YAML, function handlers, or UI components" exclusion makes collision with adjacent sub-skills unlikely.	3 / 3
	Total	12 / 12 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: 3 suspicious	Warning

	Total	13 / 16 Passed

Repository: CrowdStrike/foundry-skills
Commit: 2f0ce35

Reviewed: about 22 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.