firecrawl-advanced-troubleshooting
Apply FireCrawl advanced debugging techniques for hard-to-diagnose issues. Use when standard troubleshooting fails, investigating complex race conditions, or preparing evidence bundles for FireCrawl support escalation. Trigger with phrases like "firecrawl hard bug", "firecrawl mystery error", "firecrawl impossible to debug", "difficult firecrawl issue", "firecrawl deep debug".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill firecrawl-advanced-troubleshooting78
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
89%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 well-structured skill description with excellent trigger term coverage and clear completeness. The explicit 'Use when' and 'Trigger with' clauses make selection criteria unambiguous. The main weakness is that the specific debugging techniques and actions could be more concrete (e.g., what specific advanced techniques are applied).
Suggestions
Add 2-3 specific concrete debugging actions, such as 'analyze request timing logs', 'trace async callback chains', or 'capture network waterfall diagnostics' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (FireCrawl debugging) and mentions some actions like 'investigating complex race conditions' and 'preparing evidence bundles for support escalation', but lacks comprehensive concrete actions like specific debugging techniques or tools used. | 2 / 3 |
Completeness | Clearly answers both what (advanced debugging techniques for hard-to-diagnose issues, race conditions, evidence bundles) and when (standard troubleshooting fails, complex race conditions, support escalation) with explicit 'Use when' and 'Trigger with' clauses. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger phrases users would say: 'firecrawl hard bug', 'firecrawl mystery error', 'firecrawl impossible to debug', 'difficult firecrawl issue', 'firecrawl deep debug'. These are realistic user expressions for this scenario. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche: specifically for FireCrawl advanced/difficult debugging scenarios, explicitly differentiated from standard troubleshooting. The specific trigger phrases and 'when standard troubleshooting fails' clause minimize conflict with basic FireCrawl skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid advanced troubleshooting skill with excellent actionable code examples and comprehensive coverage of debugging techniques. The main weaknesses are the length (could benefit from splitting detailed code into reference files) and the lack of explicit validation checkpoints in the workflow for what is inherently a complex, iterative debugging process.
Suggestions
Add explicit validation checkpoints in the Instructions section, e.g., 'Verify bundle contains all expected files before proceeding' and 'If layer isolation doesn't identify failure, return to evidence collection with extended time window'
Move the detailed TypeScript classes (TimingAnalyzer, FireCrawlConcurrencyChecker) to a separate ADVANCED-CODE.md reference file to reduce main skill length
Add a decision tree or flowchart for when to use each technique (timing analysis vs memory analysis vs race condition detection) based on symptom patterns
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary elements like the 'Prerequisites' section listing things Claude would know to check, and some verbose comments in code. The support template section could be more compact. | 2 / 3 |
Actionability | Provides fully executable bash scripts and TypeScript code that can be directly used. The debug bundle script, layer-by-layer testing, and timing analysis are all copy-paste ready with concrete implementations. | 3 / 3 |
Workflow Clarity | The 'Instructions' section provides a clear 4-step sequence, but validation checkpoints are implicit rather than explicit. There's no feedback loop for what to do if evidence collection fails or if layer isolation doesn't identify the issue. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but the skill is quite long (200+ lines) with detailed code that could be split into separate reference files. The 'Next Steps' reference to another skill is good, but inline content is heavy. | 2 / 3 |
Total | 9 / 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.
Validation — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 13 / 16 Passed | |
- 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.