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
Quiet since March.thin dataabout the whole repository
Most recently taken up by
- gooseworks-ai/goose-skillsword for word, first seen Nov 1, 2026
Who's talking about athina-ai/goose-skills
The biggest 1 of 1 mention linking to the repository that our crawl found. Each line is their own headline.
Other versions1 project uses a version of this.
Word for word · 1
- gooseworks-ai/goose-skills★ 1.3k100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository180 other files it gives its agents.
- goose-adsSkill
- goose-product-photosSkill
- goose-video-localSkill
- goose-videoSkill
- gooseworksSkill
- make-custom-videoSkill
- ad-policy-checkSkill
- analyze-performance-call-and-learnSkill
- analyze-performance-diagnoseSkill
- analyze-performance-intakeSkill
- analyze-performance-rank-and-readSkill
- analyze-performance-revenue-joinSkill
- analyze-performanceSkill
- claims-gateSkill
- email-lifecycle-broadcast-plannerSkill
- email-lifecycle-flow-writerSkill
- email-lifecycle-lifecycle-auditSkill
- email-lifecycle-offer-mathSkill
- email-lifecycle-send-checkSkill
- email-lifecycleSkill
- improve-search-visibility-citation-checkSkill
- improve-search-visibility-entity-footprintSkill
- improve-search-visibility-fix-writerSkill
- improve-search-visibility-page-and-foundation-checkSkill
- improve-search-visibility-question-setSkill
- improve-search-visibilitySkill
- improve-search-visibility-store-listing-auditSkill
- make-content-content-briefSkill
- make-contentSkill
- make-content-source-to-unitsSkill
- make-content-two-pass-editSkill
- make-static-ads-ad-copySkill
- make-static-ads-claims-extractSkill
- make-static-ads-composeSkill
- make-static-ads-concept-gridSkill
- make-static-ads-copy-variantsSkill
- make-static-ads-find-referencesSkill
- make-static-ads-fix-rejectedSkill
- make-static-ads-graphic-requestSkill
- make-static-ads-render-reviewSkill
- make-static-adsSkill
- marketing-data-accessSkill
- marketing-guideSkill
- outcomes-ledgerSkill
- plan-campaign-brief-and-assetsSkill
- plan-campaign-budget-and-testsSkill
- plan-campaign-channel-decisionSkill
- plan-campaign-goal-chainSkill
- plan-campaignSkill
- research-audience-account-sourcingSkill
- research-audience-fit-definitionSkill
- research-audience-people-and-contactsSkill
- research-audience-score-segment-qaSkill
- research-audience-segment-passSkill
- research-audience-signals-and-hooksSkill
- research-audienceSkill
- research-competitors-category-passSkill
- research-competitors-edge-casesSkill
- research-competitors-rival-passSkill
- research-competitorsSkill
- The first 60 shown.
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
- Distinctive: line 36
Never call generated media "ready" on automatic reads alone — "ready for your look" / "ready for your watch-through".
- Distinctive: line 41
Only for a defect that is real (seen by eye, or confirmed by the human).
≈ “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.
Files
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 can | How | Say |
| See images | The host shows them, or a shell host downloads the file and opens it | "checked by eye" |
| Read an automatic description | gooseworks: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 audio | Almost never — a transcript and sampled frames are not watching | never 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-learningskill (../save-learning/SKILL.md).
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
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.

