voice-post-call

Ingest voice-call transcripts into brain pages with summaries and audio links.

174|144|Updated Jun 10, 2026
One-click install
npx skills add https://github.com/inbrainfun/inbrain --skill voice-post-call-inbrainfun
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: voice-post-call
Source: https://github.com/inbrainfun/inbrain/tree/main/recipes/agent-voice/skills/voice-post-call
Command: npx skills add https://github.com/inbrainfun/inbrain --skill voice-post-call-inbrainfun

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Voice-call transcripts are often scattered across tools and lack a canonical record. This skill ingests transcripts, generates a structured brain page with key details, and creates a concise summary for quick decision-making, while archiving the audio for later review.

Core Features & Use Cases

  • Automated brain-page creation: Convert transcripts into a rich brain page with structured fields and cross-links to entities mentioned.
  • Automated summarization: Produce a concise 3-5 sentence summary suitable for operator reviews and decision logs.
  • Audio archiving & cross-linking: Archive the original audio file and link it to the brain page; automatically update related timelines and people/companies pages.

Quick Start

Invoke the post-call pipeline to convert transcripts into a brain page with an attached summary and link the associated audio.

Frequently Asked Questions about voice-post-call

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

FAQPage Schema
How do I turn voice call transcripts into structured summaries and pages?

Voice call transcripts are ingested to automatically generate a structured brain page with cross-linked entities and a concise summary for quick decision-making. The workflow processes live or end-of-call transcripts and archives the original audio for later review.

What is the best way to archive voice call audio and transcripts together?

The best way to archive voice call audio and transcripts is using a post-call pipeline that writes canonical records and links audio files to structured brain pages. This ensures idempotent repeated invocations and preserves privacy by not exposing raw transcripts beyond the brain page.

Can I apply this to live voice calls or only end-of-call ingestion?

You can apply this workflow to both live voice calls and end-of-call ingestion. The pipeline processes transcripts in real-time or post-call, creating brain pages and summaries with entity cross-linking regardless of the ingestion method.

Does voice post-call processing expose raw transcripts or compromise privacy?

Voice post-call processing preserves user privacy by not exposing raw transcripts beyond the generated brain page. The workflow stores canonical records with audio references under meetings/ or voice-calls/ directories, maintaining traceability without compromising sensitive transcript data.

How do I ensure repeated voice call ingestion won't create duplicate records?

The voice call ingestion workflow is idempotent on repeated invocations, meaning repeated processing of the same call will not create duplicate records. It writes canonical records following established conventions, ensuring consistent archival and review across multiple pipeline triggers.