task-orchestrator-cron-heartbeat-subagent
v1.0.2Unified Task Orchestration Hub v2 - Integrates Heartbeat, Cron, Subagent and Task Management. Provides task identification, standardized setup, execution tra...
⭐ 0· 45·0 current·0 all-time
byChloechiien@chloechien511-cloud
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description match the files and instructions: templates, README, and Python utilities implement cron/heartbeat/subagent task identification and helper workflows; required binary (openclaw) and use of ~/.openclaw config are reasonable for the stated purpose.
Instruction Scope
SKILL.md tells the agent to read ~/.openclaw/openclaw.json, copy templates, write workspace/memory files and run local scripts (e.g., check_cron_config.py); these actions are within scope but will read local OpenClaw configuration and can create scheduled cron tasks that send messages — users should confirm placeholders (accountId, user IDs, channel) are replaced before running commands.
Install Mechanism
No install spec or remote downloads are present (instruction-only with bundled scripts), so nothing arbitrary is fetched or executed on install; code is provided as plain Python files under the skill directory.
Credentials
The package declares no secrets or environment variables (SKILL.md metadata references the openclaw binary), and the scripts operate on local config paths under the user's home directory — no unrelated credentials are requested.
Persistence & Privilege
Skill is not always-enabled and does not request system-wide privileges, but its runtime actions (creating cron tasks that send messages) can perform observable actions on behalf of the user — ensure account/channel placeholders are correct and confirm actions before allowing autonomous invocation.
Assessment
This skill appears to be what it says: a local helper for scheduling and heartbeat/subagent orchestration. Before installing or giving it autonomous invocation, review the bundled scripts (especially scripts/check_cron_config.py) to confirm they do not call external endpoints or echo secrets, and replace all template placeholders ({YOUR_USER_ID}, {CHANNEL}, {AGENT_ID}, {ACCOUNT_ID}) before executing any openclaw cron add commands. Also check ~/.openclaw/openclaw.json and the intended accountId to avoid sending messages from the wrong bot, and test the scripts in a non-production environment first.Like a lobster shell, security has layers — review code before you run it.
latestvk97cdkn3qp00k3rrwcmhagnwf184ce85
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
