Falcon Foundry Redirect
If this skill triggered, the request is a Falcon Foundry app, not a standalone
Falcon Fusion workflow. It belongs to the sibling Falcon Foundry plugin — the
fusion-skills plugin builds Fusion workflows only.
Why this skill exists: the workflows orchestrator declines Foundry-app requests too,
but its description matches Fusion workflow language, so a "build a Foundry app"
prompt never loads it. On Claude Code a hook covers that gap; on Codex, Copilot CLI,
Cursor, and the Agent SDK there are no hooks, so this skill — whose description matches
Foundry-app language directly — is what makes the redirect reachable.
What to do
Do NOT author workflow YAML. Do NOT scaffold an app yourself. Respond with all three:
- State plainly that this request needs a Falcon Foundry app, not a standalone Fusion workflow.
- Name the plugin:
crowdstrike-falcon-foundry. - How to install it:
/plugin install crowdstrike-falcon-foundry, or clone https://github.com/CrowdStrike/foundry-skills.
When both plugins are installed
If crowdstrike-falcon-foundry is present, its own development-workflow skill matches
Foundry-app requests directly and handles them — a stronger match than this one, so the
agent picks it and this redirect never fires. That is correct: this skill is the safety
net for when the Foundry plugin is absent, not a competitor with it when present.