agentleFS
CSPulseCSPulse/customer-success-skills/skills/csm-hiring/SKILL.md

csm-hiring

Skill2 starsChanged 3 months agoMITView on GitHub

Use when the user says "interview kit for a CSM", "hiring a CSM", "CSM interview questions", "work sample for a CSM candidate", "scorecard for the CSM role", "how do I tell a good CSM from a nice one". Produces a role scorecard, eight structured questions with what strong and weak answers sound like, a 30 minute work sample with a rubric, red flags and a debrief template. Not for onboarding the hire (use csm-ramp) or coaching a current CSM (use coaching).

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If the user gave the segment, the book size and the level, go straight to "Do this".

    line 13
  2. Distinctive:

    If an "Account context" block exists in the conversation, use it for the product and the typical customer.

    line 21

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

CSM Hiring

An interview kit a hiring manager can run next week: the same questions for every candidate, a work sample that shows judgement, and a way to decide that does not depend on who liked whom.

Start here

If the user gave the segment, the book size and the level, go straight to "Do this".

Otherwise ask for these in ONE message, then proceed with whatever comes back:

  1. Segment, rough book (accounts and ARR), and whether the hire owns renewals and expansion
  2. Level and the experience the user expects
  3. What the last strong hire and the last weak one did differently

If an "Account context" block exists in the conversation, use it for the product and the typical customer. Do not ask for anything protected or personal about candidates.

Do this

  1. Write the scorecard from the outcomes. Three to five outcomes the hire must deliver in year one (renewals owned, accounts led, quality of reads). Then weight the competencies for this segment. Common defaults, set your own: mid-market leans on prioritization and commercial judgement, enterprise on executive communication.
  2. Choose eight questions. One per heavy competency, drawn from: commercial judgement, prioritization under load, ownership, hard customer, executive communication, written clarity, data comfort, technical fluency. Write what strong and weak answers sound like, and one probe for "what did you personally do, and what was the dollar figure".
  3. Assign who asks what. Same questions, same order, every candidate. One interviewer owns each competency, and a second scorer sits in on the panel to calibrate.
  4. Build the work sample. A fictional messy account of 8 to 10 facts with three planted traps: a signer nobody has met, a date that is not the renewal date, and a number whose measure is unclear. Thirty minutes to write a read, 15 to discuss. Score it against the renewal-risk format.
  5. Write the rubric. A 1 to 4 scale per competency with a described anchor, a 0 to 2 score per line of the work sample, a hiring bar and the red flags.
  6. Write the debrief. Scores in writing before anyone speaks, evidence beside each score, then discussion, then the decision and its one reason.

Output

CSM INTERVIEW KIT: [role] | [segment] | [level]
Year-one outcomes: [3 to 5]

Scorecard | competency | why it matters here | weight (points of 100) |
Hiring bar: [no 1 on which competencies; weighted total of at least N]

Questions
[n]. [competency] [question]
   Strong: [what it sounds like]  Weak: [what it sounds like]  Probe: [follow-up]

Who asks what: [rounds, interviewers, second scorer]

Work sample: [brief, traps, time] | Rubric: [lines scored 0 to 2, pass mark]
Red flags: [list]
Debrief: [template]

What I could not check
- [gap]

A filled example is in examples/sample.md. Match its length and tone.

Rules

  • Judgement and ownership outrank charm. Relationship skill is the easiest thing to see in an interview and the weakest predictor of whether a book gets run well. A likable CSM who cannot prioritize loses accounts politely.
  • Ask every candidate the same job-related questions. Different questions make candidates incomparable and let first impressions decide. Stay off age, family, health, origin and other protected topics, and have HR or legal confirm local rules.
  • The work sample is the best signal. Interview answers are rehearsed, but a messy account shows how someone reads evidence under a clock. Use invented data, never a real customer.
  • Score before you discuss. The first confident voice anchors the room. Written scores first keep the quiet interviewer's evidence in play.
  • Ask what went wrong, then who did it. A candidate who cannot name a failure has not owned a book, or cannot see their part in it. Blaming customers is the commonest tell.
  • Listen for dollars. A candidate who talks only about relationships and never ARR, notice dates or contraction will avoid the commercial half of the role.
  • Probe the "we". Credit for team outcomes is fine when the candidate can say which part was theirs. If they cannot, they were present, not responsible.
  • Anchor scores to evidence, not to the person. A 3 means a specific answer met the bar. Write the line they said, so the debrief argues about evidence.

Related (only if installed)

renewal-risk as the format for the work sample rubric. csm-ramp for the first 90 days once hired. coaching for development after.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.