Task Router Skill
Task Router
usewhisper autohook OpenClaw Skill
Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.
SkillHub CLI
skillhub install alinxus/usewhisper-autohookInspect the source and compatibility requirements, then follow its installation steps.
Give your agent the source link and ask it to inspect instructions and dependencies before explaining the installation steps.
This skill is a thin wrapper designed to make "automatic memory" easy:
get_whisper_context(user_id, session_id, current_query) for pre-response context injectioningest_whisper_turn(user_id, session_id, user_msg, assistant_msg) for post-response ingestionIt defaults to the token-saving settings you almost always want:
compress: true
compression_strategy: "delta"
use_cache: true
include_memories: true
It also persists the last context_hash locally (per api_url + project + user_id + session_id) so delta compression works by default without you needing to pass previous_context_hash.
npx clawhub@latest install usewhisper-autohook
Set env vars wherever OpenClaw runs your agent:
WHISPER_CONTEXT_API_URL=https://context.usewhisper.dev
WHISPER_CONTEXT_API_KEY=YOUR_KEY
WHISPER_CONTEXT_PROJECT=openclaw-yourname
Notes:
WHISPER_CONTEXT_API_URL is optional (defaults to https://context.usewhisper.dev).Add this to your agent's system instruction (or equivalent):
Before you think or respond to any message:
1) Call get_whisper_context with:
user_id = "telegram:{from_id}"
session_id = "telegram:{chat_id}"
current_query = the user's message text
2) If the returned context is not empty, prepend it to your prompt as:
"Relevant long-term memory:\n{context}\n\nNow respond to:\n{user_message}"
After you generate your final response:
1) Call ingest_whisper_turn with the same user_id and session_id and:
user_msg = the full user message
assistant_msg = your full final reply
Always do this. Never skip.
If you are not on Telegram, keep the same structure: the important part is that user_id and session_id are stable.
If you cannot c...
These signals come from indexed source analysis and may lag behind changes. Check the current source files.
Two commands meant to be called on every agent turn:
get_whisper_context (pre-query)ingest_whisper_turn (post-response)Install:
npx clawhub@latest install usewhisper-autohook
Env:
WHISPER_CONTEXT_API_URL=https://context.usewhisper.dev
WHISPER_CONTEXT_API_KEY=YOUR_KEY
WHISPER_CONTEXT_PROJECT=openclaw-yourname
One-liners:
node usewhisper-autohook.mjs get_whisper_context --current_query "USER_MESSAGE" --user_id "telegram:FROM_ID" --session_id "telegram:CHAT_ID"
echo '{ "user_msg": "USER_MESSAGE", "assistant_msg": "ASSISTANT_REPLY" }' | node usewhisper-autohook.mjs ingest_whisper_turn --session_id "telegram:CHAT_ID" --user_id "telegram:FROM_ID" --turn_json -
# usewhisper-autohook (OpenClaw Skill)
This skill is a thin wrapper designed to make "automatic memory" easy:
- `get_whisper_context(user_id, session_id, current_query)` for pre-response context injection
- `ingest_whisper_turn(user_id, session_id, user_msg, assistant_msg)` for post-response ingestion
It defaults to the token-saving settings you almost always want:
- `compress: true`
- `compression_strategy: "delta"`
- `use_cache: true`
- `include_memories: true`
It also persists the last `context_hash` locally (per `api_url + project + user_id + session_id`) so delta compression works by default without you needing to pass `previous_context_hash`.
## Install (ClawHub)
```bash
npx clawhub@latest install usewhisper-autohook
```
## Setup
Set env vars wherever OpenClaw runs your agent:
```bash
WHISPER_CONTEXT_API_URL=https://context.usewhisper.dev
WHISPER_CONTEXT_API_KEY=YOUR_KEY
WHISPER_CONTEXT_PROJECT=openclaw-yourname
```
Notes:
- `WHISPER_CONTEXT_API_URL` is optional (defaults to `https://context.usewhisper.dev`).
- The helper will auto-create the project on first use if it does not exist yet.
## The "Auto Loop" Prompt (Copy/Paste)
Add this to your agent's **system instruction** (or equivalent):
```text
Before you think or respond to any message:
1) Call get_whisper_context with:
user_id = "telegram:{from_id}"
session_id = "telegram:{chat_id}"
current_query = the user's message text
2) If the returned context is not empty, prepend it to your prompt as:
"Relevant long-term memory:\n{context}\n\nNow respond to:\n{user_message}"
After you generate your final response:
1) Call ingest_whisper_turn with the same user_id and session_id and:
user_msg = the full user message
assistant_msg = your full final reply
Always do this. Never skip.
```
If you are not on Telegram, keep the same structure: the important part is that `user_id` and `session_id` are stable.
## If Your Agent Still Replays Full Chat History (Proxy Mode)
If you cannot c...# usewhisper-autohook (OpenClaw Skill)
Two commands meant to be called on every agent turn:
- `get_whisper_context` (pre-query)
- `ingest_whisper_turn` (post-response)
Install:
```bash
npx clawhub@latest install usewhisper-autohook
```
Env:
```bash
WHISPER_CONTEXT_API_URL=https://context.usewhisper.dev
WHISPER_CONTEXT_API_KEY=YOUR_KEY
WHISPER_CONTEXT_PROJECT=openclaw-yourname
```
One-liners:
```bash
node usewhisper-autohook.mjs get_whisper_context --current_query "USER_MESSAGE" --user_id "telegram:FROM_ID" --session_id "telegram:CHAT_ID"
```
```bash
echo '{ "user_msg": "USER_MESSAGE", "assistant_msg": "ASSISTANT_REPLY" }' | node usewhisper-autohook.mjs ingest_whisper_turn --session_id "telegram:CHAT_ID" --user_id "telegram:FROM_ID" --turn_json -
```Task Router
Register, communicate, and earn on the x402hub AI agent marketplace. Use when an agent needs to register on x402hub, browse or claim bounties, submit deliverables, send messages to other agents via x402 Relay,...
Real-time event bus for AI agents. Publish, subscribe, and share live signals across a network of agents with Unix-style simplicity.
OpenClaw integration guidance for CAPTCHAS Agent API, including OpenResponses tool schemas and plugin tool registration.