marketing-reporting-pack
Skill1 starsChanged 3 months agoMITView on GitHub
Generate weekly and monthly marketing reports that consolidate acquisition, activation, pipeline, channel performance, paid ads, SEO, social, outbound, website analytics, experiments, blockers, and next actions. Use when the user asks for a marketing weekly report, monthly review, growth summary, KPI recap, channel review, founder update, investor-style marketing snapshot, or data-backed team report. Outputs a compact report with headline bullets, metric tables, source-traceable numbers, experiment notes, risks, and next actions.
In this repository9 other files it gives its agents.
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
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
- Distinctive: line 10
Use this skill to create compact marketing reports with traceable metrics and clear next actions.
- Distinctive: line 24
Avoid mixing raw leads, qualified leads, opportunities, and revenue without labels.
- Distinctive: line 36
Do not start with a wall of numbers.
- Distinctive: line 47
Use WoW, MoM, or campaign baseline.
- Distinctive: line 79
Every number must trace back to a dashboard, export, or named source.
- Distinctive: line 82
Do not hide missing data. Label it and state the next step.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.
Files
Marketing Reporting Pack
Use this skill to create compact marketing reports with traceable metrics and clear next actions.
Inputs
- Reporting period
- Data exports or dashboard links
- Channel list
- Targets or prior-period benchmarks
- Known experiments and launches
Workflow
- Align metric definitions
- Confirm what each metric means.
- Avoid mixing raw leads, qualified leads, opportunities, and revenue without labels.
- Pull channel data
- Paid ads
- Organic search
- Social
- Outbound
- Website/product analytics
- CRM or pipeline data
- Write the headline
- Three plain bullets on what changed and why.
- Do not start with a wall of numbers.
- Break down by module
- Acquisition
- Activation
- Pipeline
- Channel notes
- Experiments
- Next actions
- Explain changes
- Use WoW, MoM, or campaign baseline.
- Mark unknown causes as unknown instead of guessing.
Report Template
# Marketing Report: {period}
## Headline
-
-
-
## Acquisition
| Channel | This period | Previous period | Change | Notes |
|---|---:|---:|---:|---|
## Activation
## Pipeline
## Channel Notes
## Experiments
## Risks / Blockers
## Next ActionsQuality Gates
- Every number must trace back to a dashboard, export, or named source.
- Weekly reports should fit on one page when possible.
- Monthly reports should be concise enough for leadership review.
- Do not hide missing data. Label it and state the next step.
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
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.

