post-call-followup

post-call-followup is a skill for Claude Code from Arise-AI-Group/lead-management-plugin. It costs 0 tokens per session (1,865 once invoked), scanned A, original, Apache-2.0.

A post-meeting assistant that reads call notes or a transcript and identifies important sales details, such as customer problems, objections, next steps, and budget signals.

In plain words
What is it for?
Use it to draft a personalized follow-up email, summarize the call for your team, and recommend a sales-pipeline stage change. With connected tools, it can also retrieve transcripts, update a customer record, route the draft for review, and send it.
Why use it?
It removes the need to manually turn a sales call into an email, internal summary, and suggested customer-record update.

Skill for Claude Code

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

Part of the lead-management plugin — 9 skills shipped together

Good fit Use it to draft a personalized follow-up email, summarize the call for your team, and recommend a sales-pipeline stage change. With connected tools, it can also retrieve transcripts, update a customer record, route the draft for review, and send it.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/arise-ai-group/lead-management-plugin/post-call-followup
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 Arise-AI-Group/lead-management-plugin --skill post-call-followup
Clone the repo
git clone --depth 1 https://github.com/Arise-AI-Group/lead-management-plugin

Made for: Claude Code.

Or install lead-management, the plugin that ships this one along with the rest of its 9 skills.

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 post-call-followup

README.md
[![agentmods](https://agentmods.dev/badge/skills/arise-ai-group/lead-management-plugin/post-call-followup/github.svg)](https://agentmods.dev/skills/arise-ai-group/lead-management-plugin/post-call-followup)
Your own site
<a href="https://agentmods.dev/skills/arise-ai-group/lead-management-plugin/post-call-followup"><img src="https://agentmods.dev/badge/skills/arise-ai-group/lead-management-plugin/post-call-followup/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 post-call-followup

Your own site · 80×15
<a href="https://agentmods.dev/skills/arise-ai-group/lead-management-plugin/post-call-followup"><img src="https://agentmods.dev/badge/skills/arise-ai-group/lead-management-plugin/post-call-followup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,865 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.
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.00000 $0.01865
Opus 5 $0.00000 $0.00932
Sonnet 5 $0.00000 $0.00373
Haiku 4.5 $0.00000 $0.00186

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

Security

Grade A, and why

post-call-followup 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 12d 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.

lead-management/skills/post-call-followup/SKILL.md · 238 lines

How it starts

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

Post-Call Follow-Up

Process call notes or transcripts to extract key insights, draft a personalized follow-up email, and update your pipeline — all within minutes of hanging up.

How It Works

┌─────────────────────────────────────────────────────────────────┐
│                   POST-CALL FOLLOW-UP                            │
├─────────────────────────────────────────────────────────────────┤
│  STANDALONE (always works)                                       │
│  ✓ Paste call notes, transcript, or describe what happened      │
│  ✓ Extract: pain points, objections, next steps, budget signals │
│  ✓ Draft personalized follow-up email (150-250 words)           │
│  ✓ Generate internal team summary with deal impact              │
│  ✓ Recommend pipeline stage update                              │
├─────────────────────────────────────────────────────────────────┤
│  SUPERCHARGED (when you connect your tools)                      │
│  + Transcripts: Pull recording automatically from Fireflies/Gong│
│  + CRM: Update lead record, log activity, advance pipeline      │
│  + Chat: Route follow-up for team review with approve/send      │
│  + Email: Send approved follow-up directly                      │
└─────────────────────────────────────────────────────────────────┘

Getting Started

Option 1: Paste a transcript If you have a full transcript from Fireflies, Gong, Zoom, or any other tool, paste it. I'll extract everything.

Option 2: Paste your notes Bullet points, rough notes, stream of consciousness — whatever you have. I'll structure it.

Option 3: Describe the call Tell me what happened: "Had a discovery call with Acme Corp. Met with their VP Ops. They're drowning in manual data entry, team of 30, looking to automate onboarding. Budget is ~$5k/month. Want to move fast."

Helpful context:

  • Who attended (names and titles)
  • What type of call (discovery, demo, follow-up, proposal review)
  • What you want the follow-up to accomplish

Read the full file on GitHub · 238 lines

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. 12d ago First seen · 238 lines · 0 tokens per session scan A 9fe8580aae68

Subscribe to this mod's changes

post-call-followup is a skill published in the GitHub repository Arise-AI-Group/lead-management-plugin (7 stars, last pushed 7mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,865 tokens. 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-31.

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

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 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