voice-post-call

Processes voice call transcripts into brain pages with summaries, audio archives, and entity cross-links.

Updated Aug 17, 2026
One-click install
npx skills add https://github.com/AMC-JTC/gbrain-1 --skill voice-post-call-amc-jtc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: voice-post-call
Source: https://github.com/AMC-JTC/gbrain-1/tree/main/recipes/agent-voice/skills/voice-post-call
Command: npx skills add https://github.com/AMC-JTC/gbrain-1 --skill voice-post-call-amc-jtc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After a voice call ends, the transcript, audio, and key decisions are easily lost unless someone manually writes them up. This Skill turns every call into a structured brain page with a summary, verbatim transcript, audio link, and entity cross-links, then posts the summary to the operator's messaging surface. ## Core Features & Use Cases - Six-step post-call pipeline: captures audio via MediaRecorder, transcribes with Whisper, summarizes with an LLM, writes a brain page under meetings/ or voice-calls/, cross-links mentioned people and companies, and posts the summary to Telegram, Slack, or Discord. - Idempotent dual firing paths: supports both a persona-initiated mid-call log_to_brain tool call and a call-end handler, where the second invocation updates rather than duplicates the page. - Use Case: After ending a 2-minute voice call with the Venus persona, the Skill produces meetings/2026-05-17-call-venus.md containing frontmatter, a 3-5 sentence summary, the verbatim block-quoted transcript, the audio file link, and timeline entries on each mentioned person's page. ## Quick Start After the call ends, ask the agent to summarize the call and file the transcript into the brain with links to everyone mentioned.

Frequently Asked Questions about voice-post-call

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I save a voice call transcript to my knowledge base?

Run the post-call pipeline after the session ends: it transcribes the captured audio with Whisper, generates a 3-5 sentence summary, and writes a brain page under meetings/ or voice-calls/ containing the verbatim transcript, summary, and audio link.

What happens if the voice persona forgets to log the call mid-session?

The mid-call log_to_brain tool is opt-in via the operator's tools-allowlist.local.json. The shipped server has no automatic call-end handler, so you must implement one in your host repo to guarantee every call gets processed when the tool never fires.

Does the pipeline create duplicate pages if both firing paths run?

No. The pipeline is idempotent: if the persona-initiated tool call and the call-end handler both fire, the second invocation detects the existing brain page and updates it instead of creating a duplicate.

Can the call summary be posted to Slack or Telegram?

Yes. The final pipeline step sends the summary to whichever messaging surface is wired in the host repo's .env file, including Telegram, Slack, or Discord. The brain page is always written first since it is the canonical record.

Why are transcripts stored verbatim instead of paraphrased?

The verbatim transcript is the primary signal, while the summary is only the agent's interpretation. Paraphrasing the transcript is listed as an anti-pattern because exact wording matters more than a cleaned-up version.