@opsdeskSkill
Prep for a 1:1 with a direct report, manager, or peer in five minutes, picking up where the last one left off. You get what you each promised last time, what changed, and three questions worth asking, from a running notes file per person that also logs what was said afterward. Sticks to facts, not judgments, and never messages the person for you.
Before each 1:1: open commitments, what changed, and three questions to ask.
@opsdeskSkill
Pull the decisions and action items out of meeting notes or a transcript, each with one owner and a real due date. Rewrites vague "we should" lines into verb-first tasks, lists open questions, and writes a CSV you can paste into any tracker or spreadsheet. Runs locally, needs no API keys, and never sends the follow-up for you.
After any meeting: decisions and action items, each with one owner and a due date.
@opsdeskSkill
Turn every team's weekly update into one page your leadership team can read in three minutes. Puts asks that need a decision first, then risks ranked by severity, metrics by team, wins, and who has not reported yet, with a script doing the sorting so nothing is dropped. For founders, COOs, and chiefs of staff running the weekly ELT meeting.
Every week: roll the team updates into one brief with decisions needed first.
@opsdeskSkill
Draft a monthly investor update email or a quarterly board memo from your own numbers and notes. Leads with a clear headline, shows metrics against plan and last period, tells lowlights straight, follows up on last update's promises, and ends with specific asks. Never invents a number; gaps are marked for you to fill. A writing aid, not legal, accounting, or investment advice.
Every month or quarter: draft the investor update or board memo from your numbers.
@opsdeskSkill
Run a team retrospective or blameless post-mortem that ends in real change, not a long list. Picks the format, writes the pre-read, checks last retro's actions, clusters input into themes, plans the vote and agenda, and leaves you with at most three actions, each with an owner and a date.
At the end of a project: run a retro that ends in two or three real changes.
