Scoville Research

Scoville Research

More links are easy. Better evidence is not.

It usually looks harmless:

• Six articles confirm a release claim. Five copied the sixth, which copied the press release.
• A paper reports a strong benchmark result, so the method is called production-ready before anyone checks the repository, license, or missing implementation pieces.
• A citation is real, current, and topically relevant. It still does not support the sentence attached to it.
• One retrieved page contains instructions for the agent. Apparently the web has promoted itself to project owner.

That is research slop: visible activity without a reliable evidence chain. The result looks researched because the source list is long, while the actual decision still rests on repetition, inference, or an uninspected abstract.

Scoville Research is a read-only Agent Skill for current multi-source web research, GitHub-first implementation discovery, academic literature work, and durable deep research. It routes each question to the evidence that can answer it, preserves contradictions and inspection limits, and stops when the remaining uncertainty is visible and another query would not change the decision.

Do not use it for one known page or paper summary, an ordinary repository inspection, pure brainstorming, planning, implementation, or wording work.

Why "Scoville"?

The family is named for useful signal that remains detectable after dilution. Research accumulates pages quickly. Its useful heat is the smaller evidence chain that survives source tracing, contradiction search, and an honest check of what was actually inspected.

How to use

Name Scoville Research and the actual decision in the request. The Skill chooses the smallest route that can answer it.

**Development** - investigate an implementation landscape rather than compare README feature tables:

Use Scoville Research to find open-source libraries for offline-first conflict handling on Windows. Inspect GitH