agentleFS
nthnclrknthnclrk/enablement-skills/skills/call-insights-to-objections/SKILL.md

call-insights-to-objections

Skill14 starsChanged 8 months agoMITView on GitHub

Analyze a defined set of sales calls or notes and produce an evidence-backed objection brief by segment, persona, or stage. Use for recurring pushback, proof gaps, and message patterns across multiple conversations. Use call-review-coach for one-call coaching, win-loss-synthesis for outcome-cause research, and objection-library-builder for the governed response asset.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 6 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask only for the inputs that change the clusters:

    line 18
  2. Distinctive:

    Do not force shared-context setup for a self-contained source set.

    line 25
  3. Distinctive:

    Read references/objection-coding-framework.md before you code, count, or assign confidence.

    line 29
  4. Distinctive:

    Check concentration and privacy.

    line 47
  5. Distinctive:

    Do not write findings back to a system or publish messaging without explicit approval.

    line 50
  6. Very specific:

    Do not produce the governed objection library.

    line 62
  7. Distinctive:

    No invented outcomes, win rates, or approved responses.

    line 69

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Call insights to objections

Identify recurring buyer concerns in a defined call set and recommend what the team should investigate or change.

Fails. "Approved response: 'Our implementation is proven and low-risk across similar rollouts.'"

Passes. "Implementation capacity appeared in 6 of 18 usable discovery calls across 4 accounts. Buyer language: 'we do not have anyone to own the rollout.' Observed consequence: extra validation, not a hard stop. Route the response asset to objection-library-builder."

One recorded call is call-review-coach. Why deals were won or lost is win-loss-synthesis.

Inputs

Ask only for the inputs that change the clusters:

  1. The decision this brief must inform
  2. Time window, call types, segments, personas, and available call count
  3. Source format: transcript, notes, or mixed, plus which metadata exists
  4. Whether the audience needs a diagnostic brief, an action backlog, or inputs for a later library

Do not force shared-context setup for a self-contained source set. Do not invent outcomes, quotes, or usage.

Supporting material

Read references/objection-coding-framework.md before you code, count, or assign confidence. Read references/source-system-guide.md when the evidence comes from a call platform, shared notes, or a message export.

Procedure

  1. Frame the set. Decision question, inclusion rules, window, slices, and unit of analysis. Done when a reviewer can see which conversations are in and which are out.
  2. Register every eligible conversation. Stable source ID and the metadata needed to trace a finding. Unusable or missing content is missing coverage, not an objection-free call.
  3. Code without collapsing too early. Explicit objection, implied concern, buyer question, and seller interpretation stay separate. Tag type, buyer language, response, observed consequence, and a root-cause hypothesis.
  4. Count once per conversation for prevalence. Extra mentions are intensity, not a bigger sample. Show the eligible-call denominator and unique-account breadth on every compared slice.
  5. Cluster the same concern, not the same wording. Merge only when the underlying buyer issue is the same. Keep distinct concerns separate even when the later response would overlap.
  6. Score impact from what happened on the call. Blocking, material friction, open concern, or unknown. Deal impact and root cause stay hypotheses unless the evidence establishes them.
  7. Recommend a response to the underlying concern. Distinguish a message the buyer misunderstood from a real capability, capacity, or commercial constraint. Assign message clarification, proof, product feedback, seller practice, process repair, or research accordingly. Each recommendation needs an owner and a way to check whether it helped. Draft language remains unapproved.
  8. Check concentration and privacy. One rep, account, or team must not silently drive the conclusion. Redact what a broad audience should not see.

Do not write findings back to a system or publish messaging without explicit approval.

What to return

Return the findings needed for the stated decision. For a full analysis, include:

  • Scope and coverage: question, inclusion rules, eligible vs usable calls, account and rep breadth, metadata gaps
  • Objection register: theme, buyer wording, count and denominator, slices, observed consequence, confidence, source IDs
  • Evidence pack: short redacted excerpts or labeled paraphrases
  • Action backlog: response type, owner, validation signal — not approved copy
  • Blind spots: missing coverage, conflicts, and what would change the ranking

Do not produce the governed objection library. That is objection-library-builder.

Quality bar

  • Repeated concerns within one account stay account-specific. Report independent-account breadth before calling a concern recurring across the market.
  • Buyer language, analyst interpretation, and recommendation are not the same sentence.
  • Isolated signals stay visible without being promoted to themes.
  • No invented outcomes, win rates, or approved responses.
  • A reader can trace every material theme to source IDs.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.