BF firecrawl-build-search
Integrate Firecrawl `/search` into product code and agent workflows. Use when an app needs discovery before extraction, when the feature starts with a query instead of a URL, or when the system should search the web and optionally hydrate result content.
Integrate Firecrawl /search into product code and agent workflows.
As a process F 47/100 · Will not run — References files that are not bundled: ../firecrawl-build-scrape/SKILL.md, ../firecrawl-build-interact/SKILL.md, ../firecrawl-build/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-build-scrape/SKILL.md - warning
missing-refreference to a missing file: ../firecrawl-build-interact/SKILL.md - warning
missing-refreference to a missing file: ../firecrawl-build/SKILL.md - note
frontmatter-keyunknown frontmatter key "inputs"
Process rating: all ten parameters 47/100
- 0Tools and files. 3 referenced file(s) missing: ../firecrawl-build-scrape/SKILL.md, ../firecrawl-build-interact/SKILL.md, ../firecrawl-build/SKILL.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 55Failures and branches. 1 branches
- 70When it triggers. States when to use, but not when not to
- 100Steps. 24 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 597 tokens
- 100Running it twice. No mutating operations
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
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +2Single-language instructions
- +3Description length 254: enough signal without eating the budget
- +4Structure: 8 headings
- +3Step-by-step instructions: 24 items
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 68.