Claude Code Plugins

Community-maintained marketplace

Feedback

Deep web scraping, screenshots, PDF parsing, and website crawling using Firecrawl API. Use when you need deep content extraction from web pages, page interaction is required (clicking, scrolling, etc.), or you want screenshots or PDF parsing.

Install Skill

Shared

Installs to .agents/skills, used by Codex, Amp, Warp, Cursor, OpenCode, and more.

CodexAmp
Warp
CursorOpenCode
Cline
Gemini CLI
GitHub Copilot
Personal

Available across projects.

$npx skills-installer add @sickn33/antigravity-awesome-skills/firecrawl-scraper --client shared
Project

Writes to .agents/skills.

$npx skills-installer add @sickn33/antigravity-awesome-skills/firecrawl-scraper -p --client shared
Note: Review the skill instructions before using it.

SKILL.md

name firecrawl-scraper
description Deep web scraping, screenshots, PDF parsing, and website crawling using Firecrawl API. Use when you need deep content extraction from web pages, page interaction is required (clicking, scrolling, etc.), or you want screenshots or PDF parsing.
risk unknown
source community
date_added 2026-02-27

firecrawl-scraper

Overview

Deep web scraping, screenshots, PDF parsing, and website crawling using Firecrawl API

When to Use

  • When you need deep content extraction from web pages
  • When page interaction is required (clicking, scrolling, etc.)
  • When you want screenshots or PDF parsing
  • When batch scraping multiple URLs

Installation

npx skills add -g BenedictKing/firecrawl-scraper

Step-by-Step Guide

  1. Install the skill using the command above
  2. Configure Firecrawl API key
  3. Use naturally in Claude Code conversations

Examples

See GitHub Repository for examples.

Best Practices

  • Configure API keys via environment variables

Troubleshooting

See the GitHub repository for troubleshooting guides.

Related Skills

  • context7-auto-research, tavily-web, exa-search, codex-review

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.