loop-me
Skill11 starsChanged 41 days agoMITView on GitHub
Grill me about specs for the workflows I want to build, within this workspace.
Files
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.
Trending
Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data
Other versions68 projects use a version of this.
Word for word · 25
- mattpocock/skills★ 309k100% same
- tt-a1i/matt-skills-with-to-goal★ 192100% same
- LiChangZheng10086/doyin_ai_video★ 30100% same
- VoDaiLocz/kilo-kit-mcp★ 28100% same
- George-RD/design-studio★ 10100% same
- caterpi11ar/giclaw★ 9100% same
- getmodern-ai/graft★ 9100% same
- anis-dr/skills★ 3100% same
- George-RD/openspine★ 2100% same
- nomdedev/agent-manager-template★ 2100% same
- aaaxn/skills★ 2100% same
14 more not listed
Edited · 35
- shobcoder/shob★ 57599% same
- loulanyue/skills★ 23199% same
- GAGAA-HUE/ASHUO-claude-skills★ 599% same
- Roentek/Claude_Code_Boilerplate_Framework★ 499% same
- 47thtechcorner/RayCodes_Mattpocock_Skills★ 299% same
- AaronAbuUsama/whatsappd★ 299% same
- AndyMelnykov/TeamOSTemplate★ 2100% same
- IsKenKenYa/skills★ 298% same
- IvanGomezMartinez/MatStudyLab★ 2100% same
- 20231118185SSPU/prompt-optimizer★ 199% same
25 more not listed
Wrote their own version · 8
- vinvcn/mattpocock-skills-zh-CN★ 5.5ksame name
- devcxl/mattpocock-skills-zh★ 522same name
- WenWuZhiDao/mattpocock-skills-zh★ 27same name
- Boom-Vitt/skills-thai★ 5same name
- KroxiDev/engineering-skills★ 4same name
- shumingyang-opencode/mattpocock-skills-zh-tw★ 3same name
- Artknighty/skills-ptbr★ 0same name
- snehilshah/skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Used alongsideProjects with it also use setup-ts-deep-modules, claude-handoff and 2 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
liufeng1976Skillsetup-ts-deep-modules
Wire dependency-cruiser into a TypeScript repo so each package is a deep module — implementation hidden in subfolders, reachable only through its entry-point files. User-invoked.
Also in 36 projects that use this
ryotaroh180105Skillclaude-handoff
Hand the current conversation off to a fresh background agent that picks up the work immediately.
Also in 37 projects that use this
boyingliu01Skillbatch-grill-me
A relentless interview that asks every frontier question at once, round by round. Thin alias of `grilling` (#540) — upstream mattpocock/skills absorbed this protocol into grilling; XP-Gate keeps this name as the sprint-flow Phase 2 entry point so orchestration docs stay stable.
Also in 6 projects that use this
getnaoSkillchief-of-staff
Also in 10 projects that use this
In this repository95 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- ask-mattSkill
- brainstormingSkill
- cavecrewSkill
- caveman-commitSkill
- caveman-compressSkill
- caveman-helpSkill
- caveman-reviewSkill
- cavemanSkill
- caveman-statsSkill
- codebase-designSkill
- code-reviewSkill
- design-an-interfaceSkill
- diagnosing-bugsSkill
- dispatching-parallel-agentsSkill
- domain-modelingSkill
- executing-plansSkill
- finishing-a-development-branchSkill
- git-guardrails-claude-codeSkill
- grillingSkill
- grill-meSkill
- grill-with-docsSkill
- handoffSkill
- implementSkill
- implement-specSkill
- improve-codebase-architectureSkill
- prototypeSkill
- receiving-code-reviewSkill
- requesting-code-reviewSkill
- researchSkill
- resolving-merge-conflictsSkill
- setup-matt-pocock-skillsSkill
- subagent-driven-developmentSkill
- systematic-debuggingSkill
- tddSkill
- teachSkill
- test-driven-developmentSkill
- to-questionnaireSkill
- to-specSkill
- to-ticketsSkill
- triageSkill
- using-git-worktreesSkill
- using-superpowersSkill
- verification-before-completionSkill
- wait-whatSkill
- wayfinderSkill
- wizardSkill
- writing-for-agentsSkill
- writing-great-skillsSkill
- writing-plansSkill
- writing-skillsSkill
- brainstormingSkill
- dispatching-parallel-agentsSkill
- executing-plansSkill
- finishing-a-development-branchSkill
- playwright-cliSkill
- receiving-code-reviewSkill
- requesting-code-reviewSkill
- subagent-driven-developmentSkill
- systematic-debuggingSkill
- The first 60 shown.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

