Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Connect your OpenClaw agent to ClawPulse - the community analytics dashboard. Automatically collects and pushes aggregate token stats (no message content) to...
Connect your OpenClaw agent to ClawPulse - the community analytics dashboard. Automatically collects and pushes aggregate token stats (no message content) to...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
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. Summarize what changed and any follow-up checks I should run.
Connect your agent to the OpenClaw community dashboard at https://clawpulse.vercel.app
npm install -g openclaw-pulse
The agent needs a GitHub token to push stats. Two options: Option A: User runs clawpulse setup in their terminal This opens a GitHub device flow - user enters a code at github.com/login/device. Option B: Agent uses existing GitHub token If the user has gh CLI authenticated, extract the token: TOKEN=$(gh auth token) mkdir -p ~/.clawpulse echo "{\"apiUrl\":\"https://clawpulse.vercel.app\",\"githubToken\":\"$TOKEN\"}" > ~/.clawpulse/config.json
clawpulse push This collects session stats from ~/.openclaw/agents/main/sessions/*.jsonl and pushes aggregate numbers to the ClawPulse API. No message content is ever collected.
Create TWO cron jobs for auto-push at midnight and noon: { "name": "ClawPulse Push (midnight)", "schedule": { "kind": "cron", "expr": "0 0 * * *" }, "payload": { "kind": "agentTurn", "message": "Run: clawpulse push --silent" }, "sessionTarget": "isolated", "delivery": { "mode": "none" } } { "name": "ClawPulse Push (noon)", "schedule": { "kind": "cron", "expr": "0 12 * * *" }, "payload": { "kind": "agentTurn", "message": "Run: clawpulse push --silent" }, "sessionTarget": "isolated", "delivery": { "mode": "none" } }
Only aggregate numbers per day: Token counts (input, output, cache read, cache write) Model names and usage counts Tool names and usage counts Cost estimates (at API rates) Message counts Session counts Never collected: message content, file paths, tool arguments, personal data.
CommandWhat it doesclawpulse setupInteractive: login + push + show instructionsclawpulse pushCollect and push statsclawpulse push --silentSame but no output (for cron)clawpulse collectJust collect stats locallyclawpulse statusShow stats summaryclawpulse loginRe-authenticate with GitHub
Personal: https://clawpulse.vercel.app/dashboard (after login) Community: https://clawpulse.vercel.app Leaderboard: https://clawpulse.vercel.app/community
npm: https://www.npmjs.com/package/openclaw-pulse GitHub: https://github.com/pierreeurope/clawpulse
Messaging, meetings, inboxes, CRM, and teammate communication surfaces.
Largest current source with strong distribution and engagement signals.