analytics
Skill1 starsChanged 17 days agoMITView on GitHub
Full data and analytics department: measurement tracking, dashboards, marketing attribution, performance reporting, conversion-rate optimization, server-side event ingestion, and multi-touch Shapley attribution graphs — routed through eight modes. Use when asked to set up analytics or event tracking, build a KPI dashboard, work out which channel drives conversions, calculate game theory Shapley attribution, report on marketing performance, run a CRO audit, or ingest server-side events. Not for ad platform management (paidads) or content performance alone (smm analytics).
We split this skill into the rules it gives an agent
4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 57 edited versions we read keep these.
4
Distinctive
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 38
Every invocation resolves to exactly one mode.
- Distinctive: line 51
Only the resolved mode's reference is loaded — the rest stay on disk, saving tokens on every run.
- Distinctive: line 88
Every metric maps to a named decision or owner.
- Distinctive: line 118
No data-quality check — bot traffic and internal traffic pollute results.
“Common” is measured: kept by at least 6 in 10 of the 57 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
📊 analytics — Data & Analytics Department
One head skill for measurement. Decide the question before the tool. Every metric must map to a decision someone will actually make — untracked data is guesswork and vanity dashboards are noise. Clean tracking, then honest attribution, then experiments that raise conversion.
Modes
Every invocation resolves to exactly one mode. Match the request, then load only the matched reference:
| Mode | Trigger phrases | Behavior | Reference |
| tracking | "set up tracking", "GA4 events", "GTM", "event tracking", "tag setup", "dream funnel", "developer funnel", "telemetry", "utm tags" | Event/tag plan, DREAM developer adoption telemetry, UTM parameter sanitizer, and live verification | references/tracking.md |
| dashboards | "build a dashboard", "looker studio", "kpi dashboard", "reporting view", "ndr", "net developer retention", "developer metrics" | KPI and Net Developer Retention (NDR) dashboards built for a decision-making audience | references/dashboards.md |
| attribution | "attribution", "which channel converts", "marketing mix", "hero channel" | Multi-touch attribution and channel contribution analysis | references/attribution.md |
| reporting | "marketing report", "monthly report", "performance report", "client report" | Recurring performance reports that end in decisions | references/reporting.md |
| cro | "increase conversions", "cro", "a/b test", "funnel audit", "conversion audit" | Funnel audit and conversion experiments | references/cro.md |
| events | "event ingestion", "server-side events", "event tracking", "pii scrub", "schema validation", "event payload", "idempotency" | Server-side event ingestion, privacy PII scrubbing, JSON schema validation, and deterministic multi-touch attribution | references/events.md |
| attribution-graph | "attribution graph", "shapley value", "multi-touch attribution", "identity stitching", "haircut deduplication", "budget advisor" | Multi-touch Shapley value attribution, cross-device identity stitching, channel haircut deduplication, and automated budget reallocation | references/attribution-graph.md |
| audit | "audit analytics", "data audit", "event audit", "definition drift" | Data audit (events firing, definitions match implementation) + reporting audit (dashboards accurate) | references/audit.md |
Only the resolved mode's reference is loaded — the rest stay on disk, saving tokens on every run.
When to Use
- Designing or auditing event/tag tracking (GA4, GTM, product events).
- Building KPI dashboards for a client or marketing team.
- Understanding which channels and touchpoints drive conversions.
- Producing recurring performance reports.
- Auditing pages/funnels and running conversion experiments.
Anti-Triggers
- Managing paid campaigns and budgets →
paidads. - Keyword and indexation work →
seo. - Building the pages/funnels themselves →
webdevordesign. - Social-only performance →
smm(analytics mode).
Quick Reference
Measurement ladder (decide before any mode)
| Question | Mode |
| 'Is the data even collected correctly?' | tracking |
| 'Can the team see performance at a glance?' | dashboards |
| 'Which channel actually earned this sale?' | attribution |
| 'What happened this month and what do we do?' | reporting |
| 'Why is this page not converting, and can we fix it?' | cro |
Order: tracking → attribution → reporting → dashboards → cro. Instrument before you interpret.
Verification gate (every mode)
- Every metric maps to a named decision or owner.
- Tracking verified against the live site/app (not just configured).
- Attribution limits stated honestly (no false certainty).
- Reports end in decisions, not just numbers.
Suite contracts
- Tag implementation in page code →
webdev(frontend mode). - Channel definitions and spend →
paidads. - Experiment page variants →
design/webdev.
Procedure
- Intake. name the decision the data must inform and the metric that drives it — before installing a tag or building a chart; measurement without a question becomes junk data.
- Resolve the mode. Match the request against the mode table; exactly one mode. Ambiguous → ask one question, then proceed.
- Execute the mode playbook. Load
references/<mode>.mdand follow its Intake → Deliverable → Procedure → Quality gate in order. - Gate and deliver. Pass this file's Verification checklist plus the mode's quality gate, then deliver the artifact where the client expects it.
Pitfalls
- Installing tags before defining the question — unfocused data.
- Vanity dashboards nobody opens or acts on.
- Trusting last-click attribution as the whole truth.
- Duplicate or double-firing events (inflated conversion counts).
- Reports that describe numbers without recommending action.
- Running CRO experiments without enough sample or a single variable.
- No data-quality check — bot traffic and internal traffic pollute results.
Verification
- Every metric maps to a decision or an owner.
- Tracking verified on the live site/app via debug/preview.
- Attribution model and its limits stated explicitly.
- Internal/bot traffic filtered.
- Reports conclude with prioritized actions.
- Experiments change one variable with a defined sample and success metric.
Other versions68 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 68
- coreyhaines31/marketingskills★ 58ksame name
- getsentry/sentry★ 46ksame name
- thewh1teagle/vibe★ 8ksame name
- microsoft/power-platform-skills★ 1.1ksame name
- Nexus-JPF/note-companion★ 874same name
- microsoft/rayfin★ 646same name
- LedgerHQ/ledger-live★ 624same name
- Cesarjoquin/Marketing-Skills★ 190same name
- microsoft/awesome-rayfin★ 108same name
- TheAceTeam/CC-Flight★ 93same name
58 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Used alongsideProjects with it also use popups, free-tools and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
CesarjoquinSkillpopups
When the user wants to create or optimize popups, modals, overlays, slide-ins, or banners for conversion purposes. Also use when the user mentions "exit intent," "popup conversions," "modal optimization," "lead capture popup," "email popup," "announcement banner," "overlay," "collect emails with a popup," "exit popup," "scroll trigger," "sticky bar," or "notification bar." Use this for any overlay or interrupt-style conversion element. For forms outside of popups, see cro. For general page conversion optimization, see cro.
Also in 22 projects that use this
- CesarjoquinSkill
free-tools
When the user wants to plan, evaluate, or build a free tool for marketing purposes — lead generation, SEO value, or brand awareness. Also use when the user mentions "engineering as marketing," "free tool," "marketing tool," "calculator," "generator," "interactive tool," "lead gen tool," "build a tool for leads," "free resource," "ROI calculator," "grader tool," "audit tool," "should I build a free tool," or "tools for lead gen." Use this whenever someone wants to build something useful and give it away to attract leads or earn links. For downloadable content lead magnets (ebooks, checklists, templates), see lead-magnets.
Also in 23 projects that use this
coreyhaines31Skillmarketing-council
When the user wants multiple expert perspectives on a marketing question — a simulated board of advisors staffed by legendary marketers (Seth Godin, David Ogilvy, Eugene Schwartz, April Dunford, Rory Sutherland, Alex Hormozi, Byron Sharp, and more). Also use when the user mentions 'marketing council,' 'board of advisors,' 'advisory board,' 'what would Seth Godin say,' 'what would Ogilvy think,' 'channel Hormozi,' 'get multiple perspectives,' 'debate this,' 'have the council review,' 'marketing mentors,' or asks how a famous marketer would approach their problem. The council gives each advisor's take through their documented frameworks, surfaces where they disagree, and synthesizes a recommendation. For executing the winning direction, hand off to positioning, offers, copywriting, ads, or the relevant skill.
Also in 18 projects that use this
pixelswithblissSkillco-marketing
When the user wants to find co-marketing partners, plan joint campaigns, or brainstorm partnership opportunities. Use when the user says 'co-marketing,' 'partner marketing,' 'joint campaign,' 'who should we partner with,' 'integration marketing,' 'cross-promotion,' 'collaborate with another company,' 'partnership ideas,' or 'co-brand.' For customer referral programs, see referrals. For launch-specific partnerships, see launch.
Also in 22 projects that use this
ukunal91appSkillcommunity-marketing
Build and leverage online communities to drive product growth and brand loyalty. Use when the user wants to create a community strategy, grow a Discord or Slack community, manage a forum or subreddit, build brand advocates, increase word-of-mouth, drive community-led growth, engage users post-signup, or turn customers into evangelists. Trigger phrases: "build a community," "community strategy," "Discord community," "Slack community," "community-led growth," "brand advocates," "user community," "forum strategy," "community engagement," "grow our community," "ambassador program," "community flywheel.
Also in 25 projects that use this
roerohanSkillemails
When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding.
Also in 18 projects that use this
- +6 more from Cesarjoquin
In this repository49 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- llms.txtllms.txt
- accountsSkill
- automationSkill
- brandSkill
- client-commsSkill
- contentSkill
- crmSkill
- databaseSkill
- designSkill
- devopsSkill
- growthSkill
- gtmSkill
- incident-responseSkill
- mobileSkill
- opsSkill
- paidadsSkill
- qa-launchSkill
- researchSkill
- retainSkill
- sales-enablementSkill
- seoSkill
- smmSkill
- telegramSkill
- webdevSkill
- context-anchorSkill
- coupling-routerSkill
- evidence-ledgerSkill
- relaySkill
- secretarySkill
- gitSkill
- new-projectSkill
- updateagentsSkill
- updatedocsSkill
- animateSkill
- designscopeSkill
- refactorSkill
- auditSkill
- code-reviewSkill
- dead-letterSkill
- gauntlet-loopSkill
- humanizeSkill
- muse-securitySkill
- puaSkill
- clean-system-cacheSkill
- coachSkill
- periodic-retreatSkill
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.