loop-me
この Skill は、対話型の「グリル」セッションを通じてユーザーのニーズを深く掘り下げ、自動化されたワークフローのための非常に詳細で曖昧さのない仕様を生成します。ユーザーの生活における繰り返しのパターン（「ループ」）を特定し、AI エージェントが直接実行できる明確な指示に変換することに焦点を当てています。これにより、タスクの効果的な委任と自動化が可能になり、追加の質問なしに実装できるほど明確な仕様が保証されます。
npx skills add https://github.com/mattpocock/skills --skill loop-meBefore / After 効果比較
1 组ユーザーが手動でワークフローを定義する際、記述が曖昧であったり詳細が欠けていたりすることが多く、実際の開発や自動化の過程で頻繁なコミュニケーションや手戻りが発生し、多大な時間と労力を費やします。
この Skill は、対話的な質問を通じて、ユーザーが非常に明確で曖昧さのないワークフロー仕様を作成するのを支援し、AI エージェントが追加の確認なしに直接実装できるようにすることで、効率を大幅に向上させます。
Run a stateful /grilling session whose only output is workflow specs. Use the grilling discipline — relentless, one question 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.
ユーザーレビュー (0)
レビューを書く
レビューなし
統計データ
ユーザー評価
この Skill を評価