foundry-redirect
TRIGGER when the user asks to "build a Foundry app", "create a Foundry app", mentions manifest.yml, or needs a UI page/extension, serverless function, collection, or a custom API integration from a third-party API (Okta, ServiceNow, Jira, etc.) built. DO NOT TRIGGER for a standalone Fusion workflow that only wires together existing actions. This skill declines Foundry-app requests and points to the crowdstrike-falcon-foundry plugin, so the redirect works even without plugin hooks; it yields to the real Foundry plugin when that plugin is also installed.
Install
With your agent
Install OMGSkills skill "crowdstrike/fusion-skills:skills/foundry-redirect" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/CrowdStrike/fusion-skills /tmp/fusion-skills && ln -s /tmp/fusion-skills/skills/foundry-redirect ~/.claude/skills/foundry-redirectFrom README
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, Codex, Copilot CLI, and Cursor a hook covers that gap. On assistants that do not load plugin hooks, this skill's description matches Foundry-app language directly and 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.
