account-review
Skill2 starsChanged 3 months agoMITView on GitHub
Use when the user says "account on a page", "monthly account review", "account review for", "one page on [account]", "what changed on this account since last month", "run my monthly review". Produces a one page review in a fixed shape: what changed, health by part, goals and proof, who has not been met, open commitments, risks, expansion signal, the next 30 days and the single decision or ask. Not for the renewal call (use renewal-risk), the customer meeting (use business-review) or a twelve month strategy (use account-plan).
1 other project uses a version of this.
Adopted by
Most recently taken up by
- pradeep-sankaran-07/team-os-gdrive-templatetheir own version, first seen Sep 17, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- pradeep-sankaran-07/team-os-gdrive-template★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository54 other files it gives its agents.
- account-contextSkill
- account-planSkill
- adoption-planSkill
- advocacy-askSkill
- book-reviewSkill
- book-triageSkill
- business-reviewSkill
- call-prepSkill
- call-recapSkill
- champion-lossSkill
- churn-postmortemSkill
- coachingSkill
- commitmentsSkill
- coverage-modelSkill
- csm-hiringSkill
- csm-rampSkill
- csql-motionSkill
- cs-scorecardSkill
- cs-startSkill
- customer-updateSkill
- day-planSkill
- email-criticSkill
- escalationSkill
- exec-conversationSkill
- expansion-caseSkill
- expansion-scanSkill
- handoffSkill
- hard-conversationSkill
- health-scoreSkill
- internal-askSkill
- invoice-chaseSkill
- mutual-action-planSkill
- nrr-narrativeSkill
- offboardingSkill
- onboarding-planSkill
- one-pagerSkill
- playbook-builderSkill
- portfolio-reviewSkill
- price-increaseSkill
- renewal-forecastSkill
- renewal-negotiationSkill
- renewal-riskSkill
- renewal-runwaySkill
- sales-handoffSkill
- save-planSkill
- stakeholder-mapSkill
- status-updateSkill
- survey-follow-upSkill
- team-rollupSkill
- usage-emailSkill
- value-ledgerSkill
- voice-of-customerSkill
- what-do-i-oweSkill
- skill-nameSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
If the user pasted notes, usage, tickets or emails for one account plus ARR and renewal date, go.
- Distinctive: line 19
If an "Account context" block exists, use it for what normal looks like.
- Very specific: line 25
Show health in parts,: never one blended color: usage, proof of value, relationship coverage, support, commercial.
≈ “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.
Files
Account Review
One page per account per month, in the same shape every time, so change is visible and one decision gets made.
Start here
If the user pasted notes, usage, tickets or emails for one account plus ARR and renewal date, go. Last month's review, if pasted, makes the change section real. Otherwise ask for these in ONE message, then proceed with whatever comes back:
- Account, ARR, renewal date, notice period
- What happened this month: calls, people, usage, tickets, requests
- Last month's review, or "none"
If an "Account context" block exists, use it for what normal looks like. Use whatever the user has connected opportunistically, and never require it.
Do this
- Set the clock: opt-out date = renewal date minus notice period. Report days to it, not to renewal.
- Change first. Diff against last month: people, usage, requests, commitments, tickets. With no prior review, write "baseline month, no change shown" and make this page next month's comparison.
- Show health in parts, never one blended color: usage, proof of value, relationship coverage, support, commercial. Each gets a number, its measure, a trend and a tag (
said,seen,inferred). The weakest part sets the headline. - Goals and proof. One line per goal: baseline, now, target, newest customer-stated proof and its age. Mandatory, even if the line reads "no proof".
- People. Named roles (champion, economic buyer, technical, any new name), met or not, last contact. Count roles met out of roles named.
- Commitments. Firm promises open, ours and theirs, with days overdue. Mandatory.
- Risks and expansion. Risks with a trigger date. Expansion only as a signal until the customer states a need; if sized, label it an estimate with its rule.
- Next 30 days as dated actions, then one decision or ask for the user's manager or the user. Pick the one that moves the clock.
Output
ACCOUNT REVIEW: [Account] | [ARR] | renews [date] | opt-out by [date] ([n] days) | [month]
Decision needed: [one] Headline: [state, set by which part]
Changed since [last review date]
- [change, tag]
Health by part
| Part | Value (measure) | Trend | Tag |
Goals and proof
- [goal]: [baseline] to [now], target [x]; newest proof [date, who, age]
People: [n] of [n] named roles met
| Name | Role | Met | Last contact |
Commitments (firm, open): ours [n], theirs [n]
- [item, owner, due, days overdue]
Risks: [risk, trigger date] Expansion: [signal, status, estimate if any]
Next 30 days: [date: action]
What I could not check
- [gap]A filled example is in examples/sample.md. Keep it to one page.
Rules
- Same shape every month. Change only shows when the page does not, and a reader who knows where to look reads it in two minutes.
- One decision per review. A page that asks for three things gets none, so choose the one that moves the clock.
- Health stays in parts. Averaging lets strong usage hide an unmet decider, and the weakest part is the one that renews or does not.
- Proof and commitments cannot be skipped. They are the first sections dropped under time pressure and the first things a renewal turns on.
- Name the measure on every count. "112 of 140 seats active in the last 30 days" can be challenged. "Usage is healthy" cannot.
- Silence from a decider outranks good usage. The people who run the tool are not the people who sign, so an unmet economic buyer is a finding, not a gap.
- A signal is not an opportunity. Someone mentioning a second site is a reason for a conversation. Size it only as an estimate and only on a deployment that works.
- List what you could not check. An unchecked ticket queue reads as a clean one.
Related (only if installed)
value-ledger for the proof section. commitments for the ledger behind that section. renewal-risk when the headline turns to watch or worse. stakeholder-map for the people section.
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
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.

