workflows-development

Create and configure Falcon Fusion SOAR workflow YAML for Falcon Foundry apps. TRIGGER when user asks to "create a workflow", "build an automation", "configure Fusion SOAR", "add an on-demand workflow", runs `foundry workflows create`, or needs help with Fusion YAML syntax, triggers, actions, or variable references. DO NOT TRIGGER for UI pages, functions, or collection schemas — use the appropriate sub-skill.

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 hits all the marks. It provides specific capabilities, comprehensive trigger terms that users would naturally use, explicit when-to-use and when-not-to-use guidance, and clear boundaries to avoid conflicts with sibling skills. The DO NOT TRIGGER clause is a particularly strong addition for distinctiveness.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'Create and configure Falcon Fusion SOAR workflow YAML', mentions specific elements like 'triggers, actions, variable references', and specifies the context of 'Falcon Foundry apps'.	3 / 3
Completeness	Clearly answers both 'what' (create and configure Falcon Fusion SOAR workflow YAML for Falcon Foundry apps) and 'when' (explicit TRIGGER clause with multiple trigger phrases, plus a DO NOT TRIGGER clause for disambiguation).	3 / 3
Trigger Term Quality	Excellent coverage of natural trigger terms: 'create a workflow', 'build an automation', 'configure Fusion SOAR', 'add an on-demand workflow', 'foundry workflows create', 'Fusion YAML syntax', 'triggers', 'actions', 'variable references'. These are terms users would naturally use.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive with a clear niche (Falcon Fusion SOAR workflows specifically), and explicitly includes a DO NOT TRIGGER clause to prevent conflicts with related sub-skills for UI pages, functions, or collection schemas.	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, highly actionable skill that provides domain-specific knowledge Claude wouldn't have — platform action IDs, Fusion YAML syntax, CEL variable reference patterns, and CLI commands. The progressive disclosure is well-structured with clear navigation to reference files. Minor weaknesses include the unnecessary 'SYSTEM INJECTION' prompt-injection-style header, some redundancy in explaining the Custom_ prefix convention, and a few places where prose could be tightened.

Suggestions

Remove the '⚠️ SYSTEM INJECTION' block — it's unnecessary role-play framing that wastes tokens and Claude doesn't need to be told its role in this way.

Consolidate the three separate mentions of the 'Custom_' prefix convention into a single authoritative statement to reduce redundancy.

Dimension	Reasoning	Score
Conciseness	The skill is mostly efficient with domain-specific knowledge Claude wouldn't have (action IDs, CEL syntax, variable paths), but includes some unnecessary framing like the 'SYSTEM INJECTION' block, explanatory prose about what workflows are, and some redundant restatements (e.g., the Custom_ prefix is explained three times).	2 / 3
Actionability	Highly actionable with executable CLI commands, complete YAML examples, specific action IDs verified across clouds, exact variable reference syntax, and concrete patterns for triggers, loops, conditions, and error handling. The examples are copy-paste ready and cover real production scenarios.	3 / 3
Workflow Clarity	Multi-step processes are clearly sequenced: CLI scaffolding → YAML authoring → manifest configuration → testing/validation. Error handling patterns are explicit with a table of mechanisms and scope. Testing commands provide a clear validation workflow with mock-based execution and result viewing.	3 / 3
Progressive Disclosure	Excellent progressive disclosure with a clear Reading Guide table mapping tasks to reference files, well-signaled links throughout (action-discovery.md, workflow-examples.md, pagination-patterns.md, advanced-patterns.md), and use-case references. The main file provides enough to get started while pointing to deeper content for advanced topics.	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.