account-contextlisted

Captures the shared context every other customer success skill needs, once, so they stop asking for it. Trigger whenever the user says "account context", "set up account context", "set up the CS skills", "first time using these skills", "let me tell you about our product", "onboard me to these skills", or when any other skill in this library needs product, segment, contract or value-metric context that has not been established yet. Also trigger when the user says the skills keep asking the same questions, or that a skill's output felt generic. It interviews once, then writes a context document covering what the product does in the customer's words, how the segments differ, the contract shapes, the value metric the customer actually bought, what healthy usage looks like in this business, the go-to-market motion, and what customer success owns. Runs on whatever the user already knows and marks every gap as a gap rather than stalling.
CSPulse/customer-success-skills · ★ 1 · Data & Documents · score 67

Install: claude install-skill CSPulse/customer-success-skills

# Account Context Every other skill in this library needs the same handful of facts before it can say anything useful. What the product does. How the segments differ. Whether a flat usage line is a problem or the intended state. Who signs. Without this, each skill interviews the user from scratch and the library stops feeling like a library. It feels like a room full of strangers who have never met. The failure this exists to prevent: **a renewal risk read that says "usage is down, this may indicate risk" because it had no idea that in this business, low usage is what a healthy compliance deployment looks like.** --- ## What this needs **Minimum: five minutes and what the user already knows.** Nothing here is looked up. It is what someone who has worked the book for a month can answer from memory, and the gaps are recorded as gaps. **Better with** the pricing page, a sample contract, and a health-score definition if one exists. **Best with** the original business case for two or three accounts, because that is where the value metric is actually written down. --- ## Step 0: Check whether one already exists Before asking anything, look for an existing context document. It may be a file the user can point to, or a block they paste in. If one exists, read it back in one short paragraph, ask what has changed, and update only that. Re-running the full interview on someone who already did it is the fastest way to get this skill uninstalled. --- ## Step 1: The product,