Auto-generate action items from meeting recordings and video with Gemini
Upload a 60-minute meeting recording and Gemini surfaces every action item, owner, and timestamp.
You are an executive assistant analyzing a {{duration}}-minute meeting recording I've uploaded. The meeting was about: {{topic}}.
Produce:
## 1. Action items (table)
| Owner | Action | Deadline | Quote | Timestamp |
Only include items where someone clearly committed (not vague "we should..."). If a deadline wasn't mentioned, write "—". Quote should be 5-15 words verbatim. Timestamp in mm:ss.
## 2. Decisions made (bullets)
Things explicitly agreed on during the meeting (different from action items — these are conclusions, not next steps).
## 3. Open questions / unresolved (bullets)
Things discussed but not resolved. These usually need follow-up.
## 4. Vibe check (1 sentence)
Was the meeting productive / contentious / focused / wandering? Honest assessment.
Rules: don't invent names. If you're unsure who said something, write "unclear speaker". Don't paraphrase quotes — copy verbatim.Swap the variables inside the [ ] brackets for your own content, then paste into Gemini 2.5 Pro.
See what this prompt actually produces without leaving the site (live AI run, 1 credit).
Manually writing up meeting notes after a PM or leadership meeting is low-ROI work. Gemini ingests the recording directly and returns action items (with cited timestamps) plus a vibe check.
4 段：action items table / decisions / open questions / vibe check，全有 timestamp 引言
A description of the intended result. Check this entry's testing notes and try the prompt with your own inputs.
[duration]會議長度（30 / 60 / 90 / 120 分鐘）
[topic]會議主題（如：Q2 product roadmap review / customer escalation triage / engineering planning）
填下面的欄位，上方 prompt 會即時替換 [方括號] 內容。填好後按「複製組好的 prompt」直接丟進工具。
You are an executive assistant analyzing a {{duration}}-minute meeting recording I've uploaded. The meeting was about: {{topic}}.
Produce:
## 1. Action items (table)
| Owner | Action | Deadline | Quote | Timestamp |
Only include items where someone clearly committed (not vague "we should..."). If a deadline wasn't mentioned, write "—". Quote should be 5-15 words verbatim. Timestamp in mm:ss.
## 2. Decisions made (bullets)
Things explicitly agreed on during the meeting (different from action items — these are conclusions, not next steps).
## 3. Open questions / unresolved (bullets)
Things discussed but not resolved. These usually need follow-up.
## 4. Vibe check (1 sentence)
Was the meeting productive / contentious / focused / wandering? Honest assessment.
Rules: don't invent names. If you're unsure who said something, write "unclear speaker". Don't paraphrase quotes — copy verbatim.Suno Engineer's Mindset: 4 Steps to a Song That Doesn't Sound Like AI
A studio engineer's breakdown of Suno's fatal weaknesses (fried vocals, high-frequency artifacts), plus a 4-step DAW workflow and a Suno Studio cleanup prompt.
5 Claude Weekly Workflows That Stuck After 6 Months
Proposal generator / meeting processor / content repurposer / Friday review / shutdown reset — out of 40 I tried, only these 5 survived, each saving 30+ minutes per run.
7 Cross-Model A/B-Tested Prompt Techniques (Not Vibes)
Written after six months of A/B testing 200+ prompts on Claude, GPT-4, and Gemini with human raters. Covers persona + constraint stacking, anti-examples, role-reversal QA, cognitive scaffolds, emotional priming, uncertainty CoT, and steelman-first.
5 trust-checking one-liner prompts (no role-play)
After a year of role-play system prompts and 14-step frameworks, here's the takeaway: the thing that actually moved the needle on quality was 5 one-line prompts. No roles, no markdown, no "you are an expert."