Loop Me
Matt PocockCommunityCreated by Matt Pocock
- Skill
- Meta (authoring, orchestration, planning, memory)
- Agent tooling
- MIT
- No issues found
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
loop-me is a meta-skill designed to help users identify and formalize recurring life or work patterns into actionable workflow specifications. By applying the loop lens, the agent interviews the user to uncover predictable activities, then iteratively refines these into clear, implementation-ready documents. The process focuses on minimizing human intervention through the push-right principle, ensuring that any necessary checkpoints are presented as concise, decision-ready briefs.
What it does
- Conducts a stateful grilling session to extract workflow requirements.
- Maintains a workspace of workflow specifications in markdown format.
- Identifies recurring patterns in user activities to propose new workflows.
- Refines terminology and tool usage in a central notes file.
- Iterates on specifications until they are complete enough for implementation without further questions.
When to use it
- When you want to automate a recurring task but need help defining the requirements.
- When you have identified a repetitive activity that could be delegated.
- When you need to create a clear, unambiguous specification for a workflow.
- When you need to organize your workspace and standardize the language used for your processes.
Advantages
- Ensures workflow specifications are complete and ready for implementation.
- Promotes efficient automation by prioritizing event-based triggers.
- Reduces cognitive load by designing workflows that minimize human checkpoints.
- Creates a shared, canonical language for your personal or professional processes.
Usage examples
- “I want to automate my weekly report generation.”
- The agent begins a grilling session to understand the report's triggers, data sources, and the specific decisions you need to make during the review process.
- “Help me find a new loop to automate in my morning routine.”
- The agent analyzes your current activities to identify recurring patterns and proposes a workflow that could be delegated or streamlined.
Install
Download the skill as a ZIP:
https://autogineer.com/agent-skills/mattpocock/loop-me/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip loop-me.zip -d .agents/skills
Documentation by Matt Pocock
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.
Files
- ATTRIBUTION.mdAdded by AutoGineer855 B
- LICENSELicence file added by AutoGineer1.0 KiB
- SKILL.md2.5 KiB
- agents/openai.yaml140 B
agents/openai.yaml
interface: display_name: "Loop Me" short_description: "Spec the workflows you want to build" policy: allow_implicit_invocation: false
Requirements and compatibility
Written for: Claude Code
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Claude Code frontmatter
Security
No issues found by our static scan· No issues found
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Created by
- Matt Pocock
- Publisher
- Matt Pocock (Community)
- Source
- mattpocock/skills · skills/in-progress/loop-me · commit 4ae2317
- Licence
- MIT License (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by Matt Pocock or Matt Pocock.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download loop-me.zip