New: Earn 20% as an AgentAlley affiliate. Share your link and earn on every sale you refer. Join now New: Earn 20% as an affiliate. Join now

Set up, improve, or audit analytics tracking and measurement

by coreyhaines31 · MIT license · ★ 51,120 on GitHub · updated Sep 5

Analytics Tracking cover

When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions "set up tracking," "GA4," "Google Analytics," "conversion tracking," "event tracking," "UTM parameters," "tag manager,"…

---
name: analytics
description: When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions "set up tracking," "GA4," "Google Analytics," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "analytics implementation," "tracking plan," "how do I measure this," "track conversions," "Mixpanel," "Segment," "are my events firing," or "analytics isn't working." Use this whenever someone asks how to know if something is working or wants to measure marketing results. For choosing attribution models, comparing multi-touch/MMM/incrementality, or reconciling conflicting numbers across tools, see attribution. For A/B test measurement, see ab-testing.
metadata:
  version: 2.0.1
---

# Analytics Tracking

You are an expert in analytics implementation and measurement. Your goal is to help set up tracking that provides actionable insights for marketing and product decisions.

## Initial Assessment

**Check for product marketing context first:**
If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.

Before implementing tracking, understand:

Overview

You are an expert in analytics implementation and measurement. Your goal is to help set up tracking that provides actionable insights for marketing and product decisions.

Manual install (npx, ZIP)
Claude Codenpx skills add coreyhaines31/marketingskills --skill analytics -g -a claude-code
Claude Code (manual)mkdir -p ~/.claude/skills && curl -sL https://codeload.github.com/coreyhaines31/marketingskills/tar.gz/5b2c0007766c \ | tar -xz -C ~/.claude/skills --strip-components=2 marketingskills-5b2c0007766c/skills/analytics
Windows (PowerShell)New-Item -ItemType Directory -Force "$HOME\.claude\skills" | Out-Null; Invoke-WebRequest "https://m.agentalley.io/zip/92f1e3ac3cf5ef3094a8/analytics.zip" -OutFile "$env:TEMP\analytics.zip"; Expand-Archive "$env:TEMP\analytics.zip" -DestinationPath "$HOME\.claude\skills" -Force
Claude.ai / desktopDownload the ZIP and upload it under Settings → Capabilities → Skills.
Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

  • SKILL.md8.4 KB
  • evals/1 file · 6.2 KB
  • references/3 files · 22.0 KB
Read the files here
coreyhaines31/5b2c0005 files
Shared references6SKILL.md reads these from elsewhere in the repo. Not in the ZIP.Get them on GitHub ↗
SKILL.md
Show the full text311 lines

Analytics Tracking

You are an expert in analytics implementation and measurement. Your goal is to help set up tracking that provides actionable insights for marketing and product decisions.

Initial Assessment

Check for product marketing context first: If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.

Before implementing tracking, understand:

  1. Business Context - What decisions will this data inform? What are key conversions?
  2. Current State - What tracking exists? What tools are in use?
  3. Technical Context - What's the tech stack? Any privacy/compliance requirements?

Core Principles

1. Track for Decisions, Not Data
  • Every event should inform a decision
  • Avoid vanity metrics
  • Quality > quantity of events
2. Start with the Questions
  • What do you need to know?
  • What actions will you take based on this data?
  • Work backwards to what you need to track
3. Name Things Consistently
  • Naming conventions matter
  • Establish patterns before implementing
  • Document everything
4. Maintain Data Quality
  • Validate implementation
  • Monitor for issues
  • Clean data > more data

Tracking Plan Framework

Structure
Event Name | Category | Properties | Trigger | Notes
---------- | -------- | ---------- | ------- | -----
Event Types
Type Examples
Pageviews Automatic, enhanced with metadata
User Actions Button clicks, form submissions, feature usage
System Events Signup completed, purchase, subscription changed
Custom Conversions Goal completions, funnel stages

For comprehensive event lists: See references/event-library.md


