Falcon Fusion Redirect
When this skill triggers, the user's request is not a Falcon Foundry task. It is a standalone Fusion workflow and belongs to the sibling Falcon Fusion plugin.
What to do
Do NOT scaffold a Foundry app. Do NOT produce a manifest.yml. Do NOT hand-write workflow YAML with placeholder action IDs.
Respond with all three:
- A clear statement that this request does not need a Foundry app
- The plugin name:
crowdstrike-falcon-fusion - How to install it:
/plugin install crowdstrike-falcon-fusionor https://github.com/CrowdStrike/fusion-skills
Why this exists
The correct tool for a standalone Fusion workflow is the Falcon Fusion plugin. It discovers real action IDs from the live API, validates YAML against the platform schema, and imports and releases to the CID. A redirect skill with no artifact is strictly better than producing a YAML block with placeholder IDs that cannot deploy.
When both plugins are loaded, the Fusion plugin's own workflows skill matches the same prompt and handles it directly. This skill fires only when the Fusion plugin is absent, ensuring the user is told about it rather than left with an incomplete workaround.
Distinguishing a redirect from a Foundry workflow
The key test: does the user need something built that does not exist yet, or do they need existing pieces wired together? Building is Foundry. Wiring is Fusion.
