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.
69
86%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
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.
This is an excellent skill description that hits all the marks. It provides specific capabilities, comprehensive trigger terms including both natural language and CLI commands, explicit when-to-use guidance, and a DO NOT TRIGGER clause that actively prevents skill conflicts. The description is concise yet thorough.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: designing JSON Schema collections, CRUD patterns, indexable fields, FQL queries, and collection access patterns. Also specifies the platform context (Falcon Foundry apps). | 3 / 3 |
Completeness | Clearly answers both 'what' (design JSON Schema collections and CRUD patterns for Falcon Foundry apps) and 'when' (explicit TRIGGER clause with multiple specific scenarios). Also includes a DO NOT TRIGGER clause to reduce false positives. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms: 'create a collection', 'define a JSON schema', 'store data in Foundry', 'foundry collections create', 'indexable fields', 'FQL queries', 'collection access patterns'. These are terms users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche (Falcon Foundry collections/JSON Schema). The explicit DO NOT TRIGGER clause for workflow YAML, function handlers, and UI components actively prevents conflicts with sibling skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, comprehensive skill for Foundry Collections development with excellent actionability — complete code examples in both TypeScript and Python, concrete CLI commands, and well-formatted reference tables. The main weaknesses are some redundancy (pitfalls repeating earlier content) and the lack of explicit validation/error-recovery workflows for schema creation and data operations. Overall it serves as an effective reference document.
Suggestions
Add a validation workflow for schema creation: write schema → validate against draft-07 → run CLI create → verify collection exists, with error recovery steps if validation fails.
Remove redundant information in Common Pitfalls that restates constraints already covered in earlier sections (e.g., naming rules, draft-07 requirement, max 10 indexes) to improve conciseness.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with good use of tables and code blocks, but it's quite long (~250 lines) and includes some explanatory text that Claude wouldn't need (e.g., explaining what NoSQL document stores are, explaining what upsert means). The Common Pitfalls section repeats information already stated earlier in the document. | 2 / 3 |
Actionability | Excellent actionability with fully executable CLI commands, complete TypeScript and Python code examples for CRUD operations, concrete JSON Schema examples, specific API endpoints, and FQL query syntax with examples. Everything is copy-paste ready. | 3 / 3 |
Workflow Clarity | The CLI scaffolding section provides a clear sequence (write schema to /tmp, run create command, edit project copy), but there are no validation checkpoints or error recovery steps. For schema creation and CRUD operations that could fail (schema validation errors, naming constraint violations), there's no validate-then-proceed workflow. | 2 / 3 |
Progressive Disclosure | Well-structured with clear sections, a Reading Guide table pointing to advanced-patterns.md for migrations/testing/pagination, use case references, and a reference implementation link. Content is appropriately split with one-level-deep references that are clearly signaled. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 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 |
Total | 9 / 11 Passed | |
- Repository
- CrowdStrike/foundry-skills
- Commit
631c815
- Reviewed
Table of Contents
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.