projectb-loop

Schedules recurring checks and /loop prompts through host automation tools.

Updated May 28, 2023
One-click install
npx skills add https://github.com/steveulrich/ProjectB --skill projectb-loop-steveulrich
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: projectb-loop
Source: https://github.com/steveulrich/ProjectB/tree/main/.agents/skills/projectb-loop
Command: npx skills add https://github.com/steveulrich/ProjectB --skill projectb-loop-steveulrich

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Recurring tasks like monitoring deployments, checking CI status, or re-running prompts on an interval require the agent to wake up repeatedly on a schedule, which is easy to misconfigure with duplicate loops, missed wakeups, or unsupported shell hacks. ## Core Features & Use Cases - Host Automation Scheduling: Creates recurring tasks, reminders, and monitors through the host's automation capability, inspecting existing automations first to avoid duplicates. - Interval and Stop-Condition Preservation: Honors the requested interval, runs the prompt immediately when asked, and notifies only on meaningful changes, failures, or required user action. - Legacy Monitored-Shell Fallback: Supports sentinel-based background shell loops (fixed and dynamic schedules) only when explicitly requested and the tool schema supports notify_on_output. - Use Case: Ask the agent to check a deployment status every 5 minutes until it succeeds; it schedules the recurring check, runs once immediately, and reports only when the status changes. ## Quick Start Ask the agent to run a check every 5 minutes, such as monitoring a deploy or CI pipeline, and it will schedule the recurring task and notify you on meaningful changes.

Frequently Asked Questions about projectb-loop

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I schedule a recurring task or reminder with an AI agent?▼

Request the task with an interval, such as checking a deploy every 5 minutes, and the agent creates it through the host's automation tool. It inspects existing automations first to avoid duplicates and preserves your requested interval and stopping condition.

How does the /loop command parse intervals?▼

The /loop syntax accepts leading intervals like "5m /foo" or trailing ones like "check deploy every 5m", using units such as 30s, 5m, 2h, or 1d. With no interval it runs in dynamic mode where the agent picks the next delay after each run.

When should I use monitored shell loops instead of host automation?▼

Use legacy monitored-shell loops only when you explicitly request that runtime and the tool schema supports notify_on_output for background output notifications. If the schema lacks notify_on_output, the host automation tool is the supported path.

Can the agent run a task immediately and also on a schedule?▼

Yes, an immediate run is separate from scheduling. When requested, the agent runs the prompt once right away, then follows the saved schedule for subsequent executions.

How do I stop a running loop or scheduled check?▼

Ask the agent to stop, and it kills any tracked loop or watcher PID and avoids arming the next heartbeat. For shell-based loops it also awaits the shell task so its completion notification does not wake the agent later.

Why does the agent avoid duplicate schedules?▼

Duplicate loops cause repeated wakeups and conflicting notifications, so the agent checks existing terminals and automations before creating a new one. It also refuses to promise wakeups the host cannot deliver.