loop-me
- Use it when:
- You'd like to hand recurring work or routines to automation, but haven't pinned down how they should run.
- It does:
- Questions you round by round, each question with a recommended answer, until every routine is specified.
- You get:
- One Markdown spec per workflow in workflows/, plus NOTES.md on your tools and your words for things.
- Done when:
- An agent could build the workflow without asking you a single question.
- Runs:
- Only when you invoke it; it sits in its author's in-progress folder, so expect changes.
TL;DR
It calls each recurring pattern in your life a loop, from your week or your morning down to one repeated task, and the spec for running one a workflow. Name a workflow to design, or none and it goes looking, proposing loops you hadn't noticed. If NOTES.md is thin, it first asks about your world: the tools you use, the channels you process and your own terms for them. Then it questions you in rounds, each question with its recommended answer, and creates, edits or deletes files in workflows/ as answers land. It brings a few terms, used only when a workflow needs them: a trigger, what starts each run, either an event such as a new email or a schedule such as every morning; a checkpoint, where you verify or decide, pushed as late as possible so you're asked once, with everything prepared; a brief, the short, decision-ready summary you read there instead of the raw output. Nothing is assumed: a workflow only gets AI, a checkpoint or a schedule if your answers call for one. It writes specs only; building them is another agent's job.
Summarizes the skill at 5beb35b.
npx skills add https://github.com/mattpocock/skills --skill loop-me skills.sh pageSource on GitHubAll skills from mattpocock/skills
- Total Downloads
- 485,920 on skills.sh, Nov 9, 2026
- Repo stars
- 318,714 mattpocock/skills
- First seen
- Jun 24, 2026 on skills.sh
Weekly values
| Week to | Installs |
|---|---|
| Sep 21 | 26,963 |
| Sep 28 | 24,164 |
| Oct 5 | 23,906 |
| Oct 12 | 29,880 |
| Oct 19 | 25,821 |
| Oct 26 | 23,304 |
| Nov 2 | 21,406 |
| Nov 9 | 20,568 |
| Category |
Make the agent question you and write the plan down before it writes code. Everything for building software: planning, coding, debugging, design, frameworks, cloud, agents and skills. |
|---|---|
| Type |
A multi-step process the agent follows: interview, debug, run a TDD loop, review. |
| Effect |
Its own steps create or change files, git state or local tools. |
| Needs |
Instructions only. Works in any agent that supports skills. |
| Publisher |
Everyone else. Unverified vendor claims default to community. |
| Topics |
SKILL.md
From mattpocock/skills at 5beb35b. Checked daily, last changed Oct 20, 2026.
Frontmatter
name: loop-me
description: Grill me about specs for the workflows I want to build, within this workspace.
disable-model-invocation: true
argument-hint: "A workflow to design, or nothing to go find one"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.
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.