What the launch did
Read how a campaign did per channel -- clicks, signups, replies -- from analytics and the Distribution table, and say which channel to repeat and which to drop, with the numbers.
In Lobstack: Skills › Library › Add
What your agent will do.
A day and a week after a launch or post went out, or when someone asks whether posting there is worth it.
- 01
Read the Distribution table for the campaign: every channel, link and publish time.
- 02
For each channel pull visits and signups by utm_source and campaign from analytics, over the same window for every channel. Add replies, reposts or opens where the service reports them.
- 03
Lay it out as a table: channel, published, visits, signups, rate. Mark any channel with too little traffic to judge.
- 04
Name the best and worst channel, with the numbers that say so, and one thing to try next time on each.
- 05
Say what you could not read and why — a missing tag, a channel with no stats.
Read-only. Never estimate a number the analytics did not return.
The whole SKILL.md: 29 lines of Markdown.
Add it in the app from Skills › Library, or copy it and paste it into Skills › Add a skill.
---name: engagement-reportdescription: "Read how a campaign did per channel -- clicks, signups, replies -- from analytics and the Distribution table, and say which channel to repeat and which to drop, with the numbers."metadata: title: "What the launch did" category: data tags: [analytics, distribution, reporting]--- ## When to use this A day and a week after a launch or post went out, or when someone askswhether posting there is worth it. ## How 1. Read the Distribution table for the campaign: every channel, link and publish time.2. For each channel pull visits and signups by utm_source and campaign from analytics, over the same window for every channel. Add replies, reposts or opens where the service reports them.3. Lay it out as a table: channel, published, visits, signups, rate. Mark any channel with too little traffic to judge.4. Name the best and worst channel, with the numbers that say so, and one thing to try next time on each.5. Say what you could not read and why -- a missing tag, a channel with no stats. Read-only. Never estimate a number the analytics did not return.
- Data
Answer a question from data
Answer a question from a database or table: read the schema, write a read-only query, sanity-check the result, and answer with the query shown.
SKILL.md · App - Data
Data report with spreadsheet
Turn a dataset or export into a report: the working spreadsheet with formulas, and a short document with charts that says what the numbers mean.
SKILL.md · App - Data
What changed in the numbers
Check a set of numbers for what changed: compare to the usual range, find the biggest moves, and say which ones are real.
SKILL.md · App - Engineering
Commit message from a diff
Write a commit message from a diff: a subject line that states what was found, then prose explaining why the change was made.
SKILL.md · App - Engineering
Triage a failing build
Triage a red CI run: find the first real failure, attribute it to a change, and say whether the code is wrong or the runner was.
SKILL.md · App - Engineering
Review what a linter cannot
Review a change for what a linter cannot see: whether it is correct, what it breaks elsewhere, and which parallel list it forgot to update.
SKILL.md · App