skills.rest
douglasjarquin
douglasjarquinCOMMUNITY
Explore all skills by this author →
Website𝕏@douglasjarquinGitHub

sweep

Assigns standing sweeps to a dedicated worker with scheduled routines.

Updated Sep 5, 2026
Search Tags:#automation#multi-agent#scheduled tasks#worker#sweep#routine#inbox digest
One-click install
npx skills add https://github.com/douglasjarquin/sum --skill sweep-douglasjarquin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sweep
Source: https://github.com/douglasjarquin/sum/tree/main/grok-bots/sum/skills/sweep
Command: npx skills add https://github.com/douglasjarquin/sum --skill sweep-douglasjarquin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Standing sweeps like inbox digests would otherwise hang timers on the coordinator chat, blocking it from acting as the user-facing liaison. This Skill moves that repeating work onto a dedicated Sweep worker with its own routine. ## Core Features & Use Cases - Dedicated Sweep Worker: Signs on or reuses a worker Bot that owns one standing sweep at a time, keeping the coordinator chat free. - Cadence Selection: Uses event listeners only for integration-backed events and the coarsest useful schedule for local-file sweeps such as /workspace/sum/inbox.md. - Coordinator Relay: The Sweep worker never messages the user directly; the coordinator relays outcomes and remains the liaison. - Use Case: You want a recurring digest of /workspace/sum/inbox.md without tying up your coordinator session. This Skill assigns the digest to a Sweep worker on a coarse schedule while the weekday Inbox rundown stays with the coordinator Bot. ## Quick Start Set up a standing sweep of my inbox file on a dedicated Sweep worker with a coarse schedule and keep the coordinator as my liaison.

Frequently Asked Questions about sweep

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

FAQPage Schema
How do I set up a recurring inbox digest without blocking my coordinator?▼

Assign the digest to a dedicated Sweep worker with its own routine instead of hanging a timer on the coordinator chat. The worker owns one standing sweep at a time, and the coordinator relays outcomes to you.

Should I use an event listener or a schedule for a local file sweep?▼

Use event listeners only for integration-backed events. For local-file sweeps such as /workspace/sum/inbox.md, use the coarsest useful schedule and treat it as the preferred path, not a fallback.

Can the Sweep worker message the user directly?▼

No. The Sweep worker never messages the user; the coordinator remains the user-facing liaison and relays all outcomes. Messaging anyone except the coordinator requires explicit approval.

What does the Sweep skill need before it can run?▼

It needs a worker Bot that can own one standing sweep, the Persist skill so the sweep gets a task id under /workspace/sum/, and a Grok Bot routine or integration event to trigger the sweep.

When should the weekday Inbox rundown not move to a Sweep worker?▼

The weekday Inbox rundown in routines.md stays owned by the coordinator Bot by default. Changing its owner to a Sweep worker is an action that requires explicit approval.

Related Skills

Explore More Software Engineering Skills→
unitarylabunitarylab
30

lcu

Apply a weighted sum of unitaries to a quantum state via PREPARE and SELECT circuits.

Official
Advanced
imbue-aiimbue-ai
1

handle-messages

Process incoming user messages and determine follow-up actions in conversations.

Official
Intermediate
whd4whd4

context-save

Capture git state, decisions, and remaining work for session resumption.

Community
Advanced
brikkoAIbrikkoAI
1

qqbot-remind

Create, query, and cancel one-time and recurring reminders via QQ chat.

Official
Intermediate