القائمة
Summarize meetings and extract action items. Use when processing meeting transcripts, notes, or recordings to get summaries, decisions, and follow-ups.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Set up Jazz as a GitHub Action for automated PR code review and on-demand /jazz PR assistance. Use when the user asks to add Jazz to CI, create a GitHub Action workflow, set up PR review automation, enable /jazz commands on PRs, or integrate Jazz with GitHub. Triggers on "github action", "github actions", "ci", "pr review", "pr assistant", "jazz in ci", "/jazz".
Extract clean markdown content from web pages using Defuddle CLI, removing clutter and navigation to save tokens. Use instead of WebFetch when the user provides a URL to read or analyze, for online documentation, articles, blog posts, or any standard web page.
Use the official Obsidian CLI (v1.12+) to manage vaults, notes, daily notes, search, tasks, tags, properties, links, templates, sync, publish, and workspaces. Use when the user mentions Obsidian, vaults, notes, or wants to automate note-taking and knowledge base workflows.
Help users create, manage, and refine custom personas for Jazz agents. Use when the user wants to define a new communication style, character, or identity for an agent.
Create new Jazz skills for automating workflows. Use when the user asks to create a skill, make a skill, or wants to define custom automation behavior.
Create and track task lists for complex multi-step work. Use when planning projects, breaking down work, tracking progress, or when a task has 3+ steps. Triggers on "plan", "todo", "task list", "break down", "step by step", or complex requests requiring multiple actions.
| name | meeting-notes |
| description | Summarize meetings and extract action items. Use when processing meeting transcripts, notes, or recordings to get summaries, decisions, and follow-ups. |
Summarize meetings and extract decisions, action items, and follow-ups from transcripts or notes.
# Meeting Summary: [Topic or title]
**Date**: [if known]
**Attendees**: [if known]
## Summary
[3–5 sentences: what was discussed, main outcomes, tone of meeting]
## Decisions
- [Decision 1]. [Owner/context if known.]
- [Decision 2]
## Action Items
| Owner | Action | Due |
| ------ | ------ | ---------------- |
| [Name] | [What] | [When if stated] |
| ... | ... | ... |
## Follow-up
- [Topic or question to revisit]
- [Blocked item or open question]
## Raw notes / transcript
[Optional: link or truncated copy if user wants it preserved]
Decisions: Explicit agreements, choices made, “we will do X.” Action items: Concrete tasks with owner; add “(owner TBD)” if unclear. Follow-up: Topics to revisit, open questions, blocked items. Risks or concerns: If someone raised a risk or objection, note it briefly.
Do not invent owners or due dates; use “?” or “TBD” when missing.
If user wants a short follow-up email:
**Subject**: Follow-up: [Meeting topic]
Hi all,
Quick summary from [meeting]:
- [Key point 1]
- [Key point 2]
Action items:
- [Name]: [Action] by [date]
- [Name]: [Action]
[Open question or next meeting if any.]
Thanks,
[User]
Generate only if user asks for “follow-up email” or “send summary to attendees.”