AF firecrawl-scrape
Extract clean markdown from any URL, including JavaScript-rendered SPAs. Use this skill whenever the user provides a URL and wants its content, says "scrape", "grab", "fetch", "pull", "get the page", "extract from this URL", or "read this webpage". Handles JS-rendered pages, multiple concurrent URLs, and returns LLM-optimized markdown. Use this instead of WebFetch for any webpage content extraction.
Extract clean markdown from any URL, including JavaScript-rendered SPAs.
As a process F 39/100 · Will not run — References files that are not bundled: firecrawl-cli, ../firecrawl-search/SKILL.md, ../firecrawl-interact/SKILL.md
How to improve
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: firecrawl-cli - warning
missing-refreference to a missing file: ../firecrawl-search/SKILL.md - warning
missing-refreference to a missing file: ../firecrawl-interact/SKILL.md - warning
missing-refreference to a missing file: ../firecrawl-download/SKILL.md
Process rating: all ten parameters 39/100
- 0Tools and files. 4 referenced file(s) missing: firecrawl-cli, ../firecrawl-search/SKILL.md, ../firecrawl-interact/SKILL.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 70When it triggers. States when to use, but not when not to
- 85Steps. 12 steps, 1 vague phrases
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 778 tokens
- 100Running it twice. No mutating operations
- low The response is described with custom markup (3 tags): a typed call is more reliable
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +5Description quotes 4 example trigger phrases
- +3Description length 402: enough signal without eating the budget
- +4Structure: 6 headings
- +3Step-by-step instructions: 12 items
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 77.