Release v1.1.0 (#26)

* Release v1.1.0

* Add marketplace description to suppress validation warning

* Update release date to 2026-05-13

* Disclose npx swagger2openapi network call in plugin.json

* Add foundry-js-sdk.md to ui-development Reading Guide

* Rename FalconJS SDK / Foundry-JS SDK to Foundry-JS

@crowdstrike/foundry-js is "Foundry-JS", not an SDK. The actual Falcon SDK
is @crowdstrike/falconjs. Renamed all references and foundry-js-sdk.md to
foundry-js.md per Josh Hiller's review feedback.

* Add hook-scope note to README per Anthropic review feedback

Clarifies that hooks only keyword-match Foundry-specific actions and no
data leaves the session, as requested by bryan-anthropic on PR #1842.

* Fix model ID in test scripts to use public alias

Changed --model claude-4-6-opus (internal name) to --model opus (public
alias per claude --help). The alias stays valid across version bumps.

* Pin test scripts to claude-opus-4-6 (correct public model ID)

Author: mraible

.claude-plugin/marketplace.json

@@ -1,5 +1,6 @@
 {
   "name": "foundry-marketplace",
+  "description": "AI coding assistant skills for building CrowdStrike Falcon Foundry apps",
   "owner": {
     "name": "CrowdStrike"
   },
@@ -8,7 +9,7 @@
       "name": "crowdstrike-falcon-foundry",
       "source": "./",
       "description": "CrowdStrike Falcon Foundry development skills for building cybersecurity applications on the Falcon platform. Includes UI development, collections, functions, workflows, API integration, security patterns, and debugging workflows.",
-      "version": "1.0.0",
+      "version": "1.1.0",
       "author": {
         "name": "CrowdStrike"
       },

.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "crowdstrike-falcon-foundry",
-  "description": "CrowdStrike Falcon Foundry development skills for building cybersecurity applications on the Falcon platform. Includes UI development, collections, functions, workflows, API integration, security patterns, and debugging workflows.",
-  "version": "1.0.0",
+  "description": "CrowdStrike Falcon Foundry development skills for building cybersecurity applications on the Falcon platform. Includes UI development, collections, functions, workflows, API integration, security patterns, and debugging workflows. Swagger 2.0 specs are auto-converted to OpenAPI 3.0 via npx swagger2openapi (requires Node.js; network call to npm registry).",
+  "version": "1.1.0",
   "author": {
     "name": "CrowdStrike"
   },

CHANGELOG.md

@@ -4,19 +4,20 @@ All notable changes to this project will be documented in this file.
 
 The format is based on [Keep a Changelog](https://keepachangelog.com/), and this project adheres to [Semantic Versioning](https://semver.org/).
 
-## [1.1.0] - TBD
+## [1.1.0] - 2026-05-13
 
 ### Added
 
 - **e2e-testing skill** — End-to-end testing for Foundry apps using `@crowdstrike/foundry-playwright`. Covers the 4-project pipeline (authenticate → install → test → uninstall), page objects, configuration screens, custom page objects, CI with GitHub Actions, and debugging with Playwright MCP.
 - **NGSIEM query export use case** — Export Falcon Next-Gen SIEM query results to CSV/JSON via Foundry functions with pagination and scheduled workflow patterns.
-- **Foundry-JS SDK reference** — `falcon.api.workflows`, `falcon.logscale`, `falcon.cloudFunction`, and collections CRUD patterns for `@crowdstrike/foundry-js` in `ui-development/references/foundry-js-sdk.md`.
+- **Foundry-JS reference** — `falcon.api.workflows`, `falcon.logscale`, `falcon.cloudFunction`, and collections CRUD patterns for `@crowdstrike/foundry-js` in `ui-development/references/foundry-js.md`.
 - **Visual debugging section** in debugging-workflows — Screenshot-based troubleshooting with Playwright MCP and test failure artifacts.
 - **agentskills.io metadata** — All skills now have top-level `tags`, `author`, `license`, and `compatibility` fields per the [agentskills.io](https://agentskills.io) open spec.
 
 ### Changed
 
 - **development-workflow** — Expanded e2e testing guidance with credential configuration details, non-SSO user requirement, and app name alignment.
+- **release.sh** — Added Step 8 documenting the Anthropic Plugin Marketplace update process (notify Anthropic of tag + SHA after each release).
 
 ### Removed
 
@@ -33,7 +34,7 @@ Initial public release of Falcon Foundry Skills — AI coding assistant skills f
 - **collections-development** — Design and implement Foundry collections with JSON Schema modeling, CRUD operations via CustomStorage, and access control patterns.
 - **functions-development** — Build serverless functions in Python or Go with FDK handler patterns, dependency management, and testing.
 - **functions-falcon-api** — Call CrowdStrike Falcon APIs from within Foundry functions using zero-argument FalconPy authentication.
-- **ui-development** — Build UI pages and extensions with React, Vue, or vanilla JS. Includes FalconJS SDK patterns, Shoelace theming, and iframe communication.
+- **ui-development** — Build UI pages and extensions with React, Vue, or vanilla JS. Includes Foundry-JS patterns, Shoelace theming, and iframe communication.
 - **workflows-development** — Design Falcon Fusion SOAR workflows with YAML specs, CEL expressions, loop/condition control flow, and platform action integration.
 - **debugging-workflows** — Systematic troubleshooting for CLI errors, deployment failures, blank pages, and runtime issues.
 - **security-patterns** — OAuth scoping, input validation, XSS prevention, CSP configuration, and secure coding patterns.

README.md

@@ -2,7 +2,7 @@
 
 # Falcon Foundry Skills
 
-![Version](https://img.shields.io/badge/version-1.0.0-blue)
+![Version](https://img.shields.io/badge/version-1.1.0-blue)
 [![CI](https://github.com/CrowdStrike/foundry-skills/actions/workflows/main.yml/badge.svg)](https://github.com/CrowdStrike/foundry-skills/actions/workflows/main.yml)
 
 AI coding assistant skills for building [CrowdStrike Falcon Foundry](https://www.crowdstrike.com/en-us/platform/next-gen-siem/falcon-foundry/) apps. Build Foundry apps from a natural language prompt — API integrations, workflows, UI pages, functions, and collections — all scaffolded with the Foundry CLI and deployed to the Falcon console.
@@ -133,6 +133,8 @@ The skills include hooks that ensure the right skills get used:
 
 3. **`PreToolUse` hook (CLI guard)** — Validates all Bash commands to ensure Foundry CLI commands include `--no-prompt` flag (prevents `Error: EOF` failures) and blocks manual directory creation for app structure (prevents invalid `manifest.yml`). This enforcement is automatic and transparent — you'll only see it when it catches an error.
 
+Hooks observe prompts and tool I/O to keyword-match Foundry-specific actions; no data leaves the session.
+
 ## Skills
 
 | Skill | Purpose |
@@ -334,6 +336,8 @@ gh release create v<version> --target main --title "v<version>" --generate-notes
 
 This generates release notes from merged PRs and saves them as a draft. Review and edit the notes at [github.com/CrowdStrike/foundry-skills/releases](https://github.com/CrowdStrike/foundry-skills/releases), then click **Publish** when ready.
 
+After publishing the release, notify Anthropic of the new tag and SHA so they can update the marketplace pin. Do not open PRs to `anthropics/claude-plugins-official` or re-submit through the plugin submission form.
+
 ## License
 
 See [LICENSE](LICENSE) for details.

release.sh

@@ -185,7 +185,7 @@ main() {
   printf "\n${BLUE}Step 5: Commit and create PR${RESET}\n"
   local release_branch="release/v${NEXT_VERSION}"
   git checkout -b "$release_branch"
-  git add "$PLUGIN_JSON" "$MARKETPLACE_JSON" "$SCRIPT_DIR/README.md" "$SCRIPT_DIR/skills"/*/SKILL.md "$SCRIPT_DIR/CHANGELOG.md"
+  git add "$PLUGIN_JSON" "$MARKETPLACE_JSON" "$SCRIPT_DIR/README.md" "$SCRIPT_DIR/skills"/*/SKILL.md "$SCRIPT_DIR/CHANGELOG.md" "$SCRIPT_DIR/release.sh"
   git commit -m "Release v${NEXT_VERSION}"
   printf "${GREEN}✓${RESET} Committed v${NEXT_VERSION}\n"
 
@@ -201,6 +201,13 @@ main() {
   printf "This creates a draft release with auto-generated notes from merged PRs.\n"
   printf "Review and edit the notes at https://github.com/CrowdStrike/foundry-skills/releases,\n"
   printf "then click Publish when ready.\n\n"
+
+  printf "${BLUE}Step 8: Update Anthropic Plugin Marketplace${RESET}\n"
+  printf "\nAfter publishing the GitHub release, notify Anthropic of the new tag and SHA:\n"
+  printf "  Tag: v${NEXT_VERSION}\n"
+  printf "  SHA: \$(git rev-parse v${NEXT_VERSION})\n\n"
+  printf "Anthropic handles the marketplace pin bump internally. Do not open PRs to\n"
+  printf "anthropics/claude-plugins-official or re-submit through the plugin submission form.\n\n"
   printf "${GREEN}Done.${RESET}\n"
 }
 

skills/api-integrations/SKILL.md

@@ -1,8 +1,8 @@
 ---
 name: api-integrations
 description: Expose external APIs to Falcon Foundry via OpenAPI specs. TRIGGER when user asks to "create an API integration", "adapt an OpenAPI spec for Foundry", "expose an API to workflows", "connect to a third-party API", or runs `foundry api-integrations create`. Also trigger when user has an OpenAPI/Swagger spec and wants it working in Falcon Foundry. DO NOT TRIGGER when user wants to call Falcon platform APIs from function code — use functions-falcon-api instead.
-version: 1.0.0
-updated: 2026-04-29
+version: 1.1.0
+updated: 2026-05-13
 tags: [foundry, openapi, api, workflows]
 author: CrowdStrike
 license: MIT
@@ -151,7 +151,7 @@ For autocomplete dropdown patterns and the HTTP Actions vs. Functions decision f
 
 ## Calling API Integrations
 
-UI extensions call API integrations through the Falcon JS SDK (sandboxed iframes block arbitrary HTTP requests). This pattern is from [foundry-sample-foundryjs-demo](https://github.com/CrowdStrike/foundry-sample-foundryjs-demo):
+UI extensions call API integrations through Foundry-JS (sandboxed iframes block arbitrary HTTP requests). This pattern is from [foundry-sample-foundryjs-demo](https://github.com/CrowdStrike/foundry-sample-foundryjs-demo):
 
 ```javascript
 import FalconApi from '@crowdstrike/foundry-js';

skills/api-integrations/references/calling-patterns.md

@@ -2,12 +2,12 @@
 
 Full examples for calling API integrations from UI extensions, Python functions, and Go functions.
 
-## UI Extensions (JavaScript / Falcon JS SDK)
+## UI Extensions (JavaScript / Foundry-JS)
 
 UI extensions call API integrations through `falcon.apiIntegration()`, not direct HTTP calls. Foundry UI extensions run in sandboxed iframes and cannot make arbitrary HTTP requests.
 
 ```javascript
-// React example using Falcon JS SDK
+// React example using Foundry-JS
 import FalconApi from '@crowdstrike/foundry-js';
 
 const falcon = new FalconApi();

skills/collections-development/SKILL.md

@@ -1,8 +1,8 @@
 ---
 name: collections-development
 description: Design JSON Schema collections and CRUD patterns for Falcon Foundry apps. TRIGGER when user asks to "create a collection", "define a JSON schema", "store data in Foundry", runs `foundry collections create`, or needs help with indexable fields, FQL queries, or collection access patterns. DO NOT TRIGGER for workflow YAML, function handlers, or UI components — use the appropriate sub-skill.
-version: 1.0.0
-updated: 2026-04-29
+version: 1.1.0
+updated: 2026-05-13
 tags: [foundry, collections, json-schema, nosql]
 author: CrowdStrike
 license: MIT

skills/debugging-workflows/SKILL.md

@@ -1,8 +1,8 @@
 ---
 name: debugging-workflows
 description: Systematic troubleshooting for Falcon Foundry CLI errors, manifest validation failures, deploy failures, and development server issues. TRIGGER when user encounters CLI errors, `foundry ui run` not working, deploy failures, authentication issues, or any unexpected behavior during Foundry app development. Also trigger for headless/CI environment setup failures.
-version: 1.0.0
-updated: 2026-04-29
+version: 1.1.0
+updated: 2026-05-13
 tags: [foundry, debugging, cli, deployment]
 author: CrowdStrike
 license: MIT

skills/development-workflow/SKILL.md

@@ -1,8 +1,8 @@
 ---
 name: development-workflow
 description: Orchestrates the complete Falcon Foundry app lifecycle from requirements through deployment. TRIGGER when user asks to "create a Foundry app", "build a Foundry app", "plan a Foundry app", runs any `foundry apps` CLI command, or discusses Foundry app architecture. DO NOT TRIGGER when user is working on a specific capability (UI, function, workflow, collection) within an existing app — use the appropriate sub-skill instead. This skill OWNS the entire Foundry development flow. Do not delegate Foundry app creation to superpowers:brainstorming or superpowers:writing-plans — those skills do not know about the Foundry CLI.
-version: 1.0.0
-updated: 2026-04-29
+version: 1.1.0
+updated: 2026-05-13
 tags: [foundry, lifecycle, cli, deployment]
 author: CrowdStrike
 license: MIT