- Home
- Skills
- Productivity
- Not Found? Prove It — Live-Surface Absence Verifier for Catalogs, Inboxes & Marketplaces
Not Found? Prove It — Live-Surface Absence Verifier for Catalogs, Inboxes & Marketplaces
Script-based negative guards exist for codebases and PDFs: they run a command per item and count N of N.
$1
Works with the AI Agents you already use
Not Found? Prove It — Live-Surface Absence Verifier for Catalogs, Inboxes & Marketplaces
Example session with this skill installed
Check whether my paperback is really missing from the marketplace — a previous report said it is not listed anywhere.
- Read your context and instructions
- Compiled the not found prove
Verdict: FOUND UNDER VARIANT — live in Active under the title-only form with the author indexed Last, First. The original search used the subtitle form, which the site index does not tokenize. Coverage: 6 variants, 2 surfaces, Active/Sold/Ended, filters reset, second route (direct author page) checked.
Connects securely to your tools. The creator never sees your data.
About this skill
"There is no such listing." "That book isn't on the site." "No email about it." "The portal doesn't exist." "It's sold out everywhere." On live surfaces — a marketplace, a bookshelf, an inbox, a dashboard, a directory, a storefront — a confident not found is the most expensive sentence an agent produces, because it usually does not mean the thing is absent. It means the agent searched one spelling, on one tab, under one default filter, on a results page that silently capped at 20, and stopped.
Script-based negative guards exist for codebases and PDFs: they run a command per item and count N of N. They cannot help here, because live surfaces have no command to run. The item hides under a name variant, a former title, a second account, the Sold tab instead of Active, an archived folder, a placeholder page that returns a friendly 200, or a search index that has not caught up. This skill is the absence-verification discipline for those surfaces: expand the variants, exhaust the surfaces, log the coverage, triangulate by a second independent route, and only then issue one of four honest verdicts — never a bare "not found."
Built from a live operation where false negatives caused real damage: a benefits portal confidently declared non-existent that the user then opened himself, documents declared missing that were already in the Downloads folder, and a listing reported absent that was live under a variant author name.
- Before reporting that a listing, product, book, record, message, account feature, page, or person is not found, does not exist, is unavailable, sold out, or has no results.
- When a first search came back empty and the answer matters — money, a deadline, a filing, a purchase, a customer, a deliverable.
- When a previous "not found" was wrong, or the user disputes it.
- When several surfaces could hold the item (multiple accounts, stores, tabs, folders, sites) and nobody has checked them all.
- As a standing gate: any absence or totality claim ("none", "no X", "all Y are…") in a report must pass this workflow before the report ships.
No search proves a universal negative; the strongest verdict is NOT FOUND — COVERAGE COMPLETE for the surfaces and variants in the ledger. Login-walled or capped surfaces cap the verdict at COULD NOT VERIFY with the blocker named.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 3 days ago
The agent must be able to search or browse the target surfaces, or you supply their contents.
Permissions
Instruction-only workflow. The agent searches only the surfaces the user names, under the user's own accounts and access.