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".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill firecrawl-debug-bundle82
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 when/what guidance. The main weakness is the lack of specific concrete actions - it describes the general purpose but doesn't detail what specific evidence, logs, or diagnostic information is collected. The description uses proper third-person voice throughout.
Suggestions
Add specific concrete actions like 'Collects API response logs, configuration files, error traces, and system state' to improve specificity
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (FireCrawl debug/support) and general actions ('collect debug evidence', 'diagnostic information'), but doesn't list specific concrete actions like what evidence is collected, what logs are gathered, or what the output format is. | 2 / 3 |
Completeness | Clearly answers both what ('Collect FireCrawl debug evidence for support tickets and troubleshooting') and when ('Use when encountering persistent issues, preparing support tickets, or collecting diagnostic information') with explicit trigger phrases. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'firecrawl debug', 'firecrawl support bundle', 'collect firecrawl logs', 'firecrawl diagnostic'. These are specific, natural phrases a user would actually type. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche focused specifically on FireCrawl debugging and support. The explicit trigger phrases and FireCrawl-specific terminology make it highly unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides actionable, executable bash scripts for creating a FireCrawl debug bundle with good organization and clear references. The main weaknesses are some redundant content (prerequisites, duplicated info in the error handling table) and missing validation steps to verify the bundle contents before submission.
Suggestions
Add a validation step after Step 4 to verify the bundle contents (e.g., `tar -tzf "$BUNDLE_DIR.tar.gz"` and check file sizes)
Remove the prerequisites section - Claude understands SDK installation requirements
Consolidate the error handling table with the Output section to avoid duplication
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some unnecessary elements like the prerequisites section (Claude knows what SDK installation means) and the error handling table which duplicates information already shown in the script. | 2 / 3 |
Actionability | Provides fully executable bash scripts that are copy-paste ready, with specific commands for each step of the debug bundle creation process. The code is complete and functional. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced (1-4) but lacks explicit validation checkpoints. There's no verification that the bundle was created correctly or that the collected data is complete before packaging. The 'Review for sensitive data' step in submission is mentioned but not integrated into the workflow. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections, appropriate length for inline content, and references to external resources (support portal, status page) and related skills (firecrawl-rate-limits) without deep nesting. | 3 / 3 |
Total | 10 / 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.