api-integrations

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.

Quality

92%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Discovery

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is an excellent skill description that clearly defines its purpose, provides rich trigger terms covering natural user language and CLI commands, and explicitly delineates its boundary from a related skill. The DO NOT TRIGGER clause is a particularly strong feature that reduces conflict risk. The description uses proper third-person voice and is concise yet comprehensive.

Dimension	Reasoning	Score
Specificity	The description lists concrete actions: 'Expose external APIs to Falcon Foundry via OpenAPI specs', 'create an API integration', 'adapt an OpenAPI spec for Foundry', 'expose an API to workflows', 'connect to a third-party API'. It also references a specific CLI command. These are multiple specific concrete actions.	3 / 3
Completeness	Clearly answers both 'what' (expose external APIs to Falcon Foundry via OpenAPI specs) and 'when' (explicit TRIGGER clause with multiple scenarios, plus a DO NOT TRIGGER clause distinguishing it from a related skill). This is exemplary completeness.	3 / 3
Trigger Term Quality	Excellent coverage of natural trigger terms: 'create an API integration', 'adapt an OpenAPI spec for Foundry', 'expose an API to workflows', 'connect to a third-party API', 'OpenAPI/Swagger spec', 'Falcon Foundry', and the CLI command 'foundry api-integrations create'. These are terms users would naturally use.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive with a clear niche (OpenAPI specs for Falcon Foundry integrations) and explicitly differentiates itself from a related skill ('functions-falcon-api') with a DO NOT TRIGGER clause, minimizing conflict risk.	3 / 3
	Total	12 / 12 Passed

Implementation

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a strong, well-structured skill that provides highly actionable guidance for a complex domain-specific task. Its main weakness is repetition — several warnings (don't read large specs, don't write specs from scratch, the adapt script runs automatically) appear multiple times across sections, which wastes tokens. The workflow is clear, the code examples are executable, and the progressive disclosure to reference files is well-organized.

Suggestions

Consolidate repeated warnings (large spec reading, adapt script auto-run, don't write specs from scratch) into a single location — the Common Pitfalls section or the workflow steps, but not both — to save ~30-40 lines of redundant content.

Dimension	Reasoning	Score
Conciseness	The skill is mostly efficient with domain-specific knowledge Claude wouldn't have, but there's notable repetition — the 'never read large specs' warning appears 3 times, the adapt script's automatic hook behavior is mentioned 3 times, and the 'don't write specs from scratch' point is repeated. The Common Pitfalls section largely restates guidance already given in the workflow. Some trimming would improve token efficiency.	2 / 3
Actionability	Highly actionable with executable CLI commands, concrete Python and JavaScript code examples, specific flags (e.g., `--description` with `--no-prompt`), exact JSON/YAML configuration patterns, and a clear decision tree. The `gh api` command for browsing repos, the adapt script invocation, and the `foundry api-integrations create` command are all copy-paste ready.	3 / 3
Workflow Clarity	The 3-step workflow (Download → Adapt → Register) is clearly sequenced with explicit validation (`foundry apps validate --no-prompt` after registration), a safety net (PreToolUse hook), and clear guidance on when to skip optional steps. The decision tree at the top provides good routing, and the 'only proceed when valid' pattern is present.	3 / 3
Progressive Disclosure	Excellent progressive disclosure with a clear overview in the main file and well-signaled one-level-deep references to spec-adaptation-examples.md, auth-examples.md, calling-patterns.md, and use-case files. The Reading Guide table provides clean navigation. The main file contains enough to complete most tasks without needing references, while detailed patterns are appropriately externalized.	3 / 3
	Total	11 / 12 Passed

Validation

81%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 9 / 11 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	9 / 11 Passed

Repository: CrowdStrike/foundry-skills
Commit: 631c815

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.