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

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

86%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 well-structured, highly actionable skill body that front-loads concrete YAML and CLI examples and offloads depth to real, well-signaled reference files. The main improvement area is collapsing the few repeated warnings and surfacing a validation checkpoint inline in the creation workflow rather than only in a referenced file.

Suggestions

Deduplicate the recurring warnings: state the '$action_name.output.body is a literal string' rule and the 'Custom_' prefix convention once in their canonical sections and reference back instead of repeating full explanations.

Add an inline validation checkpoint to the CLI Scaffolding sequence (e.g. run `foundry apps validate` after `foundry workflows create`) so the destructive/batch creation flow does not rely solely on a referenced file for verification.

Tighten the 'Calling Functions from Workflows' and 'Calling API Integration Operations' sections, which re-explain the manifest-binding mechanics with some overlap, into a single cohesive binding guide.

Dimension	Reasoning	Score
Conciseness	Lean and domain-dense with no padding about basic concepts Claude knows, but a few warnings recur (the `$action_name.output.body` literal-string warning and the `Custom_` prefix note each appear more than once), which is minor over-explanation that could be tightened.	4 / 5
Actionability	Fully executable guidance throughout: copy-paste CLI commands with flags (`foundry workflows create --name ... --spec /tmp/workflow.yaml --no-prompt`), complete YAML blocks, a platform action ID table, and specific property examples covering the common cases.	5 / 5
Workflow Clarity	The creation sequence is clear (write YAML to /tmp, create, edit to refine) and the destructive case is explicitly handled via the 'NEVER Delete and Recreate Workflows' section with an 'update in place' recovery pattern; validation exists (`foundry apps validate`, mock triggers) but is delegated to a referenced file rather than presented as an inline checkpoint in the main flow, a minor gap.	4 / 5
Progressive Disclosure	Clear overview body with a 'Reading Guide' table mapping tasks to one-level-deep reference files; all referenced files exist (action-discovery.md, advanced-patterns.md, cel-expressions.md, event-query-vs-api.md, http-actions.md, pagination-patterns.md, workflow-examples.md) plus scripts/action_search.py, and detailed material is appropriately split out rather than inlined.	5 / 5
	Total	18 / 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 explicit what/when structure, rich natural trigger phrases, and a clear negative boundary that reduces conflict with sibling skills. The only minor weakness is that the concrete action verbs are essentially create+configure rather than a broader enumerated action set.

Dimension	Reasoning	Score
Specificity	Names the domain ('Falcon Fusion SOAR workflow YAML for Falcon Foundry apps') and concrete actions (create, configure) plus sub-topics (triggers, actions, variable references), but the core verb set is create+configure rather than an exhaustive multi-action list, leaving minor coverage gaps.	4 / 5
Completeness	Explicitly answers both 'what' (Create and configure Falcon Fusion SOAR workflow YAML) and 'when' via a dedicated 'TRIGGER when...' clause with concrete trigger phrases, plus an explicit 'DO NOT TRIGGER' boundary.	5 / 5
Trigger Term Quality	Comprehensive natural trigger phrases users would actually say ('create a workflow', 'build an automation', 'configure Fusion SOAR', 'add an on-demand workflow') plus the literal CLI command `foundry workflows create` and sub-topics like 'Fusion YAML syntax'.	5 / 5
Distinctiveness Conflict Risk	Clear niche (Fusion SOAR workflow YAML for Foundry apps) with a negative boundary ('DO NOT TRIGGER for UI pages, functions, or collection schemas — use the appropriate sub-skill') that minimizes overlap with sibling 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/workflows-development/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.