development-workflow

Orchestrates the complete Falcon Foundry app lifecycle from requirements through deployment. TRIGGER when user asks to "create a Foundry app", "build a Foundry app", "plan a Foundry app", runs any `foundry apps` CLI command, or discusses Foundry app architecture. DO NOT TRIGGER when user is working on a specific capability (UI, function, workflow, collection) within an existing app — use the appropriate sub-skill instead. This skill OWNS the entire Foundry development flow. Do not delegate Foundry app creation to superpowers:brainstorming or superpowers:writing-plans — those skills do not know about the Foundry CLI.

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

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

An exceptional orchestration skill: concrete, executable CLI guidance with explicit validation checkpoints and error-recovery loops, and a well-signaled reference layer. Its only real gaps are mild redundancy in the CRITICAL warnings, an unreferenced bundled script, and some inline detail that belongs in reference files.

Dimension	Reasoning	Score
Conciseness	Nearly every line encodes platform-specific knowledge Claude cannot already know (--no-prompt EOF behavior, cwd-relative path resolution, deploy-once, KBs-before-agents ordering). Falls short of 5 because the CRITICAL root-directory warning is repeated between the header block and Step 7, and the "Improving These Skills" section is meta-content that earns its tokens only weakly.	4 / 5
Actionability	Copy-paste-ready `foundry` CLI commands with exact flags throughout, a user-phrase-to-command mapping table, dependency-ordered capability creation, and concrete multi-cloud ID-stripping commands. Fully executable guidance covering the common cases.	5 / 5
Workflow Clarity	Steps 1-7 are explicitly sequenced with fail-fast validation ("VALIDATE EARLY... If validation fails, STOP"), a deploy-once/poll-status loop, and error-recovery feedback (read deploy errors in the console, validate fails during an in-progress deploy is not a manifest error). The destructive/batch cap does not apply since validation checkpoints are present.	5 / 5
Progressive Disclosure	The Reading Guide table clearly signals five one-level-deep references, all of which exist as real files in references/. Not 5 because scripts/detect_fusion_redirect.py ships in the bundle but is never referenced from the body, and the ~300-line body carries substantial inline detail (e.g., the full alerts-vs-Event-Query note) that an overview-style split would push into a reference.	4 / 5
	Total	18 / 20 Passed

Description

82%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, boundary-aware description: it states what the skill does, gives explicit trigger and anti-trigger phrases, and cleanly scopes itself against sub-skills. The main weakness is that the capability statement relies on the abstract verb "Orchestrates" rather than enumerating the concrete lifecycle actions.

Dimension	Reasoning	Score
Specificity	The description names the domain ("Falcon Foundry app lifecycle from requirements through deployment") with one orchestrating action, but "Orchestrates" is abstract and does not list the several concrete operations the 4/5 anchors show. It is well above the domain-only 2 anchor because the trigger phrases quote exact CLI commands and sub-skill boundaries.	3 / 5
Completeness	Explicitly answers what ("Orchestrates the complete Falcon Foundry app lifecycle from requirements through deployment") and when ("TRIGGER when user asks to 'create a Foundry app'...") with concrete trigger phrases, matching the top anchor. It even adds negative trigger guidance ("DO NOT TRIGGER when...").	5 / 5
Trigger Term Quality	Covers natural phrases users would say — "create a Foundry app", "build a Foundry app", "plan a Foundry app", "discusses Foundry app architecture" — with create/build/plan synonym variation. Not 5 because common variations like "deploy a Foundry app", "scaffold", or "new Foundry app" are absent.	4 / 5
Distinctiveness Conflict Risk	Clear niche (the Foundry app development flow) with explicit "DO NOT TRIGGER... use the appropriate sub-skill instead" boundaries and anti-delegation guidance against superpowers skills, giving minimal conflict risk with other skills.	5 / 5
	Total	17 / 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
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	13 / 16 Passed

Repository: CrowdStrike/foundry-skills
Path: skills/development-workflow/SKILL.md
Commit: 61572f3

Reviewed: 6 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.