Analytics skills for your AI agent

Conversion fell.
Rollback is the wrong call.

Both channels improved. Mix did the damage. One skill, four rows, two minutes — before someone acts on the average.

No warehouse. No Engine. Copy the prompt; the CSV is already on GitHub.

Tomorrow’s standup. Four rows.

Conversion fell.
Both channels improved.

Before
8.8%
After
6.2%

Tempting call: roll back signup. The weights moved, not the rates.

/diagnose-change Should we roll back signup? Separate mix from within-channel change.

Install one skill and run it

Four-row CSV on GitHub · prompt hits the live file · not a model transcript

Install the skill. Paste the prompt.

diagnose-change is enough for this case. The rest of the set is one command.

npx skills add patrickjmorris/aftergrid --skill diagnose-change
01The traps

The average will
run the meeting.

These are the moments an agent without judgment ships the wrong story.

Then use the same skills on your CSV, notebook, or warehouse.

Choose a workflow
02The skills

Pick the skill
the stuck point needs.

14 portable skills, plus optional Engine setup. Unsure which? ask-aftergrid names one and stops.

15 skills

03In practice

See the miss,
then the catch.

A rollback on a mix-shift, growth that hid churn, a causal headline on self-selected retention, and a follow-up that has to re-test last week’s lesson.

Explore the examples
04Fieldnotes

The habits
behind the skills.

Ask first. Diagnose the move. Keep what you learned.

05From the maintainer

Built by an analyst.
Available for hire.

I’m Patrick Morris. I made these because the agent answers reaching product and growth decisions were fast, confident, and wrong in ways an analyst catches in a minute.

About the project

Next time a metric moves,
don’t let the average run the meeting.

Install one skill. Paste the four-row prompt. See whether the agent still recommends the rollback.

Try the conversion trap