Skip to content
Back to skills

Account Brief

ASecurity

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

  • 2 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 6, 2026
ai-agentsrustgo

Works with

  • cli

Security analysis

A100/100

Scanned September 6, 2026

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

Installs into .claude/skills of the current project.

Are you the author of Account Brief?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Account Brief
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/onewave-ai-account-brief/badge)](https://www.skillsdirectory.com/skills/onewave-ai-account-brief)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: account-brief
description: 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.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…