Turn a meeting's raw record — a video/audio transcript, the notes someone typed during the call, or both — into a short summary plus a clear list of next steps with owners. Use this whenever the user shares meeting notes or a transcript and wants to know what was decided and what happens next, OR asks for "action items", "next steps", "follow-ups", "takeaways", "who's doing what", "recap this meeting", or "what did we agree on". Trigger even when the user doesn't say the word "meeting" — a pasted transcript with speaker labels, or notes that read like a discussion, is enough of a signal.
Capture conversations and decisions into structured Notion pages; use when turning chats/notes into wiki entries, how-tos, decisions, or FAQs with proper linking.
Build a structured PRD that connects problem, users, solution, and success criteria. Use when turning discovery notes into an engineering-ready document for a major initiative.
Convert raw notes, error logs, voice dictation, or screenshots into crisp GitHub-flavored markdown issue reports. Use when the user pastes bug info, error messages, or informal descriptions and wants a structured GitHub issue. Supports images/GIFs for visual evidence.
Use this skill any time a .pptx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates, layouts, speaker notes, or comments. Trigger whenever the user mentions \"deck,\" \"slides,\" \"presentation,\" or references a .pptx filename, regardless of what they plan to do with the content afterward. If a .pptx file needs to be opened, created, or touched, use this skill.
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
Summarize a meeting transcript into structured notes with date, participants, topic, key decisions, summary points, and action items. Use when processing meeting recordings, creating meeting notes, writing meeting minutes, or recapping discussions.
Turn raw notes, ticket/task data, metrics, and standup updates into polished, consistent status reports and executive summaries in a reusable house format. Use this skill whenever the user wants to write, draft, generate, or clean up a weekly status report, team/project update, exec or leadership summary, stakeholder update, or "what I did this week / where things stand" report — or asks to define a house format for reports, make last week's format consistent, or summarize progress for leadership. Trigger even when the user just pastes messy notes, a task export, or last week's report and says "turn this into an update," and even if they don't use the exact word "status report.