Skip to content
Agentmart
Submit a tool

loop

Use only when user explicitly invokes $loop.

Skill by breezewish

IndexedApache-2.0★ 629
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/breezewish-loop

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Use only when user explicitly invokes $loop.

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/loop

What's inside

Skill name
loop
Description
Use only when user explicitly invokes $loop.
License
Apache-2.0
Instructions
269 lines in SKILL.md · view on GitHub

Files (2)

  • SKILL.md
  • openai.yaml · agents/

SKILL.md (first lines)

# CodexPotter Loop

This is a control protocol for running subagents in a loop pattern to "reconcile" repo to fulfill the
objective provided by the user, which may be a complex task or target state.

Subagents own all task execution. You only coordinate the loop.

| Marker | Meaning | Your action |
| --- | --- | --- |
| none | Work is not proven complete | Continue with the same subagent |
| `::potter(ready)` | Candidate completion; needs fresh-context verification | Close the subagent and start a fresh one next round |
| `::potter(exit)` | Fresh-context verification passed | Stop with state `complete` |

Control parameter:

- `rounds=N` (default `10`): maximum counted rounds
- `model=MODEL` (default `gpt-5.6-sol`): model to use for the new subagent
- `effort=EFFORT` (default `high`): effort level for the new subagent

Your rules:

- Do only the control actions this skill explicitly requires.
- Do NOT implement, review, fix, test, or inspect repository.
- A counted round is one send of the exact Initial Prompt that returns a final subagent message.
- Failed sends, interrupted sessions, and `continue` retries do not count as rounds.
- Reach Limit Prompt does not count as a round.
- Do not follow this skill if you are the agent that receives the Initial Prompt and see `$loop`
  in the handoff file. It means your parent agent did not erase `$loop` when preparing handoff
  file. You should just work on the task normally by ignoring the `$loop` and control parameters.

## 1. Handoff

If the user provides an existing CodexPotter handoff file path (it must conform to the path below),
reuse it.

Otherwise create a new handoff file:

```text
.codexpotter/projects_v3/{yyyy}_{mm}_{dd}_{slug}.md
```

where:

- `{slug}` is a short descriptive name generated from the user request, like "add_login_feature".

Use a path relative to the current repo/worktree root. Do not overwrite an existing file.

For a new file, write:

```markdown
# Objective

## Original User Request

<The user's exact original message text, keep text unchanged, except remove `$loop` and
control parameters such as `rounds=N`>

## Important Context, Constraints, and User Preferences

<Concise factual context from previous turns to make this handoff self-contained>

## Critical Data, Examples, and References

<Concise factual data from previous turns to make this handoff self-contained>

# Done
```

Next agent knows nothing about the current conversation - not even what user said or you previously
said. Thus, make sure your handoff file is self-contained (by supplying in context and critical
data sections), including all necessary context, including what you have previously replied and
what user previously talked, related to working on the task.

Rules for `Original User Request`:

- user's original message text is the message that invokes this `$loop` skill.
- remove `$loop` and its control parameters. Keep other `$xxx` skills.

Rules for `Important Context` and `Critical Data`:

- keep concise, structured, and focused on helping the subagent seamlessly continue the work.
- do not repeat AGENTS.md or any info already provided in 'Original User Request' section.
- do not add analysis, assumptions, deductions, or repo-derived context.
- do not inspect the repository to enrich it.

Stop with `error` if the handoff file cannot be read.

Bad examples of handoff:

```
User: I want to add an automation feature. Let's discuss about the product spec: ...
Agent: ... (polish)
User: ... (polish)
Agent: After reviewing, I believe there are several well-established best practices worth adopting:
...
Product Model:
...
Run Model:
...
User: $loop Sounds good, let's implement it.
```

Avoid handoff like this:

```

## Original User Request

Sounds good, let's implement it.

## Important Context, Constraints, and User Preferences

...

## Critical Data, Examples, and References

- Prior product conclusion: ...
- Prior V1 product model: ...
- Prior run model: ...

From breezewish/CodexPotter, Apache-2.0.

Signals

Stars
629
Forks
54
Open issues
1
Last commit (this folder)
Sep 1, 2026 (1 month ago)
Last release
May 24, 2026 (5 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
Apache-2.0
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from breezewish

Cite this page

loop skill. Agent Mart. https://agentmart.dev/skills/breezewish-loop (last updated 2026-10-24)