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
—
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 trigger terms, clear 'when' guidance, and excellent distinctiveness due to the specific product focus. Its main weakness is that the 'what' could be more specific about the concrete actions performed (e.g., what logs are collected, what output is produced). Overall it's a solid description that would perform well in skill selection.
Suggestions
Add more specific concrete actions to improve specificity, e.g., 'Collects server logs, API response traces, configuration snapshots, and error reports for Firecrawl debug evidence.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (Firecrawl debug evidence) and some actions ('collect debug evidence', 'preparing support tickets', 'collecting diagnostic information'), but doesn't list multiple specific concrete actions like what evidence is collected, what formats are produced, or what diagnostic steps are taken. | 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 listed. | 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'. Also includes contextual triggers like 'persistent issues', 'support tickets', and 'troubleshooting'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche — Firecrawl-specific debug/diagnostic collection. The specific product name 'Firecrawl' combined with 'debug evidence' and 'support bundle' makes it very 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 debug bundle skill with executable code and a clear purpose. Its main weaknesses are the fragmented bash scripts that share state across steps without being presented as a unified script, and the lack of explicit validation checkpoints (e.g., verifying the bundle contents before packaging). The content could be tighter by removing the redundant Error Handling table and consolidating the bash steps.
Suggestions
Consolidate Steps 1-3 and 5 into a single continuous bash script to avoid confusion about shared variables like BUNDLE_DIR, or explicitly note they should be combined into one script.
Add an explicit validation checkpoint before Step 5 (e.g., 'Verify summary.txt contains expected sections: ls -la $BUNDLE_DIR/ and review summary.txt before packaging').
Remove or condense the 'Error Handling' table since it merely restates what each step already collects — replace with a brief checklist if needed.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly 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 somewhat redundantly describes what the steps already show. The 'Current State' dynamic checks at the top are a nice touch but the overall content could be tightened. | 2 / 3 |
Actionability | The skill provides fully executable bash scripts and TypeScript code that are copy-paste ready. Each step has concrete commands with proper error handling (set -euo pipefail), specific API endpoints, and real curl commands with proper headers. The diagnostic scrape TypeScript is complete and runnable. | 3 / 3 |
Workflow Clarity | The steps are clearly sequenced (create dir → collect info → capture errors → run diagnostic → package), but there are no explicit validation checkpoints or feedback loops. Steps 1-3 are bash fragments that depend on a shared BUNDLE_DIR variable but aren't presented as a single continuous script, which could cause confusion. There's no 'verify the bundle contents before sharing' validation step beyond a print statement. | 2 / 3 |
Progressive Disclosure | The content is reasonably well-structured with clear sections, but it's somewhat monolithic — the diagnostic scrape TypeScript and the full bash scripts could be referenced as separate files rather than inlined. The reference to 'firecrawl-rate-limits' at the end is a good cross-reference, but the Resources section is minimal. No bundle files are provided to offload detail. | 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
3a2d27d
- 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.