[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M786V4V2ZNMS1BMSRWJJ0MFA":3,"skill-same:01M786V4V2ZNMS1BMSRWJJ0MFA":57},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M786V4V2ZNMS1BMSRWJJ0MFA","agent-self-scheduling",null,"Make an AI agent run on a schedule, loop, or interval — cron, heartbeats, recurring autonomous checks. Use for \"run every N minutes\", \"schedule a task\", \"run on a loop\", \"heartbeat\". Covers external clocks (Claude Code, Codex, Pi) vs Hermes' built-in scheduler.","Solizardking\u002Fskillhub-main","Solizardking","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F108096810?v=4","01M786KDB10AYV042N0F9BD5B5","Clawd","01M786NYYXSZK1D05WM8JQPC48",0,"MIT","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fpublic\u002Fapi\u002Fskills\u002Fagent-orchestration\u002Fagent-self-scheduling\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: agent-self-scheduling\ndescription: Make an AI agent run on a schedule, loop, or interval — cron, heartbeats, recurring autonomous checks. Use for \"run every N minutes\", \"schedule a task\", \"run on a loop\", \"heartbeat\". Covers external clocks (Claude Code, Codex, Pi) vs Hermes' built-in scheduler.\n---\n\n# Agent Self-Scheduling\n\nFirst question: does the agent have a built-in scheduler (Hermes → Camp B), or do you own the clock (everything else → Camp A)?\n\nUniversal floor: cron is 1 minute minimum (5-field expr, no seconds) — every camp. For sub-minute you MUST use a `while ...; sleep N; done` loop, a TS extension, or an event hook. Never put an LLM on a tight timer.\n\n## Camp A — one-shot agents, you own the clock\n\nThese run once and exit (amnesiac unless resumed). Schedule them externally.\n\n```bash\nclaude -p \"PROMPT\" --output-format json --allowedTools \"Read,Edit,Bash\"  # Claude Code\ncodex exec --json \"PROMPT\"                                                # Codex\npi run \"PROMPT\"                                                           # Pi\n```\n\nWrap in a clock:\n\n```bash\n# 1. cron (>= 1 min floor)\n*\u002F10 * * * * cd \u002Fpath\u002Fto\u002Fproject && pi run \"check X and report\" >> ~\u002Fagent.log 2>&1\n# 2. systemd timer (Linux, survives reboot, better logging) — OnUnitActiveSec=10min\n# 3. dumb loop (sub-minute, or no cron available)\nwhile true; do pi run \"check X\"; sleep 30; done\n```\n\nGotchas (each breaks unattended runs if ignored):\n- **Permissions hang forever.** Pass `--allowedTools` (Claude) or sandbox\u002Fauto-approve flags (Codex), or the run blocks on a prompt.\n- **Use JSON output** (`--output-format json` \u002F `--json`) so the wrapper parses results deterministically.\n- **Runs are amnesiac.** Resume (`codex exec resume --last`) or persist state to a file the next run reads.\n\nPi has NO built-in scheduler\u002Floop\u002Fheartbeat by design — external clock only (or a TS extension for agent-side timers).\n\n### cmux — orchestration only, NO scheduler\n\ncmux has no timer\u002Fwatch\u002Fcron. Three ways to loop it: orchestrator-driven (`send` → `sleep` → `read-screen` on your own clock), a dumb while-sleep wrapper, or — preferred — event-driven via `cmux notify` + OSC terminal hooks, which is cheaper and more responsive than polling. `read-screen` is non-interruptive, safe to poll.\n\nIf a loop checks another agent, send the user a one-line status each check: what the agent is doing, on track or not. (Claude Code may prefill a predicted next user message after finishing — that's Claude, not the user.)\n\n## Camp B — Hermes built-in scheduler\n\nHermes' gateway ticks every 60s and runs due jobs in fresh isolated sessions. State-check first:\n\n```bash\nhermes gateway install            # user-level ( --system to survive reboot)\nhermes cron create \"every 1h\" \"summarize new emails and report\" --skill himalaya\nhermes cron create \"0 9 * * *\" \"post daily standup\"      # cron expr\nhermes cron create \"30m\" \"one-shot reminder in 30 min\"   # one-shot delay\n```\n\nHermes-unique: **zero-token mode** (run a script, deliver stdout verbatim — use for watchdogs), **chaining** (`context_from` pipes one job's output into the next), **self-terminating loops**, and **loop safety** (scheduled sessions cannot create more cron jobs — don't schedule from inside a scheduled job). Each run is a fresh session: the prompt must carry all context.\n\n## Heartbeat pattern\n\nOne fast recurring tick gates many slower per-task checks: the tick reads a task list + per-task `last_run` timestamps and only acts on tasks that are due. In Hermes use a recurring job (zero-token mode when nothing's due); in Camp A use a while-sleep loop. Define active-hours, and stay silent when nothing is due — no empty noise.\n\n## Verify it fires (before reporting success)\n\n1. Camp A: log file grows after one interval, or run the wrapped command once by hand → clean JSON, exit 0.\n2. Camp B: `hermes cron list` shows the job + sane `next_run`; trigger a run-now to confirm delivery.\n3. Confirm permission\u002Fsandbox flags are present — the #1 silent failure is a hung permission prompt.\n4. Heartbeats: confirm a nothing-due tick stays silent.\n","# Agent Self-Scheduling\n\nFirst question: does the agent have a built-in scheduler (Hermes → Camp B), or do you own the clock (everything else → Camp A)?\n\nUniversal floor: cron is 1 minute minimum (5-field expr, no seconds) — every camp. For sub-minute you MUST use a `while ...; sleep N; done` loop, a TS extension, or an event hook. Never put an LLM on a tight timer.\n\n## Camp A — one-shot agents, you own the clock\n\nThese run once and exit (amnesiac unless resumed). Schedule them externally.\n\n```bash\nclaude -p \"PROMPT\" --output-format json --allowedTools \"Read,Edit,Bash\"  # Claude Code\ncodex exec --json \"PROMPT\"                                                # Codex\npi run \"PROMPT\"                                                           # Pi\n```\n\nWrap in a clock:\n\n```bash\n# 1. cron (>= 1 min floor)\n*\u002F10 * * * * cd \u002Fpath\u002Fto\u002Fproject && pi run \"check X and report\" >> ~\u002Fagent.log 2>&1\n# 2. systemd timer (Linux, survives reboot, better logging) — OnUnitActiveSec=10min\n# 3. dumb loop (sub-minute, or no cron available)\nwhile true; do pi run \"check X\"; sleep 30; done\n```\n\nGotchas (each breaks unattended runs if ignored):\n- **Permissions hang forever.** Pass `--allowedTools` (Claude) or sandbox\u002Fauto-approve flags (Codex), or the run blocks on a prompt.\n- **Use JSON output** (`--output-format json` \u002F `--json`) so the wrapper parses results deterministically.\n- **Runs are amnesiac.** Resume (`codex exec resume --last`) or persist state to a file the next run reads.\n\nPi has NO built-in scheduler\u002Floop\u002Fheartbeat by design — external clock only (or a TS extension for agent-side timers).\n\n### cmux — orchestration only, NO scheduler\n\ncmux has no timer\u002Fwatch\u002Fcron. Three ways to loop it: orchestrator-driven (`send` → `sleep` → `read-screen` on your own clock), a dumb while-sleep wrapper, or — preferred — event-driven via `cmux notify` + OSC terminal hooks, which is cheaper and more responsive than polling. `read-screen` is non-interruptive, safe to poll.\n\nIf a loop checks another agent, send the user a one-line status each check: what the agent is doing, on track or not. (Claude Code may prefill a predicted next user message after finishing — that's Claude, not the user.)\n\n## Camp B — Hermes built-in scheduler\n\nHermes' gateway ticks every 60s and runs due jobs in fresh isolated sessions. State-check first:\n\n```bash\nhermes gateway install            # user-level ( --system to survive reboot)\nhermes cron create \"every 1h\" \"summarize new emails and report\" --skill himalaya\nhermes cron create \"0 9 * * *\" \"post daily standup\"      # cron expr\nhermes cron create \"30m\" \"one-shot reminder in 30 min\"   # one-shot delay\n```\n\nHermes-unique: **zero-token mode** (run a script, deliver stdout verbatim — use for watchdogs), **chaining** (`context_from` pipes one job's output into the next), **self-terminating loops**, and **loop safety** (scheduled sessions cannot create more cron jobs — don't schedule from inside a scheduled job). Each run is a fresh session: the prompt must carry all context.\n\n## Heartbeat pattern\n\nOne fast recurring tick gates many slower per-task checks: the tick reads a task list + per-task `last_run` timestamps and only acts on tasks that are due. In Hermes use a recurring job (zero-token mode when nothing's due); in Camp A use a while-sleep loop. Define active-hours, and stay silent when nothing is due — no empty noise.\n\n## Verify it fires (before reporting success)\n\n1. Camp A: log file grows after one interval, or run the wrapped command once by hand → clean JSON, exit 0.\n2. Camp B: `hermes cron list` shows the job + sane `next_run`; trigger a run-now to confirm delivery.\n3. Confirm permission\u002Fsandbox flags are present — the #1 silent failure is a hung permission prompt.\n4. Heartbeats: confirm a nothing-due tick stays silent.\n",{"name":5,"description":7},"main","be3de0244dc1a57e323d8160787ebb40fb64930e","public\u002Fapi\u002Fskills\u002Fagent-orchestration\u002Fagent-self-scheduling","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main","https:\u002F\u002Fskills.x402.wtf","https:\u002F\u002Fgithub.com\u002FSolizardking","https:\u002F\u002Fmusebook.trade","Got a mile high and never came down","2026-10-08 23:20:13",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add Solizardking\u002Fskillhub-main --skill agent-self-scheduling",{"tool":39,"command":40},"bunx","bunx skills add Solizardking\u002Fskillhub-main --skill agent-self-scheduling",{"tool":42,"command":43},"pnpm","pnpm dlx skills add Solizardking\u002Fskillhub-main --skill agent-self-scheduling","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fpublic\u002Fapi\u002Fskills\u002Fagent-orchestration\u002Fagent-self-scheduling\u002FSKILL.md",true,[47,53],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"metadata.json","REFERENCE","参考文档",498,"https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fpublic\u002Fapi\u002Fskills\u002Fagent-orchestration\u002Fagent-self-scheduling\u002Fmetadata.json",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"verification.json",1203,"https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fpublic\u002Fapi\u002Fskills\u002Fagent-orchestration\u002Fagent-self-scheduling\u002Fverification.json",[58,65,72,79,86,94],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M78E0TGCAMNPS207BA3G07S7","zkrouter","Self-hosted OpenAI-compatible LLM router — smart tier-based routing, ZK-stamped routing decisions, mode overrides, free OpenRouter at install via the Birth bot. Save 60-80% on inference costs by routing to the cheapest capable model across 12+ OpenRouter models.","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fskills\u002Fzkrouter\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M78E0R1Z8BDT6EDTHY17MTNB","zk","For custom ZK Solana programs and privacy-preserving applications to prevent double spending. Guide to integrate rent-free nullifier PDAs for double-spend prevention.","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fskills\u002Fzk\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M78E0P3ZTZ1YWF8MD5MM23QE","zk-omni-messaging","Zero-knowledge omnichain messaging between Robinhood Chain and Solana using CheshireZkOmniMessenger (msgType 4) with nullifier anti-replay and the zk-omni-relayer service.","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fskills\u002Fzk-omni-messaging\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M78E0JXZ2PNB1896VXAGDBWD","zerion-wallet-data","Use when the user asks to check a wallet's portfolio, token balances, DeFi positions, PnL, transaction history, or NFTs. Provides interpreted on-chain data across 40+ EVM chains and Solana via x402 pay-per-request or API key — no raw RPC decoding needed.","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fskills\u002Fzerion-wallet-data\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":90,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M78E0G14FH9GRRTQYMKD5E59","youtube-clipper","YouTube 视频智能剪辑工具。下载视频和字幕，AI 分析生成精细章节（几分钟级别）， 用户选择片段后自动剪辑、翻译字幕为中英双语、烧录字幕到视频，并生成总结文案。 使用场景：当用户需要剪辑 YouTube 视频、生成短视频片段、制作双语字幕版本时。 关键词：视频剪辑、YouTube、字幕翻译、双语字幕、视频下载、clip video","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube-clipper\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube-clipper\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M78E0C2ZYA99CFFDNB7ZMK5S","yield-optimization","Multi-chain yield optimization via yield.xyz (StakeKit). Discover 2,988+ yield opportunities across 75+ blockchains, build deposit\u002Fwithdrawal transactions with shell scripts, and sign them with a MoonPay wallet. Use when the user wants to earn yield, find the best lending or staking rate, enter\u002Fexit a position, or check portfolio balances.","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fskills\u002Fyield-optimization\u002FSKILL.md",[],[]]