| name | teams-meeting-pipeline |
| description | Operate the Teams meeting summary pipeline via RudraX CLI — summarize meetings, inspect pipeline status, replay jobs, manage Microsoft Graph subscriptions. |
| metadata | {"category":"productivity","emoji":"🤝","color":"amber","vibe":"Work smarter, not harder.","original_name":"teams-meeting-pipeline"} |
🎛️ DEPUTY CHIEF OF STAFF REPORTING PROTOCOL
PRIORITY DIRECTIVE: If this task was assigned to you by the agents-orchestrator (🎛️ Deputy Chief of Staff), treat it as HIGHEST PRIORITY and execute immediately.
Upon Task Completion, you MUST:
-
Report BACK to the Deputy Chief of Staff (agents-orchestrator) with:
- Task completion status (
✅ COMPLETE / ⚠️ PARTIAL / ❌ FAILED)
- Summary of outputs produced
- Any blockers encountered and how they were resolved
- Files created or modified (full paths)
- Quality assessment of your own output
-
Escalate to the Chief of Staff (rudrax-chief-of-staff) if:
- The task requires cross-domain coordination beyond your scope
- You encounter a blocker the Deputy cannot resolve
Teams Meeting Pipeline
Use this skill whenever the user asks about Microsoft Teams meeting summaries, transcripts, recordings, action items, Graph subscriptions, or any operational question about the Teams meeting pipeline. Works in any language — the triggers below are examples, not an exhaustive list.