CtrlK
BlogDocsLog inGet started
Tessl Logo

debugging-workflows

Systematic troubleshooting for Falcon Foundry CLI errors, manifest validation failures, deploy failures, and development server issues. TRIGGER when user encounters CLI errors, `foundry ui run` not working, deploy failures, authentication issues, or any unexpected behavior during Foundry app development. Also trigger for headless/CI environment setup failures.

70

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

SKILL.md
Quality
Evals
Security

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 well-structured, highly actionable debugging reference with clear sequenced workflows, validation feedback loops, and a pre-escalation checklist. Its only real weakness is that a long single-file body with no reference bundle leaves some content inlined that could otherwise be split out.

DimensionReasoningScore

Conciseness

The body is mostly lean — decision trees, a symptom/cause/action table, and copy-paste code blocks carry the weight — but the multi-paragraph 'connection issue' token-cache narrative and the Visual Debugging section contain explanation that could be tightened without losing the non-obvious domain knowledge, so it sits above the 3 anchor but below a fully trimmed 5.

4 / 5

Actionability

Fully executable, copy-paste-ready commands throughout — 'foundry functions run --name my-function', the FOUNDRY_API_* env var exports, the 'foundry profile create ... --no-prompt' block — with concrete examples covering the common CLI, deploy, auth, and headless cases.

5 / 5

Workflow Clarity

Multi-step processes are explicitly sequenced (CLI Troubleshooting Step 1/Step 2, the numbered App Install Failure isolation, Recovery Strategies) with validation checkpoints ('foundry apps validate --no-prompt'), a feedback loop ('Fix and re-validate incrementally'), and a Pre-Escalation Checklist for error recovery.

5 / 5

Progressive Disclosure

Section headers and a signaled one-level external reference ('See e2e-testing/references/debugging-with-mcp.md for details') give good navigation, but with no bundle files present the ~240-line body is a single inlined file, so content is not actually split across files as the 5 anchor requires.

4 / 5

Total

18

/

20

Passed

Description

87%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 clearly states what the skill does and gives explicit, concrete trigger conditions tied to a narrow product niche. It is held back only by a single generic action verb and the absence of synonym/file-extension terms.

DimensionReasoningScore

Specificity

Lists several concrete failure domains — 'CLI errors, manifest validation failures, deploy failures, and development server issues' plus auth and headless/CI setup — but the only stated action is the generic 'Systematic troubleshooting', leaving minor coverage gaps on the action side that keep it just below comprehensive.

4 / 5

Completeness

Explicitly answers both what ('Systematic troubleshooting for Falcon Foundry CLI errors, manifest validation failures, deploy failures, and development server issues') and when ('TRIGGER when user encounters CLI errors... Also trigger for headless/CI environment setup failures') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural phrases a user would actually say are present ('foundry ui run not working', 'deploy failures', 'authentication issues', 'headless/CI environment setup failures'), but synonym variants and file extensions (e.g. manifest.yml, .yaml) are missing, so it falls short of the 5 anchor.

4 / 5

Distinctiveness Conflict Risk

The 'Falcon Foundry' niche and product-specific triggers ('foundry ui run', manifest validation) are highly distinct, with minimal overlap risk against other skills.

5 / 5

Total

18

/

20

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: 1 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.