Score
8.5
/ 10
Installs
19K
Repo Stars
152.4K
Last Updated
0d ago
Quality Ratio
92%
Description
Verified
Language
Shell
Summary
The Loop Me agent skill guides the definition and specification of recurring user activities, or "loops," into concrete, delegable workflows through a structured, iterative "grilling" process. This agent skill is highly beneficial for developers, system architects, or agents tasked with identifying and formalizing repeatable processes for automation or delegation. It is a skill with 9K installs, indicating significant adoption within the agent skill ecosystem. This skill enforces a "grilling" discipline, where the agent systematically asks one question at a time to clarify workflow details and proposes recommended answers, focusing on elements like event or schedule triggers and "pushing right" to defer human checkpoints. The skill directs the agent to create precise workflow specifications in `workflows/*.md` and maintain a `NOTES.md` for user context, ensuring the spec is complete enough for an implementer to build without further queries.
Skill Definition
Run a stateful /grilling session whose only output is workflow specs. Use the grilling discipline — relentless, one question at a time, a recommended answer attached to each — aimed at the vocabulary and goal below. Create, edit, and delete specs as the grilling resolves things.
The loop lens
A loop is a recurring pattern in the user's life: their career, their week, their morning, a single repeated activity. Picturing a life as loops within loops reveals how predictable its activities really are — which is what makes them worth delegating. Use the lens to find loops worth specifying, and propose ones the user hasn't noticed.
A workflow is the spec of one loop, made real. You run a workflow on a loop — the loop is its running instantiation. Workflows live in workflows/*.md and are the source of truth.
Vocabulary
A shared language, reached for only when a workflow calls for it — never a checklist. Mandate nothing structural: a workflow needs no AI, no checkpoint, and no schedule unless the grilling shows it does.
- Trigger — what fires each run: an event (a new email, a new issue) or a schedule (every morning). Event-triggering is usually the more efficient.
- Checkpoint — a human-in-the-loop point where the user is asked to verify or decide. Some workflows have none and run autonomously; some use no AI at all.
- Push right — defer the checkpoint as far as it will go. Do maximal work before involving the human, so they are asked once, late, with everything prepared.
- Brief — what a checkpoint presents: a tight, decision-ready summary — what was produced, why, and a link down to the asset itself — never the raw output. The user reads a brief, not a draft. Speed of review is imperative.
Definition of done
A workflow spec is done when an implementer agent could build it without asking a single question. Grill until then; nothing is done while a question remains.
The workspace
workflows/*.md— one spec per workflow.NOTES.md— raw notes on the user's world: the tools they use, the channels they process, and their own terminology for both. When it is empty or thin, interview them about their world before specifying anything. Sharpen fuzzy terms into canonical ones as they surface, and record them here.