The Claude SDR Stack: A Full Junior Rep Replacement System

Sources: the 80+ Claude Code Sales Skills lead mag already built in this workspace, TheCraigHewitt/skills (47 skills, MIT), HubSpot/agent-cli-skills (official CRM skills), gtm-skills.com (2,500+ prompts, MIT, role playbooks including a dedicated SDR track), plus 6 full original skills chaining the whole thing into one daily routine.

The framing: a full SDR's day has 6 real jobs, prospecting, research, outreach, CRM logging, meeting prep, and reporting. Individually, plenty of tools cover one of these. This stack chains all 6 into a single daily routine a founder or GTM engineer can run without hiring the headcount, using skills already documented in this workspace plus 3 sourced repos filling the remaining gaps.

6 modules, one per job:

1. Morning: Prospecting and List Building
2. Research: The Account and Contact Brief
3. Outreach: Multi-Channel Sequencing
4. CRM: Logging Without Opening the Browser
5. Pre-Call: Meeting Prep in 5 Minutes
6. End of Day: Pipeline Reporting

The honest scope of this stack

This replaces the repetitive, high-volume work a junior SDR does: building lists, writing first-draft outreach, logging activity, prepping briefs. It does not replace judgment calls that need a human: deciding whether a prospect is genuinely worth pursuing past the data, reading tone on a live call, or negotiating. Route those to a human every time; automate everything else.

The morning job: building today's target list before any outreach happens.

Sourced skills for this stage

From the 80+ Claude Code Sales Skills lead mag: /sales-prospect, /sales-research, /sales-icp for defining and searching against ICP criteria.

From TheCraigHewitt/skills: lead-research (account/contact research covering trigger events, org charts, tech stack, intent signals) and icp-scoring from LeadMagic/gtm-skills for prioritisation tiers.

npx skills add TheCraigHewitt/skills/sales
npx skills add LeadMagic/gtm-skills

From gtm-skills.com: role-specific SDR prompts for prospecting are organised inside their Role Playbooks section, covering the full SDR workflow specifically rather than a generic sales prompt applied to every seat.

Full original skill: daily-prospect-list

mkdir -p .claude/skills/daily-prospect-list

---
name: daily-prospect-list
description: >
  When building today's outreach target list, load this skill. Runs first
  in the daily SDR routine.
---

# Daily Prospect List

## Input
ICP from CLAUDE.md. Yesterday's contacted list (to exclude). Target
volume for today: [N]

## Process
1. Search against ICP criteria (title, company type, size, geography)
2. Check each result against yesterday's contacted list and the last
   30 days of campaign logs, exclude duplicates
3. Prioritise: any prospect with a visible trigger signal (job posting,
   funding, recent LinkedIn activity) ranks above ones without
4. Stop at target volume or when signal-quality prospects run out,
   whichever first

## Output
todays-list.csv: name, title, company, signal type (if any), signal
detail, priority (high/medium/low)

## Rules
Never pad the list with low-fit prospects to hit a volume target.
Report the actual count if it falls short and why.

The research job: turning a name on a list into enough context to write something real.

Sourced skills for this stage

From the 80+ Claude Code Sales Skills lead mag: /sales-research for the account and contact deep-dive.

From chadboyda/agent-gtm-skills: lead-enrichment (enrichment waterfalls, ICP scoring formulas, Clay workflows, confidence thresholds).

npx skills add chadboyda/agent-gtm-skills

Full original skill: account-brief

mkdir -p .claude/skills/account-brief

---
name: account-brief
description: >
  When researching a specific prospect or account before outreach or a call,
  load this skill.
---

# Account Brief

## Input
Prospect name, title, company. Any signal already identified from
daily-prospect-list.

## Research
1. Company overview: what they do, size, recent news (last 90 days)
2. The specific trigger signal, verified and detailed
3. The prospect's likely priorities based on their role and the
   company's current stage
4. One specific, real detail worth referencing in outreach (not
   generic praise)
