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

85%

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 with concrete commands and a solid reference structure. Weaker on conciseness due to a redundant Common Pitfalls section, and on progressive disclosure due to three broken use-cases file references.

Suggestions

Collapse the 'Common Pitfalls' bullets that merely restate rules already in 'Workflow' and 'Efficiency Rules' (large-spec Read/sed, unasked x-cs-operation-config, hand-writing specs, skipping the adapt script) into cross-references or delete them to remove duplication.

Remove or create the three missing use-cases/*.md files referenced in the 'Use Cases' section so navigation does not lead to dead ends.

Add an explicit validate→fix→retry loop after 'foundry apps validate --no-prompt' (e.g., what to inspect and re-run on validation failure) to complete the workflow's feedback loop.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and domain-specific (Foundry credential management is non-obvious), but the 'Common Pitfalls' section restates ~6 rules already given verbatim above (never Read/sed large specs, don't add x-cs-operation-config unasked, don't write specs from scratch, run the adapt script), and 'Efficiency Rules' repeats the step-2 auth guidance — material that could be tightened.	3 / 5
Actionability	Fully executable guidance throughout: exact CLI commands, the adapt script invocation with --dry-run, a venv setup block, grep/python3 patch snippets, and a copy-paste Foundry-JS calling example covering the common cases.	5 / 5
Workflow Clarity	The 'Download, Adapt, Register' workflow is explicitly numbered and ordered with a validation checkpoint ('Validate immediately after registering: foundry apps validate --no-prompt') and a --dry-run preview, but lacks an explicit validate→fix→retry feedback loop after registration.	4 / 5
Progressive Disclosure	Good structure with a Reading Guide table mapping tasks to three real one-level-deep reference files (auth-examples.md, calling-patterns.md, spec-adaptation-examples.md), but the 'Use Cases' section links to three files (use-cases/http-actions.md, greynoise-deep-dive.md, custom-soar-actions.md) that do not exist in the bundle.	4 / 5
	Total	16 / 20 Passed

Description

95%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, third-person description with concrete trigger phrases, a CLI command, synonym coverage, and an explicit negative boundary that disambiguates it from a sibling skill. Minor gap: the listed actions overlap rather than spanning distinct capabilities.

Dimension	Reasoning	Score
Specificity	Names the domain ('Expose external APIs to Falcon Foundry via OpenAPI specs') and lists several concrete actions ('create an API integration', 'adapt an OpenAPI spec for Foundry', 'expose an API to workflows', 'connect to a third-party API'), but the actions are variations of one core capability rather than comprehensive coverage.	4 / 5
Completeness	Explicitly answers what ('Expose external APIs to Falcon Foundry via OpenAPI specs') and when (concrete 'TRIGGER when...' phrases plus a 'DO NOT TRIGGER' negative boundary), satisfying both halves with concrete trigger phrases.	5 / 5
Trigger Term Quality	Comprehensive natural-term coverage including synonyms ('OpenAPI/Swagger spec'), user phrases ('create an API integration', 'connect to a third-party API'), and the literal CLI command 'foundry api-integrations create'.	5 / 5
Distinctiveness Conflict Risk	Clear Foundry-specific niche with a disambiguating 'DO NOT TRIGGER... use functions-falcon-api instead' clause, giving minimal conflict risk with adjacent skills.	5 / 5
	Total	19 / 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: 1854e7d

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