CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

69

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

72%

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-structured reference with concrete code and clean progressive disclosure; its main weaknesses are a redundant leading injection block and incomplete validation feedback loops for destructive/deploy operations.

Suggestions

Remove or trim the "SYSTEM INJECTION — READ THIS FIRST" block: it duplicates later content and its "Implement onError blocks" line contradicts the Error Handling section, which explicitly says workflows use conditional routing rather than onError blocks.

Add a single ordered deploy/validate workflow with an explicit validate→fix→re-validate feedback loop (e.g. `foundry apps validate --no-prompt` → fix schema → re-validate → deploy) to give fragile operations a clear checkpoint sequence.

Consolidate the validation guidance currently spread across Testing, Workflow Name Uniqueness, and Error Handling into one checklist so checkpoints are not scattered.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence (no padding about what YAML/workflows are), but the leading "SYSTEM INJECTION — READ THIS FIRST" block is overhead and partially contradicts the later Error Handling section ("onError blocks" vs "not onError blocks").

2 / 3

Actionability

Provides concrete, executable CLI commands (e.g. `foundry workflows create --name ... --spec /tmp/workflow.yaml --no-prompt`) and complete YAML examples with real platform action IDs, copy-paste ready.

3 / 3

Workflow Clarity

Sequences for scaffolding and testing are present with some validation (`foundry apps validate --no-prompt`, `executions validate --mocks`), but the fragile deploy/manifest operations lack a unified validate→fix→retry feedback loop.

2 / 3

Progressive Disclosure

A clear overview with well-signaled, one-level-deep references — all six referenced files (action-discovery, workflow-examples, http-actions, cel-expressions, pagination-patterns, advanced-patterns) exist — and a Reading Guide table maps tasks to references.

3 / 3

Total

10

/

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 strong, specific description with explicit trigger guidance, concrete actions, natural user phrasings, and a negative-trigger clause that sharply reduces conflict risk with sibling skills.

DimensionReasoningScore

Specificity

Names multiple concrete actions — "Create and configure Falcon Fusion SOAR workflow YAML", "triggers, actions, or variable references" — rather than vague language.

3 / 3

Completeness

Explicitly answers both what (create/configure workflow YAML) and when via a clear "TRIGGER when..." clause, satisfying both requirements.

3 / 3

Trigger Term Quality

Includes natural user phrasings in quotes ("create a workflow", "build an automation", "configure Fusion SOAR", "add an on-demand workflow") plus the CLI invocation users would type.

3 / 3

Distinctiveness Conflict Risk

A clear Fusion SOAR workflow niche, with an explicit "DO NOT TRIGGER for UI pages, functions, or collection schemas" clause that actively prevents wrong-skill triggering.

3 / 3

Total

12

/

12

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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

Total

13

/

16

Passed

Repository
CrowdStrike/foundry-skills
Reviewed

Table of Contents

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.