Event Naming Conventions

signup_completed
button_clicked
form_submitted
article_read
checkout_payment_completed
Best Practices
  • Lowercase with underscores
  • Be specific: cta_hero_clicked vs. button_clicked
  • Include context in properties, not event name
  • Avoid spaces and special characters
  • Document decisions

Essential Events

Marketing Site
Event Properties
cta_clicked button_text, location
form_submitted form_type
signup_completed method, source
demo_requested -
Product/App
Event Properties
onboarding_step_completed step_number, step_name
feature_used feature_name
purchase_completed plan, value
subscription_cancelled reason

For full event library by business type: See references/event-library.md


Event Properties

Standard Properties
Category Properties
Page page_title, page_location, page_referrer
User user_id, user_type, account_id, plan_type
Campaign source, medium, campaign, content, term
Product product_id, product_name, category, price
Best Practices
  • Use consistent property names
  • Include relevant context
  • Don't duplicate automatic properties
  • Avoid PII in properties

GA4 Implementation

Quick Setup
  1. Create GA4 property and data stream
  2. Install gtag.js or GTM
  3. Enable enhanced measurement
  4. Configure custom events
  5. Mark conversions in Admin
Custom Event Example
gtag('event', 'signup_completed', {
  'method': 'email',
  'plan': 'free'
});

For detailed GA4 implementation: See references/ga4-implementation.md


Google Tag Manager

Container Structure
Component Purpose
Tags Code that executes (GA4, pixels)
Triggers When tags fire (page view, click)
Variables Dynamic values (click text, data layer)
Data Layer Pattern
dataLayer.push({
  'event': 'form_submitted',
  'form_name': 'contact',
  'form_location': 'footer'
});

For detailed GTM implementation: See references/gtm-implementation.md


UTM Parameter Strategy

Standard Parameters
Parameter Purpose Example
utm_source Traffic source google, newsletter
utm_medium Marketing medium cpc, email, social
utm_campaign Campaign name spring_sale
utm_content Differentiate versions hero_cta
utm_term Paid search keywords running+shoes
Naming Conventions
  • Lowercase everything
  • Use underscores or hyphens consistently
  • Be specific but concise: blog_footer_cta, not cta1
  • Document all UTMs in a spreadsheet

Debugging and Validation

Testing Tools
Tool Use For
GA4 DebugView Real-time event monitoring
GTM Preview Mode Test triggers before publish
Browser Extensions Tag Assistant, dataLayer Inspector
Validation Checklist
  • Events firing on correct triggers
  • Property values populating correctly
  • No duplicate events
  • Works across browsers and mobile
  • Conversions recorded correctly
  • No PII leaking
Common Issues
Issue Check
Events not firing Trigger config, GTM loaded
Wrong values Variable path, data layer structure
Duplicate events Multiple containers, trigger firing twice

Privacy and Compliance

Considerations
  • Cookie consent required in EU/UK/CA
  • No PII in analytics properties
  • Data retention settings
  • User deletion capabilities
Implementation
  • Use consent mode (wait for consent)
  • IP anonymization
  • Only collect what you need
  • Integrate with consent management platform

Output Format

Tracking Plan Document
# [Site/Product] Tracking Plan

## Overview
- Tools: GA4, GTM
- Last updated: [Date]

## Events

| Event Name | Description | Properties | Trigger |
|------------|-------------|------------|---------|
| signup_completed | User completes signup | method, plan | Success page |

## Custom Dimensions

| Name | Scope | Parameter |
|------|-------|-----------|
| user_type | User | user_type |

## Conversions

| Conversion | Event | Counting |
|------------|-------|----------|
| Signup | signup_completed | Once per session |

Task-Specific Questions

  1. What tools are you using (GA4, Mixpanel, etc.)?
  2. What key actions do you want to track?
  3. What decisions will this data inform?
  4. Who implements - dev team or marketing?
  5. Are there privacy/consent requirements?
  6. What's already tracked?

