Procedure for answering a question with a thorough, cross-checked, cited web-research report using the Keenable search + fetch tools.
Scanned 8/31/2026
Install to Claude Code
npx -y skills add omnigent-ai/omnigent --skill deep-research --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Deep Research?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/omnigent-ai-deep-research)More formats (shields.io, HTML) on the badges page.
---
name: deep-research
description: Procedure for answering a question with a thorough, cross-checked, cited web-research report using the Keenable search + fetch tools.
---
# deep-research — cited, cross-checked web research
Use this for any question that needs current, verifiable information from the
web. The deliverable is a synthesized answer where every load-bearing claim is
backed by a source you actually read.
## Tools
- `search_web_pages(query, [site], [published_after], [published_before], [mode])`
— discover candidate sources. Write the `query` as a natural-language
description of the ideal page, not keywords. Use `mode: pro` (default).
- `fetch_page_content(url, [max_chars])` — read the full page (markdown). A
search snippet is NEVER sufficient evidence — fetch before you cite.
## Procedure
1. **Plan.** Break the question into 3-6 focused sub-queries that together
cover it. For contested or high-stakes questions, plan at least two
independent angles.
2. **Search.** Run `search_web_pages` per sub-query. Prefer primary sources;
use `published_after` for anything time-sensitive.
3. **Read.** `fetch_page_content` on the 2-3 most promising results per
sub-query. Quote/cite only what you read, not what a snippet implied.
4. **Cross-check.** Verify every load-bearing claim against ≥2 INDEPENDENT
sources (independent = different owners, not mirrors of one another). When
sources disagree, surface the disagreement rather than picking silently.
5. **Synthesize.** Write a structured answer. Each non-obvious claim gets an
inline citation to the URL you fetched. Separate "well-supported" from
"uncertain / single-source".
6. **Cite.** End with a `Sources` list of the URLs you actually fetched.
## Notes
- Don't answer from prior knowledge with a disclaimer — search and read first.
- If coverage is thin or sources conflict irreconcilably, say so explicitly;
an honest "the evidence is mixed" beats false confidence.
- Keep each sub-query narrow enough that a couple of fetches resolve it.
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.