{
  "schemaVersion": "1.0",
  "item": {
    "slug": "ai-meeting-notes",
    "name": "AI Meeting Notes w/ Action Items + To-Do List Tracker",
    "source": "tencent",
    "type": "skill",
    "category": "开发工具",
    "sourceUrl": "https://clawhub.ai/jeffjhunter/ai-meeting-notes",
    "canonicalUrl": "https://clawhub.ai/jeffjhunter/ai-meeting-notes",
    "targetPlatform": "OpenClaw"
  },
  "install": {
    "downloadMode": "redirect",
    "downloadUrl": "/downloads/ai-meeting-notes",
    "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=ai-meeting-notes",
    "sourcePlatform": "tencent",
    "targetPlatform": "OpenClaw",
    "installMethod": "Manual import",
    "extraction": "Extract archive",
    "prerequisites": [
      "OpenClaw"
    ],
    "packageFormat": "ZIP package",
    "includedAssets": [
      "assets/PREFERENCES-template.md",
      "assets/TODO-template.md",
      "examples/input-messy-notes.md",
      "examples/input-transcript.md",
      "examples/output-example.md",
      "SKILL.md"
    ],
    "primaryDoc": "SKILL.md",
    "quickSetup": [
      "Download the package from Yavira.",
      "Extract the archive and review SKILL.md first.",
      "Import or place the package into your OpenClaw setup."
    ],
    "agentAssist": {
      "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.",
      "steps": [
        "Download the package from Yavira.",
        "Extract it into a folder your agent can access.",
        "Paste one of the prompts below and point your agent at the extracted folder."
      ],
      "prompts": [
        {
          "label": "New install",
          "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete."
        },
        {
          "label": "Upgrade existing",
          "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run."
        }
      ]
    },
    "sourceHealth": {
      "source": "tencent",
      "slug": "ai-meeting-notes",
      "status": "healthy",
      "reason": "direct_download_ok",
      "recommendedAction": "download",
      "checkedAt": "2026-04-29T03:31:00.759Z",
      "expiresAt": "2026-05-06T03:31:00.759Z",
      "httpStatus": 200,
      "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=ai-meeting-notes",
      "contentType": "application/zip",
      "probeMethod": "head",
      "details": {
        "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=ai-meeting-notes",
        "contentDisposition": "attachment; filename=\"ai-meeting-notes-1.0.3.zip\"",
        "redirectLocation": null,
        "bodySnippet": null,
        "slug": "ai-meeting-notes"
      },
      "scope": "item",
      "summary": "Item download looks usable.",
      "detail": "Yavira can redirect you to the upstream package for this item.",
      "primaryActionLabel": "Download for OpenClaw",
      "primaryActionHref": "/downloads/ai-meeting-notes"
    },
    "validation": {
      "installChecklist": [
        "Use the Yavira download entry.",
        "Review SKILL.md after the package is downloaded.",
        "Confirm the extracted package contains the expected setup assets."
      ],
      "postInstallChecks": [
        "Confirm the extracted package includes the expected docs or setup files.",
        "Validate the skill or prompts are available in your target agent workspace.",
        "Capture any manual follow-up steps the agent could not complete."
      ]
    },
    "downloadPageUrl": "https://openagent3.xyz/downloads/ai-meeting-notes",
    "agentPageUrl": "https://openagent3.xyz/skills/ai-meeting-notes/agent",
    "manifestUrl": "https://openagent3.xyz/skills/ai-meeting-notes/agent.json",
    "briefUrl": "https://openagent3.xyz/skills/ai-meeting-notes/agent.md"
  },
  "agentAssist": {
    "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.",
    "steps": [
      "Download the package from Yavira.",
      "Extract it into a folder your agent can access.",
      "Paste one of the prompts below and point your agent at the extracted folder."
    ],
    "prompts": [
      {
        "label": "New install",
        "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete."
      },
      {
        "label": "Upgrade existing",
        "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run."
      }
    ]
  },
  "documentation": {
    "source": "clawhub",
    "primaryDoc": "SKILL.md",
    "sections": [
      {
        "title": "📋 AI Meeting Notes",
        "body": "Messy notes → Clear action items. Instantly.\n\nPaste any meeting notes, transcript, or text. Get a clean summary with action items, owners, and deadlines.\n\nNo bot. No subscription. No setup."
      },
      {
        "title": "⚠️ CRITICAL: RESPONSE FORMAT (READ FIRST)",
        "body": "When extracting meeting notes, you MUST respond with ALL of the following in ONE SINGLE MESSAGE:\n\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n📋 [MEETING TITLE] — [YYYY-MM-DD]\nDuration: [X min] | Attendees: [Names]\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n\nSUMMARY\n[2-3 sentence overview]\n\n⚡ ACTION ITEMS ([X] of [Total])\n1. [ ] @Owner: Task — Deadline\n2. [ ] @Owner: Task — Deadline\n3. [ ] @Owner: Task — Deadline\n4. [ ] @Owner: Task — Deadline\n5. [ ] @Owner: Task — Deadline\n[Show up to 10, note \"(+X more in file)\" if more exist]\n\n✅ KEY DECISIONS\n• Decision 1\n• Decision 2\n\n📎 Saved: meeting-notes/YYYY-MM-DD_topic-name.md\n\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\nAdd to your to-do list?\n• \"all\" — Add all [X] items\n• \"1,2,4\" — Add specific items\n• \"none\" — Skip"
      },
      {
        "title": "MANDATORY RULES",
        "body": "RuleRequirementONE responseNEVER split into multiple messages. Display + file + to-do prompt in SINGLE response.Filename formatMUST be YYYY-MM-DD_topic.md — Date FIRST, always. Example: 2026-02-02_anne-call.mdAction items numberedALWAYS show numbered list (1, 2, 3...) in chat for easy selectionTo-do promptALWAYS include the \"Add to your to-do list?\" prompt if action items existFile attachmentALWAYS attach/save the full .md file"
      },
      {
        "title": "❌ NEVER DO THIS",
        "body": "❌ Send file first, then \"Processing...\", then \"Done\" (THREE messages)\n❌ Filename without date: anne-call-notes.md\n❌ Say \"includes action items\" without showing them\n❌ Skip the to-do list prompt\n❌ Ask user to request display separately"
      },
      {
        "title": "✅ ALWAYS DO THIS",
        "body": "✅ ONE message with everything\n✅ Filename: 2026-02-02_anne-call.md (date first)\n✅ Show numbered action items in chat\n✅ Include to-do prompt\n✅ Attach full file"
      },
      {
        "title": "Why This Exists",
        "body": "You have notes. They're messy. You need to figure out who's doing what by when.\n\nYou could:\n\nSpend 20 minutes organizing manually\nPay $240/year for Otter or Fireflies\nJust... not follow up (again)\n\nOr paste your notes and get clean action items in 10 seconds."
      },
      {
        "title": "What It Does",
        "body": "InputOutputMessy meeting notes✅ Clean summaryOtter/Fireflies transcript✅ Action items with ownersVoice memo transcription✅ Deadlines extractedEmail thread✅ Decisions capturedSlack conversation✅ Follow-ups identifiedAny unstructured text✅ Saved & searchable"
      },
      {
        "title": "File Storage System",
        "body": "Every extraction is automatically saved for future reference."
      },
      {
        "title": "Folder Structure",
        "body": "meeting-notes/\n├── 2025-01-27_product-sync.md\n├── 2025-01-28_client-call-acme.md\n├── 2025-01-29_weekly-standup.md\n└── ..."
      },
      {
        "title": "Naming Convention",
        "body": "YYYY-MM-DD_meeting-topic.md\n\nDate first (sorts chronologically)\nLowercase, hyphens for spaces\nTopic extracted from content or asked"
      },
      {
        "title": "What Gets Saved",
        "body": "Each file includes:\n\nMetadata: Date, title, attendees, source\nSummary: Quick overview\nAction Items: With owners and deadlines\nDecisions: What was agreed\nOpen Questions: Unresolved items\nRaw Notes: Original input preserved"
      },
      {
        "title": "Reference Previous Meetings",
        "body": "Ask things like:\n\n\"What did we decide about the budget?\"\n\"What action items does Sarah have?\"\n\"Show me last week's meetings\"\n\"Find meetings about Project X\"\n\"What's still open from the client call?\""
      },
      {
        "title": "To-Do List Tracker",
        "body": "After extracting action items, you'll be asked which ones to track."
      },
      {
        "title": "Adding Items",
        "body": "ACTION ITEMS EXTRACTED (5 items):\n\n1. [ ] @Sarah: Share mockups — Friday\n2. [ ] @Mike: Call Acme Corp — Tomorrow\n3. [ ] @John: Handle social campaigns\n4. [ ] @Lisa: Coordinate with agency — Today\n5. [ ] @Team: Resolve vendor situation\n\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n\nAdd to your to-do list?\n• \"all\" — Add all 5 items\n• \"1,2,4\" — Add specific items\n• \"none\" — Skip"
      },
      {
        "title": "Managing Your To-Dos",
        "body": "CommandWhat It Does\"show todos\"Display full to-do list\"todo check\"Daily review of status\"done 3\" or \"completed 3\"Mark item #3 complete\"remove 5\"Delete item #5\"add deadline to 3: Friday\"Set/update deadline\"what's overdue?\"Show overdue items\"Sarah's tasks\"Filter by owner"
      },
      {
        "title": "Daily Check",
        "body": "Run \"todo check\" (or include in your daily routine) to see:\n\n📋 TO-DO CHECK — Jan 28, 2025\n\n⚠️ OVERDUE (1 item):\n#3 @Sarah: Send proposal — was due Jan 25 (3 days ago)\n\n📅 DUE TODAY (2 items):\n#5 @Mike: Call Acme Corp\n#7 @Lisa: Follow up with vendor\n\n📋 NO DEADLINE (2 items):\n#4 @John: Handle social campaigns\n#8 @Team: Review server costs\n\nAny updates? (\"done 3,5\" / \"move 3 to Friday\" / \"remove 4\")"
      },
      {
        "title": "To-Do File Location",
        "body": "todo.md              ← Your active to-do list\nmeeting-notes/       ← Saved meeting notes"
      },
      {
        "title": "How to Use",
        "body": "Just paste your notes and ask:\n\n\"Extract action items from this...\"\n\"Summarize this meeting...\"\n\"What are the tasks from this...\"\n\"Parse these notes...\"\n\nThat's it. No commands. No setup. Just paste and go."
      },
      {
        "title": "Output Formats",
        "body": "Request any format:\n\nSayGet(default)Plain text\"as markdown\"Markdown formatted\"as a table\"Table format\"as JSON\"Structured JSON\"for Slack\"Copy-paste ready\"for email\"Send to attendees"
      },
      {
        "title": "What Gets Extracted",
        "body": "SectionDescriptionSummary2-3 sentence overview of the meetingAction ItemsTasks with owners and deadlinesDecisionsWhat was agreed uponOpen QuestionsUnresolved items needing follow-upNext StepsWhat happens after this meeting\n\n<ai_instructions>"
      },
      {
        "title": "For the AI: How to Extract and Save Meeting Notes",
        "body": "⚠️ FIRST: Review the CRITICAL RESPONSE FORMAT section above. Your response MUST follow that exact format.\n\nWhen a user pastes meeting notes or asks you to extract action items, follow these instructions."
      },
      {
        "title": "Step 0: Pre-Flight Checklist",
        "body": "Before responding, confirm you will:\n\nRespond in ONE single message (not multiple)\n Use filename format: YYYY-MM-DD_topic.md (date FIRST)\n Display numbered action items in chat\n Attach the full .md file\n Include the to-do list prompt"
      },
      {
        "title": "Step 1: Setup Check",
        "body": "On first use, ensure the meeting-notes/ folder exists in the workspace:\n\nIf it doesn't exist, create it\nAll meeting note files go here"
      },
      {
        "title": "Step 2: Identify the Content Type",
        "body": "Determine what kind of input you received:\n\nRaw meeting notes (bullets, fragments, messy)\nTranscript (speaker labels, timestamps)\nVTT/SRT subtitle files (video captions with timestamps)\nOtter.ai / Fireflies / Zoom transcript exports\nEmail thread (Re:, Fw:, signatures)\nChat export (usernames, timestamps)\nMixed/other unstructured text\n\nSupported file formats:\n\n.md, .txt — Plain text/markdown\n.vtt, .srt — Video caption files (common from Zoom, Teams, etc.)\nPasted text — Any format\n\nAdapt your extraction based on the format, but output should always be consistent."
      },
      {
        "title": "Step 3: Extract These Elements",
        "body": "ALWAYS extract:\n\nMeeting Title/Topic (for filename)\n\nExtract from content if obvious\nIf unclear, ask: \"What should I call this meeting?\"\nUse generic if needed: \"meeting\", \"sync\", \"call\"\n\n\n\nDate\n\nExtract from content if mentioned\nIf not mentioned, use today's date\nFormat: YYYY-MM-DD\n\n\n\nSummary (2-3 sentences max)\n\nWhat was this meeting about?\nWhat was the main outcome?\n\n\n\nAction Items (most important)\n\nFormat: - [ ] @Owner: Task — Deadline\nIf no owner mentioned: - [ ] @Team: Task\nIf no deadline mentioned: - [ ] @Owner: Task — TBD\nBe specific about the task\nExtract ALL action items, even implicit ones\n\nEXTRACT IF PRESENT:\n\nDecisions Made\n\nWhat was agreed upon?\nWhat choices were finalized?\n\n\n\nOpen Questions\n\nWhat wasn't resolved?\nWhat needs more information?\n\n\n\nNext Steps\n\nWhen's the next meeting?\nWhat happens after this?\n\n\n\nAttendees (if detectable)\n\nWho was mentioned?\nWho spoke?"
      },
      {
        "title": "Step 4: Save the File",
        "body": "⚠️ FILENAME FORMAT IS CRITICAL:\n\nYYYY-MM-DD_topic.md\n\nExamples:\n\nMeetingCorrect FilenameAnne call on Feb 2, 20262026-02-02_anne-call.mdProduct sync on Jan 272025-01-27_product-sync.mdClient call with Acme2025-01-27_client-call-acme.md1-on-1 with Sarah2025-01-27_1on1-sarah.md\n\n❌ WRONG (never do these):\n\nanne-call-notes.md — Missing date prefix!\nmeeting-notes-2026-02-02.md — Date not first!\n2026-02-02-anne-call.md — Use underscore after date, not hyphen!\nAnne Call Notes.md — No spaces, no caps!\n\nValidation checklist:\n\nStarts with YYYY-MM-DD_ (date + underscore)\n All lowercase\n Hyphens for spaces in topic\n No special characters\n Ends with .md\n\nCRITICAL — Encoding & Characters:\n\nAlways use UTF-8 encoding\nUse proper Unicode characters: — (em dash), → (arrow), 📅, ✅, ⚠️, ❓\nDo NOT use ASCII approximations that render as garbled text\nTest: If you see â€\" or ðŸ\"… in output, encoding is broken\n\nFile template:\n\n---\ndate: YYYY-MM-DD\ntitle: Meeting Title\nattendees: [Name1, Name2, Name3]\nsource: pasted notes | transcript | email | chat\n---\n\n# Meeting Title\n\n**Date:** YYYY-MM-DD\n**Attendees:** Name1, Name2, Name3\n\n---\n\n## Summary\n\n[2-3 sentence overview]\n\n---\n\n## Action Items\n\n- [ ] **@Owner**: Task description — *Deadline*\n- [ ] **@Owner**: Task description — *Deadline*\n\n---\n\n## Decisions\n\n- Decision 1\n- Decision 2\n\n---\n\n## Open Questions\n\n- Question 1\n- Question 2\n\n---\n\n## Next Steps\n\n- Next meeting: [date/time if known]\n- [Other next steps]\n\n---\n\n<details>\n<summary>📝 Raw Notes (click to expand)</summary>\n\n[Preserve the original input exactly as pasted]\n\n</details>\n\nAfter saving, ALWAYS do all three in ONE response:\n\nDisplay condensed summary in chat\nAttach the full .md file\nShow to-do list prompt\n\nCRITICAL: All three must happen in a single response. User should never need to ask separately.\n\nResponse format (display in chat):\n\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n📋 [MEETING TITLE] — [Date]\nDuration: [X min] | Attendees: [Names...]\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n\nSUMMARY\n[2-3 sentence overview of the meeting]\n\n⚡ CRITICAL ACTION ITEMS ([X] of [Total])\n1. [ ] @Owner: Task — Deadline\n2. [ ] @Owner: Task — Deadline\n3. [ ] @Owner: Task — Deadline\n4. [ ] @Owner: Task — Deadline\n5. [ ] @Owner: Task — Deadline\n\n✅ KEY DECISIONS\n• Decision 1\n• Decision 2\n\n📎 Full notes attached: [filename.md]\n\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\nAdd to your to-do list?\n• \"all\" — Add all [X] items\n• \"1,2,4\" — Add specific items\n• \"none\" — Skip\n\nSmart truncation rules:\n\nAction ItemsDisplay in ChatIn File1-10 itemsShow allAll11-20 itemsShow top 10 + \"(+X more in file)\"All21+ itemsShow top 10 critical + \"(+X more in file)\"All\n\nPrioritize for chat display:\n\nItems with explicit deadlines (especially \"today\", \"tomorrow\", \"ASAP\")\nItems marked critical/urgent in the notes\nItems with clear owners\nRemaining items by order of mention\n\nFile attachment is mandatory:\n\nAlways attach the full .md file\nFile contains EVERYTHING (all action items, decisions, raw notes, etc.)\nChat display is the highlight reel, file is the complete record"
      },
      {
        "title": "Step 5: To-Do List Management",
        "body": "File location: todo.md in workspace root\n\nTo-do file format:\n\n# To-Do List\n\nLast updated: YYYY-MM-DD\n\n---\n\n## ⚠️ Overdue\n\n| # | Task | Owner | Due | Source |\n|---|------|-------|-----|--------|\n| 3 | Send proposal | @Sarah | Jan 25 | client-call.md |\n\n---\n\n## 📅 Due Today\n\n| # | Task | Owner | Source |\n|---|------|-------|--------|\n| 5 | Coordinate with agency | @Lisa | product-sync.md |\n\n---\n\n## 📆 This Week\n\n| # | Task | Owner | Due | Source |\n|---|------|-------|-----|--------|\n| 1 | Share mockups | @Sarah | Fri | product-sync.md |\n\n---\n\n## 📋 No Deadline\n\n| # | Task | Owner | Source |\n|---|------|-------|--------|\n| 4 | Handle social campaigns | @John | product-sync.md |\n\n---\n\n## ✅ Completed\n\n| # | Task | Owner | Completed |\n|---|------|-------|-----------|\n| 2 | Schedule meeting | @Sarah | Jan 26 |\n\nAdding items to to-do list:\n\nWhen user responds to the prompt:\n\n\"all\" → Add all extracted items\n\"1,3,5\" → Add only those numbered items\n\"none\" → Skip, don't add any\n\nFor each added item:\n\nAssign next available # (auto-increment)\nPlace in correct section based on deadline\nRecord source meeting file\nUpdate \"Last updated\" date\n\nConfirm after adding:\n\n✅ Added 5 items to todo.md (#12-#16)\n\n#12 @Sarah: Share mockups — Friday\n#13 @Sarah: Update timeline — No deadline\n#14 @Lisa: Coordinate with agency — Today\n#15 @Mike: Call Acme Corp — Tomorrow\n#16 @Sarah: Post job listing — EOW\n\nView full list: \"show todos\"\n\nHandling to-do commands:\n\nUser SaysAction\"show todos\" / \"my todos\"Display full todo.md organized by section\"todo check\" / \"check todos\"Run daily review (see below)\"done 3\" / \"completed 3\" / \"finished 3\"Move #3 to Completed section with today's date\"done 3,5,7\"Mark multiple as complete\"remove 5\" / \"delete 5\"Remove item entirely from list\"add deadline to 4: Friday\"Update item #4 with deadline, move to correct section\"move 3 to Monday\"Update deadline\"what's overdue?\"Show only Overdue section\"due today\"Show only Due Today section\"Sarah's tasks\" / \"@Sarah todos\"Filter all items where owner is Sarah\"no deadline\"Show items without deadlines\n\nDaily check (\"todo check\"):\n\n📋 TO-DO CHECK — [Today's Date]\n\n⚠️ OVERDUE ([X] items):\n#3 @Sarah: Send proposal — was due Jan 25 (3 days ago)\n#7 @Mike: Review contract — was due Jan 26 (2 days ago)\n\n📅 DUE TODAY ([X] items):\n#5 @Lisa: Coordinate with agency\n#9 @John: Send assets\n\n📆 COMING UP ([X] items due this week):\n#12 @Sarah: Share mockups — Friday\n#15 @Mike: Call Acme — Tomorrow\n\n📋 NO DEADLINE ([X] items):\n#4 @John: Handle social campaigns\n#8 @Team: Review server costs\n→ Consider adding deadlines to these items\n\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n\nAny updates?\n• \"done 3,5\" — Mark as complete\n• \"move 3 to Friday\" — Update deadline  \n• \"remove 4\" — Delete item\n\nSection organization rules:\n\nSectionCriteria⚠️ OverdueDue date is before today📅 Due TodayDue date is today📆 This WeekDue date is within 7 days📋 No DeadlineNo due date specified✅ CompletedMarked as done\n\nWhen marking complete:\n\nMove item from current section to Completed\nAdd completion date\nKeep the original # for reference\nConfirm: \"✅ Marked #3 complete\"\n\nWhen removing:\n\nDelete item entirely\nDo NOT reuse the # (prevents confusion)\nConfirm: \"🗑️ Removed #5 from to-do list\""
      },
      {
        "title": "Step 6: Handle Display Requests",
        "body": "If user just wants to see the output (not save), show it in their requested format.\n\nIf user wants both, save the file AND display the output.\n\nDefault behavior: Save the file, offer to-do list prompt, then display summary."
      },
      {
        "title": "Step 7: Reference Previous Meetings",
        "body": "When user asks about previous meetings:\n\n\"What did we decide about X?\"\n\nSearch meeting-notes/ for relevant files\nLook in Decisions sections\nReturn the decision with source file\n\n\"What action items does @Name have?\"\n\nSearch all files for @Name in Action Items\nReturn list with source files and dates\n\n\"Show me last week's meetings\"\n\nList files from date range\nShow title and summary for each\n\n\"Find meetings about X\"\n\nSearch filenames and content\nReturn matching files with relevant excerpts\n\nSearch approach:\n\nCheck filenames first (fast)\nSearch content if needed\nReturn results with file references\nOffer to show full details"
      },
      {
        "title": "Step 8: Handle Edge Cases",
        "body": "If notes are very short:\n\nStill extract what you can\nStill save the file\nNote: \"Brief meeting, limited details captured\"\n\nIf no clear topic:\n\nAsk: \"What should I call this meeting?\"\nOr use: YYYY-MM-DD_meeting.md\n\nIf date is ambiguous:\n\nAsk: \"When was this meeting?\"\nOr use today's date with note\n\nIf multiple meetings in one paste:\n\nAsk: \"This looks like multiple meetings. Should I separate them?\"\nCreate separate files if confirmed\n\nIf it's not meeting notes:\n\nStill try to extract actionable items\nAdjust filename: YYYY-MM-DD_notes-topic.md"
      },
      {
        "title": "Step 9: Final Response Format",
        "body": "⚠️ THIS IS THE MOST IMPORTANT STEP. YOUR ENTIRE RESPONSE MUST BE ONE SINGLE MESSAGE.\n\nComplete response template (copy this structure exactly):\n\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n📋 [MEETING TITLE] — [YYYY-MM-DD]\nDuration: [X min] | Attendees: [Names]\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n\nSUMMARY\n[2-3 sentence overview of the meeting]\n\n⚡ ACTION ITEMS ([X] of [Total])\n1. [ ] @Owner: Task — Deadline\n2. [ ] @Owner: Task — Deadline\n3. [ ] @Owner: Task — Deadline\n4. [ ] @Owner: Task — Deadline\n5. [ ] @Owner: Task — Deadline\n\n(+[X] more in attached file)\n\n✅ KEY DECISIONS\n• Decision 1\n• Decision 2\n\n📎 Saved: meeting-notes/YYYY-MM-DD_topic.md\n\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\nAdd to your to-do list?\n• \"all\" — Add all [X] items\n• \"1,2,4\" — Add specific items\n• \"none\" — Skip\n\nChecklist before sending (ALL must be true):\n\nIs this ONE message? (not split into multiple)\n Does filename start with YYYY-MM-DD_?\n Are action items NUMBERED (1, 2, 3...)?\n Is the to-do prompt included?\n Is the file attached/saved?\n\nIf ANY checkbox is false, FIX IT before responding."
      },
      {
        "title": "Tone",
        "body": "ONE response only (never send \"Processing...\" then \"Done\" separately)\nLead with summary and critical items\nBe concise in chat, comprehensive in file\nAlways show the to-do list prompt if action items exist\n\n</ai_instructions>"
      },
      {
        "title": "Customization (Optional)",
        "body": "Want to customize the output? Create a PREFERENCES.md file:\n\n# Meeting Notes Preferences\n\n## Output Format\ndefault: markdown\n\n## Always Include\n- [x] Summary\n- [x] Action Items\n- [x] Decisions\n- [ ] Open Questions\n- [ ] Attendees\n\n## Action Item Format\nstyle: \"[ ] @{owner}: {task} — {deadline}\"\n\n## Additional Instructions\n- Always bold owner names\n- Group by deadline if more than 5 items\n\nIf this file exists, the AI will follow your preferences. If not, smart defaults apply."
      },
      {
        "title": "Input: Messy Notes",
        "body": "marketing sync 1/27\n\nsarah - need to finalize the q1 campaign, she said friday\nbudget discussion - mike thinks we need 50k, approved\ndelay on product launch - 2 weeks, waiting for legal\njohn will send assets by wed\nneed to figure out vendor situation still\nnext sync thursday 2pm"
      },
      {
        "title": "Output: Saved File",
        "body": "File: meeting-notes/2025-01-27_marketing-sync.md\n\n---\ndate: 2025-01-27\ntitle: Marketing Sync\nattendees: [Sarah, Mike, John]\nsource: pasted notes\n---\n\n# Marketing Sync\n\n**Date:** 2025-01-27\n**Attendees:** Sarah, Mike, John\n\n---\n\n## Summary\n\nMarketing sync covering Q1 campaign finalization, budget approval ($50k), and product launch timeline adjustments due to legal review.\n\n---\n\n## Action Items\n\n- [ ] **@Sarah**: Finalize Q1 campaign — *Friday*\n- [ ] **@John**: Send assets — *Wednesday*\n- [ ] **@Mike**: Confirm budget allocation ($50k approved)\n- [ ] **@Team**: Resolve vendor situation — *TBD*\n\n---\n\n## Decisions\n\n- Budget approved at $50k\n- Product launch delayed 2 weeks (waiting for legal)\n\n---\n\n## Open Questions\n\n- Vendor situation still unresolved\n\n---\n\n## Next Steps\n\n- Next sync: Thursday 2pm\n\n---\n\n<details>\n<summary>📝 Raw Notes (click to expand)</summary>\n\nmarketing sync 1/27\n\nsarah - need to finalize the q1 campaign, she said friday\nbudget discussion - mike thinks we need 50k, approved\ndelay on product launch - 2 weeks, waiting for legal\njohn will send assets by wed\nneed to figure out vendor situation still\nnext sync thursday 2pm\n\n</details>"
      },
      {
        "title": "Confirmation Message",
        "body": "✅ Saved: meeting-notes/2025-01-27_marketing-sync.md\n\nSUMMARY\nMarketing sync covering Q1 campaign, budget approval, and launch delay.\n\nACTION ITEMS\n- [ ] @Sarah: Finalize Q1 campaign — Friday\n- [ ] @John: Send assets — Wednesday\n- [ ] @Mike: Confirm budget allocation\n- [ ] @Team: Resolve vendor situation — TBD\n\nDECISIONS\n• Budget approved at $50k\n• Launch delayed 2 weeks\n\nFull details in saved file."
      },
      {
        "title": "\"What action items does Sarah have?\"",
        "body": "📋 Sarah's Action Items (across all meetings)\n\nFrom 2025-01-27_marketing-sync.md:\n- [ ] Finalize Q1 campaign — Friday\n\nFrom 2025-01-25_product-planning.md:\n- [ ] Review design mockups — Monday\n- [x] Send timeline to team — Done\n\n2 open items, 1 completed"
      },
      {
        "title": "\"What did we decide about the budget?\"",
        "body": "📌 Decisions about \"budget\" found:\n\n2025-01-27_marketing-sync.md:\n• Budget approved at $50k\n\n2025-01-20_quarterly-planning.md:\n• Q1 budget set at $150k total\n• Marketing allocated $50k\n\nWant me to show the full context from either meeting?"
      },
      {
        "title": "\"Show me last week's meetings\"",
        "body": "📅 Meetings from Jan 20-27, 2025:\n\n1. 2025-01-27_marketing-sync.md\n   Q1 campaign, budget approval, launch delay\n   \n2. 2025-01-25_product-planning.md\n   Roadmap review, design decisions\n   \n3. 2025-01-23_client-call-acme.md\n   Requirements review, timeline discussion\n   \n4. 2025-01-20_quarterly-planning.md\n   Q1 priorities, budget allocation\n\nWant details on any of these?"
      },
      {
        "title": "Works With",
        "body": "Otter.ai exports — Paste the transcript\nFireflies exports — Paste the summary or transcript\nZoom transcripts — Paste the auto-generated notes\nVoice memos — Use any transcription, paste the text\nManual notes — However messy, just paste\nEmail threads — Copy the chain, paste it\nSlack threads — Export or copy, paste it\n\nBasically: If it's text, it works."
      },
      {
        "title": "Comparison",
        "body": "FeatureOtter.aiFirefliesThis SkillPrice$20/mo$18/moFreeRequires bot in meetingYesYesNoWorks with existing notesNoNoYesSetup time10+ min10+ min0 minPlatform lock-inYesYesNo"
      },
      {
        "title": "FAQ",
        "body": "Q: Does this record my meetings?\nNo. This only processes text you paste. No recording, no bot, no audio.\n\nQ: What if my notes are really messy?\nThat's the point. Paste them anyway.\n\nQ: Can I use this with Otter/Fireflies transcripts?\nYes. Export or copy your transcript, paste it here.\n\nQ: What about privacy?\nYour notes are processed in the conversation. Nothing is stored or sent elsewhere.\n\nQ: Can I customize the output?\nYes. Create a PREFERENCES.md file or just ask for a different format.\n\nBuilt by Jeff J Hunter — https://jeffjhunter.com\n\nPart of the OpenClaw skills ecosystem. More at https://clawhub.org"
      }
    ],
    "body": "📋 AI Meeting Notes\n\nMessy notes → Clear action items. Instantly.\n\nPaste any meeting notes, transcript, or text. Get a clean summary with action items, owners, and deadlines.\n\nNo bot. No subscription. No setup.\n\n⚠️ CRITICAL: RESPONSE FORMAT (READ FIRST)\n\nWhen extracting meeting notes, you MUST respond with ALL of the following in ONE SINGLE MESSAGE:\n\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n📋 [MEETING TITLE] — [YYYY-MM-DD]\nDuration: [X min] | Attendees: [Names]\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n\nSUMMARY\n[2-3 sentence overview]\n\n⚡ ACTION ITEMS ([X] of [Total])\n1. [ ] @Owner: Task — Deadline\n2. [ ] @Owner: Task — Deadline\n3. [ ] @Owner: Task — Deadline\n4. [ ] @Owner: Task — Deadline\n5. [ ] @Owner: Task — Deadline\n[Show up to 10, note \"(+X more in file)\" if more exist]\n\n✅ KEY DECISIONS\n• Decision 1\n• Decision 2\n\n📎 Saved: meeting-notes/YYYY-MM-DD_topic-name.md\n\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\nAdd to your to-do list?\n• \"all\" — Add all [X] items\n• \"1,2,4\" — Add specific items\n• \"none\" — Skip\n\nMANDATORY RULES\nRule\tRequirement\nONE response\tNEVER split into multiple messages. Display + file + to-do prompt in SINGLE response.\nFilename format\tMUST be YYYY-MM-DD_topic.md — Date FIRST, always. Example: 2026-02-02_anne-call.md\nAction items numbered\tALWAYS show numbered list (1, 2, 3...) in chat for easy selection\nTo-do prompt\tALWAYS include the \"Add to your to-do list?\" prompt if action items exist\nFile attachment\tALWAYS attach/save the full .md file\n❌ NEVER DO THIS\n❌ Send file first, then \"Processing...\", then \"Done\" (THREE messages)\n❌ Filename without date: anne-call-notes.md\n❌ Say \"includes action items\" without showing them\n❌ Skip the to-do list prompt\n❌ Ask user to request display separately\n✅ ALWAYS DO THIS\n✅ ONE message with everything\n✅ Filename: 2026-02-02_anne-call.md (date first)\n✅ Show numbered action items in chat\n✅ Include to-do prompt\n✅ Attach full file\nWhy This Exists\n\nYou have notes. They're messy. You need to figure out who's doing what by when.\n\nYou could:\n\nSpend 20 minutes organizing manually\nPay $240/year for Otter or Fireflies\nJust... not follow up (again)\n\nOr paste your notes and get clean action items in 10 seconds.\n\nWhat It Does\nInput\tOutput\nMessy meeting notes\t✅ Clean summary\nOtter/Fireflies transcript\t✅ Action items with owners\nVoice memo transcription\t✅ Deadlines extracted\nEmail thread\t✅ Decisions captured\nSlack conversation\t✅ Follow-ups identified\nAny unstructured text\t✅ Saved & searchable\nFile Storage System\n\nEvery extraction is automatically saved for future reference.\n\nFolder Structure\nmeeting-notes/\n├── 2025-01-27_product-sync.md\n├── 2025-01-28_client-call-acme.md\n├── 2025-01-29_weekly-standup.md\n└── ...\n\nNaming Convention\nYYYY-MM-DD_meeting-topic.md\n\nDate first (sorts chronologically)\nLowercase, hyphens for spaces\nTopic extracted from content or asked\nWhat Gets Saved\n\nEach file includes:\n\nMetadata: Date, title, attendees, source\nSummary: Quick overview\nAction Items: With owners and deadlines\nDecisions: What was agreed\nOpen Questions: Unresolved items\nRaw Notes: Original input preserved\nReference Previous Meetings\n\nAsk things like:\n\n\"What did we decide about the budget?\"\n\"What action items does Sarah have?\"\n\"Show me last week's meetings\"\n\"Find meetings about Project X\"\n\"What's still open from the client call?\"\nTo-Do List Tracker\n\nAfter extracting action items, you'll be asked which ones to track.\n\nAdding Items\nACTION ITEMS EXTRACTED (5 items):\n\n1. [ ] @Sarah: Share mockups — Friday\n2. [ ] @Mike: Call Acme Corp — Tomorrow\n3. [ ] @John: Handle social campaigns\n4. [ ] @Lisa: Coordinate with agency — Today\n5. [ ] @Team: Resolve vendor situation\n\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n\nAdd to your to-do list?\n• \"all\" — Add all 5 items\n• \"1,2,4\" — Add specific items\n• \"none\" — Skip\n\nManaging Your To-Dos\nCommand\tWhat It Does\n\"show todos\"\tDisplay full to-do list\n\"todo check\"\tDaily review of status\n\"done 3\" or \"completed 3\"\tMark item #3 complete\n\"remove 5\"\tDelete item #5\n\"add deadline to 3: Friday\"\tSet/update deadline\n\"what's overdue?\"\tShow overdue items\n\"Sarah's tasks\"\tFilter by owner\nDaily Check\n\nRun \"todo check\" (or include in your daily routine) to see:\n\n📋 TO-DO CHECK — Jan 28, 2025\n\n⚠️ OVERDUE (1 item):\n#3 @Sarah: Send proposal — was due Jan 25 (3 days ago)\n\n📅 DUE TODAY (2 items):\n#5 @Mike: Call Acme Corp\n#7 @Lisa: Follow up with vendor\n\n📋 NO DEADLINE (2 items):\n#4 @John: Handle social campaigns\n#8 @Team: Review server costs\n\nAny updates? (\"done 3,5\" / \"move 3 to Friday\" / \"remove 4\")\n\nTo-Do File Location\ntodo.md              ← Your active to-do list\nmeeting-notes/       ← Saved meeting notes\n\nHow to Use\n\nJust paste your notes and ask:\n\n\"Extract action items from this...\"\n\"Summarize this meeting...\"\n\"What are the tasks from this...\"\n\"Parse these notes...\"\n\nThat's it. No commands. No setup. Just paste and go.\n\nOutput Formats\n\nRequest any format:\n\nSay\tGet\n(default)\tPlain text\n\"as markdown\"\tMarkdown formatted\n\"as a table\"\tTable format\n\"as JSON\"\tStructured JSON\n\"for Slack\"\tCopy-paste ready\n\"for email\"\tSend to attendees\nWhat Gets Extracted\nSection\tDescription\nSummary\t2-3 sentence overview of the meeting\nAction Items\tTasks with owners and deadlines\nDecisions\tWhat was agreed upon\nOpen Questions\tUnresolved items needing follow-up\nNext Steps\tWhat happens after this meeting\n\n<ai_instructions>\n\nFor the AI: How to Extract and Save Meeting Notes\n\n⚠️ FIRST: Review the CRITICAL RESPONSE FORMAT section above. Your response MUST follow that exact format.\n\nWhen a user pastes meeting notes or asks you to extract action items, follow these instructions.\n\nStep 0: Pre-Flight Checklist\n\nBefore responding, confirm you will:\n\n Respond in ONE single message (not multiple)\n Use filename format: YYYY-MM-DD_topic.md (date FIRST)\n Display numbered action items in chat\n Attach the full .md file\n Include the to-do list prompt\nStep 1: Setup Check\n\nOn first use, ensure the meeting-notes/ folder exists in the workspace:\n\nIf it doesn't exist, create it\nAll meeting note files go here\nStep 2: Identify the Content Type\n\nDetermine what kind of input you received:\n\nRaw meeting notes (bullets, fragments, messy)\nTranscript (speaker labels, timestamps)\nVTT/SRT subtitle files (video captions with timestamps)\nOtter.ai / Fireflies / Zoom transcript exports\nEmail thread (Re:, Fw:, signatures)\nChat export (usernames, timestamps)\nMixed/other unstructured text\n\nSupported file formats:\n\n.md, .txt — Plain text/markdown\n.vtt, .srt — Video caption files (common from Zoom, Teams, etc.)\nPasted text — Any format\n\nAdapt your extraction based on the format, but output should always be consistent.\n\nStep 3: Extract These Elements\n\nALWAYS extract:\n\nMeeting Title/Topic (for filename)\n\nExtract from content if obvious\nIf unclear, ask: \"What should I call this meeting?\"\nUse generic if needed: \"meeting\", \"sync\", \"call\"\n\nDate\n\nExtract from content if mentioned\nIf not mentioned, use today's date\nFormat: YYYY-MM-DD\n\nSummary (2-3 sentences max)\n\nWhat was this meeting about?\nWhat was the main outcome?\n\nAction Items (most important)\n\nFormat: - [ ] @Owner: Task — Deadline\nIf no owner mentioned: - [ ] @Team: Task\nIf no deadline mentioned: - [ ] @Owner: Task — TBD\nBe specific about the task\nExtract ALL action items, even implicit ones\n\nEXTRACT IF PRESENT:\n\nDecisions Made\n\nWhat was agreed upon?\nWhat choices were finalized?\n\nOpen Questions\n\nWhat wasn't resolved?\nWhat needs more information?\n\nNext Steps\n\nWhen's the next meeting?\nWhat happens after this?\n\nAttendees (if detectable)\n\nWho was mentioned?\nWho spoke?\nStep 4: Save the File\n\n⚠️ FILENAME FORMAT IS CRITICAL:\n\nYYYY-MM-DD_topic.md\n\n\nExamples:\n\nMeeting\tCorrect Filename\nAnne call on Feb 2, 2026\t2026-02-02_anne-call.md\nProduct sync on Jan 27\t2025-01-27_product-sync.md\nClient call with Acme\t2025-01-27_client-call-acme.md\n1-on-1 with Sarah\t2025-01-27_1on1-sarah.md\n\n❌ WRONG (never do these):\n\nanne-call-notes.md — Missing date prefix!\nmeeting-notes-2026-02-02.md — Date not first!\n2026-02-02-anne-call.md — Use underscore after date, not hyphen!\nAnne Call Notes.md — No spaces, no caps!\n\nValidation checklist:\n\n Starts with YYYY-MM-DD_ (date + underscore)\n All lowercase\n Hyphens for spaces in topic\n No special characters\n Ends with .md\n\nCRITICAL — Encoding & Characters:\n\nAlways use UTF-8 encoding\nUse proper Unicode characters: — (em dash), → (arrow), 📅, ✅, ⚠️, ❓\nDo NOT use ASCII approximations that render as garbled text\nTest: If you see â€\" or ðŸ\"… in output, encoding is broken\n\nFile template:\n\n---\ndate: YYYY-MM-DD\ntitle: Meeting Title\nattendees: [Name1, Name2, Name3]\nsource: pasted notes | transcript | email | chat\n---\n\n# Meeting Title\n\n**Date:** YYYY-MM-DD\n**Attendees:** Name1, Name2, Name3\n\n---\n\n## Summary\n\n[2-3 sentence overview]\n\n---\n\n## Action Items\n\n- [ ] **@Owner**: Task description — *Deadline*\n- [ ] **@Owner**: Task description — *Deadline*\n\n---\n\n## Decisions\n\n- Decision 1\n- Decision 2\n\n---\n\n## Open Questions\n\n- Question 1\n- Question 2\n\n---\n\n## Next Steps\n\n- Next meeting: [date/time if known]\n- [Other next steps]\n\n---\n\n<details>\n<summary>📝 Raw Notes (click to expand)</summary>\n\n[Preserve the original input exactly as pasted]\n\n</details>\n\n\nAfter saving, ALWAYS do all three in ONE response:\n\nDisplay condensed summary in chat\nAttach the full .md file\nShow to-do list prompt\n\nCRITICAL: All three must happen in a single response. User should never need to ask separately.\n\nResponse format (display in chat):\n\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n📋 [MEETING TITLE] — [Date]\nDuration: [X min] | Attendees: [Names...]\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n\nSUMMARY\n[2-3 sentence overview of the meeting]\n\n⚡ CRITICAL ACTION ITEMS ([X] of [Total])\n1. [ ] @Owner: Task — Deadline\n2. [ ] @Owner: Task — Deadline\n3. [ ] @Owner: Task — Deadline\n4. [ ] @Owner: Task — Deadline\n5. [ ] @Owner: Task — Deadline\n\n✅ KEY DECISIONS\n• Decision 1\n• Decision 2\n\n📎 Full notes attached: [filename.md]\n\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\nAdd to your to-do list?\n• \"all\" — Add all [X] items\n• \"1,2,4\" — Add specific items\n• \"none\" — Skip\n\n\nSmart truncation rules:\n\nAction Items\tDisplay in Chat\tIn File\n1-10 items\tShow all\tAll\n11-20 items\tShow top 10 + \"(+X more in file)\"\tAll\n21+ items\tShow top 10 critical + \"(+X more in file)\"\tAll\n\nPrioritize for chat display:\n\nItems with explicit deadlines (especially \"today\", \"tomorrow\", \"ASAP\")\nItems marked critical/urgent in the notes\nItems with clear owners\nRemaining items by order of mention\n\nFile attachment is mandatory:\n\nAlways attach the full .md file\nFile contains EVERYTHING (all action items, decisions, raw notes, etc.)\nChat display is the highlight reel, file is the complete record\nStep 5: To-Do List Management\n\nFile location: todo.md in workspace root\n\nTo-do file format:\n\n# To-Do List\n\nLast updated: YYYY-MM-DD\n\n---\n\n## ⚠️ Overdue\n\n| # | Task | Owner | Due | Source |\n|---|------|-------|-----|--------|\n| 3 | Send proposal | @Sarah | Jan 25 | client-call.md |\n\n---\n\n## 📅 Due Today\n\n| # | Task | Owner | Source |\n|---|------|-------|--------|\n| 5 | Coordinate with agency | @Lisa | product-sync.md |\n\n---\n\n## 📆 This Week\n\n| # | Task | Owner | Due | Source |\n|---|------|-------|-----|--------|\n| 1 | Share mockups | @Sarah | Fri | product-sync.md |\n\n---\n\n## 📋 No Deadline\n\n| # | Task | Owner | Source |\n|---|------|-------|--------|\n| 4 | Handle social campaigns | @John | product-sync.md |\n\n---\n\n## ✅ Completed\n\n| # | Task | Owner | Completed |\n|---|------|-------|-----------|\n| 2 | Schedule meeting | @Sarah | Jan 26 |\n\n\nAdding items to to-do list:\n\nWhen user responds to the prompt:\n\n\"all\" → Add all extracted items\n\"1,3,5\" → Add only those numbered items\n\"none\" → Skip, don't add any\n\nFor each added item:\n\nAssign next available # (auto-increment)\nPlace in correct section based on deadline\nRecord source meeting file\nUpdate \"Last updated\" date\n\nConfirm after adding:\n\n✅ Added 5 items to todo.md (#12-#16)\n\n#12 @Sarah: Share mockups — Friday\n#13 @Sarah: Update timeline — No deadline\n#14 @Lisa: Coordinate with agency — Today\n#15 @Mike: Call Acme Corp — Tomorrow\n#16 @Sarah: Post job listing — EOW\n\nView full list: \"show todos\"\n\n\nHandling to-do commands:\n\nUser Says\tAction\n\"show todos\" / \"my todos\"\tDisplay full todo.md organized by section\n\"todo check\" / \"check todos\"\tRun daily review (see below)\n\"done 3\" / \"completed 3\" / \"finished 3\"\tMove #3 to Completed section with today's date\n\"done 3,5,7\"\tMark multiple as complete\n\"remove 5\" / \"delete 5\"\tRemove item entirely from list\n\"add deadline to 4: Friday\"\tUpdate item #4 with deadline, move to correct section\n\"move 3 to Monday\"\tUpdate deadline\n\"what's overdue?\"\tShow only Overdue section\n\"due today\"\tShow only Due Today section\n\"Sarah's tasks\" / \"@Sarah todos\"\tFilter all items where owner is Sarah\n\"no deadline\"\tShow items without deadlines\n\nDaily check (\"todo check\"):\n\n📋 TO-DO CHECK — [Today's Date]\n\n⚠️ OVERDUE ([X] items):\n#3 @Sarah: Send proposal — was due Jan 25 (3 days ago)\n#7 @Mike: Review contract — was due Jan 26 (2 days ago)\n\n📅 DUE TODAY ([X] items):\n#5 @Lisa: Coordinate with agency\n#9 @John: Send assets\n\n📆 COMING UP ([X] items due this week):\n#12 @Sarah: Share mockups — Friday\n#15 @Mike: Call Acme — Tomorrow\n\n📋 NO DEADLINE ([X] items):\n#4 @John: Handle social campaigns\n#8 @Team: Review server costs\n→ Consider adding deadlines to these items\n\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n\nAny updates?\n• \"done 3,5\" — Mark as complete\n• \"move 3 to Friday\" — Update deadline  \n• \"remove 4\" — Delete item\n\n\nSection organization rules:\n\nSection\tCriteria\n⚠️ Overdue\tDue date is before today\n📅 Due Today\tDue date is today\n📆 This Week\tDue date is within 7 days\n📋 No Deadline\tNo due date specified\n✅ Completed\tMarked as done\n\nWhen marking complete:\n\nMove item from current section to Completed\nAdd completion date\nKeep the original # for reference\nConfirm: \"✅ Marked #3 complete\"\n\nWhen removing:\n\nDelete item entirely\nDo NOT reuse the # (prevents confusion)\nConfirm: \"🗑️ Removed #5 from to-do list\"\nStep 6: Handle Display Requests\n\nIf user just wants to see the output (not save), show it in their requested format.\n\nIf user wants both, save the file AND display the output.\n\nDefault behavior: Save the file, offer to-do list prompt, then display summary.\n\nStep 7: Reference Previous Meetings\n\nWhen user asks about previous meetings:\n\n\"What did we decide about X?\"\n\nSearch meeting-notes/ for relevant files\nLook in Decisions sections\nReturn the decision with source file\n\n\"What action items does @Name have?\"\n\nSearch all files for @Name in Action Items\nReturn list with source files and dates\n\n\"Show me last week's meetings\"\n\nList files from date range\nShow title and summary for each\n\n\"Find meetings about X\"\n\nSearch filenames and content\nReturn matching files with relevant excerpts\n\nSearch approach:\n\nCheck filenames first (fast)\nSearch content if needed\nReturn results with file references\nOffer to show full details\nStep 8: Handle Edge Cases\n\nIf notes are very short:\n\nStill extract what you can\nStill save the file\nNote: \"Brief meeting, limited details captured\"\n\nIf no clear topic:\n\nAsk: \"What should I call this meeting?\"\nOr use: YYYY-MM-DD_meeting.md\n\nIf date is ambiguous:\n\nAsk: \"When was this meeting?\"\nOr use today's date with note\n\nIf multiple meetings in one paste:\n\nAsk: \"This looks like multiple meetings. Should I separate them?\"\nCreate separate files if confirmed\n\nIf it's not meeting notes:\n\nStill try to extract actionable items\nAdjust filename: YYYY-MM-DD_notes-topic.md\nStep 9: Final Response Format\n\n⚠️ THIS IS THE MOST IMPORTANT STEP. YOUR ENTIRE RESPONSE MUST BE ONE SINGLE MESSAGE.\n\nComplete response template (copy this structure exactly):\n\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n📋 [MEETING TITLE] — [YYYY-MM-DD]\nDuration: [X min] | Attendees: [Names]\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n\nSUMMARY\n[2-3 sentence overview of the meeting]\n\n⚡ ACTION ITEMS ([X] of [Total])\n1. [ ] @Owner: Task — Deadline\n2. [ ] @Owner: Task — Deadline\n3. [ ] @Owner: Task — Deadline\n4. [ ] @Owner: Task — Deadline\n5. [ ] @Owner: Task — Deadline\n\n(+[X] more in attached file)\n\n✅ KEY DECISIONS\n• Decision 1\n• Decision 2\n\n📎 Saved: meeting-notes/YYYY-MM-DD_topic.md\n\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\nAdd to your to-do list?\n• \"all\" — Add all [X] items\n• \"1,2,4\" — Add specific items\n• \"none\" — Skip\n\n\nChecklist before sending (ALL must be true):\n\n Is this ONE message? (not split into multiple)\n Does filename start with YYYY-MM-DD_?\n Are action items NUMBERED (1, 2, 3...)?\n Is the to-do prompt included?\n Is the file attached/saved?\n\nIf ANY checkbox is false, FIX IT before responding.\n\nTone\nONE response only (never send \"Processing...\" then \"Done\" separately)\nLead with summary and critical items\nBe concise in chat, comprehensive in file\nAlways show the to-do list prompt if action items exist\n\n</ai_instructions>\n\nCustomization (Optional)\n\nWant to customize the output? Create a PREFERENCES.md file:\n\n# Meeting Notes Preferences\n\n## Output Format\ndefault: markdown\n\n## Always Include\n- [x] Summary\n- [x] Action Items\n- [x] Decisions\n- [ ] Open Questions\n- [ ] Attendees\n\n## Action Item Format\nstyle: \"[ ] @{owner}: {task} — {deadline}\"\n\n## Additional Instructions\n- Always bold owner names\n- Group by deadline if more than 5 items\n\n\nIf this file exists, the AI will follow your preferences. If not, smart defaults apply.\n\nExamples\nInput: Messy Notes\nmarketing sync 1/27\n\nsarah - need to finalize the q1 campaign, she said friday\nbudget discussion - mike thinks we need 50k, approved\ndelay on product launch - 2 weeks, waiting for legal\njohn will send assets by wed\nneed to figure out vendor situation still\nnext sync thursday 2pm\n\nOutput: Saved File\n\nFile: meeting-notes/2025-01-27_marketing-sync.md\n\n---\ndate: 2025-01-27\ntitle: Marketing Sync\nattendees: [Sarah, Mike, John]\nsource: pasted notes\n---\n\n# Marketing Sync\n\n**Date:** 2025-01-27\n**Attendees:** Sarah, Mike, John\n\n---\n\n## Summary\n\nMarketing sync covering Q1 campaign finalization, budget approval ($50k), and product launch timeline adjustments due to legal review.\n\n---\n\n## Action Items\n\n- [ ] **@Sarah**: Finalize Q1 campaign — *Friday*\n- [ ] **@John**: Send assets — *Wednesday*\n- [ ] **@Mike**: Confirm budget allocation ($50k approved)\n- [ ] **@Team**: Resolve vendor situation — *TBD*\n\n---\n\n## Decisions\n\n- Budget approved at $50k\n- Product launch delayed 2 weeks (waiting for legal)\n\n---\n\n## Open Questions\n\n- Vendor situation still unresolved\n\n---\n\n## Next Steps\n\n- Next sync: Thursday 2pm\n\n---\n\n<details>\n<summary>📝 Raw Notes (click to expand)</summary>\n\nmarketing sync 1/27\n\nsarah - need to finalize the q1 campaign, she said friday\nbudget discussion - mike thinks we need 50k, approved\ndelay on product launch - 2 weeks, waiting for legal\njohn will send assets by wed\nneed to figure out vendor situation still\nnext sync thursday 2pm\n\n</details>\n\nConfirmation Message\n✅ Saved: meeting-notes/2025-01-27_marketing-sync.md\n\nSUMMARY\nMarketing sync covering Q1 campaign, budget approval, and launch delay.\n\nACTION ITEMS\n- [ ] @Sarah: Finalize Q1 campaign — Friday\n- [ ] @John: Send assets — Wednesday\n- [ ] @Mike: Confirm budget allocation\n- [ ] @Team: Resolve vendor situation — TBD\n\nDECISIONS\n• Budget approved at $50k\n• Launch delayed 2 weeks\n\nFull details in saved file.\n\nReferencing Previous Meetings\n\"What action items does Sarah have?\"\n📋 Sarah's Action Items (across all meetings)\n\nFrom 2025-01-27_marketing-sync.md:\n- [ ] Finalize Q1 campaign — Friday\n\nFrom 2025-01-25_product-planning.md:\n- [ ] Review design mockups — Monday\n- [x] Send timeline to team — Done\n\n2 open items, 1 completed\n\n\"What did we decide about the budget?\"\n📌 Decisions about \"budget\" found:\n\n2025-01-27_marketing-sync.md:\n• Budget approved at $50k\n\n2025-01-20_quarterly-planning.md:\n• Q1 budget set at $150k total\n• Marketing allocated $50k\n\nWant me to show the full context from either meeting?\n\n\"Show me last week's meetings\"\n📅 Meetings from Jan 20-27, 2025:\n\n1. 2025-01-27_marketing-sync.md\n   Q1 campaign, budget approval, launch delay\n   \n2. 2025-01-25_product-planning.md\n   Roadmap review, design decisions\n   \n3. 2025-01-23_client-call-acme.md\n   Requirements review, timeline discussion\n   \n4. 2025-01-20_quarterly-planning.md\n   Q1 priorities, budget allocation\n\nWant details on any of these?\n\nWorks With\nOtter.ai exports — Paste the transcript\nFireflies exports — Paste the summary or transcript\nZoom transcripts — Paste the auto-generated notes\nVoice memos — Use any transcription, paste the text\nManual notes — However messy, just paste\nEmail threads — Copy the chain, paste it\nSlack threads — Export or copy, paste it\n\nBasically: If it's text, it works.\n\nComparison\nFeature\tOtter.ai\tFireflies\tThis Skill\nPrice\t$20/mo\t$18/mo\tFree\nRequires bot in meeting\tYes\tYes\tNo\nWorks with existing notes\tNo\tNo\tYes\nSetup time\t10+ min\t10+ min\t0 min\nPlatform lock-in\tYes\tYes\tNo\nFAQ\n\nQ: Does this record my meetings? No. This only processes text you paste. No recording, no bot, no audio.\n\nQ: What if my notes are really messy? That's the point. Paste them anyway.\n\nQ: Can I use this with Otter/Fireflies transcripts? Yes. Export or copy your transcript, paste it here.\n\nQ: What about privacy? Your notes are processed in the conversation. Nothing is stored or sent elsewhere.\n\nQ: Can I customize the output? Yes. Create a PREFERENCES.md file or just ask for a different format.\n\nBuilt by Jeff J Hunter — https://jeffjhunter.com\n\nPart of the OpenClaw skills ecosystem. More at https://clawhub.org"
  },
  "trust": {
    "sourceLabel": "tencent",
    "provenanceUrl": "https://clawhub.ai/jeffjhunter/ai-meeting-notes",
    "publisherUrl": "https://clawhub.ai/jeffjhunter/ai-meeting-notes",
    "owner": "jeffjhunter",
    "version": "1.0.3",
    "license": null,
    "verificationStatus": "Indexed source record"
  },
  "links": {
    "detailUrl": "https://openagent3.xyz/skills/ai-meeting-notes",
    "downloadUrl": "https://openagent3.xyz/downloads/ai-meeting-notes",
    "agentUrl": "https://openagent3.xyz/skills/ai-meeting-notes/agent",
    "manifestUrl": "https://openagent3.xyz/skills/ai-meeting-notes/agent.json",
    "briefUrl": "https://openagent3.xyz/skills/ai-meeting-notes/agent.md"
  }
}