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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

85%

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-sequenced lifecycle skill with strong validation checkpoints and clean one-level-deep reference navigation. Its main weakness is repetition — several critical warnings are stated multiple times and the opening injection block is verbose.

Suggestions

Consolidate the repeated `--no-prompt`/`Error: EOF` guidance and the 'run foundry commands from the app root / cd back' rule into one stated-once section; reference it instead of restating in Step 4, Step 5, Step 7, and the top injection block.

Trim the all-caps 'SYSTEM INJECTION — READ THIS FIRST' block; fold its non-delegation rule into the existing Decision Tree or a single concise note, since the description already carries the trigger/non-trigger scoping.

Move the multi-cloud ID-stripping and e2e local-test recipes (which are situational) into a reference file, keeping SKILL.md focused on the core creation flow.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and full of domain-specific CLI detail Claude would not know, but it repeats several warnings (the `--no-prompt`/`Error: EOF` note and the 'cd back to app root' rule each appear multiple times) and opens with a verbose, all-caps 'SYSTEM INJECTION' block that could be tightened.	2 / 3
Actionability	Provides fully executable, copy-paste-ready commands throughout — `foundry apps create --name ... --no-prompt --no-git`, the capability scaffolding sequence, `yq` ID-stripping, and `npm install && npm run build` — with concrete flags and paths.	3 / 3
Workflow Clarity	The App Creation Flow is a clearly sequenced Steps 1–7 with an explicit validation checkpoint ('VALIDATE EARLY — fail fast if specs or schemas are bad', 'If validation fails, STOP. Fix the spec/schema') and feedback loops, matching the strong anchor.	3 / 3
Progressive Disclosure	The body is an overview with a 'Reading Guide' table signaling five one-level-deep references (headless-operation, superpowers-integration, performance-optimization, counter-rationalizations, advanced-patterns), all of which exist as real files in references/.	3 / 3
	Total	11 / 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.

A strong, third-person description that states concrete capabilities, gives natural trigger phrases, and explicitly bounds when not to fire. It is distinctive and unlikely to conflict with sibling skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Orchestrates the complete Falcon Foundry app lifecycle from requirements through deployment', create/build/plan a Foundry app, and running `foundry apps` CLI commands — rather than vague language.	3 / 3
Completeness	Explicitly answers what ('Orchestrates the complete Falcon Foundry app lifecycle from requirements through deployment') and when ('TRIGGER when user asks to...'), plus a 'DO NOT TRIGGER' clause for boundary cases.	3 / 3
Trigger Term Quality	Includes natural phrases users would say — 'create a Foundry app', 'build a Foundry app', 'plan a Foundry app', 'runs any `foundry apps` CLI command', 'discusses Foundry app architecture' — with good coverage of variations.	3 / 3
Distinctiveness Conflict Risk	Clear Foundry-app-lifecycle niche with explicit 'DO NOT TRIGGER' scoping for sub-capabilities and an explicit non-delegation note for superpowers skills, making wrong-skill conflicts unlikely.	3 / 3
	Total	12 / 12 Passed

Validation

87%

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 — 14 / 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

	Total	14 / 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.