Codepit The toolbox

Build Falcon Foundry apps from a prompt

Describe the app and Claude builds it with the Foundry CLI: API integrations, workflows, UI pages, functions, collections and AI agents, deployed to your Falcon console.

Scan in Codepit View source

Scan checks all of CrowdStrike/foundry-skills on your computer, before anything installs.

Codepit runs on your computer. Open this page there to scan it before installing.

An open manual with a honey ribbon

How it works

Confirm

Claude maps your request to Foundry capabilities and confirms the app name with you before creating anything.

Scaffold

It creates the app and each capability with Foundry CLI commands, never by hand-writing the manifest.

Fill in

Sub-skills write what the CLI can't: OpenAPI specs, workflow YAML, UI code and function handlers.

Deploy

It builds the UI, then deploys and releases the app in one step.

What you get

Fourteen skills, led by development-workflow, which runs the whole build and hands each part to the right sub-skill.

  • development-workflow
  • api-integrations
  • workflows-development
  • ui-development
  • functions-development
  • functions-falcon-api
  • collections-development
  • ai-agents-development
  • security-patterns
  • debugging-workflows
  • e2e-testing
  • app-upgrades
  • app-audit
  • fusion-redirect

Before you start

  • A CrowdStrike account with Falcon Foundry access.
  • The Foundry CLI, signed in with foundry login. On macOS or Linux: brew tap crowdstrike/foundry-cli && brew install crowdstrike/foundry-cli/foundry. A session-start hook warns you if your CLI is older than 2.1.0.

Try saying

>Create a Falcon Foundry app with an API integration for our identity provider and a UI extension that lists its users

Claude confirms the app name, scaffolds it with the Foundry CLI, writes the API spec and UI code, then deploys and releases it to your Falcon console.

Worth knowing

The plugin's hooks look at your prompts and tool calls to spot Foundry work and remind Claude to use the right skill. The repo says no data leaves the session. They only advise, except that they block foundry api-integrations create when the OpenAPI spec can't be adapted for Foundry.

Swagger 2.0 specs are converted to OpenAPI 3.0 with npx swagger2openapi, which needs Node.js and makes a network call to the npm registry.

Deploys and releases go to your live Falcon tenant.

Read the author's README README.md