Install Analyze Performance Diagnose
Pick your agent. Every command is ready to paste.
npx skills add gooseworks-ai/goose-skills --skill analyze-performance-diagnoseThe open skills CLI detects your agents (Claude Code, Cursor, Codex and 70+ more) and installs to the right folder. Add -g to install globally.
01
Install it
Run the command above, or upload the folder in Claude.
02
Ask naturally
Describe the task. Your agent loads analyze-performance-diagnose when the request matches its description.
03
Name it if needed
If it does not trigger, say “use the analyze-performance-diagnose skill”. In Codex, type $analyze-performance-diagnose.
Plumbing and the why (atom)
Load: ../analyze-performance/references/diagnosis.md.
Inputs: the clean dataset; the overclaim ratio and its trend; the change log (decisions.md); push failures/disapprovals reported by run-paid-campaigns or the marketer; the competitor watch digest; research-market's "What people are saying" section (newest research/market/<D>-read.md; check its window); the promo calendar and stock notes from the brief; destination URLs of top ads.
Do:
- Plumbing: test each break signature (ratio jump/collapse, zero-conversion days with spend, ROAS spike with flat orders, LPV/click drop, UTM traffic missing). For each break: symptom, likely location, what to check, the fix when identifiable, what it blocks. Mark affected numbers suspect.
- For each metric that moved materially at equal maturity: read the change log, check noise, mix shift, breakdown effect and denominator changes, then walk the cause checklist in order. One piece of evidence per named cause; confidence; ruled-out and unconfirmed causes listed.
- Page/message match for the top 2–3 winners and losers (open the page if the host can browse; else ask for a screenshot): product, promise, offer, price, stock.
Output: the report's Plumbing and Why-it-moved sections, and mismatches to note.
Tips for Analyze Performance Diagnose
- • Start a fresh session after installing so your agent picks up the new skill.
- • It is part of a pack with 29 skills. Install only the ones you need with --skill to keep triggers precise.
- • If two skills overlap, mention the one you want by name.
Questions about Analyze Performance Diagnose
What does the Analyze Performance Diagnose skill do?
Step of the analyze-performance playbook: flags tracking breaks with fixes and explains each big metric move with evidence, confidence and ruled-out causes. Run analyze-performance instead; not for direct use.
How do I install Analyze Performance Diagnose?
Run "npx skills add gooseworks-ai/goose-skills --skill analyze-performance-diagnose" in your project. The skills CLI installs it for Claude Code, Cursor, Codex and 70+ other agents. In Claude on the web, upload the skill folder as a ZIP under Customize > Skills.
Does Analyze Performance Diagnose work in Cursor and Codex?
Yes. Analyze Performance Diagnose uses the open SKILL.md format, so it works in Claude Code, Claude, Cursor, OpenAI Codex, Gemini CLI, GitHub Copilot and other agents that support agent skills.
Is Analyze Performance Diagnose free?
Analyze Performance Diagnose is open source on GitHub under the MIT license. It is free to install; check the license before commercial use.
Who made Analyze Performance Diagnose?
Analyze Performance Diagnose is published by gooseworks-ai in the gooseworks-ai/goose-skills repository, together with 28 other skills.