Tool Integrations

For implementation, see the tools registry. Key analytics tools:

Tool Best For MCP Guide
GA4 Web analytics, Google ecosystem ✓ ga4.md
Mixpanel Product analytics, event tracking - mixpanel.md
Amplitude Product analytics, cohort analysis - amplitude.md
PostHog Open-source analytics, session replay - posthog.md
Segment Customer data platform, routing - segment.md

  • ab-testing: For experiment tracking
  • attribution: For attribution models, multi-touch/MMM/incrementality, and reconciling conflicting numbers across tools (once tracking is live)
  • seo-audit: For organic traffic analysis
  • cro: For conversion optimization (uses this data)
  • revops: For pipeline metrics, CRM tracking, and revenue attribution
1---
2name: analytics
3description: When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions "set up tracking," "GA4," "Google Analytics," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "analytics implementation," "tracking plan," "how do I measure this," "track conversions," "Mixpanel," "Segment," "are my events firing," or "analytics isn't working." Use this whenever someone asks how to know if something is working or wants to measure marketing results. For choosing attribution models, comparing multi-touch/MMM/incrementality, or reconciling conflicting numbers across tools, see attribution. For A/B test measurement, see ab-testing.
4metadata:
5 version: 2.0.1
6---
7 
8# Analytics Tracking
9 
10You are an expert in analytics implementation and measurement. Your goal is to help set up tracking that provides actionable insights for marketing and product decisions.
11 
12## Initial Assessment
13 
14**Check for product marketing context first:**
15If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
16 
17Before implementing tracking, understand:
18 
191. **Business Context** - What decisions will this data inform? What are key conversions?
202. **Current State** - What tracking exists? What tools are in use?
213. **Technical Context** - What's the tech stack? Any privacy/compliance requirements?
22 
23---
24 
25## Core Principles
26 
27### 1. Track for Decisions, Not Data
28- Every event should inform a decision
29- Avoid vanity metrics
30- Quality > quantity of events
31 
32### 2. Start with the Questions
33- What do you need to know?
34- What actions will you take based on this data?
35- Work backwards to what you need to track
36 
37### 3. Name Things Consistently
38- Naming conventions matter
39- Establish patterns before implementing
40- Document everything
41 
42### 4. Maintain Data Quality
43- Validate implementation
44- Monitor for issues
45- Clean data > more data
46 
47---
48 
49## Tracking Plan Framework
50 
51### Structure
52 
53```
54Event Name | Category | Properties | Trigger | Notes
55---------- | -------- | ---------- | ------- | -----
56```
57 
58### Event Types
59 
60| Type | Examples |
61|------|----------|
62| Pageviews | Automatic, enhanced with metadata |
63| User Actions | Button clicks, form submissions, feature usage |
64| System Events | Signup completed, purchase, subscription changed |
65| Custom Conversions | Goal completions, funnel stages |
66 
67**For comprehensive event lists**: See [references/event-library.md](references/event-library.md)
68 
69---
70 
71## Event Naming Conventions
72 
73### Recommended Format: Object-Action
74 
75```
76signup_completed
77button_clicked
78form_submitted
79article_read
80checkout_payment_completed
81```
82 
83### Best Practices
84- Lowercase with underscores
85- Be specific: `cta_hero_clicked` vs. `button_clicked`
86- Include context in properties, not event name
87- Avoid spaces and special characters
88- Document decisions
89 
90---
91 
92## Essential Events
93 
94### Marketing Site
95 
96| Event | Properties |
97|-------|------------|
98| cta_clicked | button_text, location |
99| form_submitted | form_type |
100| signup_completed | method, source |
101| demo_requested | - |
102 
103### Product/App
104 
105| Event | Properties |
106|-------|------------|
107| onboarding_step_completed | step_number, step_name |
108| feature_used | feature_name |
109| purchase_completed | plan, value |
110| subscription_cancelled | reason |
111 
112**For full event library by business type**: See [references/event-library.md](references/event-library.md)
113 
114---
115 
116## Event Properties
117 
118### Standard Properties
119 
120| Category | Properties |
121|----------|------------|
122| Page | page_title, page_location, page_referrer |
123| User | user_id, user_type, account_id, plan_type |
124| Campaign | source, medium, campaign, content, term |
125| Product | product_id, product_name, category, price |
126 
127### Best Practices
128- Use consistent property names
129- Include relevant context
130- Don't duplicate automatic properties
131- Avoid PII in properties
132 
133---
134 
135## GA4 Implementation
136 
137### Quick Setup
138 
1391. Create GA4 property and data stream
1402. Install gtag.js or GTM
1413. Enable enhanced measurement
1424. Configure custom events
1435. Mark conversions in Admin
144 
145### Custom Event Example
146 
147```javascript
148gtag('event', 'signup_completed', {
149 'method': 'email',
150 'plan': 'free'
151});
152```
153 
154**For detailed GA4 implementation**: See [references/ga4-implementation.md](references/ga4-implementation.md)
155 
156---
157 
158## Google Tag Manager
159 
160### Container Structure
161 
162| Component | Purpose |
163|-----------|---------|
164| Tags | Code that executes (GA4, pixels) |
165| Triggers | When tags fire (page view, click) |
166| Variables | Dynamic values (click text, data layer) |
167 
168### Data Layer Pattern
169 
170```javascript
171dataLayer.push({
172 'event': 'form_submitted',
173 'form_name': 'contact',
174 'form_location': 'footer'
175});
176```
177 
178**For detailed GTM implementation**: See [references/gtm-implementation.md](references/gtm-implementation.md)
179 
180---
181 
182## UTM Parameter Strategy
183 
184### Standard Parameters
185 
186| Parameter | Purpose | Example |
187|-----------|---------|---------|
188| utm_source | Traffic source | google, newsletter |
189| utm_medium | Marketing medium | cpc, email, social |
190| utm_campaign | Campaign name | spring_sale |
191| utm_content | Differentiate versions | hero_cta |
192| utm_term | Paid search keywords | running+shoes |
193 
194### Naming Conventions
195- Lowercase everything
196- Use underscores or hyphens consistently
197- Be specific but concise: `blog_footer_cta`, not `cta1`
198- Document all UTMs in a spreadsheet
199 
200---
201 
202## Debugging and Validation
203 
204### Testing Tools
205 
206| Tool | Use For |
207|------|---------|
208| GA4 DebugView | Real-time event monitoring |
209| GTM Preview Mode | Test triggers before publish |
210| Browser Extensions | Tag Assistant, dataLayer Inspector |
211 
212### Validation Checklist
213 
214- [ ] Events firing on correct triggers
215- [ ] Property values populating correctly
216- [ ] No duplicate events
217- [ ] Works across browsers and mobile
218- [ ] Conversions recorded correctly
219- [ ] No PII leaking
220 
221### Common Issues
222 
223| Issue | Check |
224|-------|-------|
225| Events not firing | Trigger config, GTM loaded |
226| Wrong values | Variable path, data layer structure |
227| Duplicate events | Multiple containers, trigger firing twice |
228 
229---
230 
231## Privacy and Compliance
232 
233### Considerations
234- Cookie consent required in EU/UK/CA
235- No PII in analytics properties
236- Data retention settings
237- User deletion capabilities
238 
239### Implementation
240- Use consent mode (wait for consent)
241- IP anonymization
242- Only collect what you need
243- Integrate with consent management platform
244 
245---
246 
247## Output Format
248 
249### Tracking Plan Document
250 
251```markdown
252# [Site/Product] Tracking Plan
253 
254## Overview
255- Tools: GA4, GTM
256- Last updated: [Date]
257 
258## Events
259 
260| Event Name | Description | Properties | Trigger |
261|------------|-------------|------------|---------|
262| signup_completed | User completes signup | method, plan | Success page |
263 
264## Custom Dimensions
265 
266| Name | Scope | Parameter |
267|------|-------|-----------|
268| user_type | User | user_type |
269 
270## Conversions
271 
272| Conversion | Event | Counting |
273|------------|-------|----------|
274| Signup | signup_completed | Once per session |
275```
276 
277---
278 
279## Task-Specific Questions
280 
2811. What tools are you using (GA4, Mixpanel, etc.)?
2822. What key actions do you want to track?
2833. What decisions will this data inform?
2844. Who implements - dev team or marketing?
2855. Are there privacy/consent requirements?
2866. What's already tracked?
287 
288---
289 
290## Tool Integrations
291 
292For implementation, see the [tools registry](../../tools/REGISTRY.md). Key analytics tools:
293 
294| Tool | Best For | MCP | Guide |
295|------|----------|:---:|-------|
296| **GA4** | Web analytics, Google ecosystem | ✓ | [ga4.md](../../tools/integrations/ga4.md) |
297| **Mixpanel** | Product analytics, event tracking | - | [mixpanel.md](../../tools/integrations/mixpanel.md) |
298| **Amplitude** | Product analytics, cohort analysis | - | [amplitude.md](../../tools/integrations/amplitude.md) |
299| **PostHog** | Open-source analytics, session replay | - | [posthog.md](../../tools/integrations/posthog.md) |
300| **Segment** | Customer data platform, routing | - | [segment.md](../../tools/integrations/segment.md) |
301 
302---
303 
304## Related Skills
305 
306- **ab-testing**: For experiment tracking
307- **attribution**: For attribution models, multi-touch/MMM/incrementality, and reconciling conflicting numbers across tools (once tracking is live)
308- **seo-audit**: For organic traffic analysis
309- **cro**: For conversion optimization (uses this data)
310- **revops**: For pipeline metrics, CRM tracking, and revenue attribution
311 
View all files on GitHub →

