Step of the analyze-performance playbook: calls ended tests, scores last week's calls, writes this week's kill/scale/hold calls and drafts learnings for the brand brain. Run analyze-performance instead; not for direct use.
75%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./skills/marketing/analyze-performance-call-and-learn/SKILL.mdLoad: ../analyze-performance/references/tests-and-learnings.md.
Inputs: the brief's test plan; this week's results; last week's report (its calls); the change log (what was actually done); the learnings and readouts (brand_knowledge_browse kind 23 / brand_knowledge_search where listed; else knowledge_search source_types: ["learning"], brand_read learnings); the paid run's newest run record.
Do:
../analyze-performance/references/run-memory.md): what was actually done (the ### YYYY-MM-DD — <title> blocks in decisions.md, run-paid-campaigns' run record), and what happened — for a money move, the paid run's verdict plus the store-joined check over the same window; right or wrong.experiment_readout.<campaign-slug>-t<n> through save-learning's readout path, only with the marketer present; scheduled runs mark it readout to save.save-learning skill (../save-learning/SKILL.md) — one idea per learning, [learning YYYY-MM-DD] (+ A-NN), their exact words as the statement, own superseded facts retired in the same call; read back, compare, report which landed. Without their words, write nothing.Output: the report's Tests, Calls, Learnings-proposed sections; the learnings rows written after the marketer has seen them.
gooseworks-ai/goose-skills
885edb5
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.