agentleFS
gooseworks-aigooseworks-ai/goose-skills/skills/marketing/honest-review/SKILL.md

honest-review

Skill1.3k starsChanged 23 days agoMITView on GitHub

Shared step of the marketing playbooks (make-static-ads, run-organic-social): how to review generated images and video honestly. Covers what was seen by eye versus read automatically, findings framed as things for the human to confirm, remakes only after a yes to the price, and at most two tries per item. Loaded by those playbooks; not for direct use.

1 other project uses a version of this.

Trending

More talk lately.about the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 1 mentionJun 2026: 0 mentionsJul 2026: 2 mentionsAug 2026: 1 mentionSep 2026: 0 mentionsOct 2026: 15 mentionsNov 2026: 1 mention
Dec 2025Jun 2026Nov 2026
Mentions a month of the gooseworks-ai/goose-skills repository that our weekly crawl found. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about gooseworks-ai/goose-skills

The biggest 5 of 20 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 20

Talked about on GitHub (20 times).

On GitHub · 20

15 more on GitHub

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never call generated media "ready" on automatic reads alone — "ready for your look" / "ready for your watch-through".

    line 36
  2. Distinctive:

    Only for a defect that is real (seen by eye, or confirmed by the human).

    line 41

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

honest-review

Used by: make-static-ads (its render-review step) and run-organic-social. The rubric — what to check — lives in each playbook; this atom is how to check and how to report.

1. Know what you can perceive

You canHowSay
See imagesThe host shows them, or a shell host downloads the file and opens it"checked by eye"
Read an automatic descriptiongooseworks:media_analyze on the asset (description, visible text, for video a word-timed transcript and sampled shots)"the automatic read shows…"
Watch motion or hear audioAlmost never — a transcript and sampled frames are not watchingnever claim it

Decide the mode at the start and label every item with how it was checked. Never present the engine's own "passed" or "checked" as your review.

2. Compare against the truth, not against expectations

  • Product: the brand's real product photos (curated — never an earlier generated image as the reference).
  • Words: the approved text (script, the image brief's exact on-image text, on-image copy) word for word.
  • Claims: the signed claims; anything drawn or spoken that is not on the approved text is a finding.
  • When you cannot see: compare the automatic read of the output with the automatic read of the reference on named fields — part or item count, readable label or on-screen text, colour words, which product is in which scene — and report each mismatch specifically ("the reference reads 'DIVE DEEP' on the label; the output read shows 'DIVE DEEEP'").

3. Report findings honestly

  • Each finding: what, where (region, scene, time), how it was found. From an automatic read: "the automatic read shows X at <place> — please confirm". Text absent from sampled frames is "not seen", never "missing"; a transcript difference may be the speech-to-text.
  • Items not checked by eye get a three-item checklist for the human, specific to that item ("zoom on the logo; count the lid loops; does the green match your Sage?").
  • Never call generated media "ready" on automatic reads alone — "ready for your look" / "ready for your watch-through".
  • Say plainly what only the human can judge (taste, motion, voice, pacing, music, overall feel).

4. Remakes

  • Only for a defect that is real (seen by eye, or confirmed by the human).
  • Only on a yes to the engine's quote for that remake, shown as given; never an unquoted paid edit, never your own price. A playbook may say its earlier yes already covers one retry at the quoted price; then that yes is enough for that one retry.
  • At most two tries per item; then drop it (or hand the choice to the human) and say why.
  • Changed words or claims in a remake are shown before it is made, even when an earlier yes covers the money.

5. Record

  • Feedback to the engine (where the tool takes it): only the human's own words, and reason codes only for engine faults the human names (garbled text, wrong product, distortion); your own verdicts go in your record, not the feedback; strategy choices go in the comment.
  • A durable lesson the human states becomes a brand rule only through the save-learning skill (../save-learning/SKILL.md).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.