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

Pending

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 scope, provides rich trigger terms users would naturally use, and explicitly delineates boundaries with a related skill via a DO NOT TRIGGER clause. It uses proper third-person voice and is concise yet comprehensive. The inclusion of both a CLI command trigger and natural language triggers ensures broad coverage.

Dimension	Reasoning	Score
Specificity	The description lists specific concrete actions: exposing external APIs via OpenAPI specs, adapting OpenAPI specs for Foundry, connecting to third-party APIs, and running a specific CLI command. It also explicitly distinguishes from a related but different skill (functions-falcon-api).	3 / 3
Completeness	Clearly answers both 'what' (expose external APIs to Falcon Foundry via OpenAPI specs) and 'when' (explicit TRIGGER and DO NOT TRIGGER clauses with specific phrases and scenarios). The negative trigger guidance further strengthens 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', 'foundry api-integrations create', 'OpenAPI/Swagger spec'. These are terms users would naturally use.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive with a clear niche (Falcon Foundry API integrations via OpenAPI specs) 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, domain-specific skill that provides highly actionable guidance for a complex integration workflow. The 3-step workflow is clear with good validation checkpoints, the auth table is an excellent reference, and progressive disclosure to supporting files is well-structured. The main weakness is repetition — several warnings (don't read large specs, don't write specs from scratch, the adapt script runs automatically) are stated multiple times across sections, inflating the token cost without adding new information.

Suggestions

Consolidate repeated warnings (large spec reading, adapt script auto-hook, don't write specs from scratch) into single authoritative statements rather than restating them in Workflow, Efficiency Rules, and Common Pitfalls sections.

Dimension	Reasoning	Score
Conciseness	The skill is mostly efficient with domain-specific knowledge Claude wouldn't know, 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. The auth table and reference implementations are valuable and dense, but the overall document could be ~30% shorter without losing information.	2 / 3
Actionability	Highly actionable with executable CLI commands, concrete Python code for spec manipulation, a complete JavaScript SDK example for calling integrations, specific `grep` patterns for large files, and exact CLI flags (including the `--description` gotcha). The auth configuration table maps specific OpenAPI patterns to Foundry behavior with named production examples.	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 decision points (when to add x-cs-operation-config, when to write specs from scratch). The decision tree at the top provides good routing. Error recovery is addressed via the adapt script's dry-run mode.	3 / 3
Progressive Disclosure	Excellent structure with a concise main workflow in the SKILL.md and clear one-level-deep references to three focused reference files (spec-adaptation-examples.md, auth-examples.md, calling-patterns.md) plus use-case files. The Reading Guide table at the bottom provides task-based navigation. Content is appropriately split — the main file covers the workflow and key patterns while deferring vendor-specific details and language-specific calling patterns to references.	3 / 3
	Total	11 / 12 Passed

Validation

72%

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 — 8 / 11 Passed

Validation for skill structure

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

	Total	8 / 11 Passed

Repository: CrowdStrike/foundry-skills
Commit: e7fa026

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