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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

62%

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

The body is a well-sequenced, largely actionable workflow with good validation and reference structure, but it is held back by internal repetition and a central mandatory script whose path is a placeholder and whose file is absent from the bundle. Fixing the script reference and de-duplicating recurring warnings would lift conciseness and actionability.

Suggestions

Resolve the adapt-script reference: either include scripts/adapt-spec-for-foundry.py in the bundle or replace the /path/to/ placeholder with the actual resolved path so the core mandatory command is copy-paste ready.

De-duplicate recurring guidance — consolidate the --description/Error:EOF note, the "don't trim vendor specs" rule, and the "trust the adapt script" rule into single canonical statements to tighten conciseness.

Verify the use-cases/ and ../../relative links resolve in the real bundle, since only the references/ files are present here and several external links are unconfirmed.

Dimension	Reasoning	Score
Conciseness	Mostly operative and dense, but key messages repeat verbatim across sections (the --description/EOF note appears 3x; "don't trim vendor specs" and "trust the adapt script, don't analyze auth" each repeat twice), so it could be tightened.	2 / 3
Actionability	Strong runnable commands exist (foundry api-integrations create, gh api download, python3 spec-patching), but the mandatory adapt step references /path/to/adapt-spec-for-foundry.py and scripts/adapt-spec-for-foundry.py, a path that is not copy-paste ready and whose file is absent from the bundle.	2 / 3
Workflow Clarity	A clearly ordered 3-step sequence (Download, Adapt, Register) with an explicit validation checkpoint (foundry apps validate --no-prompt) and error-recovery guidance for the EOF prompt, matching the top anchor.	3 / 3
Progressive Disclosure	Three real one-level references are well-signaled via a Reading Guide table, but scoring against the actual bundle reveals the repeatedly-referenced mandatory scripts/adapt-spec-for-foundry.py is missing, a broken reference that keeps it off the top level.	2 / 3
	Total	9 / 12 Passed

Description

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.

A precise, well-scoped description that states what the skill does, when to trigger it with natural phrasings, and when NOT to trigger it to avoid conflicts. It is concise and free of fluff, hitting every dimension at the top of the scale.

Dimension	Reasoning	Score
Specificity	Names the concrete domain ("Expose external APIs to Falcon Foundry via OpenAPI specs") and multiple specific actions (download/adapt/register) beyond the 2-anchor level.	3 / 3
Completeness	Explicitly answers both what (exposing external APIs to Foundry via OpenAPI) and when (TRIGGER list), matching the 3-anchor pattern including a DO NOT TRIGGER clause.	3 / 3
Trigger Term Quality	Covers natural user phrasings ("create an API integration", "connect to a third-party API", "adapt an OpenAPI spec for Foundry") plus the CLI command a user would run.	3 / 3
Distinctiveness Conflict Risk	Clear niche with distinct triggers and an explicit DO NOT TRIGGER routing to functions-falcon-api that prevents the most likely sibling-skill collision.	3 / 3
	Total	12 / 12 Passed

Validation

75%

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 — 12 / 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
relative_links	Relative link issues: 3 suspicious	Warning
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	12 / 16 Passed

Repository: CrowdStrike/foundry-skills
Commit: 2f0ce35

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