Loop Me — Workflow Grilling
A stateful grilling session that sharpens workflow specs through the "loops" lens
- What
- A stateful grilling session that sharpens workflow specs through the "loops" lens
- Cost
- Free
- Needs
- none beyond an AI coding agent that supports skills
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — a stateful `/grilling` session whose only output is workflow specs: it interviews you relentlessly, one round of questions at a time, until each spec is so complete an implementer agent could build it without asking a single question. Works through the "loop" lens — a loop is a recurring pattern in your life (your week, your morning, a repeated activity), and picturing life as loops within loops reveals what's worth delegating; a workflow is the spec of one loop, made real, living in `workflows/*.md` with `NOTES.md` as the raw material. Teaches a vocabulary (trigger, checkpoint, push-right, brief) but mandates no structure — a workflow needs no AI, checkpoint, or schedule unless the grilling shows it does. Distinct from the published mattpocock-grilling skill: that one grills general ideas, while loop-me grills workflow specifications specifically. No accounts or paid services required. By @mattpocock, listed here with credit to its creator. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Prerequisites: none beyond an AI coding agent that supports skills Install "Loop Me — Workflow Grilling" for me. A stateful grilling session that sharpens workflow specs through the "loops" lens. Repository: https://github.com/mattpocock/skills/blob/main/skills/in-progress/loop-me/SKILL.md 1. Fetch the SKILL.md file for the mattpocock-loop-me skill from the repository into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "mattpocock-loop-me". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. any accounts, API keys, or CLI tools mentioned in the prerequisites above). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. Never ask me to paste secrets in chat — credentials go through the secure vault or environment variables. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.