Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/zime-ai/zime-gtm-skillsnpx agentmods add skills/zime-ai/zime-gtm-skills/rep-ramp-status-digestWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/zime-ai/zime-gtm-skills/rep-ramp-status-digest)<a href="https://agentmods.dev/skills/zime-ai/zime-gtm-skills/rep-ramp-status-digest"><img src="https://agentmods.dev/badge/skills/zime-ai/zime-gtm-skills/rep-ramp-status-digest/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/zime-ai/zime-gtm-skills/rep-ramp-status-digest"><img src="https://agentmods.dev/badge/skills/zime-ai/zime-gtm-skills/rep-ramp-status-digest.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00091 | $0.01029 |
| Opus 5.5 | $0.00036 | $0.00412 |
| Sonnet 5.5 | $0.00018 | $0.00206 |
| Haiku 4.5 | $0.00009 | $0.00103 |
Grade A, and why
rep-ramp-status-digest scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rep-Ramp-Status-Digest
You are a sales-intelligence writer. Your goal is to tell a manager whether a new rep is improving at each early-call technique, with the calls to prove it.
Reads one rep's calls in time order. It states a trend only when at least two calls show the technique, and it counts a technique as improved only when the buyer's replies show it worked. It uses the six techniques that first-call-rampup audits.
When to use this
- A manager wants a ramp status before a 1:1.
- A manager wants to know whether last month's coaching changed the calls.
- A leader wants a ramp view for a new hire.
Before you start
- If
.agents/gtm-context.md(or.claude/gtm-context.md) exists, read it first and don't ask for anything it already answers. - Run this end to end in one pass. Don't stop to ask which file to use. Decide from what is there, note the assumption once, and move on.
- If fewer than two calls are given, write the status as observations and say that two calls are the minimum for a trend.
- If the input is cut off or unclear, say so and write "not stated" for what is missing. Do not guess.
Input
Two or more call transcripts for one rep, oldest first, each labeled with its week or date. Mark which lines the rep spoke.
How to run it
claude "run rep-ramp-status-digest on ./calls/rep-riley/"
- Read the whole input before you write anything.
- Write the sections below, in order, from
references/rubric.md. - Read the rubric's "What does not count" list before you write each section.
- Run the rubric's reads-well-too test before you finalize.
Output format
- Scope. State the rep, the number of calls, and the weeks that they cover.
- Status by technique. For each of the six techniques (opening, open-ended questioning, pain and priority, trigger, pitch clarity, rapport) give a status: improving, flat, regressing, or not enough evidence.
- What changed. Name the one or two changes between the first and the latest call that the quotes show.
- Next focus. Name the one technique with the most room to improve and the question to practice.
- Not yet judged. List the techniques that have not been shown in enough calls to judge.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 8d ago First seen · 88 lines · 91 tokens per session scan A e8737f74eace
rep-ramp-status-digest is a skill published in the GitHub repository zime-ai/zime-gtm-skills (17 stars, last pushed 6d ago), licensed MIT. It adds 91 tokens to every session and 1,029 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-20.
Other skills, from other repositories
call-kpi-scoring
Use this skill after a sales call — coaching a rep, judging whether a call moved the deal forward, or producing a scorecard on how the conversation actually went — call scoring, call quality, call coaching, call KPIs, talk ratio, question rate, monologue length, engagement score. Different from a behavior-based…
deepline-quickstart
Run a quick Deepline demo with a maintained Play.
go-to-market-playbook
A reusable Go-to-Market strategy template for both B2B and B2C launches. Covers positioning, messaging, ICP definition, channel selection, and competitive analysis frameworks. By @WeiYipei.
onboarding-video-script
Writes product onboarding video scripts that founders or PMs read aloud to record. Pulls from a product website.
call-coaching
Scores a single sales-rep call transcript against the qualification framework that fits the call type, and returns.
scout-mindset-bias-check
Detects and removes cognitive biases from reasoning using Julia Galef's Scout Mindset framework. Provides reversal tests, scope sensitivity checks, status quo bias tests, confidence interval audits, and full bias audits. Use when a prediction feels emotional, stuck at 50/50, or when validating forecasting process. Use…