10-of-my-most-popular-text-to-image-series-prompts-78b0897e
generate a bunch of images, then you curate the results to handpick the best ones
Structured Read→Plan→Execute→Verify→Report protocol for any task with side effects. Prevents false "done" reports, blind retries, and scope creep. Activate for file edits, shell commands, multi-step operations, or anything irreversible. Skip for pure Q&A. Integrates with agent-task-tracker (state persistence) and agent-step-sequencer (complex multi-step heartbeat).
Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.
SkillHub CLI
skillhub install cycy2xxx/agent-loopInspect the source and compatibility requirements, then follow its installation steps.
Give your agent the source link and ask it to inspect instructions and dependencies before explaining the installation steps.
Core rule: You must complete each phase in order. Do not skip phases. Do not report "done" until you have evidence from the Verify phase.
IF the task involves any of:
THEN apply this full protocol. ELSE (pure Q&A, one-sentence reply) → skip this skill entirely.
Before touching anything:
FORBIDDEN: Edit a file you have not read this session
FORBIDDEN: Assume file content without reading
IF task has 3+ steps → write a numbered plan before executing:
Plan:
1. Read <file>
2. Edit <file>: change X → Y
3. Run <command> to verify
4. Report result with evidence
agent-step-sequencer for plans with background processes or that must survive gateway resetsagent-task-tracker is installed → save plan to memory/tasks.md
memory/tasks.md after each stepIF a step fails:
FORBIDDEN: Retry the same failing command unchanged
FORBIDDEN: Skip a failed step and continue as if it succeeded
Before reporting done, confirm success with evidence:
| What you did | How to verify |
|---|---|
| Edited a file | Read it again — confirm the change is present |
| Ran a command | Check exit code AND output content |
| Created a file | Confirm it exists and has expected... |
These signals come from indexed source analysis and may lag behind changes. Check the current source files.
# Agent Loop > **Core rule:** You must complete each phase in order. Do not skip phases. > Do not report "done" until you have evidence from the Verify phase. --- ## Phase 0 — Trigger Check **IF** the task involves any of: - reading or writing files - running shell commands - multi-step operations (3+ steps) - actions that cannot be undone **THEN** apply this full protocol. **ELSE** (pure Q&A, one-sentence reply) → skip this skill entirely. --- ## Phase 1 — READ **Before touching anything:** - IF you need to edit a file → read it first, in this session - IF you need to know a file's content → read it, never recall from memory - IF you need to run a command → confirm what it does before running ``` FORBIDDEN: Edit a file you have not read this session FORBIDDEN: Assume file content without reading ``` --- ## Phase 2 — PLAN **IF task has 3+ steps → write a numbered plan before executing:** ``` Plan: 1. Read <file> 2. Edit <file>: change X → Y 3. Run <command> to verify 4. Report result with evidence ``` - IF the plan includes destructive or irreversible actions → ask for confirmation first - Use `agent-step-sequencer` for plans with background processes or that must survive gateway resets - IF `agent-task-tracker` is installed → save plan to `memory/tasks.md` --- ## Phase 3 — EXECUTE - Complete one step fully before starting the next - Record progress in `memory/tasks.md` after each step **IF a step fails:** 1. Read the full error message completely 2. Identify the root cause — do not guess 3. Change your approach before retrying ``` FORBIDDEN: Retry the same failing command unchanged FORBIDDEN: Skip a failed step and continue as if it succeeded ``` --- ## Phase 4 — VERIFY **Before reporting done, confirm success with evidence:** | What you did | How to verify | |---|---| | Edited a file | Read it again — confirm the change is present | | Ran a command | Check exit code AND output content | | Created a file | Confirm it exists and has expected...
generate a bunch of images, then you curate the results to handpick the best ones
generate a bunch of images, then you curate the results to handpick the best ones
Productivity system based on Maya calendar with 13 natural tones for project management and personal development
Set up and use 1Password CLI (op). Use when installing the CLI, enabling desktop app integration, signing in (single or multi-account), or reading/injecting/running secrets via op.