Records a founder’s answers, what the site shows, and the agreed first move in a brand situation file. This helps later visits and related playbooks use the same context without asking the founder to repeat it.
Step of the where-to-start playbook: saves the founder's answers and the agreed first move with the brand, so later visits and other playbooks don't ask again. Run where-to-start instead; not for direct use.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
The founder's answers (their words), the brand (id, slug, coworker_agent_id) unless there is no real brand, what the short look at the site showed, the constraint you named, the recommendation and whether they agreed, and today's date.
No real brand (none, or an empty placeholder): save nothing, and say so plainly ("I can't save these yet — there's no brand set up"). If a brand is set up later in this same conversation, run this atom then, before anything else asks the founder again.
The situation file. gooseworks:file_read brand/situation.md (brand coworker scope; no coworker → default workspace under brands/<brand-slug>/, and say so once). Replace the "Latest" section; move the previous "Latest" under "History" (keep the last three). Format:
# Situation — <Brand>
Do this first, because: <the constraint in one clause> → <the agreed first move>.
## Latest — <YYYY-MM-DD>
Founder said [owner, <date>]: sells <…> to <…>; where it sells <…>; stage <…>; goal <…> by <date>; can put in <…>/month and <…> h/week; does the work: <…>; next big date <…>; tried <…>; has <list / audience / network…>.
Seen on the site [site, read <date>]: <offer, price, first reason to buy, list sign-up>.
Unknown: <what they didn't know>.
Agent's read [guess, <date>]: constraint <…>; first move <…> (<agreed | adjusted to … | not agreed>); not yet <…>; worked if <…>; come back when <…>.
## History
<earlier "Latest" sections, newest first, at most three>
Keep the founder's words, what the site showed and your read on separate lines. Never put a guess on the "Founder said" line. No plan names or credit sums.
Save it through the save-to-brain skill (../save-to-brain/SKILL.md): path brand/situation.md, artifact Situation, title Situation — <Brand> — <YYYY-MM-DD>, tags [where-to-start, situation], versioned: supersede.
Profile fields (only those the founder stated, only clear matches to the listed values): gooseworks:brand_update with brand_id, knowledge_intent: "user_correction", user_statement = the founder's words that gave them, and patch.onboarding: role; ad_spend only if they said what they spend on ads today (question 4 asks what they can put in, which is not the same); goals and platforms only where a listed value plainly matches.
Check the answers. If a write failed, say in one line that it wasn't saved, and carry on.
not agreed keeps their own answers and marks the read as not agreed.user_context for brand facts.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
The supplied material contains only placeholder text for the skill’s purpose, inputs, steps, and completion criteria. It does not provide enough information to describe a task or result reliably.
Research supported advertising angles using buyer context, current product facts, customer language, and observed ads. Turn the evidence into static ad, video, or copy ideas, matching video concepts to available recipes. Scores rank ideas for testing; they do not predict results.
Analyze campaign data from Google, Meta, and LinkedIn to find strong and wasteful spend. The skill checks funnel performance and test results, then recommends which campaigns to pause, scale, or test and how to shift budget across channels.
Compare ad spend and signups with downstream outcomes to calculate the cost of each qualified lead. The skill checks tracking coverage, accounts for how long leads need to mature, and groups creatives into actionable categories with confidence notes.
Prepare the intake for a Meta ad campaign by reviewing available brand information first, stating reasonable assumptions, and asking only questions whose answers could affect budget, claims, or legal exposure. It records stable brand facts, a campaign brief, and what was asked versus assumed.
Review ad copy, image text, visuals, and people against platform and brand category rules. It suggests honest fixes and needed disclosures, then flags issues requiring human or legal review, with a separate result for each ad and platform.