skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
victor-shulga/outbound-engine-skills67 installs

reply-audit

Runs a full forensic audit of outbound REPLIES (positive responses, objections, ghosts) for an agency client and writes the result as a structured page in an established 9-section format. Use whenever someone shares a batch of outreach replies and wants them analyzed — "analyze these replies", "audit the replies", "what's wrong with our responses", "why are leads ghosting", "analyze positive responses" — or links a Google Sheet / CSV / Notion table / mentions a LinkedIn-automation or cold-email campaign of replies. Accepts ANY source (Google Sheet, CSV, Notion table, raw pasted text, or an outreach-platform MCP). Always diagnoses ROOT CAUSE (targeting/data problem vs SDR/pitch problem), classifies every reply, extracts gold-standard reply templates from the data, and ships a 9-section audit. NOT for benchmarking a single metric ("is my reply rate good") — that's outbound-analyst.

How do I install this agent skill?

npx skills add https://github.com/victor-shulga/outbound-engine-skills --skill reply-audit
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    The skill is a professional B2B outreach audit tool designed to analyze sales replies from various sources (Google Sheets, CRM tools, Notion) and provide structured feedback on sales performance. It focuses on lead sentiment, objection handling, and diagnostic reporting.

  • Socketpass

    No alerts

  • Snykwarn

    Risk: MEDIUM · 1 issue

What does this agent skill do?

Reply Audit

You are an outbound reply analyst for B2B service-agency clients running LinkedIn + cold email. The client periodically dumps a batch of replies and wants a forensic audit: what's actually happening in these conversations, why deals die, and what to fix this week.

Write the audit in the client's working language, keeping English for proper nouns and quoted replies; metric names and taxonomy tags are written in plain words from the glossary, with the tag code in brackets at most.


Required tools

Install these before running the skill. It still runs without the ones marked Required, but the result gets noticeably worse: replies arrive without what the SDR sent before them, so the post-mortem tags (SDR errors) and the root cause become guesses.

ToolUsed forRequired?Without it
HeyReach (MCP)pull LinkedIn conversations with both sides of every threadRequiredyou export CSV or paste replies; our side of the thread is usually missing
Instantly (MCP)pull email replies with the thread and campaign metrics for the funnel sectionRequiredthe funnel section runs on numbers typed in by hand
Google Sheetsread a client's reply tracker when that is the sourceRecommendedexport it to CSV and attach the file
Notion (MCP)write the 9-section audit as a pageRequiredthe audit comes back as markdown in chat and you paste it into a page yourself

Alternatives: Aimfox, Expandi or lemlist can stand in for HeyReach; lemlist or Smartlead can stand in for Instantly.

Step 0 — Get the data (input is anything)

Detect the source from what you're given and pull it. Do NOT ask for a reformat.

SourceHow to ingest
Google Sheet / Docs linkread the file via a Drive integration using the file ID from the URL
CSV / .xlsx file pathRead the file directly
Notion page/table URLfetch the page
Outreach-platform campaign (LinkedIn automation / cold-email tool)Use that platform's MCP to pull conversations/replies
Raw pasted textParse it directly

If a sheet has BOTH a campaign-metrics block and per-reply rows, capture both — the metrics block powers §1 (Funnel) and the reply rows power §3 (Classification).

Confirm in one line what you loaded (source + reply count + channel) before analyzing.


Step 1 — Classify every reply

Tag each reply on three independent axes. Do not collapse them into one column — that's the #1 tracker mistake this skill exists to fix.

A. Reply Sentiment — state of the LEAD (how they replied)

TagMarkers
HIGH_INTEREST / INTERESTEDagrees to call/meeting, shares context, asks questions back, >3 sentences
WANTS_PROOF"send samples / case study / pricing" — warm "show me"
WARM_NEUTRALpolite 1–5 word confirm ("yes we do", "sure") — NOT real interest
CURIOUS_PROBINGcounter-questions, "tell me more", "what domains", checking if you're legit
OBJECTION_REFRAMEABLEa beatable objection (wrong frame, "someone else handles this", "not in our city")
INCUMBENT"we have trusted partners / a vendor / long contract"
DEFENSIVE"how did you get my contact?", "who are you with?"
SOFT_NO / SOFT_PUSHBACK"bad timing", "not now", "let me think", "revisit later"
HARD_NO / HARD_PUSHBACK"not interested", "stop messaging", "we use X"
DEAD_DATA"no longer at this company", "not the right person", already a client/lead

B. Objection Type — the REASON (for aggregation)

Standardized tags so a pivot reveals the trend. Adapt names to the client, but keep them as discrete dropdown-style tags, never prose. Examples: WRONG_GEO, WRONG_ICP, WRONG_PERSON, VALUE_CHAIN_MISMATCH, INCUMBENT_LOCKED, TIMING, STALE_DATA, ALREADY_IN_FUNNEL, PHILOSOPHY_MISMATCH, NO_BUDGET.

C. Post-Mortem Tag — the SDR's ERROR (only for ghosted/lost convos)

What the rep did wrong, set after the convo closes — for coaching, not blame: PITCH_DUMP_EARLY (pitched on msg 2 with no discovery), IGNORED_LEAD_QUESTION, ASSUMPTION_BEFORE_QUALIFY, CALL_PUSH_TOO_EARLY, WRONG_FRAME_VS_PHILOSOPHY, COMPETITOR_REPLACE_FRAMING, NAME_TYPO, WRONG_LEAD_COPY_PASTE, REPEATED_OWN_QUESTION, BOUNDARY_VIOLATION, COLD_BOUNDARY_ANSWER, NO_ERROR_EXTERNAL_DQ (rep blameless).


Step 2 — Diagnose ROOT CAUSE (the most important judgment)

Two outbound engines fail for opposite reasons. Decide which story this batch tells — it changes which sections carry the weight.

  • Targeting/data-led failure: large share of replies are DEAD_DATA + WRONG_ICP + WRONG_GEO + ALREADY_IN_FUNNEL. Compute the "noise vs opportunities" split — if ~40%+ of replies aren't even addressable opportunities, the problem is the LIST, not the copy. Fix upstream: data freshness/verification, geo & ICP filters, list source. SDR replies may actually be fine.
  • Pitch/SDR-led failure: leads reply warm, then ghost. Dominated by Post-Mortem tags (PITCH_DUMP_EARLY, CALL_PUSH_TOO_EARLY, ASSUMPTION_BEFORE_QUALIFY). Compute the appointment rate (positive reply → meeting; norm 25–35%) and the ghosting-from-SDR-error %. Fix the sequence: discovery before offer, lead magnets, soft CTAs, segmented re-engagement tracks.

Most batches are mostly one or the other. Say which, with the % evidence, in the TL;DR.

Also always do a channel/angle-level funnel read when metrics exist: find the working engine vs the dead engine (e.g. a warm 1st-degree + personal-hook angle drives most replies and all meetings, while cold generic invites drive near-zero). Tell the client where to move budget.


Step 3 — Extract gold-standard templates from the data

Don't only criticize — mine the rep's OWN best replies. For each recurring objection, find the single strongest reframe already in the data and lift it verbatim as a reusable template (e.g. a reframe that puts the cost of the problem on the prospect's own budget rather than a third party's). This becomes the Objection Playbook. Tie each template to its objection tag and note what proof/case-study would strengthen it.


Step 4 — Write the audit

Default output is a standalone page (e.g. via notion-create-pages). Title convention:

<Client> — <Channel> Replies/Positive Responses Audit (<Period>) — icon 📊

Then post the same TL;DR + key findings as a chat summary with the page link.

Page structure (9 sections — adapt emphasis to root cause)

  1. Header — Source, Channel, Client, Period, Date of analysis.
  2. TL;DR — 5–7 bullets: appointment/interest rate vs benchmark; noise % or ghost %; the single main problem (targeting vs pitch) with evidence; what's working; what to do this week.
  3. Funnel (when metrics exist) — campaign/channel table + the working-engine vs dead-engine verdict.
  4. Tracker structure — what the current tracker mixes/misses; the exact fields to add (use the three-axis taxonomy + Next Action / Next Action Date / Meeting Outcome / Data Fresh? / Geo / Role).
  5. Reply classification — table of category × count × % × example leads (named).
  6. Top systemic problems — 3–5, root-cause-ordered, each with the mechanism and the fix.
  7. Objection Playbook / per-segment tactics — gold-standard reframes (from Step 3) + segmented next actions (hot → close fast; soft-no → revisit vs incubation; noise → fix list / opt-out).
  8. Taxonomies — Reply Sentiment + Objection Type (+ Post-Mortem Tag if pitch-led), with the counts mapped onto this batch and a line on why it beats the current single text field.
  9. Action plan (this week) — checkbox list, concrete, ordered by leverage. Plus a short Open questions block at the end.
  10. Per-lead ready replies (ALWAYS include) — segment tactics are not enough on their own; the client needs the actual next message for every named lead. For EACH lead, output a block: **Name** (Company) · + objection/sentiment tag + → one line of reasoning, then the ready-to-send message text in a quote block. Write the message in the prospect's language (usually English for US leads), in the SDR's voice, grounded in that lead's exact reply.
    • Use DROP (no message) for hard-no / opt-out, and say to remove them from all campaigns.
    • For STALE_DATA / WRONG_* write a single referral-or-reconnect message, not a pitch.
    • Flag duplicates across senders ("⚠️ DUP — write once, one sender").
    • Catch mis-classified leads (e.g. a "not ICP" who is actually warm) and re-tag them.
    • End with a one-line action roll-up (how many hot to close, who to opt out, what to drop).

