agentleFS
athina-aiathina-ai/goose-skills/skills/marketing/analyze-performance-intake/SKILL.md

analyze-performance-intake

Skill1.3k starsChanged 22 days agoMITView on GitHub

Step of the analyze-performance playbook: gathers the week's numbers from tools, exports and pastes, cleans them, and writes the coverage line or switches to claims-only mode. 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

Files
SKILL.md

Intake, hygiene and coverage (atom)

Load: ../analyze-performance/references/measurement-contract.md.

Inputs: the measurement contract (company type, referee, channel roster); tool reads (meta_read performance, social_analytics_get, ads_creative_read, video_read, campaign_read); the marketer's connectors / exports / screenshots / pastes from the one input message.

Do:

  1. Start from the minimum useful read (contract §4) and tick the rest against the roster; big pasted exports are totalled in code when a code tool exists; with none, never totalled by eye — ask for the summary report and mark the referee not measured until it arrives (contract §4); never echoed. Then: what arrived, what didn't ("not checked this week" — no mid-run asks).
  2. Hygiene: strip test, wholesale, staff orders and subscription renewals from new revenue; net refunds; align timezone and currency; note discount depth.
  3. Maturity: compare this week as first reported with last week as first reported; show last week restated separately. Exports are the week's source; meta_read identifies Goose ads and cross-checks — de-duplicate by ad id. 3b. Save the input summary to reports/performance/inputs/<YYYY-MM-DD>.md for run-paid-campaigns to reuse.
  4. Coverage line: per channel — truth / claimed / not measured / not used; share of Meta spend seen in detail.
  5. The type's referee missing (or no total spend) → claims-only mode (labels, no MER, calls capped at first look, first-line notice).

Output: a clean dataset per channel with labels, the coverage line, and the list of asks for next week.

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.