Agent skill · Design & Presentation

gtm-enterprise-onboarding

Four-phase framework for onboarding enterprise customers from contract to value realization. Use when implementing new enterprise customers, preventing churn during onboarding, or solving the adoption cliff that kills deals post-go-live. Includes the Week 4 ghosting pattern.

GitHub68,948★ · +463/wk · 2 repos on radarProfile →
copilotMIT
Install
npx skills add github/awesome-copilot --skill gtm-enterprise-onboarding --agent copilot

Same command for any agent — swap --agent for claude-code, codex, cursor.

Facts
Files in the skill folder: 1
SKILL.md size: 14 KB
Bundled scripts: none
Declared author: Smit Patel (https://linkedin.com/in/smitkpatel)
Path: skills/gtm-enterprise-onboarding/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 37,432 · +281 this week
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Enterprise Onboarding Four-phase framework for onboarding enterprise customers from contract to value realization. The goal isn't just go-live — it's sustained adoption that doesn't cliff at Week 12. ## When to Use **Triggers:** - "How do we onboard this enterprise customer?" - "Customer went live but adoption is weak" - "We keep losing customers 3 months after go-live" - "POC to production transition" - "How do I prevent Week 4 ghosting?" - "Customer success onboarding framework" **Context:** - Enterprise or mid-market deals - Complex technical requirements - Multiple stakeholders involved - 30-90 day implementation timelines - Risk of churn during first year --- ## Core Frameworks ### 1. The Week 4 Ghosting Problem (And How to Prevent It) **The Pattern:** Week 1: Kickoff call goes great. Everyone's excited. Week 2-3: Technical discovery, requirements gathering. Still good. Week 4: Customer stops responding. Meetings get cancelled. "Too busy." **What Happened?** You started customer onboarding before internal alignment on their side. **Who Owns This Project Internally?** - Sales rep? (Already moved to next deal) - Technical champion? (Day job took over) - Executive sponsor? (Del

What's inside
Steps it walks through
  1. When to Use
  2. Core Frameworks
  3. 1. The Week 4 Ghosting Problem (And How to Prevent It)
  4. 2. The Adoption Cliff (Week 12 Problem)
  5. 3. Pre-Onboarding: Success Is Built Before First Customer Call
  6. 4. The Four-Phase Onboarding Flow
  7. 5. The Parallel Tracks Anti-Pattern
  8. Decision Trees
  9. Should I Start Customer Onboarding?
  10. Is This Onboarding At Risk?
  11. Is Adoption Sustained Post-Go-Live?
  12. Common Mistakes
  13. Quick Reference
  14. Related Skills
More from awesome-copilot
All skills →
About this skill
What does the gtm-enterprise-onboarding skill do?

Four-phase framework for onboarding enterprise customers from contract to value realization. Use when implementing new enterprise customers, preventing churn during onboarding, or solving the adoption cliff that kills deals post-go-live. Includes the Week 4 ghosting pattern.

How do I install it?

Run `npx skills add github/awesome-copilot --skill gtm-enterprise-onboarding --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 github/awesome-copilot, a repository with 37,432 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.

Keep going