hummingbot-heartbeat▌
hummingbot/skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
An OpenClaw cron skill that runs every hour and delivers a formatted Hummingbot status report to your connected chat channel (Telegram, Discord, etc.). Covers API health, Gateway container, active bots/controllers, executors, and portfolio balances.
hummingbot-heartbeat
An OpenClaw cron skill that runs every hour and delivers a formatted Hummingbot status report to your connected chat channel (Telegram, Discord, etc.). Covers API health, Gateway container, active bots/controllers, executors, and portfolio balances.
Installation
clawhub install hummingbot-heartbeat
Or manually clone into your skills directory.
Quick Start
1. Set up the OpenClaw cron job
Ask your OpenClaw agent:
"Set up the hummingbot-heartbeat cron job"
The agent will resolve the skill path and register it with openclaw cron. Or do it manually:
# Replace <SKILL_PATH> with the actual installed path
openclaw cron add \
--name "hummingbot-heartbeat" \
--description "Hourly Hummingbot status check" \
--every 1h \
--announce \
--channel telegram \
--message "Run this and send output verbatim: python3 <SKILL_PATH>/scripts/bot_status.py"
2. Run manually (debug)
python3 scripts/bot_status.py
python3 scripts/bot_status.py --json
Configuration
Set via environment variables or a .env file in the skill directory:
# .env (optional — defaults shown)
HUMMINGBOT_API_URL=http://localhost:8000
API_USER=admin
API_PASS=admin
| Variable | Default | Description |
|---|---|---|
HUMMINGBOT_API_URL |
http://localhost:8000 |
Hummingbot API base URL |
API_USER |
admin |
API username |
API_PASS |
admin |
API password |
Requirements
- Python 3.9+
- Hummingbot API running (see
hummingbot-deployskill) - Docker (optional — Gateway status check skipped if Docker unavailable)
Sample Output
🤖 Hummingbot Status — Feb 28, 2026 09:06 AM
**Infrastructure**
API: ✅ Up (v1.0.1)
Gateway: ✅ Up 17 hours
**Active Bots:** none
**Active Executors:** none
**Portfolio** (total: $187.23)
Token Units Price Value
------------ ----------- ---------- ----------
SOL 2.0639 $81.4996 $168.20
USDC 19.0286 $1.0000 $19.03
What It Checks
| Check | Endpoint | Notes |
|---|---|---|
| API health | GET / |
Returns version |
| Gateway | docker ps | grep gateway |
Skipped if Docker unavailable |
| Active bots | GET /bot-orchestration/status |
Lists controller configs |
| Active executors | POST /executors/search |
Filters out CLOSED/FAILED |
| Portfolio | POST /portfolio/history |
Latest balances with prices |
How to use hummingbot-heartbeat on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add hummingbot-heartbeat
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches hummingbot-heartbeat from GitHub repository hummingbot/skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate hummingbot-heartbeat. Access the skill through slash commands (e.g., /hummingbot-heartbeat) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.4★★★★★38 reviews- ★★★★★Alexander Ghosh· Dec 20, 2024
Solid pick for teams standardizing on skills: hummingbot-heartbeat is focused, and the summary matches what you get after install.
- ★★★★★Ganesh Mohane· Dec 12, 2024
Keeps context tight: hummingbot-heartbeat is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Mateo Ndlovu· Dec 12, 2024
hummingbot-heartbeat is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Zaid Zhang· Dec 8, 2024
I recommend hummingbot-heartbeat for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Shikha Mishra· Dec 4, 2024
Solid pick for teams standardizing on skills: hummingbot-heartbeat is focused, and the summary matches what you get after install.
- ★★★★★Ava Choi· Nov 27, 2024
hummingbot-heartbeat reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Yash Thakker· Nov 23, 2024
We added hummingbot-heartbeat from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Hassan Khan· Nov 11, 2024
We added hummingbot-heartbeat from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Ava Abbas· Oct 18, 2024
Registry listing for hummingbot-heartbeat matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Dhruvi Jain· Oct 14, 2024
hummingbot-heartbeat fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 38