stock-search v1.0.0 (new) + stock-search-research v1.0.0 (new) + ltx-video-pipeline, better-search, better-search-research, deep-web-research, ai-brain-kb, ai-vid-stock updates (2026-07-22)
This commit is contained in:
@@ -1,7 +1,7 @@
|
||||
---
|
||||
name: better-search-research
|
||||
description: Medium-depth web research methodology — 3-move flow (initial search → AI evaluation → condense), 3-loop cap, /tmp ledger, file-only delivery. Opt-in skill for the research profile.
|
||||
version: 1.0.1
|
||||
version: 1.1.0
|
||||
author: Hermes Agent
|
||||
metadata:
|
||||
hermes:
|
||||
@@ -69,9 +69,25 @@ No credibility tier — the ledger is just URL + key facts + date. Tier judgment
|
||||
happens in the body, not the ledger.
|
||||
|
||||
**SearXNG error handling:** If `mcp_searxng_searxng_web_search` returns 0
|
||||
results or errors, count it as one search and either retry once with a different
|
||||
framing or proceed to Move 3 with what was found. Don't burn a refinement slot
|
||||
on retries.
|
||||
results or errors:
|
||||
|
||||
1. **First failure:** Reconnect VPN to get a fresh IP, then retry the SAME
|
||||
search once. The VPN reconnect procedure is:
|
||||
```bash
|
||||
nordvpn disconnect && nordvpn connect us <different_city>
|
||||
```
|
||||
Use a different city from the current connection to avoid the same server.
|
||||
Verify with `nordvpn status`. This is authorized without asking — the
|
||||
nordvpn skill grants reconnect permission. Do NOT change any other VPN
|
||||
settings.
|
||||
2. **Second failure (after VPN reconnect):** Retry once with a different
|
||||
framing (different keywords, category, or time_range).
|
||||
3. **Third failure:** Proceed to Move 3 with what was found. Don't burn a
|
||||
refinement slot on retries.
|
||||
|
||||
Count each search attempt (including retries) toward the total. The VPN
|
||||
reconnect is a recovery step, not a search — it doesn't count against the
|
||||
3-loop cap.
|
||||
|
||||
**Filesystem assumption:** `mkdir -p ~/workspace/research/results` and all `~`
|
||||
paths in Move 3 assume the research profile shares the same filesystem as the
|
||||
|
||||
Reference in New Issue
Block a user