Auto-Optimize
An Agent Skill for vibe coding and AI workflow development。Built for when you hit these walls:Vague requirements → no baseline, endless rework、Only one prompt phrasing → can't tell if the problem is you or the model、Model says "looks good" → but features are missing 、great output last time, no idea how to reproduce it.
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Badge for your README
Markdown
[](/listings/gilbertwuu--auto-optimize)HTML
<a href="/listings/gilbertwuu--auto-optimize"><img src="/api/listings/gilbertwuu--auto-optimize/badge.svg" alt="findsafeskills safety rating" /></a>Install
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
1. Keep this repo at your project root (or merge `SKILL.md`, `program.md`, `docs/`, `scripts/` into an existing repo). 2. Optional: add host-specific rules (e.g. `.cursor/rules/`, OpenClaw config) to enforce the workflow. 3. Ask for features in your host; the agent should follow the phases when this Skill is loaded. 4. Verify from **repository root**:
FINAL_TRACK_FILE=tracks/prompt-a/r05.html DELIVERY_FILE=index.html bash scripts/skill-verify.sh
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
SKILL.md · Manifest · 61 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
- ---
- name: auto-optimize
- description: >-
- Host-agnostic Agent Skill: double-layer workflow for AI-assisted delivery—requirement
- specification, multi-prompt outer loop, on-disk inner iterations, phase gates,
- optional byte-level verify. For any IDE, CLI, or Skill-capable tool (e.g. OpenClaw).
- Read program.md and docs/verifiability.md before editing delivery artifacts unless waived.
- ---
- # Double-layer auto-optimization (Skill entry)
- This file is the **Skill package entry** (`SKILL.md`). Normative text lives under `docs/`. **Not tied to a specific IDE**—any host that loads this Skill can use it.
- ## Strict execution (hard constraints)
- - The agent **must** follow **`program.md`**, **`docs/verifiability.md`**, **`docs/phase-01-spec.md`** through **`phase-04-output.md`**, and **`docs/execution.md`** in full; **must not** shorten the workflow to save tokens, time, or because it “feels enough”.
- - **Each** `tracks/prompt-*/` inner loop **must** satisfy **`docs/phase-03-inner.md`**: **gates** (e.g. at least **r01**, **r02** per scheme) and **main termination** (**all items checked** in **`tracks/phase-01-acceptance.md`**; or **5** rounds max). Self-score “≥8” **must not** alone justify stopping (**`verifiability.md` R3**). **Forbidden**: claiming a track is “deliverable” and moving to phase 4 before the acceptance checklist passes.
- - **Forbidden**: using “reduce workload” or other **reasons not in the Skill** to deviate; **only** when the user **explicitly waives in the current turn** may the full workflow be skipped.
- ## Quick start (agent)
- 1. Read **[program.md](program.md)** (shortest path) or the checklist below; **do not skip** **[docs/verifiability.md](docs/verifiability.md)** (R1–R5).
- 2. Open phases in order: **`docs/phase-01-spec.md`** → **`phase-02-prompts.md`** → **`phase-03-inner.md`** → **`phase-04-output.md`**; read **[docs/execution.md](docs/execution.md)** for cost/order reminders.
- 3. **Before** phase 1 gates pass, do not rewrite delivery code; phase 1 **must** write **`tracks/phase-01-acceptance.md`** (**R3**); phase 2 **must** write **`tracks/phase-02-consistency-check.md`** (check + scheme–dimension table); **`r01` for `prompt-b`/`prompt-c` must not** be a full-page copy of `prompt-a`; waivers **must** be explicit in the **current** user message.
- 4. Before claiming delivery matches the final track file, in a class-A environment actually run **`scripts/skill-verify.sh`** from the **repository root** (see [program.md](program.md)).
- ## Execution checklist
- ```text
- - [ ] Read docs/verifiability.md (R1–R5)
- - [ ] Phase 1: spec written, feature list non-empty; tracks/phase-01-acceptance.md exists with ≥1 item
- - [ ] Phase 2: outer prompts + consistency check; tracks/phase-02-consistency-check.md written (with table)
- - [ ] Phase 3: each tracks/prompt-*/ has at least r01.* and r02.*; non-a r01 is independently generated
- - [ ] Phase 4: compare & output; at least one track fully checked before final delivery (R3; self-score reference only)
- - [ ] Delivery claim: ran skill-verify.sh and recorded command + output (R2/R4)
- ```
- ## Resource index
- | Resource | Path |
- |----------|------|
- | Shortest entry | [program.md](program.md) |
- | R1–R5 authority | [docs/verifiability.md](docs/verifiability.md) |
- | Phases 1–4 | [docs/phase-01-spec.md](docs/phase-01-spec.md) etc. |
- | Execution | [docs/execution.md](docs/execution.md) |
- | Layout & verify | [reference.md](reference.md) |
- | Example | [examples.md](examples.md) |
- | Human guide | [SKILL-GUIDE.md](SKILL-GUIDE.md) |
- | Script | `scripts/skill-verify.sh` (run from repo root) |
- ## User waiver
- Must be **written in the current task message**, e.g.:
- `This task waives the Skill / skips phases`
- (Synonyms allowed if equally explicit; the agent **must not** infer a waiver.)
- ## High-risk domains
- Does not replace regulation, clinical procedures, or human review; model self-scores and scripts are not sole safety evidence.
README.md · README · 41 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
- # Auto-optimize — Agent Skill
- **Double-layer auto-optimization Agent Skill** — **host-agnostic**: use with any IDE, CLI, or Skill-capable tool (OpenClaw, editor integrations, etc.), not tied to a single vendor.
- ## One-liner
- An **Agent Skill** workflow (entry: root `SKILL.md` + `docs/`): lock requirements first, iterate **multiple Prompt phrasings** in parallel, write **each round to disk** under `tracks/prompt-*/`, use an **acceptance checklist** (not self-score alone) as the delivery bar, and optionally **hash-compare** delivery vs the chosen final track file.
- ## Why use it?
- - Vague requirements → churn without a baseline
- - Only one phrasing → no A/B on “how to ask”
- - “Five iterations” with **no files** → not auditable
- - Self-score 8/10 while features missing
- - **No proof** delivery matches the “final” track file
- This Skill addresses that with **four phases** and **five verifiability rules (R1–R5)**.
- ## Quick start
- 1. Keep this repo at your project root (or merge `SKILL.md`, `program.md`, `docs/`, `scripts/` into an existing repo).
- 2. Optional: add host-specific rules (e.g. `.cursor/rules/`, OpenClaw config) to enforce the workflow.
- 3. Ask for features in your host; the agent should follow the phases when this Skill is loaded.
- 4. Verify from **repository root**:
- ```bash
- FINAL_TRACK_FILE=tracks/prompt-a/r05.html DELIVERY_FILE=index.html bash scripts/skill-verify.sh
- ```
- ## Layout
- | Path | Role |
- |------|------|
- | `SKILL.md` | Skill entry (YAML `description` for discovery) |
- | `program.md` | Shortest path for agents |
- | `docs/` | R1–R5 and phase 1–4 norms |
- | `scripts/skill-verify.sh` | Optional checks (run from repo root) |
- ## License
- MIT — see [LICENSE](LICENSE).
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.