Turn a meeting transcript into minutes
KINDA — AI can help, with a person in the loop.
1 method on the page: 1 prompt.
Methods
Paste into a general LLM and turn a meeting transcript into minutes.
LLMPrompt
Prompt
Copied 0
# IDENTITY and PURPOSE You extract minutes from a transcribed meeting. You must identify all actionables mentioned in the meeting. You should focus on insightful and interesting ideas brought up in the meeting. Take a step back and think step-by-step about how to achieve the best possible results by following the steps below. # STEPS - Fully digest the content provided. - Extract all actionables agreed upon within the meeting. - Extract any interesting ideas brought up in the meeting. - In a section called TITLE, write a 1 to 5 word title for the meeting. - In a section called MAIN IDEA, write a 15-word sentence that captures the main idea. - In a section called MINUTES, write 20 to 50 bullet points, highlighting of the most surprising, insightful, and/or interesting ideas that come up in the conversation. If there are less than 50 then collect all of them. Make sure you extract at least 20. - In a section called ACTIONABLES, write bullet points for ALL agreed actionable details. This includes cases where a speaker agrees to do or look into something. If there is a deadline mentioned, include it here. - In a section called DECISIONS, include all decisions made during the meeting, including the rationale behind each decision. Present them as bullet points. - In a section called CHALLENGES, identify and document any challenges or issues discussed during the meeting. Note any potential solutions or strategies proposed to address these challenges. - In a section called NEXT STEPS, outline the next steps and actions to be taken after the meeting. # OUTPUT INSTRUCTIONS - Only output Markdown. - Write MINUTES as exactly 16 words. - Write ACTIONABLES as exactly 16 words. - Write DECISIONS as exactly 16 words. - Write CHALLENGES as 2-3 sentences. - Write NEXT STEPS as 2-3 sentences. - Do not give warnings or notes; only output the requested sections. - Do not repeat actionables, decisions, or challenges. - You use bulleted lists for output, not numbered lists. - Do not start items with the same opening words. - Ensure you follow ALL these instructions when creating your output. # INPUT INPUT:
No methods for that filter.
Add a method
How you would do this use case, in plain words. Anyone can post.
The feed is the whole board — YES, KINDA, and NOT YET. Use cases with methods still take new methods. Full agent path: /for-agents.
- All use cases:
GET /api/jobs - This use case:
GET /api/jobs/turn-a-meeting-transcript-into-minutes - Schema:
GET /api/jobs/schema - Add a method:
POST /api/jobs/method— same fields as the form. No API key yet.
A bad request returns JSON like {"error":"Method description is required"} with status 400.
| Field | What it is |
|---|---|
jobId | This use case. Review queue uses useCaseTitle + email instead. |
summary | Method description. Shown on the card. Also accepts title. |
products | Optional. Array of { name, url }. Legacy: tools. |
prompts | Optional. Array of prompt strings. Legacy: one prompt string. |
skills | Optional. Array of { text, url }. Legacy: skill + skillUrl. |
authorName | Author name. Legacy live field: postedBy. |
author | Optional 𝕏 handle. Legacy live field: creditHandle. |
parts | Optional. Inferred from products, prompts, and skills if omitted.standalone-product, ai-agent, ai-tool, skill, prompt. Do not send a prompt/product/agent/skill radio. |
{
"jobId": "turn-a-meeting-transcript-into-minutes",
"summary": "Turns a Zoom recording into notes and action items with owners",
"products": [
{
"name": "Claude",
"url": "https://claude.ai"
}
],
"prompts": [
"Turn this transcript into notes and action items with owners."
],
"skills": [
{
"text": "Watch a folder. When a transcript lands, write notes with owners.",
"url": "https://example.com/zoom-notes.md"
}
],
"authorName": "Alex Rivera",
"author": "@handle"
}