本文へ移動
cccskills
無料GitHub で公開

deep-research

Procedure for answering a question with a thorough, cross-checked, cited web-research report using the Keenable search + fetch tools.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md2.0 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

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.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Spin up a live local Omnigent server + runner and exercise the native Antigravity (agy) TUI harness (antigravity-native) end-to-end — launch the real `agy` CLI via `omnigent antigravity`, drive turns through the web UI, smoke-test, and bug-bash. Load when developing, testing, or debugging the antigravity-native harness (omnigent/inner/antigravity_native_executor.py, omnigent/antigravity_native.py, antigravity_native_bridge.py, antigravity_native_rpc.py, antigravity_native_reader.py, antigravity_native_launch.py) or its agy launch / RPC mirror / tmux delivery / OAuth / MCP-relay behavior. NOT the in-process `antigravity` Gemini SDK harness.

日本語の概要は準備中です。原文の説明を表示しています。

omnigent-ai/omnigent1.1万2026年10月11日 更新

Spin up a live local Omnigent server and exercise the Antigravity (Gemini) SDK harness end-to-end — build antigravity agents, run real turns, smoke-test, and bug-bash. Load when developing, testing, or debugging the antigravity harness (omnigent/inner/antigravity_executor.py, antigravity_harness.py, omnigent/onboarding/antigravity_auth.py) or its auth / model / tool-bridge behavior.

日本語の概要は準備中です。原文の説明を表示しています。

omnigent-ai/omnigent1.1万2026年10月11日 更新

api-docs

無料

Document a module or public API surface (functions, classes, CLI commands, endpoints) from the code itself. Use when the user asks for API reference, to document a module, or to write usage docs for a public interface.

日本語の概要は準備中です。原文の説明を表示しています。

omnigent-ai/omnigent1.1万2026年10月11日 更新

Patterns and templates for generating valid Omnigent agent directories. Load when ready to create files.

日本語の概要は準備中です。原文の説明を表示しています。

omnigent-ai/omnigent1.1万2026年10月11日 更新

changelog

無料

Turn a range of commits or merged PRs into a changelog entry grouped by change type. Use when the user asks for release notes, a changelog, or "what changed" between two points.

日本語の概要は準備中です。原文の説明を表示しています。

omnigent-ai/omnigent1.1万2026年10月11日 更新

Verify the Omnigent CLI's setup/onboarding flow, terminal UI/UX, and critical user journeys in a completely isolated, reproducible loop. Drives the real `omnigent` binary through a PTY (pexpect) inside a throwaway OMNIGENT_CONFIG_HOME / OMNIGENT_DATA_DIR sandbox that never touches the user's real ~/.omnigent, captures ANSI-stripped frames for UX inspection, and proves a change is verifiable via a before→fix→after baseline diff. Load when developing or reviewing a CLI setup/onboarding/REPL/picker change (omnigent/cli.py, omnigent/onboarding/*, omnigent/repl/*, scripts/install_oss.sh), reproducing a cold-start/first-run UX bug, or confirming a fix actually lands. Several agents can run it concurrently on separate worktrees.

日本語の概要は準備中です。原文の説明を表示しています。

omnigent-ai/omnigent1.1万2026年10月11日 更新

omnigent-ai のスキルをすべて見る

このスキルの問題を報告する