← CrowdStrike Falcon FoundryCONTENT HISTORY

Update to CrowdStrike Falcon Foundry

Snapshot Nov 12, 2026 · 18:46 UTC · version 1.7.1

Collection source: downloaded plugin package.

WHAT CHANGED

Instructions updated for app-audit

Skill instructions — Now says: version: 1.7.1 updated: 2026-11-10

Observed in instructions or declared skills. Runtime behavior has not been tested.

Save CrowdStrike Falcon Foundry and check future changes in Following.

Up to 3 plugins free · no card required.

All fields and original values.

Skill instructions

Before

Nov 4, 2026 · 12:08 UTC

version: 1.7.0 updated: 2026-10-30

After

Nov 12, 2026 · 18:46 UTC

version: 1.7.1 updated: 2026-11-10

Compare saved observations

Download comparison JSON

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -1,8 +1,8 @@
 ---
 name: app-audit
 description: Audit an existing Falcon Foundry app for documented anti-patterns and fix the safe ones, like npm audit. TRIGGER when user asks to "audit my Foundry app", "check my app for problems", "review this Foundry app", "scan for anti-patterns", "why might this deploy fail", or runs `audit_app.py`. DO NOT TRIGGER for creating a new app (use development-workflow) or for debugging an error the user already has (use debugging-workflows).
-version: 1.7.0
-updated: 2026-10-30
+version: 1.7.1
+updated: 2026-11-10
 tags: [foundry, audit, lint, best-practices]
 author: CrowdStrike
 license: MIT
Full technical diff · 1 changed fields

changed /skill_md_contents

