ctx-transcript

Convert stakeholder transcripts into validated meeting artifacts with metadata and people profiles.

4|Updated Apr 26, 2026
One-click install
npx skills add https://github.com/simonconway1979/os-intelligence --skill ctx-transcript
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ctx-transcript
Source: https://github.com/simonconway1979/os-intelligence/tree/main/.claude/skills/ctx-transcript
Command: npx skills add https://github.com/simonconway1979/os-intelligence --skill ctx-transcript

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Context for AI-native product work is hard to keep consistent: every new session starts cold, and stakeholders’ intent gets scattered across raw notes. This skill converts a confirmed stakeholder meeting transcript into structured, validated meeting artifacts that can be reused for future decisions.

Core Features & Use Cases

  • Transcript capture (raw + verbatim preservation): Saves the transcript exactly as provided into a project meeting folder for auditability.
  • Context synthesis (structured summary + metadata): Produces a validated synthesis.md with topic, themes, sentiment, commitments, and cross-referenced tags.
  • Grounded validation (interpretation checking): Verifies interpretive statements against the raw transcript, grounding them or softening/removing unsupported claims.
  • Shareable meeting notes: Generates a warm, professional shareable.md that excludes sensitive interpretive layers.
  • People file upkeep: Creates or updates root and project-level people profiles so the project “memory” stays current.

Quick Start

Run /ctx-transcript, confirm the project and inputs, then paste or provide a transcript file path to generate synthesis, validation, metadata, and shareable notes.

Frequently Asked Questions about ctx-transcript

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

FAQPage Schema
How do I turn meeting transcripts into structured product documentation?

Meeting transcript processing converts raw stakeholder discussions into structured artifacts, capturing stakeholder intent, synthesizing themes, and validating interpretive claims to produce shareable notes for product context reuse.

What is the best way to validate interpretive claims from stakeholder meeting notes?

Validating interpretive claims from stakeholder meeting notes requires cross-referencing synthesized statements against the verbatim raw transcript, grounding supported claims with evidence, and softening or removing unsupported interpretations.

How do I generate shareable meeting notes that exclude sensitive internal interpretations?

Generating shareable meeting notes that exclude sensitive interpretations involves separating the validated synthesis from a professional, warm summary document, ensuring sensitive interpretive layers remain internal while sharing only safe conclusions.

Can I use transcript processing to automatically update people profiles tagged to my project?

Yes, transcript processing can automatically update people profiles by creating or updating root and project-level people profiles tagged to the project, ensuring the project memory stays current with stakeholder interactions.

Do I need to manually save the raw transcript for auditability when synthesizing meeting context?

You do not need to manually save the raw transcript for auditability; the process saves the transcript exactly as provided into a project meeting folder, preserving verbatim raw text alongside the structured synthesis.

What metadata is included when converting stakeholder transcripts into structured meeting artifacts?

Converting stakeholder transcripts into structured meeting artifacts includes YAML-frontmatter metadata for discovery, alongside topic, themes, sentiment, commitments, and cross-referenced tags within the validated synthesis output.