Skills Quickstart

This guide walks you through installing a HeySummon skill step-by-step. No deep technical knowledge required.

What are HeySummon Skills?

HeySummon uses two self-contained skills that run on OpenClaw:

• Consumer skill — installed by the AI agent that needs help
• Provider skill — installed by the human expert who answers questions

Each skill is a folder with everything it needs: scripts, config, and lifecycle management.

Installing the Consumer Skill (for AI agents)

Step 1: Get your API key

Ask your provider (the human expert) for a consumer API key. It starts with hs_.

Step 2: Copy the skill folder

cp -r hitlaas-consumer/ ~/your-workspace/skills/hitlaas-consumer/

Step 3: Configure the .env file

cd ~/your-workspace/skills/hitlaas-consumer/
cp .env.example .env

Edit .env and fill in:

HITLAAS_API_KEY=hs_your_key_here
HITLAAS_BASE_URL=https://cloud.heysummon.ai
HITLAAS_MERCURE_HUB=https://your-mercure-hub/.well-known/mercure

Step 4: Run setup

bash setup.sh

That’s it! The skill is now active. When your AI submits a help request, the Mercure watcher will automatically start to listen for responses.

How it works behind the scenes

• submit-request.sh — sends the help request to the platform
• mercure-watcher.sh — auto-starts when a request is submitted, listens for responses via SSE
• The watcher auto-stops 1 hour after the last response or after 72 hours max
• It cleans itself up from pm2 automatically

Installing the Provider Skill (for human experts)

Step 1: Create your provider account

Go to the HeySummon dashboard and sign in.

Step 2: Generate your API key

In the dashboard, create a provider API key. It starts with hs_prov_.

Step 3: Copy the skill folder

cp -r hitlaas-provider/ ~/your-workspace/skills/hitlaas-provider/

Step 4: Configure the .env file

cd ~/your-workspace/skills/hitlaas-provider/
cp .env.example .env

Edit .env and fill in:

HITLAAS_API_KEY=hs_prov_your_key_here
HITLAAS_BASE_URL=https://cloud.heysummon.ai
HITLAAS_MERCURE_HUB=https://your-mercure-hub/.well-known/mercure

Step 5: Run setup

bash setup.sh

The provider skill starts:

• mercure-watcher.sh — persistent background process listening for new requests
• reply-handler.sh — processes your replies and sends them back encrypted

Both run via pm2 and are managed by setup.sh/teardown.sh.

Removing a Skill

To cleanly remove either skill:

cd ~/your-workspace/skills/hitlaas-consumer/  # or hitlaas-provider
bash teardown.sh

This stops all background processes and removes them from pm2.

Key Format Reference

Troubleshooting

Skill not receiving messages?

• Check that the Mercure Hub URL is correct in your .env
• Run pm2 list to see if the watcher is running
• Check logs with pm2 logs hitlaas-watcher

Watcher stopped unexpectedly?

• Consumer watchers auto-stop after 72 hours or 1 hour after the last response
• Re-submit a request to start a new watcher

Setup.sh fails?

• Make sure you have Node.js installed
• Check that pm2 is available: npm install -g pm2