How do I install the Loop Deliver skill?

Run npx skillmds@latest add levi-qiao/loop-deliver in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Loop Deliver safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Loop Deliver?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Loop Deliver free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Loop Deliver?

levi-qiao (@levi-qiao) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Loop Deliver by levi-qiao — Agent Skill

Name: Loop Deliver
Author: levi-qiao

Loop Deliver

Author and optionally direct-launch a two-node loop-graph run for implementing a product or engineering requirement through verified vertical slices. Use when a requested feature, integration, migration, or behavior change needs multiple rounds, durable acceptance proof, and independent audit. Not for code cleanup, comparing alternatives before choosing, or a one-shot implementation. Do not execute or resume generated runtime node files from this authoring skill.

levi-qiao c381f38 4 files · 9.5 KB Updated Sep 17, 2026

File contents

loop-deliver — a loop-graph preset for requirements

A thin authoring entry. It binds a requirement-delivery pack, starts the owner interview, then follows loop-graph to compile the normal executor, ledger, directives, ops, and supervisor artifacts. It is not a second runtime and it does not ship a second template set.

Fit check

Use this when a feature, integration, migration, or behavior change needs several verified slices and an independent acceptance audit.
Use ../loop-converge/SKILL.md when the goal is code cleanup or consolidation. Use ../loop-research/SKILL.md when the decision between approaches is still open.
If the requirement fits one normal host task, say so and send it directly. Do not wrap it in a graph.

On invoke

Inspect the workspace and current host the same way loop-graph does. Never ask which client this is when context already identifies it.
Read and bind preset.md. That pack is the North Star, supervisor requirement, interview, shape, method guards, knob overrides, and artifact emphasis. Do not redesign them.
Start the owner interview immediately. Ask only the pack's unresolved choices — outcome/acceptance, authority, and launch — as recommended A/B (or A/B/C) choices. Do not ask the owner to invent a plan.
Read and follow ../loop-graph/SKILL.md from When called from a preset skill through generate and deliver. Compile only from loop-graph's templates/. This skill never executes the generated nodes.

---name: loop-deliverdescription: Author and optionally direct-launch a two-node loop-graph run for implementing a product or engineering requirement through verified vertical slices. Use when a requested feature, integration, migration, or behavior change needs multiple rounds, durable acceptance proof, and independent audit. Not for code cleanup, comparing alternatives before choosing, or a one-shot implementation. Do not execute or resume generated runtime node files from this authoring skill.---# loop-deliver — a loop-graph preset for requirementsA thin authoring entry. It binds a requirement-delivery pack, starts the ownerinterview, then follows [`loop-graph`](../loop-graph/SKILL.md) to compile the normalexecutor, ledger, directives, ops, and supervisor artifacts. It is not a second runtimeand it does not ship a second template set.## Fit check- Use this when a feature, integration, migration, or behavior change needs several verified slices and an independent acceptance audit.- Use [`../loop-converge/SKILL.md`](../loop-converge/SKILL.md) when the goal is code cleanup or consolidation. Use [`../loop-research/SKILL.md`](../loop-research/SKILL.md) when the decision between approaches is still open.- If the requirement fits one normal host task, say so and send it directly. Do not wrap it in a graph.## On invoke1. Inspect the workspace and current host the same way loop-graph does. Never ask which client this is when context already identifies it.2. Read and bind [`preset.md`](preset.md). That pack is the North Star, supervisor requirement, interview, shape, method guards, knob overrides, and artifact emphasis. Do not redesign them.3. Start the owner interview immediately. Ask only the pack's unresolved choices — outcome/acceptance, authority, and launch — as recommended A/B (or A/B/C) choices. Do not ask the owner to invent a plan.4. Read and follow [`../loop-graph/SKILL.md`](../loop-graph/SKILL.md) from **When called from a preset skill** through generate and deliver. Compile only from loop-graph's [`templates/`](../loop-graph/templates/). This skill never executes the generated nodes.

Frequently asked questions