pmo-universal
Universal PM productivity skills that work across all projects without any project-specific context. Useful for anyone on a software team — PM, developer, tester, or designer.
Included assets
skills/pmo-universal-usage/SKILL.md — explains what this plugin does and when to use each universal PMO skill
skills/reports-morning-briefing/SKILL.md — produces a sourced morning catch-up and meeting-prep digest
skills/wyjasnij-typa/SKILL.md — checks blame claims against project sources and prepares a fact-based rebuttal
Skills
| Skill | What it does |
|---|
/pmo-universal-usage | Explains this plugin, lists triggers, and shows example prompts |
/reports-morning-briefing | Morning catch-up — scans Slack, Jira, Fireflies, Gmail, and Google Calendar since you last worked and produces a scannable digest with today's meeting prep |
/wyjasnij-typa | Blame Shield — cross-checks project accusations against real sources (Slack, Fireflies, Jira, Confluence) and prepares a fact-based rebuttal |
Required connectors
| Connector | Required by |
|---|
| Slack | both skills |
| Fireflies | reports-morning-briefing |
| Atlassian (Jira + Confluence) | reports-morning-briefing, wyjasnij-typa |
| Google Calendar | reports-morning-briefing |
| Gmail | reports-morning-briefing |
Setup
No project-specific setup required. Both skills work out of the box.
Optional: if you have Slack channel IDs for your main project channels, add them to your Claude project instructions. The morning briefing will scan them directly instead of searching by name, which is faster:
## My Slack channels
- <project-name>: <channel-id>
- <project-name>: <channel-id>
Example prompts
/reports-morning-briefing What did I miss since Friday?
/reports-morning-briefing Good morning — catch me up before standup
/wyjasnij-typa [paste the message where someone is blaming you]
/wyjasnij-typa The PM says we didn't deliver X on time — is that accurate?
Notes
wyjasnij-typa — the skill body is written in Polish (built for Polish-speaking PMs in a software house context), but the output adapts to whatever language you use in the conversation. The source-checking logic and rebuttal structure are fully language-agnostic. English triggers work fine: "am I being blamed unfairly?", "is this my fault?", "someone's blaming me for X".
reports-morning-briefing — works best at the start of a workday or after time away. It asks for a scan window, or uses the period you already gave in the prompt, then scans the selected sources and produces a concise digest. For best results, run it before opening Slack rather than after.