firecrawl-debug-bundle
Collect Firecrawl debug evidence for support tickets and troubleshooting. Use when encountering persistent issues, preparing support tickets, or collecting diagnostic information for Firecrawl problems. Trigger with phrases like "firecrawl debug", "firecrawl support bundle", "collect firecrawl logs", "firecrawl diagnostic".
80
77%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/firecrawl-pack/skills/firecrawl-debug-bundle/SKILL.mdQuality
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 strong completeness and distinctiveness. It clearly communicates when to use the skill and provides explicit trigger phrases. The main weakness is that the specific actions/capabilities could be more concrete — listing what evidence is actually collected (e.g., logs, config files, error traces) would strengthen the specificity.
Suggestions
Add more specific concrete actions describing what is collected, e.g., 'Gathers server logs, configuration files, error traces, and API response samples for Firecrawl debug evidence.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (Firecrawl debug evidence) and mentions some actions like 'collect debug evidence' and 'preparing support tickets', but doesn't list multiple specific concrete actions (e.g., what logs are collected, what diagnostic checks are run, what output is produced). | 2 / 3 |
Completeness | Clearly answers both 'what' (collect Firecrawl debug evidence for support tickets and troubleshooting) and 'when' (encountering persistent issues, preparing support tickets, collecting diagnostic information) with explicit trigger phrases. | 3 / 3 |
Trigger Term Quality | Excellent trigger term coverage with natural phrases users would say: 'firecrawl debug', 'firecrawl support bundle', 'collect firecrawl logs', 'firecrawl diagnostic', plus contextual triggers like 'persistent issues', 'support tickets', and 'troubleshooting'. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct niche — specifically targets Firecrawl debug/diagnostic evidence collection. The combination of 'Firecrawl' + 'debug'/'diagnostic'/'support bundle' makes it highly unlikely to conflict with other 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, actionable skill with executable code throughout and a clear purpose. Its main weaknesses are the lack of explicit validation checkpoints between steps (e.g., verifying the bundle directory was created, checking if the API test succeeded before proceeding) and the ambiguity about whether steps 1-3 are meant to be a single continuous script or separate executions sharing state. The content could be slightly more concise by removing the redundant Error Handling table.
Suggestions
Clarify whether steps 1-3 are a single script or separate commands — currently BUNDLE_DIR is set in step 1 but referenced in steps 2-3 without re-declaration, which would fail if run separately.
Add a validation checkpoint after Step 2 (e.g., 'If HTTP_CODE is not 200, check API key and network before proceeding') to create a feedback loop for the most common failure point.
Remove or consolidate the 'Error Handling' table since it merely restates what's already evident from the script steps, saving tokens.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary elements like the 'Error Handling' table which just restates what's already obvious from the script steps, and the Overview section explains what the script does rather than just showing it. The 'Current State' dynamic checks at the top are a nice touch though. | 2 / 3 |
Actionability | Fully executable bash scripts and TypeScript code are provided throughout. Commands are copy-paste ready with proper error handling (set -euo pipefail), real API endpoints, and concrete curl commands with proper headers. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced (1-5) and the workflow is logical, but there are no explicit validation checkpoints between steps. There's no 'verify the bundle was created correctly' step, no feedback loop if the API connectivity test fails, and the scripts across steps 1-3 depend on a shared BUNDLE_DIR variable but there's no note about running them as a single script vs. sequentially. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear sections, but the inline bash scripts are quite long and could benefit from being referenced as downloadable files. The 'Next Steps' reference to firecrawl-rate-limits is good, and the Resources section provides useful links, but the main content is somewhat monolithic for what it covers. | 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 — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
70e9fa4
- 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.