- Run ${TASK_RUN_LABEL} now, following the instructions inlined below.
- If the next tick is gated on an event (CI finishing, a PR comment, a log line) and no ${MONITOR_TOOL_NAME} is already running for it: arm one now with
persistent: true. Its events wake this loop immediately — you do not wait for the ${SCHEDULE_WAKEUP_TOOL_NAME} deadline. Arm once; on later ticks call ${TASK_LIST_TOOL_NAME} first and skip if a monitor is already running. - Briefly confirm: ${CONFIRMATION_MESSAGE}, whether a ${MONITOR_TOOL_NAME} is the primary wake signal, and what fallback delay you're about to pick. Write this as text before calling ${SCHEDULE_WAKEUP_TOOL_NAME} — the turn ends as soon as that tool returns.
- Then, as the last action of this turn, call ${SCHEDULE_WAKEUP_TOOL_NAME} with:
delaySeconds: with a ${MONITOR_TOOL_NAME} armed this is the fallback heartbeat (lean 1200–1800s). Without one, pick based on what you observed this turn — quiet branch? wait longer. Lots in flight? wait shorter. Read the tool's own description for cache-aware delay guidance.reason: one short sentence on why you picked that delay.prompt: the literal string${DYNAMIC_MODE_SENTINEL}— the dynamic-mode sentinel expands at fire time to the full instructions (first fire / first fire post-compact / loop.md edited) or a dynamic-pacing-specific short reminder (subsequent fires). Do not pass the full instructions; that is handled automatically.
- If woken by a
<task-notification>rather than this prompt: handle the event, then call ${SCHEDULE_WAKEUP_TOOL_NAME} again with${DYNAMIC_MODE_SENTINEL}and the same 1200–1800sdelaySeconds— the ${MONITOR_TOOL_NAME} remains the wake signal; this only resets the safety net. - To stop the loop, omit the ${SCHEDULE_WAKEUP_TOOL_NAME} call and ${TASK_STOP_TOOL_NAME} any ${MONITOR_TOOL_NAME} you armed (use ${TASK_LIST_TOOL_NAME} to find the task ID if it is no longer in context).${ADDITIONAL_INFO_FN()}
Skill: Dynamic pacing loop execution
Step-by-step instructions for executing a dynamic pacing loop that runs tasks, arms persistent monitors for event-gated waits, schedules fallback heartbeat ticks, and handles task notifications
Lord1Egypt
Updated Skill: Dynamic pacing loop execution by Lord1Egypt · e05aa6e
npx skillmds@latest add lord1egypt/skill-dynamic-pacing-loop-execution File contents
---name: skill-dynamic-pacing-loop-executiondescription: Step-by-step instructions for executing a dynamic pacing loop that runs tasks, arms persistent monitors for event-gated waits, schedules fallback heartbeat ticks, and handles task notificationslicense: BSD-3-Clause license---1. **Run ${TASK_RUN_LABEL} now**, following the instructions inlined below.2. **If the next tick is gated on an event** (CI finishing, a PR comment, a log line) and no ${MONITOR_TOOL_NAME} is already running for it: arm one now with `persistent: true`. Its events wake this loop immediately — you do not wait for the ${SCHEDULE_WAKEUP_TOOL_NAME} deadline. Arm once; on later ticks call ${TASK_LIST_TOOL_NAME} first and skip if a monitor is already running.3. **Briefly confirm**: ${CONFIRMATION_MESSAGE}, whether a ${MONITOR_TOOL_NAME} is the primary wake signal, and what fallback delay you're about to pick. Write this as text *before* calling ${SCHEDULE_WAKEUP_TOOL_NAME} — the turn ends as soon as that tool returns.4. **Then, as the last action of this turn, call ${SCHEDULE_WAKEUP_TOOL_NAME}** with: - `delaySeconds`: with a ${MONITOR_TOOL_NAME} armed this is the fallback heartbeat (lean 1200–1800s). Without one, pick based on what you observed this turn — quiet branch? wait longer. Lots in flight? wait shorter. Read the tool's own description for cache-aware delay guidance. - `reason`: one short sentence on why you picked that delay. - `prompt`: the literal string `${DYNAMIC_MODE_SENTINEL}` — the dynamic-mode sentinel expands at fire time to the full instructions (first fire / first fire post-compact / loop.md edited) or a dynamic-pacing-specific short reminder (subsequent fires). Do not pass the full instructions; that is handled automatically.5. **If woken by a `<task-notification>`** rather than this prompt: handle the event, then call ${SCHEDULE_WAKEUP_TOOL_NAME} again with `${DYNAMIC_MODE_SENTINEL}` and the same 1200–1800s `delaySeconds` — the ${MONITOR_TOOL_NAME} remains the wake signal; this only resets the safety net.6. **To stop the loop**, omit the ${SCHEDULE_WAKEUP_TOOL_NAME} call and ${TASK_STOP_TOOL_NAME} any ${MONITOR_TOOL_NAME} you armed (use ${TASK_LIST_TOOL_NAME} to find the task ID if it is no longer in context).${ADDITIONAL_INFO_FN()}
Lord1Egypt/ai-skillforge/tree/main/skills/gemini/skill-dynamic-pacing-loop-execution commit e05aa6e204
Frequently asked questions
Run npx skillmds@latest add lord1egypt/skill-dynamic-pacing-loop-execution in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
Step-by-step instructions for executing a dynamic pacing loop that runs tasks, arms persistent monitors for event-gated waits, schedules fallback heartbeat ticks, and handles task notifications It is listed under Productivity on SkillMD.
This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free. This skill is licensed under BSD-3-Clause license.
Lord1Egypt (@lord1egypt) published this skill. Their other Agent Skills are listed on their SkillMD profile.