v0.20 alpha skill-driven python core

2026-05-06 16:26:41 +08:00
parent d1169646b8
commit db626f1d58
87 changed files with 5213 additions and 2865 deletions
@@ -0,0 +1,53 @@
+---
+name: search-gateway
+description: Use when Deep Research agents or subagents need web, scholar, patent, news, regulatory, or source-discovery search without using platform MCP tools or browser search directly.
+---
+
+# Search Gateway
+
+## Rule
+
+Use the project Python search gateway as the only default search interface. Do not call Tavily MCP, browser MCP, generic web tools, or platform-native search from a subagent unless the user explicitly asks for that escape hatch.
+
+## Commands
+
+Run searches from the repository root:
+
+```bash
+uv run python scripts/search.py "<query>" --route general --json --trace
+uv run python scripts/search.py "<query>" --route scholar --year-low 2020 --json --trace
+uv run python scripts/search.py "<query>" --route news --time-range y --json --trace
+uv run python scripts/search.py "<query>" --route patents --json --trace
+uv run python scripts/search.py "<query>" --profile biomed_literature --json --trace
+```
+
+If `uv` cannot use the user cache in a sandbox, set a local cache:
+
+```bash
+UV_CACHE_DIR=/private/tmp/deep_research_uv_cache uv run python scripts/search.py "<query>" --route general --json --trace
+```
+
+## Routing
+
+- `general`: Exa first, Tavily fallback.
+- `scholar`: Serper Scholar first; use for papers, guidelines, and technical literature.
+- `news`: Serper News first; use for recent industry/current information.
+- `patents`: Serper Google Patents first.
+- `biomed_literature`: scholar plus general discovery.
+
+API keys are loaded from `secrets.env` by `scripts/search.py`; do not ask the user to authorize MCP calls when the env keys are available.
+
+## Subagent Protocol
+
+For evidence packets:
+
+1. Search through `scripts/search.py`, save or summarize the returned JSON in the packet’s `raw_quotes_or_notes`.
+2. Use search hits only as candidate sources; whenever possible, cite the original regulator, guideline, paper, or official document.
+3. Put every used source in `sources` with `id`, `title`, `url`, `tier`, and `score`.
+4. Do not write a final chapter during search; produce structured evidence only.
+
+For chapter assembly:
+
+1. Do not search. Use only `phase2/chapter_briefs`, `phase2/packets`, `phase2/sources.jsonl`, `phase0/extracted`, and `phase1/framework.md`.
+2. Do not create new `source_id`.
+3. If evidence is thin, mark the chapter as needing Phase 2 enrichment instead of filling with generic prose.