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:
Hermes Agent
+48
-9
@@ -1,7 +1,7 @@
|
||||
---
|
||||
name: better-search
|
||||
description: Medium-depth web research dispatcher — delegates to the research profile for a 3-move search flow (initial search → AI evaluation → condense). File-only delivery. Trigger phrases: "better search", "do a better search".
|
||||
version: 1.0.1
|
||||
description: 'Medium-depth web research dispatcher — delegates to the research profile for a 3-move search flow (initial search → AI evaluation → condense). File-only delivery. Trigger phrases: "better search", "do a better search".'
|
||||
version: 1.1.0
|
||||
author: Hermes Agent
|
||||
metadata:
|
||||
hermes:
|
||||
@@ -107,6 +107,38 @@ The research agent writes the result file to
|
||||
`~/workspace/research/results/<YYYY-MM-DD>-<slug>.md`. The operator reads it
|
||||
with `cat` or their preferred reader.
|
||||
|
||||
### Variant: agent needs the results itself (multi-step research chains)
|
||||
|
||||
The §5 default is fire-and-forget — the operator reads the file. But when the
|
||||
*agent* needs the research output to feed a downstream step (e.g. collecting
|
||||
3 layer-research files, then sending the digest to Claude for adversarial
|
||||
review), the agent must collect the results itself. Pattern (used successfully
|
||||
2026-07-07 for a 3-layer AI-video landscape research chain):
|
||||
|
||||
1. **Dispatch each question as a background terminal process** with
|
||||
`notify_on_complete=true`. One question per dispatch (the 3-loop cap is
|
||||
per-dispatch). Run them in parallel — they're independent.
|
||||
```bash
|
||||
terminal(background=true, notify_on_complete=true,
|
||||
command="cd ~/workspace/research && hermes -p research -s better-search-research chat -q \"<question>\" -Q --max-turns 50 --yolo 2>&1 | tail -5")
|
||||
```
|
||||
2. **Wait for each to finish** via `process(action='wait', session_id=...)`.
|
||||
The `tail -5` keeps stdout small — the real deliverable is the result file,
|
||||
not the terminal output. Capture the `session_id` from the final stdout
|
||||
line for the operator's reference.
|
||||
3. **Read the result files** from `~/workspace/research/results/` with
|
||||
`read_file` (sorted by mtime: `ls -t ~/workspace/research/results/ | head`).
|
||||
The files are the authoritative output — the terminal stdout is just a
|
||||
summary + session_id.
|
||||
4. **Proceed with the downstream step** (digest, Claude review, plan-writing)
|
||||
using the file contents.
|
||||
|
||||
This variant does NOT violate the no-poll/no-background rule (§7 pitfall 4) —
|
||||
that rule is about not stranding the *operator* with a pending research job
|
||||
they have to babysit. When the agent is the consumer and is actively working
|
||||
the chain, background dispatch + wait is correct. The fire-and-forget rule
|
||||
still applies when the operator is the audience.
|
||||
|
||||
## §6 No-Resume Rule
|
||||
|
||||
**No `--resume`.** The dispatcher reports `session_id` for the operator's
|
||||
@@ -135,7 +167,9 @@ iterative drilling on the same evidence matters, use `deep-research` instead
|
||||
to the operator immediately after capturing the session_id. It does NOT run
|
||||
the research in the background, does NOT periodically check whether the
|
||||
result file has appeared, and does NOT auto-deliver the result inline or to a
|
||||
chat platform.
|
||||
chat platform. (Exception: the agent-needs-results variant in §5 — when the
|
||||
agent is the consumer and actively working a multi-step chain, background
|
||||
dispatch + wait is correct.)
|
||||
|
||||
5. **Max 3 clarifying questions (see §4).** Multi-part questions get condensed
|
||||
into a single noun-phrase question or split into separate dispatches.
|
||||
@@ -149,12 +183,15 @@ iterative drilling on the same evidence matters, use `deep-research` instead
|
||||
other ordinary English — they collide with normal agent tasks on dev/code
|
||||
profiles.
|
||||
|
||||
8. **Do NOT second-guess the dispatch command.** The command `research -s
|
||||
better-search-research chat -q "..." -Q --max-turns 50 --yolo` is verified
|
||||
and correct. `research` is a profile alias at `~/.local/bin/research` — it
|
||||
works from any directory. Do NOT assume it doesn't exist and fall back to
|
||||
doing the search yourself. The dispatcher's ONLY job is to run this command
|
||||
and report the session_id — never substitute your own search.
|
||||
8. **The `-p` flag exists. Do NOT hallucinate that it doesn't.** Some models
|
||||
(observed: minimax-m3:cloud) read the dispatch command, decide `-p` is a
|
||||
"wrong flag," and fall back to running the search themselves with SearXNG
|
||||
MCP — bypassing the entire dispatcher. This is a hallucination. `hermes -p
|
||||
<profile>` is a standard Hermes CLI feature. If you're unsure, run `hermes
|
||||
--help` to verify — do NOT assume the command is wrong and silently
|
||||
substitute your own approach. The dispatcher MUST run the command as
|
||||
written in §3. If the command fails, report the actual error — don't
|
||||
fabricate a reason not to run it.
|
||||
|
||||
## §8 See Also
|
||||
|
||||
@@ -164,3 +201,5 @@ iterative drilling on the same evidence matters, use `deep-research` instead
|
||||
Use for quick factual lookups.
|
||||
- `ask-hermes` — persistent peer Hermes agent for delegated work. Use for
|
||||
general-purpose delegation, not research-specific flows.
|
||||
- `nordvpn` — VPN management. The methodology skill auto-reconnects VPN on
|
||||
SearXNG engine failure to get a fresh IP before retrying.
|
||||
|
||||
Reference in New Issue
Block a user