Hey summon - provider
by @thomasansems
Provides human-help support to AI agents via HeySummon by monitoring requests, sending notifications, and handling provider replies through a secure platform.
clawhub install heysummon-providerπ About This Skill
HeySummon Provider Skill
You are a human-help provider for AI agents via HeySummon.
Setup
Step 1: Configure .env
Check if .env exists in {baseDir}. If not, copy from .env.example:
cp {baseDir}/.env.example {baseDir}/.env
Required variables:
HEYSUMMON_BASE_URL β Platform URL (cloud: https://cloud.heysummon.ai, self-hosted: user provides)HEYSUMMON_API_KEY β Provider key (hs_prov_...) from the dashboardHEYSUMMON_NOTIFY_TARGET β Chat ID for notificationsStep 2: Validate key
The API key MUST start with hs_prov_. Reject keys with hs_cli_ prefix β those are client keys.
Step 3: Start the watcher
bash {baseDir}/scripts/setup.sh
To stop: bash {baseDir}/scripts/teardown.sh
Architecture
AI Agent β HeySummon Platform β SSE β Watcher β OpenClaw β Notification
All communication flows through the platform. No direct infrastructure access.
Scripts
| Script | Purpose |
|--------|---------|
| scripts/setup.sh | Start the event watcher |
| scripts/teardown.sh | Stop the watcher |
| scripts/mercure-watcher.sh | SSE listener β notifications via OpenClaw |
| scripts/reply-handler.sh | Reply by refCode: reply-handler.sh HS-XXXX "response" |
| scripts/respond.sh | Reply by request ID: respond.sh |
Reply-to-Respond
When the user replies to a π¦ notification, parse the refCode (HS-XXXX) from the quoted message and use reply-handler.sh. Always forward immediately β no AI processing, no confirmation.
Statuses
| Status | Meaning |
|---|---|
| pending | Waiting for provider |
| active | Conversation in progress |
| responded | Provider sent a response |
| closed | Closed by either party |
| expired | No response within 72 hours |
βοΈ Configuration
Step 1: Configure .env
Check if .env exists in {baseDir}. If not, copy from .env.example:
cp {baseDir}/.env.example {baseDir}/.env
Required variables:
HEYSUMMON_BASE_URL β Platform URL (cloud: https://cloud.heysummon.ai, self-hosted: user provides)HEYSUMMON_API_KEY β Provider key (hs_prov_...) from the dashboardHEYSUMMON_NOTIFY_TARGET β Chat ID for notificationsStep 2: Validate key
The API key MUST start with hs_prov_. Reject keys with hs_cli_ prefix β those are client keys.
Step 3: Start the watcher
bash {baseDir}/scripts/setup.sh
To stop: bash {baseDir}/scripts/teardown.sh