[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DF1AK6YRW84DR4RN74DZAC":3,"skill-same:01M7DF1AK6YRW84DR4RN74DZAC":60},{"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":6,"ownerDescription":6,"updatedAt":45,"install":46,"resources":59},"01M7DF1AK6YRW84DR4RN74DZAC","agent-self-scheduling",null,"Schedule AI agent runs with cron, loops, or external clocks while avoiding unsafe tight autonomous timers.","Hazek-dc\u002FPresensiGuru_FaceNet_EMAR","Hazek-dc","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F75208960?v=4","01M7DEQV5B4YGS86A81DYH81DR","Hazek","01M7DEQV5XP4TM0C6NTHXCXCHR",1,"MIT","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002F.agents\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","b1e4ffadb4f933bbbcaa03a83f8b9929171ac28b",".agents\u002Fskills\u002Fagent-self-scheduling",0,"https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR","https:\u002F\u002Fgithub.com\u002FHazek-dc","2026-10-22 08:36:44",{"source":8,"skillName":5,"commands":47,"prompt":57,"zipAvailable":58},[48,51,54],{"tool":49,"command":50},"npx","npx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill agent-self-scheduling",{"tool":52,"command":53},"bunx","bunx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill agent-self-scheduling",{"tool":55,"command":56},"pnpm","pnpm dlx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill agent-self-scheduling","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fagent-self-scheduling\u002FSKILL.md",true,[],[61,68,75,82,89,96],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7DS6GGYRZAYD33PFPS8Z2T3","testing-best-practices","Laravel test design and review. Use when selecting coverage, naming or structuring tests, choosing assertions or test data, isolating dependencies, testing HTTP or security boundaries, improving suite performance, or reviewing test value. Use framework guidance or search-docs for Pest and PHPUnit syntax.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Ftesting-best-practices\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7DS6BC3AW7HTPRHE2TTVKWM","tailwindcss-development","Always invoke when the user's message includes 'tailwind' in any form. Also invoke for: building responsive grid layouts (multi-column card grids, product grids), flex\u002Fgrid page structures (dashboards with sidebars, fixed topbars, mobile-toggle navs), styling UI components (cards, tables, navbars, pricing sections, forms, inputs, badges), adding dark mode variants, fixing spacing or typography, and Tailwind v3\u002Fv4 work. The core use case: writing or fixing Tailwind utility classes in HTML templates (Blade, JSX, Vue). Skip for backend PHP logic, database queries, API routes, JavaScript with no HTML\u002FCSS component, CSS file audits, build tool configuration, and vanilla CSS.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Ftailwindcss-development\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7DS66GE6B11MYJDVC74HXM4","laravel-best-practices","Apply this skill whenever writing, reviewing, or refactoring Laravel PHP code. This includes creating or modifying controllers, models, migrations, form requests, policies, jobs, scheduled commands, service classes, and Eloquent queries. Triggers for N+1 and query performance issues, caching strategies, authorization and security patterns, validation, error handling, queue and job configuration, route definitions, and architectural decisions. Also use for Laravel code reviews and refactoring existing Laravel code to follow best practices. Covers any task involving Laravel backend PHP code patterns.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Flaravel-best-practices\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7DS5ZW717DMS6P1E90AQCKV","infer-conventions","Use this skill to analyze how a Laravel application is actually written and record its conventions as shared rules. Trigger when the user wants to detect, infer, document, or standardize project conventions or coding style, set up or grow `.ai\u002Frules`, resolve mixed or conflicting patterns (e.g. \"are we using Form Requests or inline validation?\"), or onboard agents and teammates to \"how we do things here\". Covers: a systematic sweep of ~49 Laravel convention dimensions (validation, models, architecture, testing, frontend, database, console), open-ended house-pattern discovery, conflict reporting, and recording rules scoped to the right paths via the Boost `record-rule` MCP tool. Only run this skill when the user explicitly asks for it; never start a sweep as part of another task. Do not use for one-off code review, enforcing formatting a linter already handles, or editing `.ai\u002Frules` files by hand.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Finfer-conventions\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M7DS5W12RGCVJTFQJ1N0GB8E","inertia-react-development","Develops Inertia.js v2 React client-side applications. Activates when creating React pages, forms, or navigation; using \u003CLink>, \u003CForm>, useForm, or router; working with deferred props, prefetching, or polling; or when user mentions React with Inertia, React pages, React forms, or React navigation.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Finertia-react-development\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M7DS5PVDPMPCWSK2RXPDC9BB","deploying-to-cloud","Deploys and manages Laravel applications on Laravel Cloud using the `cloud` CLI. Use when the user wants to deploy an app, ship to Cloud, create or manage applications, environments, databases, caches, object storage, queues, domains, instances, background processes, secrets, compute, scheduled tasks, or Laravel Cloud infrastructure; or check billing, usage, or spend. Triggers on deployment, shipping, Cloud management, environment setup, database provisioning, billing or usage queries, the `cloud` CLI, and Laravel Cloud deployment troubleshooting.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Fdeploying-to-cloud\u002FSKILL.md",[],[]]