/4 CONNECTED STEPS
Retrieve evidence and diagnose empty results
Choose a suitable retrieval route and distinguish missing evidence from broken extraction or ignored filters.
Download complete workflow .md ↓Use with your AI
Complete workflow download included with library membership. Try the free starters without signup.
What you need
A known source or query, required fields, a working fetch tool and access appropriate to the source.
Why these fit together
Response inspection chooses the route; diagnostics explain empty bodies; filter tests prevent false absence; stored responses make later parsing reproducible.
Follow this order
Choose HTML extraction or a JSON API
Choose extraction from the actual response format.
Diagnose an empty scrape before giving up
Inspect response evidence before declaring content absent.
Validate API filters before trusting absence
Prove filtering and pagination before interpreting absence.
Retain raw API responses for later parsing
Persist source responses for inspection and later parsing.
Give this task to your AI
Use the Retrieve evidence and diagnose empty results workflow. My task and inputs are supplied below. Read the prerequisites and check your available tools. Follow the core steps in order, passing the actual output of each step to the next. Adapt installation and commands to this environment; do not copy another agent's configuration blindly. If a required tool or input is missing, identify it before that step. Run the completion check and report observed results and unresolved work.
Setup to provide or build
One supported HTTP/fetch client, stored response fixtures, a retrieval receipt schema and pagination handling. Private search is an optional runtime.
Check the result
Known positive and negative cases behave differently; ignored filters, navigation shells and access failures produce distinct receipts.
Curated implementation workflow. End-to-end execution must be verified in your environment.
Optional additions
Load these only when your task needs them.