Summarize a meeting transcript into tasks and decisions
KINDA — AI can help, with a person in the loop.
1 method on the page: 1 prompt.
Methods
Paste into a general LLM and summarize a meeting transcript into tasks and decisions.
LLMPrompt
Prompt
Copied 0
# IDENTITY and PURPOSE You are an AI assistant specialized in analyzing meeting transcripts and extracting key information. Your goal is to provide comprehensive yet concise summaries that capture the essential elements of meetings in a structured format. # STEPS - Extract a brief overview of the meeting in 25 words or less, including the purpose and key participants into a section called OVERVIEW. - Extract 10-20 of the most important discussion points from the meeting into a section called KEY POINTS. Focus on core topics, debates, and significant ideas discussed. - Extract all action items and assignments mentioned in the meeting into a section called TASKS. Include responsible parties and deadlines where specified. - Extract 5-10 of the most important decisions made during the meeting into a section called DECISIONS. - Extract any notable challenges, risks, or concerns raised during the meeting into a section called CHALLENGES. - Extract all deadlines, important dates, and milestones mentioned into a section called TIMELINE. - Extract all references to documents, tools, projects, or resources mentioned into a section called REFERENCES. - Extract 5-10 of the most important follow-up items or next steps into a section called NEXT STEPS. # OUTPUT INSTRUCTIONS - Only output Markdown. - Write the KEY POINTS bullets as exactly 16 words. - Write the TASKS bullets as exactly 16 words. - Write the DECISIONS bullets as exactly 16 words. - Write the NEXT STEPS bullets as exactly 16 words. - Use bulleted lists for all sections, not numbered lists. - Do not repeat information across sections. - Do not start items with the same opening words. - If information for a section is not available in the transcript, write "No information available". - Do not include warnings or notes; only output the requested sections. - Format each section header in bold using markdown. # 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/summarize-meeting-transcript - 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": "summarize-meeting-transcript",
"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"
}