# Quarterly Connection > Summarizes team accomplishments over the past 90 days aligned to user-specified strategy priorities, drafts next-90-day expected outcomes, and produces Workday-ready Quarterly Connection text. Gathers evidence from Gmail, Calendar, and Google Tasks. Use when the user asks for quarterly connection, quarterly self-assessment, Workday performance reflection, or QBR accomplishment summary. - Skill: `cgray-redhat/quarterly-connection` (Agent Skill, multi-file: 7 files) - Install (CLI): `npx skillmds@latest add cgray-redhat/quarterly-connection` - Raw SKILL.md: https://api.skillmd.com/api/skills/cgray-redhat/quarterly-connection/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Productivity - Author: cgray-redhat (https://skillmd.com/u/cgray-redhat) - Updated: 2026-09-22 - Page: https://skillmd.com/skills/cgray-redhat/quarterly-connection --- # Quarterly Connection Produce **Workday-ready quarterly connection text**: one executive bullet per priority for the **past 90 days** (WHAT + HOW accomplishments) and one bullet per priority for the **next 90 days** (expected outcomes). Scope: **Chris Gray and the Global Renewals, Dealmaking, and Ecosystem team** — not personal-only. ## Prerequisites 1. `gws` CLI authenticated (`gws auth status`). Scopes: `calendar`, `gmail`, `tasks`, `drive`, `documents`, `presentations`. 2. Read `ME.md` at the project root (if present). 3. Read `TEAM.md` at the project root (if present) for team context when synthesizing. 4. **Priority source must be specified by the user** — do not infer silently from `TEAM.md`. ## Workflow ``` Quarterly Connection: - [ ] Step 0: Confirm priority source and date window - [ ] Step 1: Check connections (refresh-connections) - [ ] Step 2: Extract priorities from user-specified source - [ ] Step 3: Gather 90-day evidence - [ ] Step 4: Read Workday guidance - [ ] Step 5: Map evidence to priorities and synthesize bullets - [ ] Step 6: Save output and present for Workday paste - [ ] Step 7: Confirm with user and ask for feedback ``` ### Step 0 — Required intake (hard gate) **Stop and ask** if the user has not specified the priority source. | Input | Required | Default | |-------|----------|---------| | **Priority source** | Yes | None — user must choose | | Lookback window | No | 90 days ending today | | Forward window | No | 90 days from today | **Priority source options** (user picks one): 1. **Google Slides** — deck URL/ID + slide number(s), e.g. `CY26 Executive Summary, slides 3–7` 2. **Google Doc** — doc URL/ID with priority sections 3. **`TEAM.md`** — `Our Priorities` section only (when user explicitly names it) Example CY26 deck (reference in `TEAM.md`): `1nOkeUfWYdk_pYyRI7OiJ0nETdrse79LiYXtqXfZMBSU` ### Step 1 — Check connections ```bash python3 ~/.cursor/skills/refresh-connections/scripts/check_connections.py \ --project-mcp .cursor/mcp.json ``` **gws** must pass. If auth fails, run `gws auth login` before continuing. ### Step 2 — Extract priorities ```bash python3 ~/.cursor/skills/quarterly-connection/scripts/extract_priorities.py \ --deck-id "" \ --slides "3-7" \ --format json > /tmp/quarterly-priorities.json ``` Alternates: `--doc-id `, `--team-md /path/to/TEAM.md` Validate **5–8 top-level priorities** with the user if extraction is ambiguous or slide bodies are thin. ### Step 3 — Gather evidence ```bash python3 ~/.cursor/skills/quarterly-connection/scripts/gather_quarterly_connection.py \ --priorities-json /tmp/quarterly-priorities.json \ --lookback-days 90 \ --forward-days 90 \ --format json > /tmp/quarterly-evidence.json ``` Review `counts` and `warnings` in the bundle before synthesizing. ### Step 4 — Read Workday guidance Read [data/workday-guidance.md](data/workday-guidance.md). If older than 30 days, refresh via **thesource** skill (`quarterly connections`, `performance development`) and update the cache file. **Verbatim reflection prompt** (accomplishments section): > What accomplishments are you most proud of last quarter? Reflect not only on WHAT you've accomplished but also on HOW you've accomplished it. ### Step 5 — Synthesize bullets For **each priority**, produce exactly **one bullet** in each section. #### Past 90 days — Accomplishments ``` • {Priority title}: {WHAT — concrete team outcome} — {HOW — leadership/operating model used to deliver it} ``` **Evidence hierarchy:** 1. Sent emails / leadership communications authored by Chris 2. Gemini notes / meeting outcomes from calendar 3. Completed Google Tasks tied to priority keywords 4. Calendar forums where strategy was advanced Use team names from `TEAM.md` when attributing org outcomes. Mark gaps `[needs input]` — never invent metrics. #### Next 90 days — Forward look ``` • {Priority title}: {Expected accomplishment by end of forward period — specific, measurable where possible} ``` Derive from: open tasks, stated next steps in recent emails/notes, deck expected outcomes, in-flight programs. ### Step 6 — Save output and present Use this template: ```markdown # Quarterly Connection — {Quarter label, e.g. Q2 2026} **Priority source:** {deck/doc/TEAM.md reference} **Period reviewed:** {startLabel} – {endLabel} **Forward period:** {endLabel} – {forwardEndLabel} ## Reflection prompt What accomplishments are you most proud of last quarter? Reflect not only on WHAT you've accomplished but also on HOW you've accomplished it. ## Accomplishments (past 90 days) • ... (one bullet per priority) ## Priorities and expected accomplishments (next 90 days) • ... (one bullet per priority) ## Notes for Workday entry {Field tips from workday-guidance.md} ``` **Delivery:** 1. Present in chat for copy/paste into Workday 2. Save to `notes/quarterly-connection-{YYYY-MM-DD}.md` in the active project 3. **Email (HTML for Workday):** send with `send_quarterly_connection.py` so bullets render as `