agentsclimarketplace

Account brief

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

Open-source plugins, managed agents, multi-agent orchestrators, and design tokens for Claude Code, the Agent SDK, and any AI tool. By OneWave AI.

Install
npx -y skills add OneWave-AI/open-agent-stack --skill account-brief

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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?"

SKILL.md

2.2 KB, as published. Nobody here has run it

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.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.