5. Any visible reason this might NOT be a fit (be honest, do not spin
   a weak lead into a strong one)

## Output
A one-paragraph brief: company context, the signal, the angle to lead
with, and a confidence rating (high/medium/low) on whether this is
worth prioritising.

## Rules
If research turns up nothing beyond generic company info, say so
plainly rather than manufacturing a false signal.

The outreach job: turning the research into an actual multi-channel sequence.

Sourced skills for this stage

From the 80+ Claude Code Sales Skills lead mag: /sales-outreach, /sales-cadence, plus the platform-specific sequencing skills (/sales-salesloft, /sales-apollo-sequences, /sales-lemlist, /sales-smartlead, and more, one per major sequencing tool).

From TheCraigHewitt/skills: cold-email (plain text, under 100 words, one ask), outbound-sequence (orchestrates across email, LinkedIn, and cold call, deciding when to use which channel), linkedin-outreach.

npx skills add TheCraigHewitt/skills/sales

Full original skill: daily-outreach-batch

mkdir -p .claude/skills/daily-outreach-batch

---
name: daily-outreach-batch
description: >
  When running today's outreach across the full prospect list, load this
  skill. Uses account-brief output for each prospect.
---

# Daily Outreach Batch

## Input
todays-list.csv with account briefs completed. My offer and brand voice
from CLAUDE.md.

## For each prospect
1. Write a cold email: under 100 words, one specific reference from the
   brief, one ask
2. If a LinkedIn signal exists, write a connection note under 200
   characters referencing it
3. Score each draft 1-10 for specificity before including it. Only
   include drafts scoring 7+; flag the rest for manual rewrite

## Output
outreach-batch.csv: name, company, email_subject, email_body,
linkedin_note (if applicable), specificity_score

## Rules
No em dashes. No fabricated facts about the prospect. Never send two
touches with the same angle to the same prospect on the same day.

The CRM job: logging activity so nothing lives only in someone's memory.

Sourced skills for this stage

