agentleFS
athina-aiathina-ai/goose-skills/skills/marketing/analyze-performance-call-and-learn/SKILL.md

analyze-performance-call-and-learn

Skill1.3k starsChanged 22 days agoMITView on GitHub

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.

1 other project uses a version of this.

Trending

Quiet since March.thin dataabout the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 1 mentionApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the athina-ai/goose-skills repository that our weekly crawl found: only 1 in all, so this is a hint, not a trend. There is no adoption data for this file yet.

Most recently taken up by

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.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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:

    Call each ended test Win / Loss / Unclear against its written criteria with the brief's action.

    line 17
  2. Distinctive:

    Write this week's calls (kill / scale / hold, Google negatives) with object, why, how sure and "would change if".

    line 19
  3. Distinctive:

    Check fired replan triggers against the brief's thresholds.

    line 20

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Test calls, calls and learnings (atom)

Load: ../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:

  1. Call each ended test Win / Loss / Unclear against its written criteria with the brief's action; state how sure (confirmed / likely / first look).
  2. Score last week's recommendations through run-memory's outcome check (../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.
  3. Write this week's calls (kill / scale / hold, Google negatives) with object, why, how sure and "would change if"; first look → "watch".
  4. Check fired replan triggers against the brief's thresholds.
  5. Draft ≤ 3 learnings as one-line rules (template in the reference); only ended tests, 2+ week patterns that clear the test n floors on the referee-joined number, confirmed surprises or failures; each shows what it would retire.
  6. Readouts: each Win / Loss → kind 23 experiment_readout.<campaign-slug>-t<n> through save-learning's readout path, only with the marketer present; scheduled runs mark it readout to save.
  7. After the marketer's reply to the decisions block: write the kept learnings through the 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.

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.