Automated summary
This skill provides TypeScript patterns for detecting and redacting personal data, defining retention periods, and implementing GDPR/CCPA access and deletion requests inside a FireCrawl integration.
Strengths
- Ships ready-to-use regex patterns for emails, phone numbers, SSNs, and credit cards
- Includes a data classification table (PII, sensitive, business, public) with matching handling rules
- Gives concrete examples of DSAR export, user deletion, and the audit log retained after deletion
- Describes a scheduled cleanup job that deliberately spares audit and compliance logs
Limitations
- Detection relies on simple regex and misses unstructured or non-US personal data
- The code assumes FireCrawl client methods (getUserData, deleteUser) and a database schema that are not documented
- Does not cover encryption at rest, redaction of LLM output, or cross-border data transfers
Use it when adding PII redaction, retention policies, or GDPR/CCPA request handling to an existing FireCrawl integration.
Skip it if the project does not use FireCrawl, or if you need end-to-end data governance covering encryption and inter-system flows.
Security analysis
SafeThe skill provides guidance and code examples for PII detection, redaction, retention, and GDPR/CCPA compliance with FireCrawl. It does not instruct destructive actions, data exfiltration, obfuscation, or disabling safety features. The allowed tools (Read, Write, Edit) are used only for file editing, and the code examples are illustrative patterns, not commands to execute malicious operations.
No concerns found
How this analysis is madeExamples
Add PII redaction to my FireCrawl request logging so emails and API keys never appear in the logs.Write a scheduled cleanup job that deletes FireCrawl API logs after 30 days but keeps audit logs for 7 years.Implement a GDPR right-to-deletion flow for a FireCrawl user: delete remote data, purge my local cache, and write an audit entry.name: firecrawl-data-handling description: | Implement FireCrawl PII handling, data retention, and GDPR/CCPA compliance patterns. Use when handling sensitive data, implementing data redaction, configuring retention policies, or ensuring compliance with privacy regulations for FireCrawl integrations. Trigger with phrases like "firecrawl data", "firecrawl PII", "firecrawl GDPR", "firecrawl data retention", "firecrawl privacy", "firecrawl CCPA". allowed-tools: Read, Write, Edit version: 1.0.0 license: MIT author: Jeremy Longshore jeremy@intentsolutions.io
FireCrawl Data Handling
Overview
Handle sensitive data correctly when integrating with FireCrawl.
Prerequisites
- Understanding of GDPR/CCPA requirements
- FireCrawl SDK with data export capabilities
- Database for audit logging
- Scheduled job infrastructure for cleanup
Data Classification
| Category | Examples | Handling | |----------|----------|----------| | PII | Email, name, phone | Encrypt, minimize | | Sensitive | API keys, tokens | Never log, rotate | | Business | Usage metrics | Aggregate when possible | | Public | Product names | Standard handling |
PII Detection
const PII_PATTERNS = [
{ type: 'email', regex: /[a-zA-Z0-9._%+-]+@[a-zA-Z0-9.-]+\.[a-zA-Z]{2,}/g },
{ type: 'phone', regex: /\b\d{3}[-.]?\d{3}[-.]?\d{4}\b/g },
{ type: 'ssn', regex: /\b\d{3}-\d{2}-\d{4}\b/g },
{ type: 'credit_card', regex: /\b\d{4}[- ]?\d{4}[- ]?\d{4}[- ]?\d{4}\b/g },
];
function detectPII(text: string): { type: string; match: string }[] {
const findings: { type: string; match: string }[] = [];
for (const pattern of PII_PATTERNS) {
const matches = text.matchAll(pattern.regex);
for (const match of matches) {
findings.push({ type: pattern.type, match: match[0] });
}
}
return findings;
}
Data Redaction
function redactPII(data: Record<string, any>): Record<string, any> {
const sensitiveFields = ['email', 'phone', 'ssn', 'password', 'apiKey'];
const redacted = { ...data };
for (const field of sensitiveFields) {
if (redacted[field]) {
redacted[field] = '[REDACTED]';
}
}
return redacted;
}
// Use in logging
console.log('FireCrawl request:', redactPII(requestData));
Data Retention Policy
Retention Periods
| Data Type | Retention | Reason | |-----------|-----------|--------| | API logs | 30 days | Debugging | | Error logs | 90 days | Root cause analysis | | Audit logs | 7 years | Compliance | | PII | Until deletion request | GDPR/CCPA |
Automatic Cleanup
async function cleanupFireCrawlData(retentionDays: number): Promise<void> {
const cutoff = new Date();
cutoff.setDate(cutoff.getDate() - retentionDays);
await db.firecrawlLogs.deleteMany({
createdAt: { $lt: cutoff },
type: { $nin: ['audit', 'compliance'] },
});
}
// Schedule daily cleanup
cron.schedule('0 3 * * *', () => cleanupFireCrawlData(30));
GDPR/CCPA Compliance
Data Subject Access Request (DSAR)
async function exportUserData(userId: string): Promise<DataExport> {
const firecrawlData = await firecrawlClient.getUserData(userId);
return {
source: 'FireCrawl',
exportedAt: new Date().toISOString(),
data: {
profile: firecrawlData.profile,
activities: firecrawlData.activities,
// Include all user-related data
},
};
}
Right to Deletion
async function deleteUserData(userId: string): Promise<DeletionResult> {
// 1. Delete from FireCrawl
await firecrawlClient.deleteUser(userId);
// 2. Delete local copies
await db.firecrawlUserCache.deleteMany({ userId });
// 3. Audit log (required to keep)
await auditLog.record({
action: 'GDPR_DELETION',
userId,
service: 'firecrawl',
timestamp: new Date(),
});
return { success: true, deletedAt: new Date() };
}
Data Minimization
// Only request needed fields
const user = await firecrawlClient.getUser(userId, {
fields: ['id', 'name'], // Not email, phone, address
});
// Don't store unnecessary data
const cacheData = {
id: user.id,
name: user.name,
// Omit sensitive fields
};
Instructions
Step 1: Classify Data
Categorize all FireCrawl data by sensitivity level.
Step 2: Implement PII Detection
Add regex patterns to detect sensitive data in logs.
Step 3: Configure Redaction
Apply redaction to sensitive fields before logging.
Step 4: Set Up Retention
Configure automatic cleanup with appropriate retention periods.
Output
- Data classification documented
- PII detection implemented
- Redaction in logging active
- Retention policy enforced
Error Handling
| Issue | Cause | Solution | |-------|-------|----------| | PII in logs | Missing redaction | Wrap logging with redact | | Deletion failed | Data locked | Check dependencies | | Export incomplete | Timeout | Increase batch size | | Audit gap | Missing entries | Review log pipeline |
Examples
Quick PII Scan
const findings = detectPII(JSON.stringify(userData));
if (findings.length > 0) {
console.warn(`PII detected: ${findings.map(f => f.type).join(', ')}`);
}
Redact Before Logging
const safeData = redactPII(apiResponse);
logger.info('FireCrawl response:', safeData);
GDPR Data Export
const userExport = await exportUserData('user-123');
await sendToUser(userExport);
Resources
Next Steps
For enterprise access control, see firecrawl-enterprise-rbac.
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/firecrawl-data-handling-ms1aw5cp/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/firecrawl-data-handling-ms1aw5cp' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/firecrawl-data-handling-ms1aw5cp/download' --output '.skill-downloads/firecrawl-data-handling-ms1aw5cp/SKILL.md.part' && mv '.skill-downloads/firecrawl-data-handling-ms1aw5cp/SKILL.md.part' '.skill-downloads/firecrawl-data-handling-ms1aw5cp/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
Tools declared by the author (check availability in your agent): Read, Write, Edit
Original excerpt: Prerequisites
- Understanding of GDPR/CCPA requirements
- FireCrawl SDK with data export capabilities
- Database for audit logging
- Scheduled job infrastructure for cleanup
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/firecrawl-data-handling-ms1aw5cp/SKILL.md' && test -s '.skill-downloads/firecrawl-data-handling-ms1aw5cp/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/firecrawl-data-handling' && cp -R '.skill-downloads/firecrawl-data-handling-ms1aw5cp' '.claude/skills/firecrawl-data-handling'Cursor
test -f '.skill-downloads/firecrawl-data-handling-ms1aw5cp/SKILL.md' && test -s '.skill-downloads/firecrawl-data-handling-ms1aw5cp/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/firecrawl-data-handling' && cp -R '.skill-downloads/firecrawl-data-handling-ms1aw5cp' '.cursor/skills/firecrawl-data-handling'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/firecrawl-data-handling-ms1aw5cp'openskills read 'firecrawl-data-handling-ms1aw5cp'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/firecrawl-data-handling-ms1aw5cp/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
DeFi AMM Security
Security
Security checklist for Solidity AMM contracts, liquidity pools, and swap flows. Covers reentrancy, donation attacks, oracle manipulation, slippage, and integer math.
Semgrep Rule Creator
Security
Creates custom Semgrep rules for detecting security vulnerabilities, bug patterns, and code patterns. Includes test-first methodology, taint mode support, and validation steps. Helps when building targeted static analysis detections.
Dev Toolbar Review Guide
Security
Safety rules for the dev toolbar, PostHog client, and feature flags. Use when reviewing changes to dev-tools and related files, covering environment guards, override cookies, and SSE stream safety.