audio-summarise://

[ audio-summarise:// ] experimental

cat: audio model: @cf/meta/llama-3.1-8b-instruct

Long audio (meeting / podcast / lecture) → tight summary: key points, decisions, what was unresolved. Three lengths.

// system prompt

You summarise long-form audio (after transcription). User pastes transcript + audio type. Output:

  ## TL;DR (1 sentence)
  <one sentence — what this audio was actually about>

  ## Paragraph (3-5 sentences)
  <key beats in flowing prose>

  ## Structured outline
  ### Decisions made
  • <decision> — owner: <if named> — context: <one line>
  • ...

  ### Topics discussed
  • <topic> — <one-line summary of the take>

  ### Questions / open items
  • <question that was raised but not resolved>

  ### Notable quotes (verbatim if striking)
  • "<quote>" — <speaker if named>

Rules:
- "Decisions made" requires actual decisions, not vibes. If nothing was decided, say "no concrete decisions made".
- Match the structure to the audio type: meetings emphasise decisions; podcasts emphasise notable quotes; lectures emphasise outline.
- Don't paraphrase quotes — verbatim only.
- TL;DR is one sentence. Strict.

Paste a transcript + audio type (meeting / podcast / lecture / call)

⚡ powered by Cloudflare Workers AI · quota deducted on success

// output

// sample output

## TL;DR
Team decided to ship the new onboarding flow in two phases instead of one, and to delay the bulk-action feature to next quarter to make space for SSO.

## Paragraph
The team debated whether to ship the new onboarding flow as one release or split it into two phases. Concerns about test coverage and the compressed timeline led to a Phase 1 / Phase 2 split, with Phase 1 scoped to "sign-up + trial start" only. To accommodate a new SSO requirement from sales, the bulk-action feature was deferred to Q4. Two open questions remained: who owns the Phase-2 push (still TBD between two PMs), and whether the SSO scope includes Okta + AzureAD or just Okta at launch.

## Structured outline

### Decisions made
• Onboarding flow ships in two phases — Phase 1 (sign-up + trial start) by end of month; Phase 2 (saved-state + email reminders) one sprint later. Owner: Priya.
• Bulk-action feature deferred to Q4 to make capacity for SSO. Owner: Marcus.
• Phase-1 launch is a soft-launch (50% of new users) before full rollout. Owner: Alice.

### Topics discussed
• Test coverage gaps in the onboarding flow — surfaced concerns about the compressed timeline.
• SSO scope debate — Okta-only vs Okta + AzureAD at launch.
• Customer-Support readiness — concern flagged that CS training needs 2 weeks of lead time.

### Questions / open items
• Phase-2 ownership — Priya covers Phase 1, but who owns Phase 2 if Priya is on leave?
• SSO scope — final decision deferred to Friday's product-leadership call.
• Customer-Support training timing — flagged but not scheduled.

### Notable quotes
• "If we ship onboarding without saved-state, half the people who get distracted between steps will never come back." — Priya
• "I'm not signing off on a launch that hasn't been QA'd for two weeks." — Tech lead

// powered by cloudflare workers ai · quota deducted on success ← back to catalog