aboutsummaryrefslogtreecommitdiff
path: root/skills/pi-browser-harness
diff options
context:
space:
mode:
authoramankumarsingh77 <amankumarsingh7702@gmail.com>2026-07-08 21:41:47 +0530
committeramankumarsingh77 <amankumarsingh7702@gmail.com>2026-07-08 21:41:47 +0530
commit1c12b43a674ae51a39c430ed8cfa138dbdf4dc71 (patch)
tree45d256d77c478d5cd1bae0620d5965d889bf4cce /skills/pi-browser-harness
parent3f65a30e3f78e749110ad0d883e265b3a59dec13 (diff)
feat: add deep-research skill, /deep-research command, fix web-search-researcher
deep-research skill fans out to isolated web-search-researcher subagents (now using browser_web_search + browser_read_page instead of the non-existent web_search/web_fetch), coverage-driven loop with a hard ceiling, synthesizes a cited Markdown report. /deep-research command as explicit entry point. Docs updated. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Diffstat (limited to 'skills/pi-browser-harness')
-rw-r--r--skills/pi-browser-harness/SKILL.md8
1 files changed, 8 insertions, 0 deletions
diff --git a/skills/pi-browser-harness/SKILL.md b/skills/pi-browser-harness/SKILL.md
index e4221be..60e23e0 100644
--- a/skills/pi-browser-harness/SKILL.md
+++ b/skills/pi-browser-harness/SKILL.md
@@ -21,6 +21,12 @@ What do you need to know?
├─ Network behavior on the current page?
│ → browser_network_requests
│
+ ├─ Find pages on the web about a topic?
+ │ → browser_web_search (ranked SERP — links only; follow up with browser_read_page)
+ │
+ ├─ An article's main content as clean text?
+ │ → browser_read_page (reader mode — a url or an owned targetId → boilerplate stripped)
+ │
├─ JS errors / why did nothing happen after an action?
│ → browser_console (DIAGNOSTIC — only when something looks broken)
│
@@ -30,6 +36,8 @@ What do you need to know?
Pass `@(x,y)` from `browser_snapshot` straight to `browser_click`. No screenshot round-trip.
+`browser_web_search` and `browser_read_page` each run in their own isolated tab and never touch the user's current tab. For a multi-source question that needs a synthesized, cited report, use the **deep-research** skill (or `/deep-research <question>`): it fans out isolated `web-search-researcher` subagents over both tools and writes a source-cited Markdown report.
+
## Connection Setup
Browser control is **on-demand** — the daemon does NOT start automatically.