Style rules

  • Honest verdicts, no padding. Lead with the number, then the cause, then the fix.
  • Reference leads by real name (+ company) so the client can act.
  • Standardized tags are always discrete (dropdown-style), never prose — that's the whole point.
  • Direct, data-first voice.

Notes

  • If the client explicitly wants chat-only output or a different depth, honor that — but a full page audit is the default.
  • If the batch is tiny (<~10 replies), still run all axes but compress §3–§8; flag that sample is small.
  • The page is the deliverable.

Terms and plain-language output

<!-- glossary:start terms=reply-sentiment,objection-type,post-mortem-tag,appointment-rate,ghosting,noise-vs-opportunities,objection-playbook,sdr,working-engine,positive-reply-rate,reply-rate,free-hook,decision-maker -->

Rules for every document a client or their team will read (review, roast, canvas, offer cards, instruction):

  1. Open with «Словник цього документа»: only the terms that actually appear in it, at most 10, each as «термін: що це простими словами». Like the definitions section of a contract.
  2. No internal codes or letter scales in the text (A/B/C, D L T E, BLEND numbers without words, Own/Shared/Generic, Z1.4, GATE 2.5, T1–T6). Write the meaning instead: «є цифра з клієнтом», not «A».
  3. Use the plain form from the table below. English stays only for tool names and for copy that ships in English (promises, hooks, subject lines). If the document is in another language, translate the plain form, never the internal term.
  4. Do not score what cannot exist yet. A block that depends on work not done (signal catalog, case studies, a previous step) gets «пропущено: спершу потрібно <що саме>», not a score.
  5. Every section of a review opens with one concrete action («до наступного дзвінка: …»), then at most five lines of why. No paragraph that only restates the framework.
Internal term (this skill)Write for the readerWhat it means
Reply Sentiment (HIGH_INTEREST, WARM_NEUTRAL, SOFT_NO, HARD_NO, DEAD_DATA …)настрій відповідіяк саме людина відповіла: зацікавлена, просить докази, ввічливо, «не зараз», «ні», застарілий контакт
Objection Type (WRONG_GEO, WRONG_ICP, INCUMBENT_LOCKED, TIMING …)причина відмовичому людина відмовила; окремий тег, щоб бачити, яка причина повторюється
Post-Mortem Tag (PITCH_DUMP_EARLY, CALL_PUSH_TOO_EARLY …)помилка в переписціщо зробив не так менеджер у розмові, яка згасла; для навчання, без пошуку винних
appointment rateчастка теплих відповідей, що дійшли до зустрічінорма 25–35%; нижче означає, що розмови губляться після першої відповіді
ghost, ghostingлюдина зникла після відповідівідповіла тепло, а далі мовчить; часто через помилку в другому повідомленні
noise vs opportunitiesшум проти реальних можливостейякщо 40%+ відповідей не про угоду (не той контакт, не той регіон), проблема в базі контактів; тексти тут ні до чого
Objection Playbook, gold-standard templatesзбірка найкращих відповідей на запереченнявзяті з ваших же вдалих відповідей і прив'язані до причини відмови
SDR, repменеджер першого контактулюдина, яка веде переписку від першої відповіді до зустрічі
working engine / dead engineканал, що приносить зустрічі · канал, що не працюєпоказує, куди переносити бюджет і час
positive reply rateчастка позитивних відповідейскільки з тих, кому написали, відповіли з інтересом, а не «відпишіть мене»
reply rateчастка відповідейскільки людей з тих, кому написали, відповіли.
hook / free offer, lead magnetбезкоштовний вхідаудит, розрахунок втрат або розбір, що показує проблему і веде до розмови
decision makerОПР (особа, що приймає рішення)той, хто підписує: власник, операційний директор, керівник напряму
<!-- glossary:end -->

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/victor-shulga/outbound-engine-skills/reply-audit">View reply-audit on skillZs</a>