CtrlK
BlogDocsLog inGet started
Tessl Logo

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".

67

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with concrete, executable diagnostic code and a clear step sequence, but it is held back by duplicated content, missing validation before destructive packaging/cleanup, and a dangling cross-reference.

Suggestions

Remove the redundant 'Current State' preamble and the 'Error Handling' table, both of which restate content already in Steps 1–2 and the Output section, to tighten token usage.

Add an explicit validation checkpoint before Step 5: verify the bundle directory is non-empty and confirm redaction succeeded (e.g., grep for unredacted API keys) before running tar and the destructive 'rm -rf'.

Either create the referenced firecrawl-rate-limits skill/file or remove the dangling 'see firecrawl-rate-limits' pointer, and add a URL to the bare 'Firecrawl Status' resource entry.

DimensionReasoningScore

Conciseness

Mostly efficient executable code, but it is padded with redundancy: the "Current State" section re-runs checks duplicated in Step 2, and the "Error Handling" table restates items already covered by the steps and Output section.

2 / 3

Actionability

Provides fully executable, copy-paste-ready bash and TypeScript with specific curl/jq/sed commands and redaction logic, matching the executable-code anchor rather than vague or pseudocode guidance.

3 / 3

Workflow Clarity

Steps 1–5 are clearly sequenced, but the destructive Step 5 ("rm -rf \"$BUNDLE_DIR\"") and redaction-critical packaging lack an explicit validation/verification checkpoint, which the rubric caps at 2 for destructive or batch operations.

2 / 3

Progressive Disclosure

The skill is a well-sectioned but monolithic single file with no bundle files; the "Next Steps" reference to firecrawl-rate-limits is dangling (no such file exists) and "Firecrawl Status" is listed without a URL, so navigation is only partially realized.

2 / 3

Total

9

/

12

Passed

Description

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.

The description is concise, written in third person, and clearly states both what the skill does and when to use it with natural trigger phrases. It is specific to the Firecrawl niche with low conflict risk.

DimensionReasoningScore

Specificity

Names a concrete action ("Collect Firecrawl debug evidence for support tickets and troubleshooting") plus several specific diagnostic actions (collecting evidence, preparing tickets, gathering diagnostic info), matching the multiple-concrete-actions anchor rather than the single-domain score-2 anchor.

3 / 3

Completeness

Explicitly 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 triggers, so it is not capped at 2.

3 / 3

Trigger Term Quality

Provides explicit natural trigger phrases users would say — "firecrawl debug", "firecrawl support bundle", "collect firecrawl logs", "firecrawl diagnostic" — giving good coverage rather than only some relevant keywords.

3 / 3

Distinctiveness Conflict Risk

Targets a distinct product niche (Firecrawl) with Firecrawl-specific triggers, making it unlikely to fire for unrelated skills; it is clearly distinguishable rather than merely "somewhat specific".

3 / 3

Total

12

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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

14

/

16

Passed

Repository
jeremylongshore/claude-code-plugins-plus-skills
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.