Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub ยท Content Creation
Hey summon
Request expert help by submitting queries to the HeySummon platform, which routes them to registered human providers for assistance.
skill openclawclawhub Free
Request expert help by submitting queries to the HeySummon platform, which routes them to registered human providers for assistance.
โฌ 0 downloads โ
0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- README.md, SKILL.md, scripts/setup.sh, scripts/auto-sync.sh, scripts/check-status.sh, scripts/platform-watcher.sh
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- Download the package from Yavira.
- Extract it into a folder your agent can access.
- Paste one of the prompts below and point your agent at the extracted folder.
New install
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
Upgrade existing
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 0.1.0-beta
Provenance
- Publisher
- thomasansems
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
HeySummon Consumer Skill
When you (an AI agent) get stuck, request help from a human expert via HeySummon. When someone requests help, the skill submits a request to the HeySummon platform. The platform matches it to a registered provider (human expert) who can assist. Users can say "Hey summon John Doe to help" or "Hey summon a Python expert to help". The skill then routes the request to the appropriate provider based on the registered providers in providers.json.
Step 1: Configure Environment
Create .env in the skill directory with your HeySummon platform details: HEYSUMMON_BASE_URL=http://localhost:3445 HEYSUMMON_API_KEY=hs_cli_your_key_here HEYSUMMON_NOTIFY_MODE=message HEYSUMMON_NOTIFY_TARGET=your_chat_id Platform Options: Self-hosted: Use your local/server URL (e.g., http://localhost:3445) Cloud: Use https://cloud.heysummon.ai Get API Key: Go to your HeySummon dashboard Navigate to Users โ Create user profile (or ask provider for client key) Create a client key (starts with hs_cli_...) โ ๏ธ Security: API keys starting with hs_prov_ are provider keys (not client keys). These will be rejected.
Step 2: Register Provider(s)
bash scripts/add-provider.sh "hs_cli_your_key" "FriendlyName" This fetches provider info from the platform and stores it locally. You can register multiple providers for routing. List registered providers: bash scripts/list-providers.sh
Step 3: Start Event Watcher
bash scripts/setup.sh This starts a persistent SSE listener that connects to the platform's event stream (/api/v1/events/stream). You'll receive notifications when providers respond. To stop: bash scripts/teardown.sh
Architecture
HeySummon Platform API (/api/v1/events/stream) โ SSE Event Stream โ Platform Watcher (pm2) โ OpenClaw Notification โ Your Chat All communication flows through the platform API. E2E encryption is handled server-side.
Scripts
ScriptPurposesetup.shStart the platform event watcher (pm2/nohup)teardown.shStop the watcherplatform-watcher.shSSE listener โ sends notifications via OpenClawsubmit-request.shSubmit a help requestadd-provider.shRegister a providerlist-providers.shList registered providerscheck-status.shCheck request statuscrypto.mjsE2E encryption: keygen, encrypt, decryptauto-sync.shGit auto-sync (cron job)
Submit a Help Request
To a specific provider: bash scripts/submit-request.sh "Your question" '[{"role":"user","content":"context"}]' "ProviderName" To default provider (from .env): bash scripts/submit-request.sh "Your question" '[{"role":"user","content":"context"}]' Provider routing: The script matches provider names case-insensitively from providers.json. If no match is found, it shows available providers and exits.
Wait for Response
The platform watcher handles real-time notifications: ๐ Key exchange โ provider connected ๐ฉ New message โ provider responded ๐ Closed โ conversation ended
Check Status (Fallback)
bash scripts/check-status.sh <REQUEST_ID>
When to Use
Use HeySummon when you are truly stuck: Ambiguous requirements needing clarification Domain expertise required Blocked by something you can't resolve autonomously
Request Statuses
StatusMeaningpendingWaiting for provider to acceptactiveKey exchange done โ conversation in progressclosedClosed by either partyexpiredNo response within 72 hours
Environment Variables
VariableDefaultDescriptionHEYSUMMON_BASE_URLhttp://localhost:3445Platform API URLHEYSUMMON_API_KEY(required)Client API key (hs_cli_...)HEYSUMMON_NOTIFY_MODEmessageNotification mode: message or fileHEYSUMMON_NOTIFY_TARGET(required for message mode)Chat ID for notificationsHEYSUMMON_KEY_DIR{skill}/.keysDirectory for encryption keypairsHEYSUMMON_REQUESTS_DIR{skill}/.requestsDirectory for active request trackingHEYSUMMON_PROVIDERS_FILE{skill}/providers.jsonProvider registry file
Security
โ API keys stored in .env (gitignored) โ Keypairs stored in .keys/ (gitignored) โ Providers stored in providers.json (gitignored) โ All paths relative to skill directory โ E2E encryption handled by platform โ No hardcoded credentials in code Never commit: .env providers.json .keys/ directory .requests/ directory
Category context
Writing, remixing, publishing, visual generation, and marketing content production.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
4 Scripts2 Docs
- SKILL.md
- README.md
- scripts/auto-sync.sh
- scripts/check-status.sh
- scripts/platform-watcher.sh
- scripts/setup.sh