loop-me

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

2|Updated May 12, 2026
One-click install
npx skills add https://github.com/tajo9128/BioDockify-Pharma-AI --skill loop-me-tajo9128
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: loop-me
Source: https://github.com/tajo9128/BioDockify-Pharma-AI/tree/main/.agents/skills/loop-me
Command: npx skills add https://github.com/tajo9128/BioDockify-Pharma-AI --skill loop-me-tajo9128

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Vague automation ideas stall because nobody pins down the trigger, checkpoints, and expected output. This Skill runs a structured grilling session that turns fuzzy intentions into workflow specs an implementer agent could build without asking a single question. ## Core Features & Use Cases - Stateful grilling sessions: Asks one round of questions at a time, each with a recommended answer, until every ambiguity in the workflow is resolved. - Loop discovery lens: Identifies recurring patterns in your career, week, or daily routine that are worth delegating, including ones you have not noticed. - Spec management: Creates, edits, and deletes workflow specs in workflows/*.md and records your tools, channels, and terminology in NOTES.md. - Use Case: You want your inbox triaged every morning. The session grills you on what counts as urgent, what a decision-ready brief looks like, and when you want to be interrupted, then writes a complete spec to workflows/inbox-triage.md. ## Quick Start Ask the assistant to start a loop-me grilling session to spec out a workflow for a recurring task you want to delegate.

Frequently Asked Questions about loop-me

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

FAQPage Schema
How do I turn a vague automation idea into a workflow spec?

Start a grilling session describing the recurring task you want to delegate. The Skill asks one round of questions at a time, each with a recommended answer, and writes the resolved decisions into a spec file under workflows/ until nothing remains ambiguous.

What is a workflow spec and where is it stored?

A workflow spec is the written definition of one recurring loop, covering its trigger, checkpoints, and expected output. Specs live as Markdown files in the workflows/ directory and serve as the source of truth for implementation.

When is a workflow specification considered done?

A spec is done when an implementer agent could build the workflow without asking a single question. The grilling continues until every trigger, checkpoint, brief format, and edge case is explicitly resolved.

Does every workflow need AI, checkpoints, or a schedule?

No. The Skill mandates nothing structural. A workflow may run autonomously with no checkpoints, use no AI at all, or be event-triggered rather than scheduled, depending entirely on what the grilling reveals.

What is the difference between event and schedule triggers?

An event trigger fires the workflow when something happens, such as a new email or issue, while a schedule trigger fires at fixed times like every morning. Event triggering is usually the more efficient choice.