Skip to content
Skills Library
Programming · Analysis

firecrawl-debug-bundle

/firecrawl-debug-bundle

Assemble a minimal, redacted Firecrawl diagnostic package for internal triage or vendor support. Use when a failure needs escalation without exposing keys or captured content. Trigger with "Firecrawl debug bundle", "Firecrawl support evidence", or "collect Firecrawl diagnostics".

Licence
MIT
Last repository change
26.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Assemble a minimal, redacted Firecrawl diagnostic package for internal triage or vendor support. Use when a failure needs escalation without exposing keys or captured content. Trigger with "Firecrawl debug bundle", "Firecrawl support evidence", or "collect Firecrawl diagnostics".

Triggers from the description

Firecrawl debug bundleFirecrawl support evidencecollect Firecrawl diagnostics

Arguments

/firecrawl-debug-bundle <request-or-job-id> <output-directory>
Original author description

Assemble a minimal, redacted Firecrawl diagnostic package for internal triage or vendor support. Use when a failure needs escalation without exposing keys or captured content. Trigger with "Firecrawl debug bundle", "Firecrawl support evidence", or "collect Firecrawl diagnostics".

How it works

  1. Overview
  2. Prerequisites
  3. Current Contract
  4. Authentication
  5. Instructions
  6. Tool Discipline
  7. Approval Boundaries
  8. Output
  9. Error Handling
  10. Examples
Original SKILL.md headings · 65 lines, 500 words
SKILL.md preview
---
name: firecrawl-debug-bundle
description: >-
  Assemble a minimal, redacted Firecrawl diagnostic package for internal triage or vendor support. Use when a failure needs escalation without exposing keys or captured content. Trigger with "Firecrawl debug bundle", "Firecrawl support evidence", or "collect Firecrawl diagnostics".
allowed-tools: Read,Glob,Grep,Write,Edit
argument-hint: "<request-or-job-id> <output-directory>"
version: 1.12.0
license: MIT
author: Jeremy Longshore <jeremy@intentsolutions.io>
tags: [saas, firecrawl, diagnostics, security]
model: inherit
effort: high
compatibility: "Designed for Claude Code; Firecrawl Cloud work requires network access"
---
# Firecrawl Privacy-Safe Support Evidence

## Overview

Produce structured evidence that can reproduce or classify a failure without dumping the repository, environment, request headers, URLs, or response bodies.

## Prerequisites

- The target repository or integration path and the requested operator outcome.
- The source authorization, data classification, and environment policy.
- Current Firecrawl documentation, credentials only when needed, and an owner for approvals.

## Current Contract

Useful evidence includes SDK/runtime version, v2 operation, timestamps, opaque request/job/webhook IDs, HTTP status, documented error/code, queue/job state, pagination state, option names, and content-free metrics. Firecrawl support does not need a broad tarball or the API key.

## Authentication

For authenticated Cloud operations, inject FIRECRAWL_API_KEY from an approved
secret manager. REST requests use Authorization: Bearer with the key. Never print,
commit, transmit, or place a key in a URL. Keyless access is suitable only where
the current documentation explicitly allows it and the workload accepts its
limits; production workflows should make identity and team ownership explicit.

## Instructions

1. Confirm the incident owner, destination, approved evidence fields, retention window, and whether target URLs themselves are sensitive.
2. Collect package/runtime versions, operating context, v2 endpoint or SDK method, UTC timestamps, and a normalized option-name list.
3. Record status, error/code/details after redaction, response headers on an allowlist, request/job/webhook IDs, queue state, pagination cursor presence, counts, sizes, timings, and metadata.statusCode distribution.
4. Represent URLs with approved host labels or salted hashes; never include credentials, cookies, Authorization, custom headers, page content, screenshots, uploaded bytes, prompts, or extracted values.
5. Run secret, token-pattern, URL-query, email, and content-leak scans over the proposed bundle. Manually inspect the exact files.
6. Create a manifest with file hashes, collector version, redaction policy, known omissions, recipient, expiry, and deletion owner.
7. Require recipient approval, transmit through the approved channel, and record deletion or ticket linkage.

## Tool Discipline

Use Read, Glob, and Grep to inspect code, configuration, tests, and evidence. Use
Write/Edit only for approved implementation or documentation changes. Do not call
Firecrawl, rotate keys, change account settings, scrape a target, or deploy merely
because this skill was invoked.

## Approval Boundaries

Require approval before collecting from production, including a hostname or request option value, sharing outside the organization, or extending bundle retention.

## Output

Return a small manifest and redacted structured evidence files, scan results, omissions, recipient and purpose, expiry, hashes, and cleanup receipt. Do not create a repository or home-directory archive.

## Error Handling

- Redaction scan finds a secret or content fragment: quarantine and rebuild the bundle.
- Evidence cannot distinguish request from origin failure: add status and metadata distributions, not bodies.
- Support requests raw credentials or unrestricted content: refuse and escalate through the security owner.

## Examples

- "Prepare evidence for a crawl timeout" returns timings, state, IDs, and redacted option names.
- "Zip the whole repo and .env" is refused and replaced with a minimal allowlisted manifest.

## Resources

Read [official Firecrawl evidence](references/official-docs.md) before relying on
an endpoint, SDK method, plan limit, price, retention option, or self-hosted release.
Files in this package (2)
  • SKILL.md 4 KB
  • references/official-docs.md 2 KB

Versions

RepositoryScoreLicence
This page · jeremylongshore/tons-of-skills-marketplace100MIT
HelixDevelopment/agent100MIT

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version a73488e4fdae (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100linear-debug-bundle
    Assemble a minimal, redacted Linear integration diagnostic bundle for internal or vendor escalation. Use when a failure needs reproducible evidence without exposing tokens or workspace content. Trigger with "collect Linear diagnostics", "build a Linear debug bundle", or "escalate Linear API issue".
  • 100fireflies-debug-bundle
    Assemble a content-free Fireflies diagnostic bundle covering identity, operation shape, limits, latency, processing state, and deployment configuration. Use when performing escalation without exposing meetings or secrets. Trigger with "Fireflies debug bundle", "collect Fireflies…
  • 100firecrawl-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…
  • 100firecrawl-common-errors
    Diagnose and fix FireCrawl common errors and exceptions. Use when encountering FireCrawl errors, debugging failed requests, or troubleshooting integration issues. Trigger with phrases like "firecrawl error", "fix firecrawl", "firecrawl not working", "debug firecrawl".

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.