Individual skill

firecrawl-data-handling

Validate, minimize, classify, deduplicate, retain, and dispose of Firecrawl documents and extracted JSON safely. Use when building downstream storage, RAG, or analytics pipelines. Trigger with "store Firecrawl data", "Firecrawl RAG ingestion", or "clean scraped content".

plugins/saas-packs/firecrawl-pack/skills/firecrawl-data-handling/SKILL.md

Read pinned source

Source commit 0500b275e963c027f6b410e8c49c0446945c574e

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 12, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
2,917
Repository last updated
Nov 12, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt
# Firecrawl Content Data Handling

## Overview

Treat scraped pages, metadata, screenshots, file parses, and model-extracted JSON as untrusted external data. Preserve provenance while storing only what the approved use case requires.

## 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

SDKs return document data directly; REST returns it under data. metadata.sourceURL and metadata.statusCode are essential provenance and quality fields. storeInCache, zeroDataRetention, lockdown, screenshots, raw HTML, file upload, and persistent browser profiles create materially different data-handling obligations.
Back to top