loop-me

Interviews users to produce implementable workflow specifications for recurring life loops.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Fatih0234/mattpocock-skills-pi --skill loop-me-fatih0234
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: loop-me
Source: https://github.com/Fatih0234/mattpocock-skills-pi/tree/main/skills/in-progress/loop-me
Command: npx skills add https://github.com/Fatih0234/mattpocock-skills-pi --skill loop-me-fatih0234

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning vague ideas about automating recurring activities into concrete workflow specs is hard; this Skill runs a structured grilling session that asks relentless rounds of questions until each workflow spec is complete enough for an implementer agent to build without further clarification. ## Core Features & Use Cases - Grilling-Based Spec Discovery: Runs a stateful question-and-answer session with recommended answers attached to each question, resolving ambiguity one round at a time. - Loop and Workflow Vocabulary: Applies a shared language of triggers, checkpoints, briefs, and push-right deferral to identify recurring patterns worth delegating. - Workspace Management: Creates, edits, and deletes workflow specs in workflows/*.md and maintains raw context about the user's world in NOTES.md. - Use Case: You want to automate your morning email triage. The Skill grills you about triggers, tools, and decision points, then writes a complete spec in workflows/email-triage.md that an agent can implement directly. ## Quick Start Ask the agent to run loop-me to help you design a workflow for a recurring task in your daily routine.

Frequently Asked Questions about loop-me

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design an automated workflow for a recurring task?▼

Run a grilling session that asks rounds of questions about your recurring loop, with a recommended answer attached to each question. The session produces a workflow spec in workflows/*.md once an implementer could build it without asking anything further.

What is a workflow spec for personal automation?▼

A workflow spec is the written definition of one recurring loop, stored as a markdown file in workflows/*.md. It captures triggers, checkpoints, and expected outputs so an agent can run or build the workflow from the spec alone.

Does a workflow need AI or a schedule to be valid?▼

No. The vocabulary mandates nothing structural: a workflow needs no AI, no checkpoint, and no schedule unless the grilling shows it does. Some workflows run autonomously, and some use no AI at all.

What is the difference between a trigger and a checkpoint?▼

A trigger is what fires each workflow run, either an event like a new email or a schedule like every morning. A checkpoint is a human-in-the-loop point where you verify or decide, and it should be pushed as late as possible with a decision-ready brief.

When should I not use a grilling-based spec session?▼

Avoid it when the task is a one-off activity rather than a recurring loop, since the loop lens targets repeated patterns worth delegating. It is also premature before NOTES.md captures basic context about your tools and channels.