Turn recurring work or life activities into workflow specifications through focused questions with recommended answers. Clarify triggers, human review, and decision summaries so an implementation agent can build the workflow without further questions.
Grill me about specs for the workflows I want to build, within this workspace.
loop-me turns recurring activities at work or in daily life into workflow specifications. Through /grilling, it asks successive questions with recommended answers to clarify what starts each run, where people make decisions, and what summaries they need. It creates, edits, or deletes specifications in workflows/*.md as decisions take shape. The aim is to give an implementer enough detail to build without further questions.
Use it when you want to delegate daily or weekly tasks but have not defined how much to hand over. If you have no task in mind, it suggests candidates based on recurring patterns. It also asks about your tools, information channels, and terminology, recording these in NOTES.md.
Where human review is needed, it considers completing as much preparation as possible before presenting a brief covering the results, reasoning, and references.
You invoke this skill explicitly, and it assumes access to /grilling. Its deliverables are workflow specifications. AI use, human review, and scheduled runs are optional; the questions establish whether each is needed.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI rated this skill on four points using only the contents of its SKILL.md. Stars and popularity are not taken into account.
The total counts each point as A = 25, B = 15, C = 5. Rated by AI (OpenAI Codex) as of Oct 19, 2026. Treat it as a guide and read the original before installing.
Review the instructions the agent will receive before you install.
Run a stateful /grilling session whose only output is workflow specs. Use the grilling discipline (relentless, a round of questions 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.
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.
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.
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.
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.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Choose which related skill to use and in what order for planning, building, debugging, or maintaining software. It explains routes through the available workflows and helps select the next step based on your situation and project size.
Coordinate subagents, separate agents assigned tasks, to pursue a long-running goal in one session. Maintain dialogue with the user while improving working conditions, shared rules, and access to information needed for future tasks.
Summarize an ongoing conversation and launch a fresh background agent to continue the work. The handoff includes the next focus, references to existing documents, and suggested skills, with sensitive information removed.
Review code changes from a chosen Git reference against two separate criteria: documented coding standards and the original requirements. Independent reviewers check each criterion, then present findings separately so convention problems and requirement gaps remain visible.
Design modules that offer substantial behavior through a small interface, the rules callers must understand. Use shared design terms to simplify usage, contain complexity, choose where implementations can vary, and make behavior easier to test.
Investigate difficult bugs and performance slowdowns by building a repeatable test or script that detects the exact symptom. Reduce the failing case, compare possible causes, and verify the fix with checks that catch the bug if it returns.