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

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

75%Weight 40%Scale 1-5

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

A highly actionable, well-sequenced skill body whose value is its density of non-obvious platform quirks and copy-paste commands. Its main costs are triple-stated warnings that inflate the token budget, a missing error-recovery loop around validation, and a Use Cases section referencing files absent from the bundle.

Suggestions

State each recurring warning once (e.g., the `--description` 50-character cap, 'don't trim vendor specs', 'skip x-cs-operation-config unless asked') and let the Common Pitfalls section be the single recap location instead of repeating them in the intro, workflow, and pitfalls sections.

Remove or ship the `use-cases/*.md` files referenced in the Use Cases section — as written they are dangling references that fail navigation.

Add a short error-recovery step after `foundry apps validate --no-prompt` (what to check and fix when validation fails) to close the feedback loop in the main workflow.

Dimension	Reasoning	Score
Conciseness	The body is dense with genuinely non-obvious, Foundry-specific knowledge (50-char description limit, https:// stripping, clientCredentials-only), but several points are repeated three times — the `--description` 50-char cap appears in the intro quote, step 3, and Common Pitfalls; 'Foundry handles large specs fine / don't trim' and 'skip x-cs-operation-config unless asked' each recur three times. This matches 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than the 'minor instances' of the 4 anchor.	3 / 5
Actionability	Nearly everything is copy-paste executable: exact `foundry api-integrations create` invocations, a complete venv bootstrap for the adapt script, JSON/YAML config snippets, working JavaScript for calling integrations, and grep/python3 recipes for patching large specs without reading them. Path placeholders like `/path/to/foundry-skills/` are explicitly justified by the 'resolve relative to this SKILL.md' instruction, so this is fully executable guidance covering the common cases.	5 / 5
Workflow Clarity	The three-step Download → Adapt → Register workflow is explicitly ordered, with a validation checkpoint ('Validate immediately after registering (`foundry apps validate --no-prompt`)') and a hook safety net for a missed step. It falls short of the 5 anchor because there is no error-recovery loop — what to do when validation or the import fails is not addressed (only the auth-field exception is), so checkpoints are present but feedback loops are incomplete.	4 / 5
Progressive Disclosure	The body is a well-signaled overview with details pushed one level deep into three real, substantive reference files (spec-adaptation-examples.md, auth-examples.md, calling-patterns.md), plus a Reading Guide table and a scripts/ helper. The gap keeping it from 5: the Use Cases section points to `use-cases/http-actions.md` and two sibling files that are not present in the bundle — dangling references that break navigation.	4 / 5
	Total	16 / 20 Passed

Description

90%Weight 40%Scale 1-5

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

A strong trigger-oriented description with explicit positive and negative trigger phrases, natural user vocabulary, and clean disambiguation from a sibling skill. Its only weakness is that the capability statement is a single sentence, so the range of what the skill actually does is underdescribed relative to its excellent trigger coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain and one concrete action — 'Expose external APIs to Falcon Foundry via OpenAPI specs' — but does not enumerate the actual capabilities (download, adapt, register, auth configuration). It matches 'names domain and 1-2 concrete actions, but not comprehensive'; a 4 would require several specific actions listed, and the bulk of this description is trigger phrasing rather than capability statements.	3 / 5
Completeness	It explicitly answers what ('Expose external APIs to Falcon Foundry via OpenAPI specs') and when (explicit TRIGGER clauses with concrete trigger phrases, plus a DO-NOT-TRIGGER exclusion). This matches the anchor for a clear 'what' plus explicit 'when' with concrete trigger phrases; nothing is only implied.	5 / 5
Trigger Term Quality	It covers natural user phrasings comprehensively with synonyms and concrete triggers: 'create an API integration', 'adapt an OpenAPI spec for Foundry', 'expose an API to workflows', 'connect to a third-party API', the CLI command `foundry api-integrations create`, and both 'OpenAPI/Swagger spec' variants. This matches the comprehensive anchor including synonyms and command forms.	5 / 5
Distinctiveness Conflict Risk	The niche is distinct (Falcon Foundry API integrations via OpenAPI) and conflict risk is actively minimized by the explicit 'DO NOT TRIGGER when user wants to call Falcon platform APIs from function code — use functions-falcon-api instead' disambiguation. This matches the clear-niche, minimal-conflict anchor.	5 / 5
	Total	18 / 20 Passed

Validation

87%

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 — 14 / 16 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	14 / 16 Passed

Repository: CrowdStrike/foundry-skills
Path: skills/api-integrations/SKILL.md
Commit: 61572f3

Reviewed: 6 hours 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.