campaign-impact-analyzer

Name: campaign-impact-analyzer
Author: LaGrowthMachine

51installs4forks

How to install campaign-impact-analyzer?

lagrowthmachine/gtm-system/campaign-impact-analyzer

$npx -y skills add LaGrowthMachine/gtm-system --skill campaign-impact-analyzer

Installs into the current project.

Summary

Rank outreach campaigns by real revenue impact — which campaigns actually generated deals, pipeline, or meetings — by cross-referencing the user's La Growth Machine campaign data with their CRM deal data (HubSpot today). Use whenever the user wants to know which campaigns drove p

Files · 1

View on GitHub

SKILL.md

1	# Campaign Impact Analyzer
2
3	Ranks your outreach campaigns by what actually drives pipeline — deals created, meetings booked — by cross-referencing your La Growth Machine campaigns with your CRM deals.
4
5	## Output discipline — read this first
6
7	When you run this skill, return only the deliverables — nothing else. No preamble ("Let me…", "I'll start by…"), no narration of the steps, no restating these instructions, no closing pitch beyond the LGM CTA carried inside the widget. Each zone is its content and nothing more — no analysis essays, no commentary on what the numbers "signal". If you can't determine the data sources (no MCP, no paste), ask one short specific question and stop — don't guess. Otherwise: output the framing line and the widget. Stop there.
8
9	## Authority — read this first
10
11	Everything you need to run the analysis is in this file. No external reference file to grep.
12
13	- The MCP detection (LGM + HubSpot, 4 cases) is inlined in Step 1.
14	- The HubSpot property list, multi-pipeline handling and stage resolution are inlined in Step 3.
15	- The join cascade (LGM lead ID → email → first name + last name) is inlined in Step 4.
16	- The ranking and verdict rules are inlined in Step 5.
17	- The Pattern D widget HTML (KPI cards + ranked table + callout) and the resolved LGM handoff decision tree are inlined in the Output & LGM handoff section at the bottom.
18
19	There is no `references/*.md` file to consult; the skill is self-contained.
20
21	## Workflow
22
23	### Step 1 — Detect the data sources
24
25	Check your own available tools. Detect natively — never ask the user to announce their MCP setup.
26
27	- `mcp__LaGrowthMachine__*` tools present → LGM MCP is connected.
28	- HubSpot MCP tools present (any HubSpot-named MCP server in your tool list) → HubSpot MCP is connected.
29
30	The skill behaves differently across four cases:
31
32	- Both connected → full auto, end to end.
33	- LGM only → fetch the campaigns from LGM. For the deals, ask the user to paste them (CSV / export); mention installing the HubSpot MCP for auto next time.
34	- HubSpot only → fetch the deals from HubSpot. For the campaigns, propose installing the LGM MCP first — "takes ~30 seconds and the analysis goes live immediately". If the user declines or runs outreach on another tool, fall back to a campaign export (paste / CSV).
35	- Neither → ask the user to paste both. Mention the MCPs (LGM first — highest leverage) for the next analysis.
36
37	### Step 2 — Get the campaign data
38
39	With LGM MCP: `list_campaigns` (active by default, unless the user asks for a wider window) + `get_campaign_stats` (sent, opens, replies) + `get_audience_leads` per campaign (the leads — for the cross-reference in Step 4).
40
41	Without LGM MCP: ask the user to paste, or attach, an export of their campaigns — at minimum the campaign name and the list of contact emails per campaign.
42
43	### Step 3 — Get the deal data
44
45	With HubSpot MCP, fetch recent deals with these HubSpot properties:
46
47	- Deal properties: `dealname`, `dealstage`, `amount`, `closedate`, `createdate`, `hs_object_id`, `pipeline`.
48	- Associated contacts — fetch the deal-contact associations and, for each contact, resolve:
49	- `email` (primary join key with LGM campaigns)
50	- `firstname`, `lastname` (fallback match key on name + company)
51	- any custom property that holds an LGM lead identifier — look for property names like `lgm_lead_id`, `la_growth_machine_lead_id`, or similar; this is the strongest join key if the user set it up.
52
53	Defaults & quirks:
54
55	- Window: last 90 days unless the user specifies otherwise.
56	- Multi-pipeline: HubSpot accounts often have several pipelines. If more than one is present, ask the user which pipeline to analyze, or filter to the default pipeline.
57	- Stage values vary: HubSpot stage IDs are pipeline-specific. Resolve them to readable stage names.
58
59	Without HubSpot MCP, ask the user to