From HubSpot/agent-cli-skills (official, built by HubSpot's own engineering team): deal-management (full deal lifecycle from the terminal), crm-lookup (find records by ID/email/domain), crm-data-quality (find incomplete records, normalise fields, dedupe), sales-execution (log calls, notes, meetings, and tasks against contacts and deals).

npx skills add HubSpot/agent-cli-skills

From the 80+ Claude Code Sales Skills lead mag: the 9 CRM platform skills for teams not on HubSpot (/sales-salesforce, /sales-attio, /sales-pipedrive, and others).

Full original skill: crm-activity-logger

mkdir -p .claude/skills/crm-activity-logger

---
name: crm-activity-logger
description: >
  When logging today's outreach and any call activity into the CRM,
  load this skill. Runs after daily-outreach-batch and after any calls.
---

# CRM Activity Logger

## Input
outreach-batch.csv (what was sent today). Any call notes or transcripts
from today.

## Process
1. For each row in outreach-batch.csv, log an activity: contact,
   channel, date, content sent, status (sent/pending)
2. For any call, log: contact, duration if known, outcome, next step,
   any notes worth flagging for a human
3. Flag any contact where this is the 3rd+ touch with no reply, for
   review on whether to continue the sequence

## Output
A CRM-ready activity log formatted for whichever CRM skill is
connected (HubSpot, Salesforce, or other), plus a summary: total
activities logged, contacts needing sequence review.

## Rules
Never mark an activity as complete without a real timestamp. Flag any
record that appears to be a duplicate before logging it.

The pre-call job: turning a booked meeting into a briefing document, not a scramble.

Sourced skills for this stage

From yeutterg/claude-code-sales-skills: sales-calendar, which scans your Google Calendar, identifies each meeting, and generates targeted questions based on MEDDPICC gaps and competitive intel for that specific account. Described as turning 30 minutes of manual prep into 5.

git clone https://github.com/yeutterg/claude-code-sales-skills

From the 80+ Claude Code Sales Skills lead mag: /sales-call-prep, /sales-discovery.

Full original skill: meeting-brief-generator

mkdir -p .claude/skills/meeting-brief-generator

---
name: meeting-brief-generator
description: >
  When prepping for a scheduled call or meeting, load this skill.
---

# Meeting Brief Generator

## Input
Meeting details (attendee, company, meeting type). The account-brief
and CRM history for this contact if available.

## Produce
1. Company and contact recap (2-3 sentences)
2. What we know so far: prior touches, any replies, the signal that
   started this relationship
3. 3-4 targeted questions specific to this account, not generic
   discovery questions
4. The one thing most likely to derail this call (a known objection,
   a competitor they might mention, a budget concern)
5. The specific outcome to aim for by the end of this call

## Output
A one-page brief, scannable in under a minute before the call starts.

## Rules
Questions must be specific to this account's context, not a generic
template. If prior CRM history is thin, say so rather than inventing
context.

The reporting job: closing the loop so the whole stack shows what's actually working.

Sourced skills for this stage

From yeutterg/claude-code-sales-skills: sales-weekly, which generates a weekly report with Red/Yellow/Green deal health scoring and pushes it directly to Salesforce.

From the 80+ Claude Code Sales Skills lead mag: /sales-pipeline, /sales-reporting.

Full original skill: sdr-daily-summary

mkdir -p .claude/skills/sdr-daily-summary

---
name: sdr-daily-summary
description: >
  When closing out the day, load this skill to summarise today's SDR
  activity and flag anything needing attention tomorrow.
---

# SDR Daily Summary

## Input
todays-list.csv, outreach-batch.csv, today's CRM log, today's meeting
briefs and outcomes.

## Compile
1. Prospects contacted today: count, and how many were high-priority
2. Replies received today: count and classification (positive/neutral/
   negative/out of office)
3. Meetings held or booked today
4. Anything flagged for human review (a 3rd-touch no-reply, a
   borderline lead, an ambiguous reply)
5. The one thing to prioritise first thing tomorrow

## Output
A short daily summary, under 150 words, formatted for a Slack post or
a quick morning read. Not a full report, a scan.

## Rules
Always lead with what needs human attention, not with volume metrics.
Volume without quality signal is not the headline.

The full daily chain

1. daily-prospect-list builds today's target list
2. account-brief runs on each prospect (or the top N by priority)
3. daily-outreach-batch drafts the actual outreach for each
4. crm-activity-logger logs what was sent
5. meeting-brief-generator preps any calls booked for today
6. sdr-daily-summary closes the day and flags tomorrow's priority

All 6 original skills, every sourced repo install command, and the honest handoff rule for when this stack needs a human.

All 6 original skills

daily-prospect-list: builds today's target list, excludes anyone contacted in the last 30 days.

account-brief: turns a name into a real, honest research brief.

daily-outreach-batch: drafts email and LinkedIn outreach for the full list, self-scores for specificity.

crm-activity-logger: logs every touch and call, flags stale sequences for review.

meeting-brief-generator: turns a booked call into a one-page brief in under a minute to read.

sdr-daily-summary: closes the day, leads with what needs human attention, not volume.

Install everything

mkdir -p .claude/skills/{daily-prospect-list,account-brief,daily-outreach-batch,crm-activity-logger,meeting-brief-generator,sdr-daily-summary}

# Sourced repos filling the remaining gaps
npx skills add TheCraigHewitt/skills/sales
npx skills add HubSpot/agent-cli-skills
npx skills add LeadMagic/gtm-skills
npx skills add chadboyda/agent-gtm-skills
git clone https://github.com/yeutterg/claude-code-sales-skills

# Browse gtm-skills.com's SDR-specific role playbook
# gtm-skills.com/role for the full track

Where a human has to take over

This stack drafts and logs. It does not decide whether a borderline lead is genuinely worth pursuing past what the data shows, it does not read tone on a live call, and it does not negotiate. Every skill above is built to flag rather than guess when it hits one of these judgment calls, specifically so the stack stays useful instead of becoming something that quietly produces confident-sounding nonsense at volume.