القائمة
Analyze and summarize a transcript, meeting notes, or discussion thread into a clear actionable document
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/jmagly/aiwg --skill summarize-transcriptيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
استنادا إلى تصنيف SOC المهني
عرض SKILL.md
| namespace | aiwg |
| name | summarize-transcript |
| platforms | ["all"] |
| description | Analyze and summarize a transcript, meeting notes, or discussion thread into a clear actionable document |
Analyze and summarize a transcript, meeting notes, or discussion thread into a clear, actionable document.
/summarize-transcript <path-to-transcript-or-paste-content> [--style <style-preset>] [--emphasize "<guidance>"] [--avoid "<guidance>"]
<content>: Path to transcript file OR paste content directly--style <preset>: Optional style preset (default: balanced)
technical: Dense technical detail, architecture-focusedexecutive: High-level strategic, business-focusedaction-items: Task-oriented, next-steps focuseddeveloper: Code-centric, implementation detailsbalanced: Mix of strategic and technical--emphasize "<text>": Positive guidance - what to highlight, tone to adopt--avoid "<text>": Negative guidance - what to de-emphasize or exclude/summarize-transcript meeting-notes.txt
/summarize-transcript standup-transcript.md --style action-items
/summarize-transcript design-review.txt --emphasize "Focus on security decisions and data privacy concerns"
/summarize-transcript brainstorm-session.txt --avoid "Skip bikeshedding about naming, focus on architectural decisions"
/summarize-transcript architecture-meeting.md \
--style technical \
--emphasize "Highlight consensus mechanisms and performance trade-offs" \
--avoid "Skip discussion of tooling choices, minimize meeting logistics"
The command produces a structured summary following this template:
emphasis:
- Architecture patterns and system design
- Performance characteristics and trade-offs
- Implementation details and constraints
- Security and reliability considerations
tone:
- Dense technical vocabulary
- Precise terminology
- Include metrics and measurements
avoid:
- Business justifications
- High-level platitudes
- Process discussions
emphasis:
- Strategic outcomes and business impact
- Resource allocation and timeline
- Risk assessment and mitigation
- Cross-functional dependencies
tone:
- Business-focused language
- ROI and value propositions
- Clear decision rationale
avoid:
- Implementation minutiae
- Technical jargon without context
- Low-level code discussion
emphasis:
- Who does what by when
- Blockers and dependencies
- Immediate next steps
- Accountability assignments
tone:
- Imperative verbs
- Clear ownership
- Explicit timelines
avoid:
- Background discussion
- Exploratory tangents
- Historical context
emphasis:
- Code changes and implementation approach
- API contracts and interfaces
- Testing strategy and coverage
- Debugging and troubleshooting
tone:
- Code-centric language
- Concrete examples
- Tool and framework references
avoid:
- Business strategy
- Abstract architecture theory
- Meeting meta-discussion
emphasis:
- Mix of strategic and tactical
- Context + decisions + actions
- Key takeaways for all audiences
- Both "why" and "how"
tone:
- Accessible to multiple roles
- Balance detail and clarity
- Preserve important nuance
avoid:
- Extremes in either direction
- Redundant information
- Tangential discussions
When executing this command, follow these steps:
--style preset as baseline--emphasize guidance to prioritize content--avoid guidance to filter or de-emphasizecode blocks for technical referencesBased on the provided dev update posting, here's the structure to emulate:
📢 [Meeting Title] — [Date]
TL;DR
• [Emoji] [Key decision/outcome 1]
• [Emoji] [Key decision/outcome 2]
• [Emoji] [Key decision/outcome 3]
• [Emoji] [Next steps/actions]
⸻
[Primary Section Label]
🔹 [Topic Area 1]
• [Context/background]
• [Decision made]
• [Implementation approach]
• [Open questions or next steps]
🔹 [Topic Area 2]
• [Context/background]
• [Decision made]
• [Technical details]
• [Action items]
🔹 [Topic Area 3]
• [Context/background]
• [Strategic direction]
• [Resource implications]
• [Timeline or milestones]
⸻
[Optional: Action Items]
• [@owner] Task description by [date]
• [@owner] Task description by [date]
[Optional: Open Questions]
• Question requiring follow-up?
• Decision pending [person/team]?
[Optional: Next Meeting]
• Date/time
• Agenda items
The command is flexible and adapts to various content types:
Emoji usage is optional but recommended for:
Length guidance:
Context preservation:
Template Version: 1.0 Based On: Roko Dev Community Update (Oct 7 & 9, 2025) Maintained By: AIWG Team