{
  "skill_name": "renewal-risk-brief",
  "evals": [
    {
      "id": 1,
      "prompt": "Create a renewal risk brief for Northstar Bio. Renewal is October 31, ARR is $184k, forecast is commit but I'm worried. Usage fell from 142 weekly active users in Q1 to 83 last month. Their champion moved to a new role in finance and the new ops director has not joined our last two calls. Open support ticket about SSO has been waiting on their IT team for 18 days, but they mention it every call. They asked procurement for a 12% price reduction because their headcount is flat. They still use our compliance reporting feature heavily and the VP Ops said in the QBR that it saved the audit team time. We have no relationship with the CFO. Draft the brief and the first internal escalation note.",
      "expected_output": "A Sales / Account Manager renewal risk brief that challenges the commit forecast, distinguishes adoption, champion, procurement, support, and value signals, proposes a concrete save plan, uses conditional concession guidance, and drafts an internal escalation note without overpromising."
    },
    {
      "id": 2,
      "prompt": "I need a manager-ready renewal prep brief for Atlas Retail. Renewal is in 45 days, $96k ARR, 280 seats. They used 238 seats last quarter but only 171 this quarter after closing two stores. The regional VP is still a fan and wants to add analytics for the ecommerce team next year. Their procurement lead says budget is frozen until February and asked about a 6-month extension instead of a full-year renewal. Support has no major escalations, but the customer says onboarding store managers is too much manual work. We have one call with their VP and procurement next week.",
      "expected_output": "A renewal prep brief that separates contraction, delay, and expansion potential, rates risk by evidence bucket, recommends a mutual close plan for the VP/procurement call, handles the 6-month extension carefully, and identifies adoption/process actions for store manager onboarding."
    },
    {
      "id": 3,
      "prompt": "Turn these messy account notes into a renewal risk brief and customer-facing follow-up. Customer: QuantStack, $410k ARR, renewal Dec 15, enterprise security package. Usage is steady in engineering but the security team stopped attending office hours. New CISO joined from a competitor's customer base and asked for a data residency roadmap. We had a Sev2 incident in May, resolved in 7 hours, postmortem was sent but their security architect said trust took a hit. Legal is pushing a new DPA. Our champion in platform engineering wants to expand to 300 more developers, but procurement says renewal must be flat unless security signs off.",
      "expected_output": "A renewal risk brief that identifies security trust and economic-buyer approval as primary blockers, avoids assuming engineering expansion offsets renewal risk, proposes executive/security engagement and DPA next steps, and drafts a customer-facing follow-up that does not overpromise roadmap commitments."
    }
  ]
}