debugging-workflows

Systematic troubleshooting for Falcon Foundry CLI errors, manifest validation failures, deploy failures, artifact runtime errors, and development server issues. TRIGGER when user encounters CLI errors, `foundry ui run` not working, deploy failures, authentication issues, function execution failures, "debug my function", "why did this fail", or any unexpected behavior during Foundry app development. Also trigger for headless/CI environment setup failures.

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Quality

Content

88%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 comprehensive, highly actionable debugging reference with concrete commands, decision trees, and well-sequenced workflows including validation and feedback loops. It is tight and domain-specific, with only minor verbosity and no external bundle to defer detail into.

Suggestions

Tighten the 'connection issue on Tenant Commands' prose to the actionable fix and one-line rationale; the surrounding justification can be trimmed without losing clarity.

Consider splitting the large 'Common Issue Patterns' table or 'Visual Debugging with Screenshots' section into a reference file under references/ to reduce inline length, now that no bundle exists.

Move the CLI-version time-sensitivity ('Requires Foundry CLI 2.1.0+') into a dedicated compatibility/version note so it is not lost inline within a section.

Dimension	Reasoning	Score
Conciseness	Dense and actionable with virtually no generic concept explanation, but a few prose passages (the token-cache write explanation, the 'Part of a suite' note) are slightly longer than strictly necessary.	4 / 5
Actionability	Fully executable copy-paste commands throughout, plus ASCII decision trees and symptom/cause/fix tables that map concrete failures to specific remediation commands.	5 / 5
Workflow Clarity	Multi-step procedures (Function Runtime Debugging Steps 1-5) are explicitly sequenced with validation checkpoints, feedback loops (fix -> redeploy -> verify), and a pre-escalation checklist; destructive operations include recovery procedures.	5 / 5
Progressive Disclosure	No bundle files exist, so all content is inlined in one well-sectioned document; cross-skill references ('see ui-development', 'load the development-workflow skill', 'e2e-testing/references/debugging-with-mcp.md') are clearly signaled and one level deep, but substantial detail that could live in reference files is kept inline.	4 / 5
	Total	18 / 20 Passed

Description

100%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 that names concrete failure categories and provides explicit, natural trigger phrases for both the what and the when. It clearly distinguishes itself as a Foundry-specific troubleshooting skill.

Dimension	Reasoning	Score
Specificity	Lists five concrete failure categories ('CLI errors, manifest validation failures, deploy failures, artifact runtime errors, and development server issues') giving comprehensive coverage of the skill's troubleshooting scope.	5 / 5
Completeness	Explicitly states both what the skill does ('Systematic troubleshooting for...') and when to use it ('TRIGGER when user encounters...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Combines natural user phrases ('debug my function', 'why did this fail', 'foundry ui run not working') with technical triggers, covering the ways users actually describe these problems.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear Falcon Foundry debugging niche with domain-specific triggers, making conflict with unrelated skills unlikely.	5 / 5
	Total	20 / 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/debugging-workflows/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.