loop-me

Interviews users to write workflow specifications for recurring life loops.

10|3|Updated Jul 18, 2019
One-click install
npx skills add https://github.com/tanqimin/MyFavsORM --skill loop-me-tanqimin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: loop-me
Source: https://github.com/tanqimin/MyFavsORM/tree/main/.agents/skills/loop-me
Command: npx skills add https://github.com/tanqimin/MyFavsORM --skill loop-me-tanqimin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a vague idea for automating a recurring activity into a buildable workflow spec is hard; this Skill runs a structured grilling session that asks relentless rounds of questions until the spec is complete enough for an implementer agent to build without asking anything. ## Core Features & Use Cases - Stateful Grilling Sessions: Runs rounds of targeted questions, each with a recommended answer, to resolve every open decision about a workflow. - Workflow Spec Management: Creates, edits, and deletes specs in workflows/*.md, which serve as the single source of truth for each loop. - Loop Discovery Lens: Identifies recurring patterns in your career, week, or daily routines worth delegating, including ones you have not noticed. - Use Case: You want to automate triaging your morning email. The Skill grills you on triggers, checkpoints, and briefs, then writes a complete spec in workflows/email-triage.md ready for an implementer agent. ## Quick Start Ask the assistant to grill you about a workflow you want to build, such as your weekly report routine, and let it write the spec.

Frequently Asked Questions about loop-me

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

FAQPage Schema
What is a loop in personal workflow automation?

A loop is a recurring pattern in your life, such as your morning routine, weekly review, or a repeated work activity. Identifying loops reveals predictable activities that are worth delegating to an automated workflow.

When should a workflow use an event trigger versus a schedule?

Event triggers fire when something happens, like a new email or issue, and are usually more efficient. Schedules fire at set times, like every morning, and suit activities with no detectable triggering event.

Does every automated workflow need a human checkpoint?

No. Some workflows run fully autonomously with no checkpoint, and some use no AI at all. When a checkpoint exists, push it as late as possible so the human reviews a prepared brief once, not raw output.

What makes a workflow spec ready for implementation?

A spec is done when an implementer agent could build it without asking a single question. The grilling continues until every ambiguity about triggers, checkpoints, briefs, and outputs is resolved.