loop-generator

Generate loop instruction docs, driver scripts, and Invoker workflow YAML from a structured interview.

18|5|Updated Apr 17, 2026
One-click install
npx skills add https://github.com/Neko-Catpital-Labs/Invoker --skill loop-generator-neko-catpital-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: loop-generator
Source: https://github.com/Neko-Catpital-Labs/Invoker/tree/main/skills/loop-generator
Command: npx skills add https://github.com/Neko-Catpital-Labs/Invoker --skill loop-generator-neko-catpital-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Building a reusable babysit/watch/retry loop normally requires hand-writing a loop instruction doc, a shell driver, and an Invoker workflow YAML, each with strict contracts that are easy to get wrong. This Skill turns one structured interview into all three artifacts with consistent naming, safety rules, and validation. ## Core Features & Use Cases - Interview-driven generation: Resolves a 15-field schema (goal, success criteria, evidence sources, write mode, submission mode, and more) before drafting anything, so generated loops are concrete rather than guessed. - Three coordinated artifacts: Produces a loop instruction markdown doc with a fixed section contract, a driver shell script with safe state-copy inspection and failure dedupe, and an Invoker workflow YAML routed through the plan-to-invoker handoff pipeline. - Benchmark/direct-output mode: For headless prompts with a literal required output path, writes the artifact directly without clarifying questions, validation, or submission. - Use Case: Ask for a worker-only PR babysitting loop; the Skill interviews you on success criteria and blockers, then generates the loop doc, driver script, and validated Invoker YAML ready for review and submission. ## Quick Start Ask the assistant to use the loop generator to build a reusable watch-and-retry loop and answer its interview questions about goal, success criteria, and write mode.

Frequently Asked Questions about loop-generator

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

FAQPage Schema
How do I generate a reusable retry loop for my repository?

Invoke the loop generator and answer its interview covering goal, target discovery command, success criteria, evidence sources, and write mode. It then drafts a loop instruction doc, a driver shell script, and an Invoker workflow YAML with consistent naming.

What artifacts does the loop generator produce?

It always produces three artifacts: a loop instruction markdown doc with a fixed section order, a driver shell script with target dedupe and failure summaries, and an Invoker workflow YAML. It also writes a canonical review artifact to plans/invoker-handoff.md.

Can the loop generator submit the Invoker workflow automatically?

Submission depends on the chosen submission_mode. The default review_then_submit generates and validates but waits for explicit approval, generate_only never submits, and submit_immediately submits after validation passes, except in Slack planning threads where self-submission is disabled.

How does the generated driver script avoid mutating live state?

The driver copies mutable state before running any dry-run or inspection command and never widens read-only inspection into live writes. It rebuilds the target set from the discovery command each run and dedupes by the configured identity key.

When does the loop generator skip the interview and write output directly?

Direct-output mode applies only to headless benchmark prompts that specify a literal required output path. In that mode it writes the artifact to the exact path without clarifying questions, validation, review gates, or submission.