
from zylos-core1,169
Schedule and dispatch one-time, recurring and interval tasks to an agent runtime via the C4 comm-bridge for autonomous execution.
The Task Scheduler skill lets an agent create, manage and dispatch scheduled work — one-time jobs, cron-like recurring tasks, and interval/polling jobs — through the C4 comm-bridge. It monitors agent state, resolves timezone configuration, queues tasks by priority, and hands work off to Claude when the runtime is available.
Use this skill when you need the agent to perform actions at a future time, run periodic checks, or orchestrate delayed workflows (reminders, maintenance jobs, periodic reports, polling external services). It is appropriate for autonomous agents that must reliably run tasks outside an interactive session.
Primarily built for Claude-based local runtimes using the C4 comm-bridge; usable with other agent frameworks that can accept dispatched tasks via a comm-bridge interface.
Task scheduler skill for the Zylos agent ecosystem. Provides a CLI for creating one-time, cron, and interval tasks, plus a daemon that dispatches them via a C4 comm-bridge. Code is well-structured with parameterized SQL, safe subprocess calls, and proper error handling. Scripts couldn't execute because the runner skips .js files. Tightly coupled to the Zylos ecosystem (requires C4 comm-bridge, activity-monitor) which limits standalone use.
better-sqlite3cron-parserchrono-nodedotenvClean security posture: parameterized queries, execFileSync (no shell injection), no hardcoded creds, no destructive commands, no telemetry. Architecture is solid with good module separation but SKILL.md references (add.md, update.md, etc.) were not included in the fetched content. Useful for Zylos users but the ecosystem dependency limits broader adoption.
Zylos Shell Channel
Channel skill that connects a CLI REPL to a Claude-like backend via a Unix socket, routing user input to the agent and delivering responses back to the REPL.
Check Context
Report current context/window and token usage across supported runtimes so agents can decide when to rotate or trim conversation history.
System Health Check
Run a periodic system health check: verify PM2 services, disk and memory thresholds, and produce logs/alerts for operators when issues are detected.