Execute FireCrawl secondary workflow: Core Workflow B. Use when implementing secondary use case, or complementing primary workflow. Trigger with phrases like "firecrawl secondary workflow", "secondary task with firecrawl".
From firecrawl-packnpx claudepluginhub nickloveinvesting/nick-love-plugins --plugin firecrawl-packThis skill is limited to using the following tools:
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Details PluginEval's skill quality evaluation: 3 layers (static, LLM judge), 10 dimensions, rubrics, formulas, anti-patterns, badges. Use to interpret scores, improve triggering, calibrate thresholds.
Secondary workflow for FireCrawl. Complements the primary scraping workflow by focusing on structured data extraction and scheduled monitoring use cases. Use this skill when you need to extract specific fields from pages using a defined schema, set up recurring crawls for change detection, or convert an entire documentation site into a searchable knowledge base on a regular cadence.
firecrawl-install-auth setupfirecrawl-core-workflow-aDefine the JSON schema describing the fields you want to extract from each page. FireCrawl's structured extraction mode uses this schema to return typed data rather than raw Markdown, which is more reliable for downstream database ingestion. Specify the target URLs or URL patterns and configure the recurrence schedule if monitoring for content changes.
// Step 1 implementation
Execute the structured extraction job and receive typed JSON responses for each scraped page. Validate the extracted fields against your schema to catch pages where the expected content was absent or malformed. For monitoring jobs, compare the current extraction against the previous snapshot to identify what changed.
// Step 2 implementation
Persist the structured results to your database or data pipeline. For change detection scenarios, trigger notifications or downstream workflows when meaningful diffs are detected. Archive historical snapshots for audit purposes and rotate older snapshots according to your retention policy.
// Step 3 implementation
| Aspect | Workflow A | Workflow B |
|---|---|---|
| Use Case | Primary | Secondary |
| Complexity | Medium | Lower |
| Performance | Standard | Optimized |
// Complete workflow example
// Error handling code
For common errors, see firecrawl-common-errors.