inbound-lead-audit-cx-map
Audit inbound lead handling and map the customer experience from source event to follow-up outcome.
npx skills add zapier/gtm-cheat-codes --skill inbound-lead-audit-cx-map --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Inbound Lead Audit + CX Map Use this skill to inspect how an inbound lead or hand-raiser was treated and produce an action-focused summary. ## Workflow 1. Identify the lead source and current-cycle event. 2. Review CRM timeline, owner assignment, outreach, meeting status, and routing evidence. 3. Distinguish automated touches from real human follow-up. 4. Map the customer experience in plain language. 5. Recommend the next owner action and any process fix. ## Zapier MCP And SDK Role - Use Zapier MCP to read CRM timelines, routing evidence, tracker rows, meeting status, and collaboration context. - Use Zapier SDK for scheduled audits, tracker updates, issue logging, and approval-routed summaries. - Keep rep escalations and source-of-truth writes human-reviewed. ## Guardrails - Do not count historical meetings from prior cycles as current-cycle success. - Do not infer human outreach from automation enrollment alone. - Keep any screenshots, lead data, and source URLs private.
- Workflow
- Zapier MCP And SDK Role
- Guardrails
What does the inbound-lead-audit-cx-map skill do?
Audit inbound lead handling and map the customer experience from source event to follow-up outcome.
How do I install it?
Run `npx skills add zapier/gtm-cheat-codes --skill inbound-lead-audit-cx-map --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From zapier/gtm-cheat-codes, a repository with 318 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.