Skip to content
Agentmart
Submit a tool

customer-renewal-evidence-brief

Use when a customer-success or account team needs to turn buyer-pasted account signals into a renewal-preparation brief without inventing health, intent…

Skill by Daisuke134

IndexedMIT★ 8
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/daisuke134-customer-renewal-evidence-brief

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Use when a customer-success or account team needs to turn buyer-pasted account signals into a renewal-preparation brief without inventing health, intent, commitments, or outcomes.

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/customer-renewal-evidence-brief

What's inside

Skill name
customer-renewal-evidence-brief
Description
Use when a customer-success or account team needs to turn buyer-pasted account signals into a renewal-preparation brief without inventing health, intent, commitments, or outcomes.
License
MIT
Instructions
49 lines in SKILL.md · view on GitHub

Files (4)

  • LISTING.md
  • SKILL.md
  • verified-demonstration.md · evidence/
  • icon.svg

SKILL.md (first lines)

# Customer Renewal Evidence Brief

Turn buyer-pasted account notes into a renewal-preparation brief that separates
observations, customer statements, planned actions, and missing evidence. It helps a
team prepare the next renewal conversation; it does not predict whether a customer
will renew.

## Input

Ask for the account name, renewal date if known, the period covered, usage or support
observations, customer statements, stakeholder updates, open requests, completed and
planned actions, owners, and the next customer touchpoint. Treat an omitted date,
owner, contract detail, outcome, or explanation as unknown.

## Method

1. Make an evidence ledger. Label every supplied item `observed`,
   `customer-reported`, `planned`, `completed`, `unknown`, or `needs verification`.
2. Keep activity changes separate from the reason for a change. Do not turn a usage
   observation, a cancelled meeting, or a budget comment into a renewal prediction.
3. Group the pasted material into adoption, support, stakeholder, commercial, and
   next-step signals. Leave an empty group explicit rather than filling it from
   general knowledge.
4. Draft a compact brief with known facts, open questions, and only the supplied
   owner and timing details.
5. Return a renewal-conversation agenda that asks for verification before any
   commitment, forecast, or account-health conclusion is used.

## Output

Return, in order:

1. A renewal-preparation summary with the supplied account, period, and next
   touchpoint.
2. A signal table that distinguishes evidence from unknowns.
3. An action register containing only supplied completed or planned actions, owners,
   and dates.
4. A conversation agenda and verification queue for the next customer discussion.
5. An evidence ledger for every material statement.

## Boundaries

Use only the material pasted into the chat and general language reasoning. Do not
inspect product telemetry, CRM records, support systems, contracts, invoices, emails,
or calendars. Do not calculate a renewal probability, diagnose a cause, declare
account health, make a customer commitment, or contact anyone. A responsible account
owner must verify the brief before using it in a customer or internal meeting.

From Daisuke134/life-manager, MIT.

More from Daisuke134/life-manager

Signals

Stars
8
Forks
2
Open issues
2,737
Last commit (this folder)
Oct 5, 2026 (24 days ago)
Last release
Aug 15, 2026 (2 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from Daisuke134

Cite this page

customer-renewal-evidence-brief skill. Agent Mart. https://agentmart.dev/skills/daisuke134-customer-renewal-evidence-brief (last updated 2026-10-24)