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.
88
88%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Risky
Do not use without reviewing
Quality
Discovery
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.
This is a strong skill description that clearly identifies its domain (Falcon Foundry CLI troubleshooting), lists specific problem categories it handles, and provides explicit trigger conditions. The use of product-specific terminology and concrete error scenarios makes it both highly discoverable and unlikely to conflict with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions/domains: CLI errors, manifest validation failures, deploy failures, development server issues, authentication issues, headless/CI environment setup failures. These are concrete, actionable problem categories. | 3 / 3 |
Completeness | Clearly answers both 'what' (systematic troubleshooting for Falcon Foundry CLI errors, manifest validation, deploy failures, dev server issues) and 'when' (explicit TRIGGER clause listing specific scenarios like CLI errors, deploy failures, authentication issues, headless/CI setup). | 3 / 3 |
Trigger Term Quality | Includes highly natural trigger terms users would actually say: 'CLI errors', 'foundry ui run not working', 'deploy failures', 'authentication issues', 'CI environment setup failures'. The backtick-quoted command is especially useful for matching real user queries. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: Falcon Foundry CLI specifically. The product-specific terminology ('Falcon Foundry', 'foundry ui run', 'Foundry app development') makes it very unlikely to conflict with generic troubleshooting or other CLI skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong troubleshooting skill with excellent actionability — concrete commands, decision trees, and a comprehensive issue-symptom table make it highly useful. Workflow clarity is solid with validation checkpoints and feedback loops for recovery. The main weaknesses are minor verbosity in some narrative sections and the monolithic structure that could benefit from splitting detailed subsections into referenced files.
Suggestions
Trim the 'Debugging App Install Failures' section — the example narrative is useful but could be condensed to 2-3 lines while preserving the key insight about the Custom_ prefix.
Consider extracting the Common Issue Patterns table and Headless/CI section into separate referenced files to improve progressive disclosure, keeping only the most critical items inline.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient with good use of decision trees and tables, but some sections are slightly verbose (e.g., the 'Debugging App Install Failures' example narrative, the Recovery Strategies section with obvious steps like 'clear node_modules and reinstall'). The pre-escalation checklist adds marginal value for Claude. Overall mostly lean but could be tightened. | 2 / 3 |
Actionability | Provides concrete, executable commands throughout — specific CLI commands with flags, environment variable names, config file formats with exact YAML structure, and curl examples. The diagnostic tree, troubleshooting table, and step-by-step procedures give Claude precise actions to take for each scenario. | 3 / 3 |
Workflow Clarity | Multi-step processes are clearly sequenced with explicit validation checkpoints (e.g., 'validate incrementally', 'deploy after each addition', the two-phase deployment explanation). The quick diagnosis decision tree provides clear branching logic. Recovery strategies include ordered steps with verification. The manifest issues workflow includes an incremental fix-and-validate feedback loop. | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear section headers and a logical flow from quick diagnosis to detailed troubleshooting. However, at ~200 lines with no bundle files, some sections (like the detailed app install debugging example or the comprehensive common issues table) could be split into referenced files. References to external skills like 'see ui-development' are mentioned but not linked. For a standalone file this is acceptable but not optimal. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 8 / 11 Passed | |
- Repository
- CrowdStrike/foundry-skills
- Commit
e7fa026
- 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.