Skip to content

OneWave-AI/open-agent-stack / plugins/sales-desk/skills/account-brief

account-brief

Verified

Everything about one account on one page -- relationship history, stakeholder map, health signals, renewal clock, open items, and expansion openings. Use before QBRs, escalations, handoffs, or any executive ask of "where are we with X?"

Account Brief

The account rep's answer to "catch me up on this account" -- assembled from what the systems already know. Input: account name plus whatever exists: CRM records, email threads, meeting notes, support tickets, usage exports, the contract.

Workflow

  1. Timeline. Reconstruct the relationship: when they became a customer, what they bought and why (the original pain), expansions, escalations, and champion changes. The origin story matters -- accounts drift from their buying reason and that drift is churn's early form.
  2. Stakeholder map. Who we know: champion, economic buyer, daily users, blockers -- with last-contact date per person. Flag single-threaded accounts (one contact = one resignation away from churn) and champions gone quiet.
  3. Health read. From tickets, usage, email tone and response latency: engaged / stable / drifting / at-risk, with the evidence cited. Distinguish "quiet because happy" from "quiet because gone" using usage, not vibes.
  4. The clocks. Renewal date, notice window, contract value, and any expansion or price-change conversations with their state.
  5. Openings. Where the artifacts show unmet need -- feature requests, workaround patterns in tickets, new teams appearing in threads. Expansion asks trace to observed need or they do not appear.
  6. Output. The one-pager: account vitals header, timeline, stakeholder map, health verdict with evidence, open items with owners, and the three moves that most improve this account's position.

Rules

  • Every claim cites its artifact; a brief the exec can't trust once is a brief they never trust again.
  • Gaps are stated: "no contact with the economic buyer in 6 months" is a finding, not a blank.
  • Health verdicts need two independent signals minimum -- one bad ticket is a Tuesday, not a trend.
  • Confidential internal notes (margin, team gripes) never leak into anything client-shareable; mark the brief internal-only by default.
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 197kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 194kUpdated Claude CodeCodexVerifiedInstall