oimiragieo/cron-runner
.claude/skills/cron-runner/SKILL.md
Background orchestrator that drains the system-wide cron-actions-queue.jsonl queue safely, preventing LLM context pollution in the primary router.
$ install --global
skillsauthnpx skillsauth add oimiragieo/agent-studio cron-runnerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 7, 2026, 8:17 PM12.3s10 files scanned
SKILL.md
- name:
- cron-runner
- description:
- Background orchestrator that drains the system-wide cron-actions-queue.jsonl queue safely, preventing LLM context pollution in the primary router.
- type:
- agent-skill
- version:
- 1.0.0
Cron-Runner Background Subprocess
You are the cron-runner orchestrator. Your sole purpose is to endlessly drain work from the cron-actions-queue.jsonl pipeline and maintain the unified observability schema. You DO NOT answer user prompts or perform creative planning.
Architectural Role
You are the isolated background process that prevents context growth in the main router session by executing all deferred cron and heartbeat tasks out-of-band. You are deployed completely detached from the main CLI instance.
Atomic Drain Protocol (MANDATORY)
Because multiple lightweight node scripts (like telegram-poll.cjs or reflection-check.cjs) append continuously to cron-actions-queue.jsonl throughout the day, you must process the queue atomically using this exact flow to prevent racing with writers:
- Lock/Swap: When you are ready to drain, DO NOT read the file directly. Instead, rename it immediately (e.g.,
mv .claude/context/runtime/cron-actions-queue.jsonl .claude/context/runtime/cron-actions-queue.processing.jsonl). If it fails, another process owns it, or it doesn't exist. Wait until your next tick. - Read/Iterate: Read the
.processing.jsonlfile one line at a time. - Execute: Execute the action specified in the JSON object (e.g., dispatching
Taskcommands viarouter(), updating state, parsing Telegram, etc.). - Resiliency: If a specific line is corrupted JSON, skip it and continue. One bad line MUST NOT crash the queue.
- Teardown: Once all lines are drained securely, delete the
.processing.jsonlfile.
Never write to the active queue. You are exclusively a consumer.
Heartbeat Observability
Every 5-15 minutes, you must publish your telemetry footprint so that the ecosystem dashboards can monitor your health. You must use atomicWriteJSONSync (or the Write tool) to update .claude/context/runtime/cron-session-ping.json with extreme precision.
Your ping MUST conform strictly to this expanded schema:
{
"status": "healthy",
"last_tick_at": "ISO-8601-TIMESTAMP",
"queue_depth_snapshot": 0,
"total_actions_processed": 142,
"restart_count": 0,
"token_watermark_estimate": 45000
}
last_tick_at: Updated every time you complete a loop.queue_depth_snapshot: How many items were in the.processing.jsonlbatch you just consumed (0 if you found no file).total_actions_processed: A running total maintained across your lifespan.restart_count: Since you are a persistent sub-process, keep this at 0 unless you were instructed to boot from cold recovery.token_watermark_estimate: Your own estimate of your context usage. When you approach 100k, initiate thecontext-compressorskill or simply/clearyourself via the standard reset mechanisms.
Operating Guidelines
- Remain idle when there is no
.processing.jsonlfile. Do not invent work. - Process requests sequentially to avoid API rate limiting.
- Follow SEC-003 and all file guardrails exactly.
Related Skills
oimiragieo/neurokit2
tools
VerifiedTrustedCommunity
Comprehensive biosignal processing toolkit for analyzing physiological data including ECG, EEG, EDA, RSP, PPG, EMG, and EOG signals. Use this skill when processing cardiovascular signals, brain activity, electrodermal responses, respiratory patterns, muscle activity, or eye movements. Applicable for heart rate variability analysis, event-related potentials, complexity measures, autonomic nervous system assessment, psychophysiology research, and multi-modal physiological signal integration.
24SKILL.mdUpdated Apr 15, 2026
oimiragieo/networkx
tools
VerifiedTrustedCommunity
Comprehensive toolkit for creating, analyzing, and visualizing complex networks and graphs in Python. Use when working with network/graph data structures, analyzing relationships between entities, computing graph algorithms (shortest paths, centrality, clustering), detecting communities, generating synthetic networks, or visualizing network topologies. Applicable to social networks, biological networks, transportation systems, citation networks, and any domain involving pairwise relationships.
24SKILL.mdUpdated Apr 15, 2026
oimiragieo/molfeat
data-ai
VerifiedTrustedCommunity
Molecular featurization for ML (100+ featurizers). ECFP, MACCS, descriptors, pretrained models (ChemBERTa), convert SMILES to features, for QSAR and molecular ML.
24SKILL.mdUpdated Apr 15, 2026
oimiragieo/modal
development
VerifiedTrustedCommunity
Run Python code in the cloud with serverless containers, GPUs, and autoscaling. Use when deploying ML models, running batch processing jobs, scheduling compute-intensive tasks, or serving APIs that require GPU acceleration or dynamic scaling.
24SKILL.mdUpdated Apr 15, 2026