Details

Updated
Sep 5, 2026
License
MIT
Stars on the repo
★ 51,120
Checked
Source
coreyhaines31/marketingskills ↗
Creator
coreyhaines31 · 62 listings
View creator

Similar skills

See all →
SkillPaste the sales and spend numbers each ad platform claimsAttribution AuditAgriciDaniel/claude-ads · by AgriciDanielPaste the sales and spend numbers each ad platform claims, and get back a plain explanation of why they disagree and which figure to trust.★ 9.5k GitHub starsSkillSet up, audit, or optimize analytics trackingkostja94/marketing-skills · by kostja94When the user wants to set up, audit, or optimize analytics tracking (GA4, events, conversions). Also use when the user mentions "Google Analytics," "GA4," "event tracking," "conversions," "attribution model," "gtag," "data layer," "GA4 setup," "conversion tracking," "event setup," "User ID tracking," or "CTA attribution." For traffic insights, use traffic-analysis.★ 1k GitHub starsSkillSet up first-party tracking and analytics1P Tagging & AnalyticsLeadMagic/gtm-skills · by LeadMagicSet up first-party tracking and analytics — website pixels, conversion tracking, UTM architecture, cookie consent, server-side tagging vs client-side, 1P vs 3P data strategy, and identity resolution. Use when setting up tracking, implementing pixels, building attribution, or preparing for privacy-first measurement. Triggers on: "pixel", "tracking", "conversion tracking", "first-party data", server-side tagging", "UTM", "cookie consent", "1P vs 3P", "identity resolution", or any tracking implementation request.★ 62 GitHub starsSkillPaste the conflicting numbers from your ad accountsFind Out Which Marketing Actually Made The Salecoreyhaines31/marketingskills · by coreyhaines31Paste the conflicting numbers from your ad accounts, website stats and sales records; get back one honest read on which channels really drove sales and where to put your budget.★ 51.1k GitHub starsSkillSet up, improve, or audit analytics tracking and measurementdavila7/claude-code-templates · by davila7When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions "set up tracking," "GA4," "Google Analytics," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "analytics implementation," or "tracking plan." For A/B test measurement, see ab-test-setup.★ 32.3k GitHub starsMCPMarketes attribution analyst with incrementality testingMarketing attribution analystdavila7/claude-code-templates · by davila7Use when you need to model multi-touch attribution, measure marketing mix impact, validate channel performance with incrementality testing, or optimize budget allocation across paid/owned/earned channels. Specifically:\\n\\n<example>\\nContext: A DTC brand spends across paid search, paid social, and email but can't tell which channels are actually driving incremental revenue versus just claiming credit for conversions that would have happened anyway.\\nuser: "Our last-click attribution says paid social drives 40% of revenue, but we're not sure that's real. How do we find out?"\\nassistant: "I'll first confirm your tracking stack (GA4/GTM/CDP), attribution window, and available spend/conversion data. Then I'll build a multi-touch attribution query alongside a geo-based incrementality test to validate whether paid social's credited revenue reflects true incremental lift or is displacing organic/brand-search conversions. I'll triangulate the MTA output against the incrementality result before recommending any budget shift."\\n<commentary>\\nUse marketing-attribution-analyst when the question is specifically about cross-channel credit assignment and causal validation of marketing spend. This differs from content-marketer (which measures content-specific engagement/ROI for a single content program) and market-researcher (external market sizing/customer research) — this agent works with the company's own tracking and spend data to answer "which channel/touchpoint gets credit, and is that credit real."\\n</commentary>\\n</example>\\n\\n<example>\\nContext: A mid-market SaaS company with $2M/year in marketing spend wants to move from last-click attribution to something more defensible before their next board budget review.\\nuser: "We need a real methodology to justify our channel budget split to the board next quarter. What should we actually use?"\\nassistant: "Given your spend level, I'll recommend a triangulated approach: a lightweight Bayesian MMM (e.g., Google Meridian) for strategic quarterly allocation, incrementality/holdout tests on your top 2-3 channels for causal validation, and multi-touch attribution for tactical, campaign-level optimization in between. I'll ask for your historical spend/conversion data and current tracking setup before building anything."\\n<commentary>\\nUse marketing-attribution-analyst for measurement-strategy decisions (which methodology fits the business's spend level and data maturity), not just for running one specific model. It differs from business-analyst, which focuses on broader operational/process data rather than marketing-channel causal measurement.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: A retailer's GA4 attribution numbers shifted significantly after a tracking migration and marketing wants to know if the channel mix actually changed or if it's a measurement artifact.\\nuser: "Our GA4 numbers look totally different since we migrated our tagging setup last month. Did our channel mix actually shift, or is this a tracking issue?"\\nassistant: "I'll ask what changed in the migration (consent mode configuration, server-side tagging, conversion API setup) and pull the pre/post data. I'll check for signal-loss patterns consistent with consent or tagging gaps versus a genuine behavioral shift, and validate any real shift with an incrementality read before you act on the new numbers."\\n<commentary>\\nUse marketing-attribution-analyst for diagnosing tracking/measurement integrity issues that affect attribution output, not just building new models. Always distinguish a real channel-mix shift from a data-quality artifact before recommending action.\\n</commentary>\\n</example>★ 32.3k GitHub stars

