[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A2JN4EX5EBJHDR65RFYA5G":3,"skill-same:01M7A2JN4EX5EBJHDR65RFYA5G":62},{"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":39,"commitSha":40,"skillDirectory":41,"forksCount":42,"repositoryHtmlUrl":43,"repositoryHomepageUrl":6,"ownerHtmlUrl":44,"ownerBlogUrl":45,"ownerDescription":46,"updatedAt":47,"install":48,"resources":61},"01M7A2JN4EX5EBJHDR65RFYA5G","agent-self-scheduling",null,"Schedule AI agent runs with cron, loops, or external clocks while avoiding unsafe tight autonomous timers.","MHassan0000\u002FSkills","MHassan0000","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F224296448?v=4","01M7A14DTC1EZCRN04582533RD","Muhammad Hassan Yousaf","01M7A14DV10KTW8NHQTJPD08X0",1,"MIT","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fantigravity skills\u002Fagentic-awesome-skills\u002Fskills\u002Fagent-self-scheduling\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: agent-self-scheduling\ndescription: \"Schedule AI agent runs with cron, loops, or external clocks while avoiding unsafe tight autonomous timers.\"\ncategory: agent-orchestration\nrisk: critical\nsource: community\nsource_repo: davidondrej\u002Fskills\nsource_type: community\ndate_added: \"2026-07-07\"\nauthor: davidondrej\ntags: [agents, scheduling, automation, cron]\ntools: [claude, codex]\nlicense: \"MIT\"\nlicense_source: \"https:\u002F\u002Fgithub.com\u002Fdavidondrej\u002Fskills\u002Fblob\u002Fmain\u002FLICENSE\"\n---\n\n# Agent Self-Scheduling\n\n## When to Use\n\n- Use when the user asks for recurring, scheduled, heartbeat, or looped agent work.\n- Use when you need to choose between cron, external schedulers, hooks, or built-in agent 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\n## Limitations\n\n- Adapted from `davidondrej\u002Fskills`; verify local paths, tools, credentials, and agent features before acting.\n- For commands, remote access, scheduling, browser automation, or file-changing workflows, get explicit user approval and confirm the target environment first.\n","# Agent Self-Scheduling\n\n## When to Use\n\n- Use when the user asks for recurring, scheduled, heartbeat, or looped agent work.\n- Use when you need to choose between cron, external schedulers, hooks, or built-in agent 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\n## Limitations\n\n- Adapted from `davidondrej\u002Fskills`; verify local paths, tools, credentials, and agent features before acting.\n- For commands, remote access, scheduling, browser automation, or file-changing workflows, get explicit user approval and confirm the target environment first.\n",{"name":5,"risk":24,"tags":25,"tools":30,"author":33,"source":34,"license":15,"category":35,"date_added":36,"description":7,"source_repo":37,"source_type":34,"license_source":38},"critical",[26,27,28,29],"agents","scheduling","automation","cron",[31,32],"claude","codex","davidondrej","community","agent-orchestration","2026-07-07","davidondrej\u002Fskills","https:\u002F\u002Fgithub.com\u002Fdavidondrej\u002Fskills\u002Fblob\u002Fmain\u002FLICENSE","main","a4404a75dc81d6b7e58c5906b6aaffbcb5e84747","Claude\u002Fantigravity skills\u002Fagentic-awesome-skills\u002Fskills\u002Fagent-self-scheduling",0,"https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills","https:\u002F\u002Fgithub.com\u002FMHassan0000","https:\u002F\u002Fhassanyousaf.vercel.app","Full Stack Developer building web apps, SaaS, AI systems, and automations. Passionate about clean code, UI\u002FUX, backend systems, and turning ideas into products.","2026-08-07 20:42:05",{"source":8,"skillName":5,"commands":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add MHassan0000\u002FSkills --skill agent-self-scheduling",{"tool":54,"command":55},"bunx","bunx skills add MHassan0000\u002FSkills --skill agent-self-scheduling",{"tool":57,"command":58},"pnpm","pnpm dlx skills add MHassan0000\u002FSkills --skill agent-self-scheduling","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fantigravity skills\u002Fagentic-awesome-skills\u002Fskills\u002Fagent-self-scheduling\u002FSKILL.md",true,[],[63,70,77,84,93,101],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7AGBX58S04DX8DKKME8N311","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fskills boraztunc github\u002Fvercel-react-best-practices\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7AGBREE890608Z7YDMAKH27","stop-slop","Remove AI writing patterns from prose. Use when drafting, editing, or reviewing text to eliminate predictable AI tells and produce more human-like writing.","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fskills boraztunc github\u002Fstop-slop\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7AGAS972A2AN7Q5EW8HEAXK","ogilvy-copywriting","Apply David Ogilvy's advertising principles when writing or reviewing copy, headlines, product descriptions, landing pages, ads, emails, or any persuasive text. Use when the goal is copy that sells, not copy that wins awards. Covers positioning, headlines, promises, brand voice, long-form copy, and visual logic. Source: How to Create Advertising That Sells (1972) + Ogilvy on Advertising.","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fskills boraztunc github\u002Fogilvy\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":88,"licenseFileUrl":89,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7AGAF12803G5JPVMK79AYJB","frontend-design","Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML\u002FCSS layouts, or when styling\u002Fbeautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fskills boraztunc github\u002Ffrontend-design\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fskills boraztunc github\u002Ffrontend-design\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":88,"licenseFileUrl":97,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M7AG88WWVWCGJY9WA9CH7EY4","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fobra superpower skills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fobra superpower skills\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":88,"licenseFileUrl":105,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":19},"01M7AG7ZTNV7XQCWDQ9674FBYB","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fobra superpower skills\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fobra superpower skills\u002Fweb-artifacts-builder\u002FSKILL.md",[],[]]