Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add LeadMagic/gtm-skills --skill revenue-team-onboardinggit clone --depth 1 https://github.com/LeadMagic/gtm-skillsWrote 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/leadmagic/gtm-skills/revenue-team-onboarding)<a href="https://agentmods.dev/skills/leadmagic/gtm-skills/revenue-team-onboarding"><img src="https://agentmods.dev/badge/skills/leadmagic/gtm-skills/revenue-team-onboarding/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/leadmagic/gtm-skills/revenue-team-onboarding"><img src="https://agentmods.dev/badge/skills/leadmagic/gtm-skills/revenue-team-onboarding.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00104 | $0.03161 |
| Opus 5 | $0.00052 | $0.01580 |
| Sonnet 5 | $0.00021 | $0.00632 |
| Haiku 4.5 | $0.00010 | $0.00316 |
Grade A, and why
revenue-team-onboarding 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 7d 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 — 264 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Revenue Team Onboarding
Overview
Ramp is a system output, not a personality test. Slow ramp usually means broken onboarding: no security access day one, no shadow path, Slack chaos, and enablement PDFs nobody opens. This skill designs revenue onboarding: security-first access, structured 30-60-90, certification gates, and Slack norms that accelerate time-to-first-qualified-meeting.
Parallel lifecycle: Revenue team Hire → Ramp → Productivity → Promotion/Exit.
Customer lifecycle index → references/gtm-lifecycle-stages.md (team table).
Ramp metrics → references/lifecycle-metrics-by-stage.md (Revenue Team Ramp).
Comp plans must align with ramp credit — executive-compensation/references/gtm-compensation-strategy.md
(Pattern 35) · references/benchmark-reconciliation.md (ramp vs productivity).
Enablement assets → sales-enablement. Coaching → sales-coaching (REKS).
Process → pipeline-management.
When to Use
- "Onboard new SDR/AE"
- "Onboard GTM Engineer / RevOps hire"
- "30-60-90 plan for sales hire"
- "Reduce ramp time"
- "Slack channels for sales team"
- "Security onboarding for GTM hires"
- "Sales bootcamp week one"
Authoritative Foundations
- Mark Roberge. Onboarding as measurable machine: time-to-first-call, certification scores, conversion ramp curves.
- Winning by Design (Jacco van der Kooij). REKS diagnostic from week 3; certify on SPICED, not just product trivia.
- Jon Barrows (Sell Better). Skills training in short reps — objection, discovery, demo structure.
- Kevin Dorsey. Manager standards: daily coaching rhythm during ramp.
- Jason Bay. SDR messaging quality — certify outbound before live sends.
- Henry Schuck (ZoomInfo). Inbound SDR ramp emphasizes speed-to-lead
tooling and queue certification before live MQL access — public benchmark
<90s response. See
sales-team-building→henry-schuck-sdr-model.md. - Varun Anand (Clay). Certify reps on reverse demo (prospect screen-share,
first-win in 30 min) before solo PLG-hybrid demos —
demo-scripts→reverse-demo-varun.md. - Ryan Reisert — CRM Activity Buckets. Week 2–3: certify reps on four contact
stages and backwards daily workflow before unsupervised dialing.
→
references/ryan-reisert-cold-calling.md - Ronen Pessar — ColdCall-Market Fit. Phone SDRs: certify on pattern-interrupt
opener + 50-call disposition review before full quota. Manager validates
connect → completion → meeting funnel. →
references/ronen-pessar-cold-calling.md - Tom Slocum — 3×3 + sell-the-meeting. Week 1 cert: 3 insights in 3 minutes
on mock accounts; intro calls reviewed for meeting-sell (not product pitch).
→
references/tom-slocum-cold-calling.md - Tito Bohrt (AltiSales). Ramp to leading indicators, not dials: certify the
funnel bottom-up (meetings completed → set → conversations → dials) to a ~80–85%
show rate, and coach from call recordings (AltiSales reviews ~100% of a new
rep's calls, then samples). Treat ramp as a system output (data + scripts +
coaching). Canonical →
skills/founder-led/sales-team-building/references/tito-bohrt-sdr-science.md.
What ships with it
19 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.
- references/benchmark-reconciliation.md 24 KB
- references/cold-calling-experts-index.md 3.4 KB
- references/framework-notes.md 1.2 KB
- references/gtm-data-exchange-playbook.md 7.3 KB
- references/gtm-lifecycle-stages.md 8.6 KB
- references/gtm-security-hygiene-basics.md 4.4 KB
- references/lifecycle-metrics-by-stage.md 7.9 KB
- references/onboarding-questions.md 3.9 KB
- references/ramp-benchmarks.md 2.3 KB
- references/ronen-pessar-cold-calling.md 5.6 KB
- references/ryan-reisert-cold-calling.md 6.3 KB
- references/security-access-checklist.md 1.1 KB
- references/slack-engagement.md 2.8 KB
- references/tom-slocum-cold-calling.md 5.4 KB
- scripts/check-output.py 694 B runs code
- templates/30-60-90-sales.md 2.7 KB
- templates/certification-rubric.md 2.3 KB
- templates/new-hire-questionnaire.md 1.5 KB
- templates/output-template.md 1.5 KB
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.
- 7d ago First seen · 264 lines · 104 tokens per session scan A 997d9ba0c0e4
revenue-team-onboarding is a skill published in the GitHub repository LeadMagic/gtm-skills (49 stars, last pushed 4d ago), licensed MIT. It adds 104 tokens to every session and 3,161 once invoked, about $0.0005 per session on Opus 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-09-03.
Other skills, from other repositories
call-followup-sweep
Use this skill when a day or a week of customer calls has piled up and the follow-through is owed but unwritten. Trigger on "review my calls this week", "draft my follow-ups", "what do I owe people", "what did I promise on these calls", "catch me up on yesterday's calls", "did anything fall through this week". Asks…
meeting-prep
Build a pre-meeting briefing — who's in the room, what they care about, your goal, and the questions to ask. Trigger when the user asks to prep for a meeting or call, "what should I know before", or names an upcoming meeting.
calendar-followup
Surface unfinished follow-ups from last week's external meetings. Trigger when the user asks "who do I need to follow up with", "what meetings haven't I followed up on", or as part of the morning briefing ritual.
onboarding-handoff
Run the Won→onboarding handoff — the seam most teams drop. Trigger when a deal is marked won/closed-won, when the user says "we won X", "hand this off to onboarding", "kick off the new customer", or "onboarding checklist".
product-signal
Route post-sale and field signals into product's roadmap queue, and write the buyer-facing line for anything shipped. Trigger when the user says "what should product hear", "triage the roadmap signals", "route this to product", "feature request", or "what does this feature mean for the buyer".
follow-up
Debrief a meeting and draft the follow-up. Trigger when the user asks to debrief a call, follow up, or "what do I send after that meeting".