Research current technical facts or find prior art before a substantial new build. Use primary sources and local evidence; a small local lookup does not require a full research sweep.
Installs into .claude/skills of the current project.
Are you the author of Deepsearch?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/nguyenhuy190303-deepsearch)
---
name: deepsearch
description: "Research current technical facts or find prior art before a substantial new build. Use primary sources and local evidence; a small local lookup does not require a full research sweep."
---
# Deep search
Choose depth from the unresolved claim and cost of being wrong. Existing evidence can settle a small question; do not open every research channel automatically.
- Current API/library behavior, pricing, versions, benchmarks or a sourced comparison: [research workflow](references/research-workflow.md). Search only applicable channels and prefer official docs/source plus local measurement.
- A substantial new pipeline, training method or system where an existing artifact could change the build: [prior-art workflow](references/prior-art-workflow.md). Check hard fit requirements before popularity or repository quality.
Label evidence T1 official/source, T2 maintainer issue/changelog, T3 community, T0 recollection. Recollection alone is not evidence. State which material claims remain unverified and what was not searched; do not turn a narrow verified answer into an unrelated report. No credentials, internal hostnames or private data in public search queries.
