Heartbeat Kit
v1.0.0Pre-built HEARTBEAT.md templates for common agent tasks: email checking, calendar monitoring, weather alerts, system health, news digests. Drop in and go.
⭐ 0· 265·2 current·3 all-time
byShadow Rose@theshadowrose
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
The skill is advertised as a set of HEARTBEAT.md templates. The repository contains only templates and docs and asks for no binaries, installs, or env vars — which is appropriate for a templates-only package.
Instruction Scope
Templates instruct the agent to 'check unread email', 'monitor social platforms', 'watch calendars', 'check repos', etc. Those are high-level checks (expected for templates) but the SKILL.md does not specify how to authenticate or which connectors to use. That ambiguity means an agent will need configured integrations/credentials to perform these checks or will prompt the user/agent to obtain them.
Install Mechanism
No install spec, no downloads, and no code files. This is low-risk: nothing is written to disk by an installer and there are no third-party packages being pulled in by the skill itself.
Credentials
The skill declares no required environment variables or credentials, which is consistent for templates. However, many included templates (email, calendar, social, project-status) implicitly require API keys or account access to function. Users should expect to configure their own credentials or connectors; the skill itself does not request or store them.
Persistence & Privilege
always is false and there is no instruction to modify agent/system-wide settings. The skill is a passive template collection and does not request persistent privileges or self-enabling behavior.
Assessment
This is a safe, templates-only package, but review and customize before enabling. Specifically: (1) Inspect each template and remove checks you don't want (e.g., social monitoring) — templates can cause your agent to attempt to access external services. (2) Do not paste sensitive credentials into a shared workspace file; use your agent's secure connector/secret store instead. (3) Verify which integrations your agent will use (email provider, calendar, Git hosting, social APIs) and supply only the minimal credentials/scopes needed. (4) Test in a non-production workspace first (or with dummy accounts) to confirm behavior and alert thresholds. (5) If you don't want external network access, disable or delete templates that require API access (news, social, email, calendar, project-status).Like a lobster shell, security has layers — review code before you run it.
automationvk97bmbjes9wnjpvmzfx1rjbp2182krmfhealthvk97bmbjes9wnjpvmzfx1rjbp2182krmfheartbeatvk97bmbjes9wnjpvmzfx1rjbp2182krmfheartbeat, monitoring, health, automation, proactivevk97bmbjes9wnjpvmzfx1rjbp2182krmflatestvk97bmbjes9wnjpvmzfx1rjbp2182krmfmonitoringvk97bmbjes9wnjpvmzfx1rjbp2182krmfproactivevk97bmbjes9wnjpvmzfx1rjbp2182krmf
License
MIT-0
Free to use, modify, and redistribute. No attribution required.