Skip to content

Guide · Agent skill

How to use the Review Rep Call Trends agent skill

Updated · written with AI from the project's own documentation and checked against our catalogue data

The review-rep-call-trends skill is an agent skill that teaches an AI agent to compare a sales or customer-facing rep's call behavior across time and produce a trend readout. It is built for sales managers, reps and enablement teams who want coaching notes grounded in call evidence rather than impressions. After this guide you will know what the skill does, how to install it, how to trigger it with a plain request, and what it needs before it can produce a useful result.

Review Rep Call TrendsXiaomiMiMo/MiMo-Code · MIT

Quick start

  1. 1Confirm you have a call data source. Connect a Meeting Transcripts source, or be ready to paste older and newer call summaries into the conversation.
  2. 2Install the ZIP. Unzip the downloaded skill into ~/.claude/skills/ or a project's .claude/skills/ folder, or upload the ZIP under Settings → Capabilities → Skills in the Claude apps.
  3. 3Name the rep and comparison basis. State whose calls to review and whether you want the default trailing 90 days, supplied older and newer sets, or a custom window.
  4. 4Answer the clarifying questions. If the agent asks about the rep's exact name or a date phrase, answer briefly so the sample is not skewed.
  5. 5Review the trend readout. Check the improved, regressed, stable and inconsistent categories against the linked calls.
  6. 6Practise the three coaching actions. Use the two-week drills and observable checks, then re-listen to the suggested calls.

What the skill makes the agent do

The skill reviews a representative's meeting call summaries across older and newer time periods. It splits the trailing 90 days into three slices (0-30, 31-60 and 61-90 days), compares the same behavior categories across them, and checks a few full calls to confirm patterns.

The output is a readout of what improved, what regressed, and what stayed stable, followed by three concrete coaching actions for the next two weeks and a short list of calls to re-listen to. The skill reads data from connected meeting transcript and file sources. It does not run code, create trackers, send messages or save files.

  • Improved: a behavior that moved in a clear positive direction between time slices.
  • Regressed: a behavior that moved in a clear negative direction.
  • Stable: a repeated pattern without clear movement.
  • Inconsistent: mixed evidence, labelled as such rather than forced into a trend.
  • Coaching actions: exactly three, each with a skill to practice, an if/then play, a five-to-ten-minute drill and an observable check.

Install the skill from the ZIP or the Claude apps

Download the ZIP for the skill from the page you are reading. Then choose one of two routes.

For Claude Code, unzip the skill into ~/.claude/skills/ to make it available for you across projects, or into a project's .claude/skills/ folder to limit it to that project.

In the Claude apps, upload the ZIP under Settings → Capabilities → Skills.

  • Personal install: ~/.claude/skills/
  • Project install: .claude/skills/ inside your project folder
  • Claude apps: Settings → Capabilities → Skills, then upload the ZIP

Connect the data sources the skill needs

The skill needs a connected Meeting Transcripts source. Without it, live trend review is blocked unless you supply older and newer call evidence yourself. Call summaries or transcripts are required for any trend claim; manager notes, CRM outcomes and general impressions can add context but cannot replace older-versus-newer call evidence.

A Knowledge & Files source is optional and is useful for exported transcripts, call summaries or a manager-provided call set. The optional ask_user_input tool, or the answers-ask-user-input skill, lets the agent ask structured questions. The skill also refers to other skills in the bundle (plugins/sales/skills/index) that are not included in these files, so check that those are available before relying on the full workflow.

  • Required: a connected Meeting Transcripts source, or older and newer call sets supplied in the conversation
  • Optional: a Knowledge & Files source for exported transcripts or call summaries
  • Optional: ask_user_input or the answers-ask-user-input skill for structured questions
  • Network access is used by the skill

Trigger the skill with a natural request

You do not need special syntax. Describe what you want to understand about a rep's calls and name a comparison basis. The skill will ask you to confirm the rep and time window if they are unclear. A bare request like 'review call trends' will not be assumed to mean a particular rep or window; the agent will offer explicit choices instead.

Good requests name the rep, the window or the calls to compare, and optionally a focus such as discovery, objections or next steps.

  • Review call trends for Jordan Lee over the last 90 days.
  • Show how Priya's discovery depth changed between her first and last month of calls.
  • Compare these two sets of call summaries for Sam and tell me what regressed on objection handling.
  • Review my call trends, focusing on next-step habits.

Read the readout and act on it

The readout ties each claim to evidence from the compared slices and includes live links to calls. Use the coaching actions as a two-week practice plan, and use the re-listen list to check the moments yourself before you act on them. The skill is designed to avoid claiming improvement from a single recent call or from outcomes alone. If the sample is small or skewed, the readout will be limited on purpose.

The skill also reminds you to keep the review to coaching. It is not built for formal performance decisions.

What people use it for

  • A sales manager reviewing whether a rep's discovery questions have gone deeper over a quarter.
  • A rep checking whether their objection handling or next-step habits are changing across recent calls.
  • An enablement team comparing call quality across older and newer calls before planning coaching.
  • Preparing a focused coaching note on one motion, such as renewals, using a supplied set of call summaries.

Frequently asked questions

Is the review-rep-call-trends skill free?

The skill is published under the MIT licence, which is stated on this page. Check the licence file in the source repository for the full terms before you reuse or redistribute it.

What do I need to run review-rep-call-trends?

You need a connected Meeting Transcripts source, or older and newer call summaries supplied in the conversation, because the skill requires call evidence for any trend claim. A Knowledge & Files source and the ask_user_input tool are optional. Some referenced skills in the bundle are not included in these files.

How do I install an agent skill like this one?

Download the ZIP from this page and unzip it into ~/.claude/skills/ for personal use or into a project's .claude/skills/ folder. In the Claude apps, upload the ZIP under Settings → Capabilities → Skills.

Does the skill run code or send messages?

According to its source, the skill runs no scripts and does not create trackers, send feedback, post messages or save files. It does use the network to read connected transcript and file sources.

Can I use it on only a few calls?

You can, but the skill is designed to return only a limited readout when the sample is small or skewed. It aims for roughly 30 to 60 calls when they are available.

Why won't the skill judge a rep from sales outcomes alone?

The skill treats CRM outcomes and generic impressions as context only. Trend claims need summaries or transcripts that show older-versus-newer behaviour, so outcomes alone are treated as insufficient evidence.

New agent skills, repos and AI tools — every week

The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.

Our verdict

Use this skill if you are a sales manager, rep or enablement lead who has call summaries or transcripts and wants evidence-based coaching notes on how behaviour is changing. Pick something else if you only have CRM outcomes, very few calls, or need a basis for formal performance decisions, since the skill itself warns against those uses. Confirm that calls are reviewed with consent and within your company's policies before you start.

Download the skill