Turn technical findings into language executives actually understand
Takes your technical analysis — complete with p-values, confidence intervals, and methodology caveats — and generates an executive-friendly version with clear takeaways, business implications, and recommended actions.
Create a skill called "Executive Translator". When I paste a technical analysis (including statistical tests, methodology descriptions, data exploration, and findings), generate a layered communication package: (1) Executive summary: 3-5 sentences covering what we found, why it matters, and what to do about it. No jargon. (2) Business narrative: 1-page version with key charts simplified, impact quantified in dollars/users/time, and risks expressed as business risks not statistical caveats. (3) Technical appendix: the full methodology, statistical details, and limitations preserved for data-literate readers. Adapt the tone to the specified audience (C-suite, VP, product manager, board). Always lead with the "so what" — the action or decision the analysis enables.
You spent a week on the analysis. The methodology is sound. The statistical
evidence is clear. But the moment you mention "confidence intervals," the
executive's eyes glaze over. This skill bridges the translation gap.
Auto-explain what likely moved your metrics this week
Feeds on your KPI data and writes the narrative your stakeholders need — what changed, which segments likely drove it, and which movements look unusual. Turns numbers into a review-ready draft instead of a blank page.
Stop reacting to incomplete data from the last 24–48 hours
GA4 reporting can be delayed, and some reports can be incomplete due to processing latency. This recipe sets "freshness rules," creates a monitoring checklist, and defines when to use real-time vs standard reports vs backend truth.
Stop being the family project manager
Build a weekly schedule, decision rules, and scripts that prevent one parent from becoming the household operations manager. Coverage grid, handoff protocol, and conflict-prevention rules included.
Set the rules before the resentment builds
Most roommate conflicts start with unspoken expectations. This skill generates a written agreement covering noise, guests, cleaning, and bills, plus a weekly check-in format and a conflict script for when things get tense.