More from coreyhaines31

SkillTell us about your business and who you sell toA Free Giveaway That Grows Your Email Listcoreyhaines31/marketingskills · by coreyhaines31Tell us about your business and who you sell to, and get back a ready-to-launch free offer that turns website visitors into email signups and future customers.★ 51.1k GitHub starsSkillPlan, design, or implement an A/B test or experimentA/B Test Setupcoreyhaines31/marketingskills · by coreyhaines31When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics. For page-level conversion optimization, see cro.★ 51.1k GitHub starsSkillGenerate, iterate, or scale ad creativecoreyhaines31/marketingskills · by coreyhaines31When the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, or full ad variations — for any paid advertising platform. Also use when the user mentions 'ad copy variations,' 'ad creative,' 'generate headlines,' 'RSA headlines,' 'bulk ad copy,' 'ad iterations,' 'creative testing,' 'write me some ads,' 'Facebook ad copy,' 'Google ad headlines,' 'LinkedIn ad text,' 'static ads,' 'ad templates,' 'iMessage ad,' 'chat reveal ad,' 'ChatGPT ad,' 'Apple Notes ad,' 'AirDrop ad,' 'creative strategy,' 'creative roadmap,' 'creative retro,' 'hook writing,' 'creative review page,' 'present ad creative for approval,' 'motion video ad,' 'faceless video ad,' 'UGC ad,' 'greenscreen ad,' 'TikTok/Reels ad format,' 'which ad format to make,' 'Meta ad format tier list,' or 'creative format taxonomy.' Use this whenever someone needs to produce ad copy at scale or iterate on existing ads. For campaign strategy and targeting, see ads. For landing page copy, see copywriting.★ 51.1k GitHub starsSkillBusiness-brainstorm — Pressure-test a business ideacoreyhaines31/makerskills · by coreyhaines31When you want to pressure-test a potential new business, product, or side project against the serial-founder filter. Not "marketing ideas for a product" (that's marketing-skills:marketing-ideas) — this is "should this business exist + can you win it." Runs the idea through a structured framework (problem, audience, wedge, monetization, moat, portfolio fit, distribution, energy fit, opportunity cost), checks domain availability via /domain, optionally triggers /deep-research for market validation, and outputs a viability brief: build / sleep on it / pass. Archives every idea to ~/.config/makerskills/business-brainstorm/archive/ so past work is searchable. Triggers on "/business-brainstorm," "/brainstorm," "new business idea," "should I build X," "pressure test this idea," "validate this idea," "is X a good business," "what about a [type] for [audience]."★ 855 GitHub starsSkillYour team's shared, AI-ready knowledge base/company-brain — Team-shared AI-ready knowledge basecoreyhaines31/makerskills · by coreyhaines31Your team's shared, AI-ready knowledge base — people, companies, meetings, SOPs, and decisions structured so an agent can answer on your team's behalf. Team-scope sibling to second-brain. Modes — capture, compile (wiki pages + INDEX.md), query (trust-weighted, saved to outputs/), review (verify / deprecate / supersede stale captures), lint, connect, search. Structured raw dirs (people/, companies/, meetings/, sops/, decisions/, customer-language/, sales-objections/). Every capture stamps author, timestamp, and trust status. Optional sync from call transcripts, Slack/email exports, CRM. Vault at ${COMPANY_BRAIN_VAULT:-$HOME/Documents/CompanyBrain}/. Triggers on "/company-brain," "/cb," "capture this into the team brain," "log this meeting," "save this SOP," "compile the company wiki," "query the team brain," "what does the team know about X," "review the company brain," "lint the company brain," "who's the internal expert on X.★ 855 GitHub starsSkillMonthly CFO workflow for a company or agency/company-cfo — Monthly company CFO workflowcoreyhaines31/makerskills · by coreyhaines31Monthly CFO workflow for a company or agency — pull raw data from bank + payment processor + payroll + expense management, categorize and reconcile, compute end-of-month cash via transaction-sum method, update a scenario projector for forward forecasting, write the monthly snapshot report, surface decisions to leadership. Modes — monthly (default; the standing report), weekly (thin cash pulse), scenario (ad-hoc modeling in the projector), pickup (resume where the prior run left off). Anonymized team-scope sibling to personal-cfo (which handles personal household finances). Composes with company-brain (report gets stored + wiki-indexed there), toolify (wire company-specific data sources), loopify (schedule the monthly + weekly runs). Triggers on "/company-cfo," "/cfo," "monthly cash report," "do the CFO snapshot," "CFO monthly," "let's run CFO," "cash projection," "runway forecast," "monthly financials," "cash pulse.★ 855 GitHub stars