CtrlK
BlogDocsLog inGet started
Tessl Logo

fusion-redirect

TRIGGER when user asks for a "standalone Falcon Fusion workflow" that needs NO Foundry app — just a trigger plus actions that already exist in their CID, with no UI, function, collection, or custom API integration to build. DO NOT TRIGGER when the request needs anything built (a custom action, a UI page, a function, a collection) — that is a Foundry app and development-workflow owns it. This skill exists so the redirect works without hooks and yields to the real Falcon Fusion plugin when both are loaded.

68

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

92%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 tight, highly actionable redirect body that gives exact commands and a clear routing table, with only minor conciseness slack from its rationale section. Well structured for a single-purpose skill with no bundle dependencies.

DimensionReasoningScore

Conciseness

Efficient and mostly lean; the 'Why this exists' section is brief and aids routing decisions but is mild justification Claude could partly infer, keeping it just short of a 5.

4 / 5

Actionability

Fully actionable for an instruction-only skill: exact plugin name (crowdstrike-falcon-fusion), exact install command (/plugin install crowdstrike-falcon-fusion), and a concrete URL, with a numbered three-part response spec.

5 / 5

Workflow Clarity

A simple single-purpose redirect whose single action (respond with all three parts) is unambiguous; per the simple-skill exception no multi-step validation is needed.

5 / 5

Progressive Disclosure

Under 50 lines with no external references needed and no bundle files; content is well-organized into clearly headed sections (What to do, Why this exists, Distinguishing table), satisfying the simple-skill bar.

5 / 5

Total

19

/

20

Passed

Description

73%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 well-targeted redirect description with strong trigger guidance and conflict avoidance, slightly weakened by an abstract statement of capability. Tightening the 'what' to describe the routing action concretely would lift it further.

Suggestions

Open with a concrete capability statement such as 'Routes standalone Falcon Fusion workflow requests to the sibling crowdstrike-falcon-fusion plugin' before the trigger clauses.

Add a couple of natural synonyms (e.g. 'just a workflow', 'wire existing actions together') to broaden trigger coverage.

Drop the meta-rationale ('This skill exists so the redirect works without hooks...') from the description; it belongs in the body, not the trigger line.

DimensionReasoningScore

Specificity

Names the domain (standalone Fusion workflow redirect) and a couple of concrete routing actions, but the 'what' leans on abstract phrasing like 'the redirect works without hooks and yields' rather than enumerating what the skill actually does.

3 / 5

Completeness

Both 'when' (very explicit TRIGGER/DO NOT TRIGGER clauses) and 'what' (redirect to the Fusion plugin) are present; the 'what' could be more concrete about the skill's actual behavior.

4 / 5

Trigger Term Quality

Includes natural phrases a user would say ('standalone Falcon Fusion workflow', 'no app needed', 'actions that already exist in their CID') plus explicit negative triggers, though a few common synonyms are missing.

4 / 5

Distinctiveness Conflict Risk

Highly distinctive niche with explicit positive and negative triggers and a clear handoff boundary to development-workflow, minimizing conflict risk with sibling skills.

5 / 5

Total

16

/

20

Passed

Validation

87%

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

Validation14 / 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

Total

14

/

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.