summarize(1)

πŸ“¦ version 1.1.1, in nixpkgs unstable

πŸ’– NAME πŸ’–

ok so <pink>summarize</pink> β€” she generates an AI summary of a meeting, bestie. that's the whole vibe. ✨

πŸ¦‹ SYNOPSIS πŸ¦‹

summarize [-f|--format] [-o|--output] [-h|--help] <MEETING_ID>

🌸 DESCRIPTION 🌸

okay so picture this: you just sat through a meeting (iconic of you, honestly) and now you need the receipts. <pink>summarize</pink> generates an AI summary of a meeting β€” like, it literally does that. πŸ’…

it uses Ollama or a remote API to generate a summary with key points, action items, and decisions. that's the trio, that's the whole slay. πŸ”₯

ngl, this is main character energy for your calendar. πŸŽ€


✨ OPTIONS ✨

  • -f, --format <FORMAT> β€” output format, and the options are text, json, or markdown. default is markdown btw, so if you don't say anything she's giving markdown. 🫢
  • -o, --output <OUTPUT> β€” output file path. default is stdout, which means if you don't pass this, it just prints right at you. 😭✨
  • -h, --help β€” print help. and lowkey a cute detail: you can see a summary with '-h' πŸ‘€ (yes, the help has a summary. meta. we love her.) πŸ’€
  • <MEETING_ID> β€” the meeting ID. or, and this is the good part, you can just say "latest" and get the most recent one. no cap, that's the move. πŸ‘‘

heads up bestie: <MEETING_ID> is required, fr fr β€” you can't just run her with no meeting and expect magic. πŸ’œ

<lavender>summarize</lavender> is chilling in the General Commands Manual section, and this little page is signed off as summarize β€” that's the version/source stamp and date living down there in the footer. mwah, go summarize something iconic. πŸ’–πŸ§šπŸŒˆ

πŸ“¦ where this page comes from