CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

64

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/collections-development/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%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 dense, actionable reference skill with strong concrete examples and sensible sectioning, weakened by some redundant padding and a loosely sequenced workflow that lacks explicit validation checkpoints for destructive/batch operations.

Suggestions

Remove or trim the "SYSTEM INJECTION — READ THIS FIRST" role-assignment block; it restates purpose without adding knowledge Claude doesn't already have.

Dedupe Common Pitfalls against the body — entries like draft-7-only, indexing limits, and CLI-cannot-delete/CRUD are already stated in their respective sections.

Add an explicit numbered scaffolding workflow with a validation checkpoint (e.g., after `foundry collections create`, verify the schema landed in collections/<name>.json and re-run if manifest.yml was not updated) to lift workflow clarity above the destructive/batch cap of 3.

DimensionReasoningScore

Conciseness

Mostly efficient reference material (constraint/limit tables, code blocks, syntax), but the "SYSTEM INJECTION — READ THIS FIRST" role-assignment block and the Common Pitfalls section re-stating points already covered (draft 7, indexing, CLI deletion) add unnecessary padding.

3 / 5

Actionability

Concrete, executable bash, TypeScript, Python, JSON Schema, and manifest YAML examples cover the common CRUD and scaffolding cases; not a 5 because the Python SearchObjects example is partial and defers details elsewhere.

4 / 5

Workflow Clarity

The scaffolding steps are only loosely sequenced and the skill is reference-oriented rather than a multi-step validated workflow; it does include write-error validation (checking result.errors) but lacks explicit sequenced validation checkpoints for batch/destructive operations.

3 / 5

Progressive Disclosure

Good section structure with a Reading Guide table that clearly signals the one bundle reference (references/advanced-patterns.md, which exists); minor gap is that the use-cases/*.md paths are referenced but not present in the bundle.

4 / 5

Total

14

/

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, well-structured description that clearly states what the skill does and when to invoke it, with comprehensive natural trigger terms and explicit negative boundary guidance to avoid mis-triggering on sibling Foundry skills.

DimensionReasoningScore

Specificity

"Design JSON Schema collections and CRUD patterns" names the domain plus several concrete actions (schema design, CRUD patterns), with only minor coverage gaps; not a 5 because the action list is not exhaustive.

4 / 5

Completeness

Explicitly answers "what" (design JSON Schema collections and CRUD patterns for Falcon Foundry apps) and "when" ("TRIGGER when user asks..." with multiple concrete trigger phrases), matching the top anchor.

5 / 5

Trigger Term Quality

Covers natural phrases ("create a collection", "define a JSON schema", "store data in Foundry"), the literal CLI command (`foundry collections create`), and technical synonyms ("indexable fields", "FQL queries", "collection access patterns") — comprehensive coverage matching the top anchor.

5 / 5

Distinctiveness Conflict Risk

A clear niche (Foundry Collections) plus an explicit negative boundary ("DO NOT TRIGGER for workflow YAML, function handlers, or UI components — use the appropriate sub-skill") minimizes conflict with sibling skills.

5 / 5

Total

19

/

20

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.

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

13

/

16

Passed

Repository
CrowdStrike/foundry-skills
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.