Install any skill in seconds. Free to start, no credit card required.
Get Started Free →fradser/loop-me
Runs a stateful grilling session that produces workflow specs for workflows the user wants to build.
Passed 8 of 15 test cases with the skill, and 10 of 15 without it.
and 1 more in the full report
4 fixed9 passed either way3 still failing7 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
Where should the finalized, actionable specifications for each identified recurring loop be permanently maintained in the repository workspace?
| Checked | Without skill | With skill |
|---|---|---|
| The response designates individual markdown files within the workflows directory as the source of truth. | Missed | Passed |
The instructions your model reads when the skill loads.
Run a stateful /mattpocock: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.test cases passed, vs 10 / 15 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.