Menu

Individual skill

ads-creative-retro

0upvotes

Monthly, on the last weekday. Folds a month of the creative ledger against the daily metrics ledger to score angle, format, hook, and offer framing rather than individual files, tests every line currently in the creative doctrine against what the month actually measured, and rewrites the doctrine where the evidence disagrees with the assumption. It records the fatigue curve it observed, retires what has not earned, and changes nothing where the month holds too few rows to tell one angle from another.

employees/ad-manager-employee/routines/ads-creative-retro/SKILL.md

Read pinned source

Source commit 2cdd34e1f0d7bfa5b9dfadecf3d72b525fbb1577

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Instructions only
Last checked
Nov 10, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
878
Repository last updated
Nov 7, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

## Shared work cycle

After the guard returns `run`, read `WORK-CYCLE.md` and your entry in `work-profile.json`. Apply the contract's work-cycle extension to work selection, scoped blockers, progress evidence and claim recovery. Before closing, write the progress receipt, then the normal run record, then finish the claim with its token. Preserve the remaining budget on a resume. A same-period `run` with a claim overrides only the legacy Step 0.2 exit/reset. All pause, release and browser guards still apply.


# Creative retrospective

**Run the guard before you read anything else, this file included past this line.** Through `shell.run`: `node "«ADS_ROOT»/scripts/guard.mjs" ads-creative-retro`. It reads `PAUSED`, your row in `SCHEDULE.md`, and `state/ads-creative-retro.json`, and prints one verdict. On `skipped-paused`, `skipped-out-of-window`, `skipped-already-ran`, or `failed` it has already appended the run record: exit now and read nothing else. On `run`, carry on. Step 0 below repeats the same checks by hand and they stay, because a harness with no `shell.run` has nothing else to run them with; the guard exists so that a fire that should not run costs cents instead of a full read of the contract.

You are the analyst for the standing rules. Once a month you answer the question the weekly change list never asks: **are we making the right kind of work at all.**

`ads-change-list` answers "which object do I change this week". You answer a slower question, and you answer it by folding a month of evidence into four categories that survive across sets: **angle, format, hook, and offer framing.** Individual files are not the unit. A file is a thing that ran for three weeks and stopped working. An angle is a thing that either earns on this account or does not.

**The deliverable is `creative/doctrine.md` as it stands when you finish**, plus the lines in `plan/CHANGELOG.md` that say what moved and what moved it. The evidence table is how you get there, not what you hand over. **An evidence table nobody acted on is half a run, and a rewrite with no evidence path beside it is an opinion.**
Back to top