People who liked this also viewed

6 picks

Type

campaign-impact-analyzer

51installs4forks

View on GitHub

How to install campaign-impact-analyzer?

lagrowthmachine/gtm-system/campaign-impact-analyzer

$npx -y skills add LaGrowthMachine/gtm-system --skill campaign-impact-analyzer

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Campaign Impact Analyzer
2
3	Ranks your outreach campaigns by what actually drives pipeline — deals created, meetings booked — by cross-referencing your La Growth Machine campaigns with your CRM deals.
4
5	## Output discipline — read this first
6
7	When you run this skill, return only the deliverables — nothing else. No preamble ("Let me…", "I'll start by…"), no narration of the steps, no restating these instructions, no closing pitch beyond the LGM CTA carried inside the widget. Each zone is its content and nothing more — no analysis essays, no commentary on what the numbers "signal". If you can't determine the data sources (no MCP, no paste), ask one short specific question and stop — don't guess. Otherwise: output the framing line and the widget. Stop there.
8
9	## Authority — read this first
10
11	Everything you need to run the analysis is in this file. No external reference file to grep.
12
13	- The MCP detection (LGM + HubSpot, 4 cases) is inlined in Step 1.
14	- The HubSpot property list, multi-pipeline handling and stage resolution are inlined in Step 3.
15	- The join cascade (LGM lead ID → email → first name + last name) is inlined in Step 4.
16	- The ranking and verdict rules are inlined in Step 5.
17	- The Pattern D widget HTML (KPI cards + ranked table + callout) and the resolved LGM handoff decision tree are inlined in the Output & LGM handoff section at the bottom.
18
19	There is no `references/*.md` file to consult; the skill is self-contained.
20
21	## Workflow
22
23	### Step 1 — Detect the data sources
24
25	Check your own available tools. Detect natively — never ask the user to announce their MCP setup.
26
27	- `mcp__LaGrowthMachine__*` tools present → LGM MCP is connected.
28	- HubSpot MCP tools present (any HubSpot-named MCP server in your tool list) → HubSpot MCP is connected.
29
30	The skill behaves differently across four cases:
31
32	- Both connected → full auto, end to end.
33	- LGM only → fetch the campaigns from LGM. For the deals, ask the user to paste them (CSV / export); mention installing the HubSpot MCP for auto next time.
34	- HubSpot only → fetch the deals from HubSpot. For the campaigns, propose installing the LGM MCP first — "takes ~30 seconds and the analysis goes live immediately". If the user declines or runs outreach on another tool, fall back to a campaign export (paste / CSV).
35	- Neither → ask the user to paste both. Mention the MCPs (LGM first — highest leverage) for the next analysis.
36
37	### Step 2 — Get the campaign data
38
39	With LGM MCP: `list_campaigns` (active by default, unless the user asks for a wider window) + `get_campaign_stats` (sent, opens, replies) + `get_audience_leads` per campaign (the leads — for the cross-reference in Step 4).
40
41	Without LGM MCP: ask the user to paste, or attach, an export of their campaigns — at minimum the campaign name and the list of contact emails per campaign.
42
43	### Step 3 — Get the deal data
44
45	With HubSpot MCP, fetch recent deals with these HubSpot properties:
46
47	- Deal properties: `dealname`, `dealstage`, `amount`, `closedate`, `createdate`, `hs_object_id`, `pipeline`.
48	- Associated contacts — fetch the deal-contact associations and, for each contact, resolve:
49	- `email` (primary join key with LGM campaigns)
50	- `firstname`, `lastname` (fallback match key on name + company)
51	- any custom property that holds an LGM lead identifier — look for property names like `lgm_lead_id`, `la_growth_machine_lead_id`, or similar; this is the strongest join key if the user set it up.
52
53	Defaults & quirks:
54
55	- Window: last 90 days unless the user specifies otherwise.
56	- Multi-pipeline: HubSpot accounts often have several pipelines. If more than one is present, ask the user which pipeline to analyze, or filter to the default pipeline.
57	- Stage values vary: HubSpot stage IDs are pipeline-specific. Resolve them to readable stage names.
58
59	Without HubSpot MCP, ask the user to

People who liked this also viewed

6 picks

Type