aboutsummaryrefslogtreecommitdiff
path: root/skills
diff options
context:
space:
mode:
authoramankumarsingh77 <amankumarsingh7702@gmal.com>2026-05-07 12:54:12 +0530
committeramankumarsingh77 <amankumarsingh7702@gmal.com>2026-05-07 12:54:12 +0530
commit4052e6e6afef1dc20146765963dea7c0289ca401 (patch)
tree3734869a41404e6ebcc85d35789aea4684d8e5b0 /skills
parentbd197399048212112d2337b4799ebe20de01a6e8 (diff)
release: v0.5.0 — browser_console tool for JS error/console diagnostics
Diffstat (limited to 'skills')
-rw-r--r--skills/pi-browser-harness/SKILL.md7
1 files changed, 7 insertions, 0 deletions
diff --git a/skills/pi-browser-harness/SKILL.md b/skills/pi-browser-harness/SKILL.md
index 7de9800..69105a8 100644
--- a/skills/pi-browser-harness/SKILL.md
+++ b/skills/pi-browser-harness/SKILL.md
@@ -21,6 +21,9 @@ What do you need to know?
├─ Network behavior on the current page?
│ → browser_network_requests
│
+ ├─ JS errors / why did nothing happen after an action?
+ │ → browser_console (DIAGNOSTIC — only when something looks broken)
+ │
└─ Visual rendering (layout / colors / chart drew correctly)?
→ browser_screenshot (LAST RESORT — pixels only)
```
@@ -31,6 +34,10 @@ Pass `@(x,y)` from `browser_snapshot` straight to `browser_click`. No screenshot
You're attached to the user's real Chrome — never launch your own. If auth is required, stop and ask the user. If `browser_page_info` returns a dialog, handle it first with `browser_handle_dialog`.
+## Diagnosing a "nothing happened" moment
+
+When an action runs but the page didn't change, capture `browser_console`'s `nextCursor` *before* the action, take the action, then call `browser_console({ sinceSeq: <cursor> })` after — this isolates what your action caused from what was already there. Pair with `browser_network_requests({ sinceMs: 5000 })` to see if an API call fired and failed. The console buffer is page-scoped: it clears on tab switch, capacity 500.
+
## Temporary scripts
When a workflow repeats 3+ times or needs Node.js APIs, write a script to disk and run it with `browser_run_script`. Scripts get a `daemon` binding for direct CDP access — much faster than chaining tool calls.