BEFORE
"---\nname: app-audit\ndescription: Audit an existing Falcon Foundry app for documented anti-patterns and fix the safe ones, like npm audit. TRIGGER when user asks to \"audit my Foundry app\", \"check my app for problems\", \"review this Foundry app\", \"scan for anti-patterns\", \"why might this deploy fail\", or runs `audit_app.py`. DO NOT TRIGGER for creating a new app (use development-workflow) or for debugging an error the user already has (use debugging-workflows).\nversion: 1.7.0\nupdated: 2026-10-30\ntags: [foundry, audit, lint, best-practices]\nauthor: CrowdStrike\nlicense: MIT\ncompatibility: Claude Code >=1.0\nmetadata:\n  category: quality\n---\n\n# Auditing a Foundry App\n\nRun the bundled script against the app directory (the one with `manifest.yml`). It reads the manifest and the files it points to, calls no API, and needs only `pyyaml`:\n\n```bash\npython3 skills/app-audit/scripts/audit_app.py path/to/app          # report\npython3 skills/app-audit/scripts/audit_app.py path/to/app --json   # machine-readable\npython3 skills/app-audit/scripts/audit_app.py path/to/app --fix    # apply the safe fixes, then report\n```\n\nIt exits `1` when an error-level finding remains. Each finding names the skill and section that explains it; read that section before changing anything.\n\n## What It Checks\n\n| Check | Severity | Why |\n|-------|----------|-----|\n| `function-count` | warn | More than 20 functions. Each is a separate container build, and a fresh install with 43 failed where the same handlers in 11 functions deployed. |\n| `handler-name-length` | error | Handler names must be 5 to 64 characters (the CLI's own limits). |\n| `handler-name-duplicate` | error | Handler names must be unique within a function. |\n| `request-property-undeclared` | error | A workflow passes a property the function's `request_schema` doesn't declare, so it's silently dropped. |\n| `response-key-missing` | warn | A workflow reads a `FaaS` output key the handler's `response_schema` doesn't declare. |\n| `unknown-function-action` | error | A workflow calls `functions.<name>.<handler>` that isn't in the manifest. |\n| `missing-workflow-integration` | error | A workflow calls a handler that has no `workflow_integration`, so deploy fails. |\n| `provision-on-install-missing` | warn, fixable | Installing won't create the workflow. Leave it off only when the app provisions the workflow itself through the Workflows API, as rapid-response and scalable-rtr do. |\n| `provision-on-install-false` | info | Fine when deliberate. |\n| `pycache-not-ignored` | warn, fixable | A local `__pycache__/` would deploy. The CLI already skips hidden paths like `.venv/`. |\n| `secret-in-env` | warn | A function reads a key, token, secret, or password from an environment variable, which is visible in app exports. |\n| `server-url-protocol` | error | An OpenAPI server URL with variables starts with `https://` or `http://`, so the protocol doubles. |\n| `server-variable-default` | warn | A server variable has a `default` but no `enum`, which renders as a one-value dropdown. |\n| `ui-not-built` | error | A page or extension has no `dist/`; deploy never builds the UI. |\n| `ui-stale-build` | warn | `src/` is newer than `dist/`, so deploy would ship the previous build. |\n| `invalid-file` | error | `manifest.yml`, a workflow, or an API spec it points to doesn't parse, so the checks that read it were skipped. |\n\n## Fixing Findings\n\n`--fix` applies only the fixes marked fixable: it adds the `__pycache__` pattern to `ignored:` and `provision_on_install: true` to workflows that lack it. Both are single-line insertions that leave the rest of the file as written. Tell the user what `--fix` will change before running it, and show the diff afterward.\n\nEverything else needs judgment, so handle it with the user:\n\n- **Undeclared request properties:** add each property to the handler's `request_schema.json`, then redeploy. If the handler has no schema, the function needs one bound at create time (see the `functions-development` skill → Function I/O Schemas).\n- **Missing response keys:** add the key to `response_schema.json`, or fix the workflow's data path if the key is misspelled.\n- **Too many functions:** follow the `functions-development` skill's `references/function-count-and-build-time.md`; consolidating changes workflow wiring and needs its checklist.\n- **Server URLs and defaults:** run the `api-integrations` skill's spec adapter on the spec rather than editing it by hand.\n- **UI builds:** run `npm run build` in each page or extension directory, then return to the app root.\n\nRun the audit again after fixing, and run `foundry apps validate --no-prompt` before deploying. The audit complements validation and doesn't replace it.\n\n## Reading Results\n\nThe checks are static, so treat a finding as a strong lead, not proof. A warning can be deliberate (a large app may need many functions, and an app that provisions its own workflows skips `provision_on_install`). If a finding looks wrong for the app in front of you, say why instead of forcing a fix.\n"
AFTER
"---\nname: app-audit\ndescription: Audit an existing Falcon Foundry app for documented anti-patterns and fix the safe ones, like npm audit. TRIGGER when user asks to \"audit my Foundry app\", \"check my app for problems\", \"review this Foundry app\", \"scan for anti-patterns\", \"why might this deploy fail\", or runs `audit_app.py`. DO NOT TRIGGER for creating a new app (use development-workflow) or for debugging an error the user already has (use debugging-workflows).\nversion: 1.7.1\nupdated: 2026-11-10\ntags: [foundry, audit, lint, best-practices]\nauthor: CrowdStrike\nlicense: MIT\ncompatibility: Claude Code >=1.0\nmetadata:\n  category: quality\n---\n\n# Auditing a Foundry App\n\nRun the bundled script against the app directory (the one with `manifest.yml`). It reads the manifest and the files it points to, calls no API, and needs only `pyyaml`:\n\n```bash\npython3 skills/app-audit/scripts/audit_app.py path/to/app          # report\npython3 skills/app-audit/scripts/audit_app.py path/to/app --json   # machine-readable\npython3 skills/app-audit/scripts/audit_app.py path/to/app --fix    # apply the safe fixes, then report\n```\n\nIt exits `1` when an error-level finding remains. Each finding names the skill and section that explains it; read that section before changing anything.\n\n## What It Checks\n\n| Check | Severity | Why |\n|-------|----------|-----|\n| `function-count` | warn | More than 20 functions. Each is a separate container build, and a fresh install with 43 failed where the same handlers in 11 functions deployed. |\n| `handler-name-length` | error | Handler names must be 5 to 64 characters (the CLI's own limits). |\n| `handler-name-duplicate` | error | Handler names must be unique within a function. |\n| `request-property-undeclared` | error | A workflow passes a property the function's `request_schema` doesn't declare, so it's silently dropped. |\n| `response-key-missing` | warn | A workflow reads a `FaaS` output key the handler's `response_schema` doesn't declare. |\n| `unknown-function-action` | error | A workflow calls `functions.<name>.<handler>` that isn't in the manifest. |\n| `missing-workflow-integration` | error | A workflow calls a handler that has no `workflow_integration`, so deploy fails. |\n| `provision-on-install-missing` | warn, fixable | Installing won't create the workflow. Leave it off only when the app provisions the workflow itself through the Workflows API, as rapid-response and scalable-rtr do. |\n| `provision-on-install-false` | info | Fine when deliberate. |\n| `pycache-not-ignored` | warn, fixable | A local `__pycache__/` would deploy. The CLI already skips hidden paths like `.venv/`. |\n| `secret-in-env` | warn | A function reads a key, token, secret, or password from an environment variable, which is visible in app exports. |\n| `server-url-protocol` | error | An OpenAPI server URL with variables starts with `https://` or `http://`, so the protocol doubles. |\n| `server-variable-default` | warn | A server variable has a `default` but no `enum`, which renders as a one-value dropdown. |\n| `ui-not-built` | error | A page or extension has no `dist/`; deploy never builds the UI. |\n| `ui-stale-build` | warn | `src/` is newer than `dist/`, so deploy would ship the previous build. |\n| `invalid-file` | error | `manifest.yml`, a workflow, or an API spec it points to doesn't parse, so the checks that read it were skipped. |\n\n## Fixing Findings\n\n`--fix` applies only the fixes marked fixable: it adds the `__pycache__` pattern to `ignored:` and `provision_on_install: true` to workflows that lack it. Both are single-line insertions that leave the rest of the file as written. Tell the user what `--fix` will change before running it, and show the diff afterward.\n\nEverything else needs judgment, so handle it with the user:\n\n- **Undeclared request properties:** add each property to the handler's `request_schema.json`, then redeploy. If the handler has no schema, the function needs one bound at create time (see the `functions-development` skill → Function I/O Schemas).\n- **Missing response keys:** add the key to `response_schema.json`, or fix the workflow's data path if the key is misspelled.\n- **Too many functions:** follow the `functions-development` skill's `references/function-count-and-build-time.md`; consolidating changes workflow wiring and needs its checklist.\n- **Server URLs and defaults:** run the `api-integrations` skill's spec adapter on the spec rather than editing it by hand.\n- **UI builds:** run `npm run build` in each page or extension directory, then return to the app root.\n\nRun the audit again after fixing, and run `foundry apps validate --no-prompt` before deploying. The audit complements validation and doesn't replace it.\n\n## Reading Results\n\nThe checks are static, so treat a finding as a strong lead, not proof. A warning can be deliberate (a large app may need many functions, and an app that provisions its own workflows skips `provision_on_install`). If a finding looks wrong for the app in front of you, say why instead of forcing a fix.\n"
Full snapshot data
{
  "description": "Audit an existing Falcon Foundry app for documented anti-patterns and fix the safe ones, like npm audit. TRIGGER when user asks to \"audit my Foundry app\", \"check my app for problems\", \"review this Foundry app\", \"scan for anti-patterns\", \"why might this deploy fail\", or runs `audit_app.py`. DO NOT TRIGGER for creating a new app (use development-workflow) or for debugging an error the user already has (use debugging-workflows).",
  "included_files": [
    {
      "relative_path": "scripts/audit_app.py",
      "size_in_bytes": 20191
    }
  ],
  "name": "app-audit",
  "skill_md_contents": "---\nname: app-audit\ndescription: Audit an existing Falcon Foundry app for documented anti-patterns and fix the safe ones, like npm audit. TRIGGER when user asks to \"audit my Foundry app\", \"check my app for problems\", \"review this Foundry app\", \"scan for anti-patterns\", \"why might this deploy fail\", or runs `audit_app.py`. DO NOT TRIGGER for creating a new app (use development-workflow) or for debugging an error the user already has (use debugging-workflows).\nversion: 1.7.1\nupdated: 2026-11-10\ntags: [foundry, audit, lint, best-practices]\nauthor: CrowdStrike\nlicense: MIT\ncompatibility: Claude Code >=1.0\nmetadata:\n  category: quality\n---\n\n# Auditing a Foundry App\n\nRun the bundled script against the app directory (the one with `manifest.yml`). It reads the manifest and the files it points to, calls no API, and needs only `pyyaml`:\n\n```bash\npython3 skills/app-audit/scripts/audit_app.py path/to/app          # report\npython3 skills/app-audit/scripts/audit_app.py path/to/app --json   # machine-readable\npython3 skills/app-audit/scripts/audit_app.py path/to/app --fix    # apply the safe fixes, then report\n```\n\nIt exits `1` when an error-level finding remains. Each finding names the skill and section that explains it; read that section before changing anything.\n\n## What It Checks\n\n| Check | Severity | Why |\n|-------|----------|-----|\n| `function-count` | warn | More than 20 functions. Each is a separate container build, and a fresh install with 43 failed where the same handlers in 11 functions deployed. |\n| `handler-name-length` | error | Handler names must be 5 to 64 characters (the CLI's own limits). |\n| `handler-name-duplicate` | error | Handler names must be unique within a function. |\n| `request-property-undeclared` | error | A workflow passes a property the function's `request_schema` doesn't declare, so it's silently dropped. |\n| `response-key-missing` | warn | A workflow reads a `FaaS` output key the handler's `response_schema` doesn't declare. |\n| `unknown-function-action` | error | A workflow calls `functions.<name>.<handler>` that isn't in the manifest. |\n| `missing-workflow-integration` | error | A workflow calls a handler that has no `workflow_integration`, so deploy fails. |\n| `provision-on-install-missing` | warn, fixable | Installing won't create the workflow. Leave it off only when the app provisions the workflow itself through the Workflows API, as rapid-response and scalable-rtr do. |\n| `provision-on-install-false` | info | Fine when deliberate. |\n| `pycache-not-ignored` | warn, fixable | A local `__pycache__/` would deploy. The CLI already skips hidden paths like `.venv/`. |\n| `secret-in-env` | warn | A function reads a key, token, secret, or password from an environment variable, which is visible in app exports. |\n| `server-url-protocol` | error | An OpenAPI server URL with variables starts with `https://` or `http://`, so the protocol doubles. |\n| `server-variable-default` | warn | A server variable has a `default` but no `enum`, which renders as a one-value dropdown. |\n| `ui-not-built` | error | A page or extension has no `dist/`; deploy never builds the UI. |\n| `ui-stale-build` | warn | `src/` is newer than `dist/`, so deploy would ship the previous build. |\n| `invalid-file` | error | `manifest.yml`, a workflow, or an API spec it points to doesn't parse, so the checks that read it were skipped. |\n\n## Fixing Findings\n\n`--fix` applies only the fixes marked fixable: it adds the `__pycache__` pattern to `ignored:` and `provision_on_install: true` to workflows that lack it. Both are single-line insertions that leave the rest of the file as written. Tell the user what `--fix` will change before running it, and show the diff afterward.\n\nEverything else needs judgment, so handle it with the user:\n\n- **Undeclared request properties:** add each property to the handler's `request_schema.json`, then redeploy. If the handler has no schema, the function needs one bound at create time (see the `functions-development` skill → Function I/O Schemas).\n- **Missing response keys:** add the key to `response_schema.json`, or fix the workflow's data path if the key is misspelled.\n- **Too many functions:** follow the `functions-development` skill's `references/function-count-and-build-time.md`; consolidating changes workflow wiring and needs its checklist.\n- **Server URLs and defaults:** run the `api-integrations` skill's spec adapter on the spec rather than editing it by hand.\n- **UI builds:** run `npm run build` in each page or extension directory, then return to the app root.\n\nRun the audit again after fixing, and run `foundry apps validate --no-prompt` before deploying. The audit complements validation and doesn't replace it.\n\n## Reading Results\n\nThe checks are static, so treat a finding as a strong lead, not proof. A warning can be deliberate (a large app may need many functions, and an app that provisions its own workflows skips `provision_on_install`). If a finding looks wrong for the app in front of you, say why instead of forcing a fix.\n"
}

SHA-256 of public snapshot: f422757358aaadd7c507635998dd4ddad005543023543bf2ad2a58b830299637