[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MEKK2Y8SGC0G02GGZHZ0CD":3,"skill-same:01M6MEKK2Y8SGC0G02GGZHZ0CD":92},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":29,"linkOnly":30,"markdownContent":31,"markdownBody":32,"frontMatter":33,"refName":36,"commitSha":37,"skillDirectory":38,"forksCount":39,"repositoryHtmlUrl":40,"repositoryHomepageUrl":41,"ownerHtmlUrl":42,"ownerBlogUrl":43,"ownerDescription":44,"updatedAt":45,"install":46,"resources":59},"01M6MEKK2Y8SGC0G02GGZHZ0CD","superloopy-loop",null,"Use Superloopy's lightweight strict-evidence loop for Codex tasks that need durable progress, criteria, and artifact-backed completion.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fbeefiker\u002Fsuperloopy\u002Fskills\u002Fsuperloopy-loop\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28],"loop","superloopy loop","codex","tasks","harness","use","evidence","artifact","progress","for","2026-11-10 10:12:30",false,"---\nname: superloopy-loop\ndescription: Use Superloopy's lightweight strict-evidence loop for Codex tasks that need durable progress, criteria, and artifact-backed completion.\nmetadata:\n  short-description: Lightweight strict-evidence loop harness\n---\n\n# superloopy-loop\n\nUse this skill when the user asks for Superloopy, loopywork, lpy, a loop harness, durable criteria, evidence-backed completion, strict-but-light task flow, or guided next actions.\n\n## Contract\n\n- State lives in `.superloopy\u002F`, or `.superloopy\u002Fsessions\u002F\u003Cid>\u002F` when `--session-id` is used.\n- Do not hand-edit `.superloopy\u002Fgoals.json`; use the CLI.\n- A criterion can pass only after a real artifact exists under the active evidence root.\n- User steering must use `SUPERLOOPY_STEER` JSON; do not hand-edit `.superloopy\u002Fgoals.json`.\n- Executor receipts should end with `SUPERLOOPY_EVIDENCE: \u003Cpath-under-active-evidence-root>`.\n- Legacy `EVIDENCE_RECORDED` receipts remain accepted for compatibility.\n- Tests are useful evidence, but completion requires the Superloopy evidence artifact.\n- Use `superloopy loop prove` when an active goal needs command-backed evidence for its next unresolved criterion.\n- Keep the workflow lightweight unless the task genuinely needs heavier review.\n- A leading `loopy` keyword wakes the loop engineer: take the rest of the prompt as the brief, run the loop yourself, and report progress instead of asking the user to type Superloopy commands.\n- `loopywork`, `$lpy`, and `lpy` are lighter prompt triggers; they inject guidance but never mutate `.superloopy\u002F` state by themselves.\n- Full Loopy runs default to direct, concise, complete user-facing progress and final responses. Exact `say-it-straight off` \u002F `직설 모드 끄기` and `say-it-straight on` \u002F `직설 모드 켜기` controls apply only to the current incomplete loop; new loops reset this default to enabled.\n- This output overlay changes wording only. It never silently rewrites supplied prose, task artifacts, code, documentation, comments, evidence, quotations, or user source text; direct artifact editing remains explicit-only. `i-have-adhd` still owns structure, and `humanize-korean` still owns Korean artifact rewriting.\n\n## Load on demand\n\nThese references hold the situational detail. Read the one a row names when its condition holds; the rules above and below apply to every run.\n\n| Read | When |\n|---|---|\n| [CLI flow](references\u002Fcli-flow.md) | Running Superloopy commands beyond the loop engineer's `begin` → `guide` → `prove` → `check` → `finish` path: `create`, `capture`, manual `evidence`, `trace`, `report`, a blocked `check` repair plan, custom `review`\u002F`checkpoint` gate workflows, or a cache-satisfied final proof. |\n| [Continuation engine](references\u002Fcontinuation.md) | The Stop hook re-prompted you (\"Superloopy continuation\"), a loop shown `blocked` or `paused` in `superloopy loop status`, a quota\u002Fusage limit, or scheduling an auto-resume. |\n| [Evidence audit](references\u002Fevidence-audit.md) | Running `superloopy loop audit`, dispatching `assayer`, or handling a failed, `inconclusive`, or `blocked` audit. |\n| [Crew](references\u002Fcrew.md) | Before dispatching any subagent (solo light delegation or `loopy team`\u002Fcrew): parent responsibilities, `handoff`\u002F`fleet` bookkeeping, the self-contained dispatch contract, subagent lifecycle, and agent allocation. |\n| [Reassurance copy](references\u002Freassurance-copy.md) | The reassurance-copy condition below applies. |\n\n## Loop engineer (`loopy` keyword)\n\nWhen the user opens a message with `loopy \u003Ctask>`, act as the loop engineer:\n\n- Start once with `superloopy loop begin --brief \"\u003Ctask>\" --mode light --json`; do not create a second plan if one is active.\n- Drive each step from `superloopy loop guide --json`, prove criteria with `superloopy loop prove -- \u003Ccommand>`, preflight with `superloopy loop check`, then finish with `superloopy loop finish --evidence \"\u003Csummary>\" --artifact .superloopy\u002Fevidence\u002Fgate.json --json`.\n- The user types only `loopy \u003Ctask>`. You run every Superloopy command and report progress as criteria proven and the next step.\n- `loopy` with no task asks what to build; `loopy` mid-loop resumes from existing state. After a `loopy` prompt, the packaged Stop hook keeps this session going while criteria remain, until the user sends a plain prompt (`SUPERLOOPY_STOP_HOOK=on` drives every session, `off` disables it). If it reports a worker that stopped without proof, treat that worker's reply as unproven.\n\n### Execution discipline\n\nThe loop engineer directive carries three rules distilled from a component-level harness study (arXiv 2609.20804). For strong models, most avoidable cost is redundant verification, unchanged re-runs of a failing check, and many small re-patches.\n\n- Prove each criterion once with the narrowest command that decides it, then move on. Do not re-run passing proof or broad suites between criteria; `loop finish` re-runs every passed command-backed criterion before it completes (trusted commands only; commandless proof gets an artifact-existence check). `loop check` validates artifacts and does not re-run anything.\n- When a proof fails, its output is already in the capture artifact. Read the failing part (tail or search), then change the code or the proof command before proving again; if the criterion itself is wrong, ask the user to revise it with a `revise_criterion` steer. After 3 consecutive failures of one criterion with the same command, exit, and normalized output tail, `prove`, `capture`, `trace`, `check`, and `report` emit a `repeated-failing-proof` warning. Normalization ignores run-to-run noise (timestamps, durations, labeled PIDs and ports, UUIDs, hashes, temp paths, stack positions, numbers of 10+ digits such as epoch times) but keeps other numbers, so a changed assertion value or pass\u002Ffail count breaks the streak. Any other evidence for that criterion, including a pass, a manual `loop evidence` record, or a revised criterion, resets it. The warning is advisory and never blocks; with `SUPERLOOPY_STOP_HOOK=on`, the Stop hook's no-progress cap (3 iterations without a new pass) still marks a stalled loop `blocked`.\n- Batch independent reads and shell steps into one call, and land each file change as one coherent edit.\n- After compaction, the recovery capsule lists failing proof with its artifact path. Re-read that artifact instead of re-running the command to see the error again.\n\n### Reassurance-copy gate (conditional)\n\n- Decide from the affected artifact: if it creates or changes user-visible Korean product copy about behavior, add a plan criterion for RC-1 through RC-4 and Korean naturalness.\n- State supplied outcomes, fallback, recovery, or next action; preserve verified privacy\u002Flegal commitments; never invent behavior.\n- Apply `humanize-korean` semantic review for misplaced modifiers.\n- Ignore internal logs, developer docs, quotations, general\u002Fmarketing prose, and non-Korean copy.\n\nRead the detailed [reassurance-copy reference](references\u002Freassurance-copy.md) when this condition applies. Artifact ownership decides the condition; prompt wording does not.\n\n### Two tiers: solo and crew (`loopy team`)\n\nThe loop engineer directive is injected for every `loopy` prompt, and it scales to the work:\n\n- **Solo (default).** A plain `loopy \u003Ctask>` drives one agent through the loop. The directive still permits light delegation: if the work splits into 2+ genuinely independent slices, you may fan them out with the native subagent controls exposed by the current host; keep each assignment self-contained. For a single cohesive change, stay solo.\n- **Crew (`loopy team \u003Ctask>` \u002F `loopy crew \u003Ctask>`, the connected one-word `loopycrew \u003Ctask>`, or the standalone `ultrawork \u003Ctask>`).** The same engineer escalates into full fan-out: dispatch the crew across independent lanes, collect them with the host's native lifecycle controls, and record only artifact-backed proof. The escalation keyword is stripped from the brief that seeds the loop. This is the active counterpart to \"Optional Subagent-Driven Mode\" below — same dispatch contract, receipt gate, and mandatory `handoff`\u002F`fleet` tracking.\n\nEach crew dispatch uses the configured name when the host exposes named selection: `forge` to build, `sentinel` to review, `probe` to test, `arbiter` to gate, `assayer` to audit, and `pathfinder` to navigate. The assignment also stays self-contained (`TASK: act as \u003Crole> ...`). The orchestrator itself runs on the model the user selected in the host (`gpt-6-astra` is allowed when selected); crew lanes keep their `model-policy.json` pins and never inherit the orchestrator's model. The host-owned stop callback observes the actual role identity; if the host cannot attest that identity or model, report `role_unverified` or `model_unverified`.\n\nBoth tiers are steering, not enforcement: the directive instructs the main agent, and actual spawning depends on the host's native multi-agent tool being available. Superloopy never spawns; it gates the evidence workers deliver. See \"Optional Subagent-Driven Mode\" for the full dispatch contract and crew roles.\n\n## Optional Subagent-Driven Mode\n\nUse project custom agents from `.codex\u002Fagents\u002F` only when the user asks for subagents or the work has independent implementation, review, and QA lanes. The normal single-agent Superloopy flow remains the default for small changes.\n\nSuperloopy provisions and tracks these agents; the host (Codex) spawns them. Superloopy never spawns. The host spawn surface cannot reliably select a bundled TOML role, model, or reasoning effort by name, so every dispatch must be self-contained and judged by delivered evidence — never by the role label requested. See `docs\u002Fsuperloopy-host-contract.md`.\n\nPlugin installs bootstrap the `superloopy` command wrapper and bundled custom agents on the first approved `SessionStart` hook. If the host does not run that hook, run `node src\u002Fcli.js install --json` from the Superloopy checkout or installed plugin root. `superloopy agents install` remains available to copy only the bundled custom agents into the personal Codex agents directory (`$CODEX_HOME\u002Fagents` when set, otherwise `~\u002F.codex\u002Fagents`). Restart Codex after installation.\n\nBefore dispatching any worker, read [Crew](references\u002Fcrew.md): it carries the parent agent responsibilities, the dispatch contract, the subagent lifecycle, and agent allocation.\n\n## Quality Gate\n\nEvery listed artifact must exist, be non-empty, and live under the active evidence root. Superloopy also accepts strict review gates and matrix gates when reviewer\u002Farchitect, executor QA, rerun, artifact, and coverage fields validate. `loop review` and `loop finish` always write the default gate. A review gate is JSON you write by hand and pass to `loop checkpoint --quality-gate`; write one only when `sentinel`, `probe`, and `arbiter` each actually ran, and sign it as [Crew](references\u002Fcrew.md) describes under \"Review gate actors\".\n\nFor executor receipts, use the active evidence root. A global loop normally records under `.superloopy\u002Fevidence\u002F`; a scoped loop records under `.superloopy\u002Fsessions\u002F\u003Cid>\u002Fevidence\u002F`. If a receipt is missing or invalid, the receipt block message names the active evidence root to repair.\n\nKeep the human final gate report and the Superloopy quality gate artifact separate. A `arbiter` report is Markdown evidence (for example `.superloopy\u002Fevidence\u002Farbiter-final-gate-report.md`). The `superloopy loop review` and `superloopy loop finish --artifact` flag writes the machine-validated quality gate artifact and must point to JSON, normally `.superloopy\u002Fevidence\u002Fgate.json`. Never pass the Markdown report path as the finish artifact.\n\n## Steering\n\nAccept only structured prompt-level steering:\n\n```text\nSUPERLOOPY_STEER: {\"kind\":\"annotate\",\"evidence\":\"fact\",\"rationale\":\"why it matters\"}\nSUPERLOOPY_STEER: {\"kind\":\"add_goal\",\"title\":\"New slice\",\"objective\":\"Concrete objective\",\"rationale\":\"why it changed\"}\nSUPERLOOPY_STEER: {\"kind\":\"revise_criterion\",\"goalId\":\"G001\",\"criterionId\":\"C002\",\"scenario\":\"New scenario.\",\"rationale\":\"why it changed\"}\nSUPERLOOPY_STEER: {\"kind\":\"reorder_pending\",\"goalIds\":[\"G003\",\"G002\"],\"rationale\":\"why this order\"}\n```\n\nAfter any accepted steering, follow the returned guide; run `superloopy loop status --json` when you need a fresh reorientation.\n\n## Doctor\n\n`superloopy doctor --json` checks the package, hooks, bundled skills, CLI, dependency-free boundary, runtime ignore policy, file inventory, gate notes, design audit, generic comparison scan status, dispatch coherence, model policy, and reviewability.\n\nUse `superloopy doctor --comparison-path \u002Fpath\u002Fto\u002Fcomparison --json` only when you need copied-block evidence against an external folder. The generic comparison scan compares code-shaped files for substantial contiguous blocks without naming or coupling Superloopy to any source project.\n","# superloopy-loop\n\nUse this skill when the user asks for Superloopy, loopywork, lpy, a loop harness, durable criteria, evidence-backed completion, strict-but-light task flow, or guided next actions.\n\n## Contract\n\n- State lives in `.superloopy\u002F`, or `.superloopy\u002Fsessions\u002F\u003Cid>\u002F` when `--session-id` is used.\n- Do not hand-edit `.superloopy\u002Fgoals.json`; use the CLI.\n- A criterion can pass only after a real artifact exists under the active evidence root.\n- User steering must use `SUPERLOOPY_STEER` JSON; do not hand-edit `.superloopy\u002Fgoals.json`.\n- Executor receipts should end with `SUPERLOOPY_EVIDENCE: \u003Cpath-under-active-evidence-root>`.\n- Legacy `EVIDENCE_RECORDED` receipts remain accepted for compatibility.\n- Tests are useful evidence, but completion requires the Superloopy evidence artifact.\n- Use `superloopy loop prove` when an active goal needs command-backed evidence for its next unresolved criterion.\n- Keep the workflow lightweight unless the task genuinely needs heavier review.\n- A leading `loopy` keyword wakes the loop engineer: take the rest of the prompt as the brief, run the loop yourself, and report progress instead of asking the user to type Superloopy commands.\n- `loopywork`, `$lpy`, and `lpy` are lighter prompt triggers; they inject guidance but never mutate `.superloopy\u002F` state by themselves.\n- Full Loopy runs default to direct, concise, complete user-facing progress and final responses. Exact `say-it-straight off` \u002F `직설 모드 끄기` and `say-it-straight on` \u002F `직설 모드 켜기` controls apply only to the current incomplete loop; new loops reset this default to enabled.\n- This output overlay changes wording only. It never silently rewrites supplied prose, task artifacts, code, documentation, comments, evidence, quotations, or user source text; direct artifact editing remains explicit-only. `i-have-adhd` still owns structure, and `humanize-korean` still owns Korean artifact rewriting.\n\n## Load on demand\n\nThese references hold the situational detail. Read the one a row names when its condition holds; the rules above and below apply to every run.\n\n| Read | When |\n|---|---|\n| [CLI flow](references\u002Fcli-flow.md) | Running Superloopy commands beyond the loop engineer's `begin` → `guide` → `prove` → `check` → `finish` path: `create`, `capture`, manual `evidence`, `trace`, `report`, a blocked `check` repair plan, custom `review`\u002F`checkpoint` gate workflows, or a cache-satisfied final proof. |\n| [Continuation engine](references\u002Fcontinuation.md) | The Stop hook re-prompted you (\"Superloopy continuation\"), a loop shown `blocked` or `paused` in `superloopy loop status`, a quota\u002Fusage limit, or scheduling an auto-resume. |\n| [Evidence audit](references\u002Fevidence-audit.md) | Running `superloopy loop audit`, dispatching `assayer`, or handling a failed, `inconclusive`, or `blocked` audit. |\n| [Crew](references\u002Fcrew.md) | Before dispatching any subagent (solo light delegation or `loopy team`\u002Fcrew): parent responsibilities, `handoff`\u002F`fleet` bookkeeping, the self-contained dispatch contract, subagent lifecycle, and agent allocation. |\n| [Reassurance copy](references\u002Freassurance-copy.md) | The reassurance-copy condition below applies. |\n\n## Loop engineer (`loopy` keyword)\n\nWhen the user opens a message with `loopy \u003Ctask>`, act as the loop engineer:\n\n- Start once with `superloopy loop begin --brief \"\u003Ctask>\" --mode light --json`; do not create a second plan if one is active.\n- Drive each step from `superloopy loop guide --json`, prove criteria with `superloopy loop prove -- \u003Ccommand>`, preflight with `superloopy loop check`, then finish with `superloopy loop finish --evidence \"\u003Csummary>\" --artifact .superloopy\u002Fevidence\u002Fgate.json --json`.\n- The user types only `loopy \u003Ctask>`. You run every Superloopy command and report progress as criteria proven and the next step.\n- `loopy` with no task asks what to build; `loopy` mid-loop resumes from existing state. After a `loopy` prompt, the packaged Stop hook keeps this session going while criteria remain, until the user sends a plain prompt (`SUPERLOOPY_STOP_HOOK=on` drives every session, `off` disables it). If it reports a worker that stopped without proof, treat that worker's reply as unproven.\n\n### Execution discipline\n\nThe loop engineer directive carries three rules distilled from a component-level harness study (arXiv 2609.20804). For strong models, most avoidable cost is redundant verification, unchanged re-runs of a failing check, and many small re-patches.\n\n- Prove each criterion once with the narrowest command that decides it, then move on. Do not re-run passing proof or broad suites between criteria; `loop finish` re-runs every passed command-backed criterion before it completes (trusted commands only; commandless proof gets an artifact-existence check). `loop check` validates artifacts and does not re-run anything.\n- When a proof fails, its output is already in the capture artifact. Read the failing part (tail or search), then change the code or the proof command before proving again; if the criterion itself is wrong, ask the user to revise it with a `revise_criterion` steer. After 3 consecutive failures of one criterion with the same command, exit, and normalized output tail, `prove`, `capture`, `trace`, `check`, and `report` emit a `repeated-failing-proof` warning. Normalization ignores run-to-run noise (timestamps, durations, labeled PIDs and ports, UUIDs, hashes, temp paths, stack positions, numbers of 10+ digits such as epoch times) but keeps other numbers, so a changed assertion value or pass\u002Ffail count breaks the streak. Any other evidence for that criterion, including a pass, a manual `loop evidence` record, or a revised criterion, resets it. The warning is advisory and never blocks; with `SUPERLOOPY_STOP_HOOK=on`, the Stop hook's no-progress cap (3 iterations without a new pass) still marks a stalled loop `blocked`.\n- Batch independent reads and shell steps into one call, and land each file change as one coherent edit.\n- After compaction, the recovery capsule lists failing proof with its artifact path. Re-read that artifact instead of re-running the command to see the error again.\n\n### Reassurance-copy gate (conditional)\n\n- Decide from the affected artifact: if it creates or changes user-visible Korean product copy about behavior, add a plan criterion for RC-1 through RC-4 and Korean naturalness.\n- State supplied outcomes, fallback, recovery, or next action; preserve verified privacy\u002Flegal commitments; never invent behavior.\n- Apply `humanize-korean` semantic review for misplaced modifiers.\n- Ignore internal logs, developer docs, quotations, general\u002Fmarketing prose, and non-Korean copy.\n\nRead the detailed [reassurance-copy reference](references\u002Freassurance-copy.md) when this condition applies. Artifact ownership decides the condition; prompt wording does not.\n\n### Two tiers: solo and crew (`loopy team`)\n\nThe loop engineer directive is injected for every `loopy` prompt, and it scales to the work:\n\n- **Solo (default).** A plain `loopy \u003Ctask>` drives one agent through the loop. The directive still permits light delegation: if the work splits into 2+ genuinely independent slices, you may fan them out with the native subagent controls exposed by the current host; keep each assignment self-contained. For a single cohesive change, stay solo.\n- **Crew (`loopy team \u003Ctask>` \u002F `loopy crew \u003Ctask>`, the connected one-word `loopycrew \u003Ctask>`, or the standalone `ultrawork \u003Ctask>`).** The same engineer escalates into full fan-out: dispatch the crew across independent lanes, collect them with the host's native lifecycle controls, and record only artifact-backed proof. The escalation keyword is stripped from the brief that seeds the loop. This is the active counterpart to \"Optional Subagent-Driven Mode\" below — same dispatch contract, receipt gate, and mandatory `handoff`\u002F`fleet` tracking.\n\nEach crew dispatch uses the configured name when the host exposes named selection: `forge` to build, `sentinel` to review, `probe` to test, `arbiter` to gate, `assayer` to audit, and `pathfinder` to navigate. The assignment also stays self-contained (`TASK: act as \u003Crole> ...`). The orchestrator itself runs on the model the user selected in the host (`gpt-6-astra` is allowed when selected); crew lanes keep their `model-policy.json` pins and never inherit the orchestrator's model. The host-owned stop callback observes the actual role identity; if the host cannot attest that identity or model, report `role_unverified` or `model_unverified`.\n\nBoth tiers are steering, not enforcement: the directive instructs the main agent, and actual spawning depends on the host's native multi-agent tool being available. Superloopy never spawns; it gates the evidence workers deliver. See \"Optional Subagent-Driven Mode\" for the full dispatch contract and crew roles.\n\n## Optional Subagent-Driven Mode\n\nUse project custom agents from `.codex\u002Fagents\u002F` only when the user asks for subagents or the work has independent implementation, review, and QA lanes. The normal single-agent Superloopy flow remains the default for small changes.\n\nSuperloopy provisions and tracks these agents; the host (Codex) spawns them. Superloopy never spawns. The host spawn surface cannot reliably select a bundled TOML role, model, or reasoning effort by name, so every dispatch must be self-contained and judged by delivered evidence — never by the role label requested. See `docs\u002Fsuperloopy-host-contract.md`.\n\nPlugin installs bootstrap the `superloopy` command wrapper and bundled custom agents on the first approved `SessionStart` hook. If the host does not run that hook, run `node src\u002Fcli.js install --json` from the Superloopy checkout or installed plugin root. `superloopy agents install` remains available to copy only the bundled custom agents into the personal Codex agents directory (`$CODEX_HOME\u002Fagents` when set, otherwise `~\u002F.codex\u002Fagents`). Restart Codex after installation.\n\nBefore dispatching any worker, read [Crew](references\u002Fcrew.md): it carries the parent agent responsibilities, the dispatch contract, the subagent lifecycle, and agent allocation.\n\n## Quality Gate\n\nEvery listed artifact must exist, be non-empty, and live under the active evidence root. Superloopy also accepts strict review gates and matrix gates when reviewer\u002Farchitect, executor QA, rerun, artifact, and coverage fields validate. `loop review` and `loop finish` always write the default gate. A review gate is JSON you write by hand and pass to `loop checkpoint --quality-gate`; write one only when `sentinel`, `probe`, and `arbiter` each actually ran, and sign it as [Crew](references\u002Fcrew.md) describes under \"Review gate actors\".\n\nFor executor receipts, use the active evidence root. A global loop normally records under `.superloopy\u002Fevidence\u002F`; a scoped loop records under `.superloopy\u002Fsessions\u002F\u003Cid>\u002Fevidence\u002F`. If a receipt is missing or invalid, the receipt block message names the active evidence root to repair.\n\nKeep the human final gate report and the Superloopy quality gate artifact separate. A `arbiter` report is Markdown evidence (for example `.superloopy\u002Fevidence\u002Farbiter-final-gate-report.md`). The `superloopy loop review` and `superloopy loop finish --artifact` flag writes the machine-validated quality gate artifact and must point to JSON, normally `.superloopy\u002Fevidence\u002Fgate.json`. Never pass the Markdown report path as the finish artifact.\n\n## Steering\n\nAccept only structured prompt-level steering:\n\n```text\nSUPERLOOPY_STEER: {\"kind\":\"annotate\",\"evidence\":\"fact\",\"rationale\":\"why it matters\"}\nSUPERLOOPY_STEER: {\"kind\":\"add_goal\",\"title\":\"New slice\",\"objective\":\"Concrete objective\",\"rationale\":\"why it changed\"}\nSUPERLOOPY_STEER: {\"kind\":\"revise_criterion\",\"goalId\":\"G001\",\"criterionId\":\"C002\",\"scenario\":\"New scenario.\",\"rationale\":\"why it changed\"}\nSUPERLOOPY_STEER: {\"kind\":\"reorder_pending\",\"goalIds\":[\"G003\",\"G002\"],\"rationale\":\"why this order\"}\n```\n\nAfter any accepted steering, follow the returned guide; run `superloopy loop status --json` when you need a fresh reorientation.\n\n## Doctor\n\n`superloopy doctor --json` checks the package, hooks, bundled skills, CLI, dependency-free boundary, runtime ignore policy, file inventory, gate notes, design audit, generic comparison scan status, dispatch coherence, model policy, and reviewability.\n\nUse `superloopy doctor --comparison-path \u002Fpath\u002Fto\u002Fcomparison --json` only when you need copied-block evidence against an external folder. The generic comparison scan compares code-shaped files for substantial contiguous blocks without naming or coupling Superloopy to any source project.\n",{"name":5,"metadata":34,"description":7},{"short-description":35},"Lightweight strict-evidence loop harness","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Fbeefiker\u002Fsuperloopy\u002Fskills\u002Fsuperloopy-loop",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":47,"prompt":57,"zipAvailable":58},[48,51,54],{"tool":49,"command":50},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill superloopy-loop",{"tool":52,"command":53},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill superloopy-loop",{"tool":55,"command":56},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill superloopy-loop","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fbeefiker\u002Fsuperloopy\u002Fskills\u002Fsuperloopy-loop\u002FSKILL.md",true,[60,66,70,74,78,82,86],{"path":61,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":64,"sourceHtmlUrl":65},"agents\u002Fopenai.yaml","REFERENCE","参考文档",381,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fbeefiker\u002Fsuperloopy\u002Fskills\u002Fsuperloopy-loop\u002Fagents\u002Fopenai.yaml",{"path":67,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Fcli-flow.md",4338,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fbeefiker\u002Fsuperloopy\u002Fskills\u002Fsuperloopy-loop\u002Freferences\u002Fcli-flow.md",{"path":71,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Fcontinuation.md",3829,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fbeefiker\u002Fsuperloopy\u002Fskills\u002Fsuperloopy-loop\u002Freferences\u002Fcontinuation.md",{"path":75,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Fcrew.md",6964,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fbeefiker\u002Fsuperloopy\u002Fskills\u002Fsuperloopy-loop\u002Freferences\u002Fcrew.md",{"path":79,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Fevidence-audit.md",3185,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fbeefiker\u002Fsuperloopy\u002Fskills\u002Fsuperloopy-loop\u002Freferences\u002Fevidence-audit.md",{"path":83,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Freassurance-copy.md",2020,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fbeefiker\u002Fsuperloopy\u002Fskills\u002Fsuperloopy-loop\u002Freferences\u002Freassurance-copy.md",{"path":87,"resourceType":88,"resourceTypeDesc":89,"sizeBytes":90,"sourceHtmlUrl":91},"scripts\u002Faudit-reassurance-copy.mjs","SCRIPT","脚本",8492,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fbeefiker\u002Fsuperloopy\u002Fskills\u002Fsuperloopy-loop\u002Fscripts\u002Faudit-reassurance-copy.mjs",[93,103,111,119,127,135],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":97,"licenseFileUrl":98,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":102},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":97,"licenseFileUrl":107,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":102},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":97,"licenseFileUrl":115,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":102},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":97,"licenseFileUrl":123,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":102},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":97,"licenseFileUrl":131,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":102},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":97,"licenseFileUrl":139,"sourceHtmlUrl":140,"categories":141,"keywords":142,"publishedAt":102},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]