call-analyzer

call-analyzer is a skill for Claude Code from octavehq/lfgtm. It costs 58 tokens per session (2,275 once invoked), scanned A, original, MIT.

A conversation review tool for email threads, call transcripts, and other sales conversations. It checks how well the message connects with the buyer, follows the intended story, and distinguishes the offering from competitors.

In plain words
What is it for?
Reviewing calls, emails, or chats; assessing sales messaging; finding competitive gaps; and preparing suggested improvements or follow-ups.
Why use it?
It helps identify what worked, what weakened the message, and where the conversation could improve. It can turn that review into practical changes and follow-up drafts.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the octave plugin — 29 skills, 7 agents shipped together

Good fit Reviewing calls, emails, or chats; assessing sales messaging; finding competitive gaps; and preparing suggested improvements or follow-ups.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/octavehq/lfgtm/call-analyzer
Install

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.

Any agent
npx skills add octavehq/lfgtm --skill call-analyzer
Clone the repo
git clone --depth 1 https://github.com/octavehq/lfgtm

Made for: Claude Code.

Or install octave, the plugin that ships this one along with the rest of its 29 skills, 7 agents.

Wrote 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.

agentmods badge for call-analyzer

README.md
[![agentmods](https://agentmods.dev/badge/skills/octavehq/lfgtm/call-analyzer/github.svg)](https://agentmods.dev/skills/octavehq/lfgtm/call-analyzer)
Your own site
<a href="https://agentmods.dev/skills/octavehq/lfgtm/call-analyzer"><img src="https://agentmods.dev/badge/skills/octavehq/lfgtm/call-analyzer/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.

agentmods 80×15 button for call-analyzer

Your own site · 80×15
<a href="https://agentmods.dev/skills/octavehq/lfgtm/call-analyzer"><img src="https://agentmods.dev/badge/skills/octavehq/lfgtm/call-analyzer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 58 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,275 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00058 $0.02275
Opus 5 $0.00029 $0.01137
Sonnet 5 $0.00012 $0.00455
Haiku 4.5 $0.00006 $0.00228

Measured 10d ago against content hash 75afe7d7379e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

call-analyzer 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 10d 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.

skills/call-analyzer/SKILL.md · 325 lines

How it starts

The opening of the file, as written. The whole thing — 325 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/octave:call-analyzer - Conversation Analysis

Analyze email threads, call transcripts, and sales conversations against your Octave library. Evaluates messaging resonance, Motion ICP narrative adherence, and competitive differentiation. Provides actionable insights, suggested improvements, and draft follow-ups.

Principles

Follow these standards during generation. Read each before producing output.

Content and language:

Presentation:

  • Presentation principles — use for any visual output (HTML, dashboards, tables); text follows the editorial rules above

Octave data:

  • Octave value — prioritize grounded workspace data over generic AI content

Usage

/octave:call-analyzer [--type email|call|chat]

Examples

/octave:call-analyzer                              # Interactive - paste content
/octave:call-analyzer --type email                 # Analyze email thread
/octave:call-analyzer --type call                  # Analyze call transcript

Instructions

When the user runs /octave:call-analyzer:

Step 1: Get Content to Analyze

What would you like me to analyze?

1. Paste an email thread
2. Paste a call transcript
3. Paste a chat/message thread
4. Provide a file path

(Paste content below or tell me the file path)

Accept pasted content or read from file. Content can be:

  • Email thread (with headers or without)
  • Call transcript (with speaker labels or without)
  • Chat/messaging thread
  • Meeting notes

Step 2: Parse and Structure the Content

For Email: Extract:

  • Participants (internal vs external)
  • Thread direction (outbound, inbound, back-and-forth)
  • Key messages from each party
  • Current status (awaiting response, ended, etc.)

Read the full file on GitHub · 325 lines

Files

What ships with it

1 file 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.

Changes

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.

  1. 10d ago First seen · 325 lines · 58 tokens per session scan A 75afe7d7379e

Subscribe to this mod's changes

call-analyzer is a skill published in the GitHub repository octavehq/lfgtm (11 stars, last pushed 20d ago), licensed MIT. It adds 58 tokens to every session and 2,275 once invoked, about $0.0003 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-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens