skills/general/1on1-followup/SKILL.md
Quick post-meeting follow-up for 1-on-1s. Triggers: '1on1 followup', 'follow up on my 1on1', '1on1 with [name]', 'debrief my 1on1', 'process my 1on1 with [name]'.
npx skillsauth add beam-ai-team/beam-next-skills 1on1-followupInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Quick debrief after any 1-on-1. Fetches the latest transcript, extracts commitments, and gives you 3 sharp coaching notes. Takes 2 minutes.
Before fetching transcripts, writing follow-up notes, or updating commitment trackers, show the person, meeting date range, transcript source, target file or tracker, and whether sensitive feedback is included. Require explicit user approval in the current turn before fetching from external meeting tools or writing local files. Do not send follow-ups, create tasks, or share coaching notes externally from this skill.
Run this right after a 1-on-1 ends. It's the "close the loop" skill — capture what happened before you forget.
| Use This | Not This |
|----------|----------|
| "Just finished my 1on1 with Saqib" | "Deep review of my meeting" → use 1on1-review |
| "Process my 1on1 with Brad" | "How am I doing overall?" → use 1on1-review |
| Quick debrief, action capture | Full expert coaching analysis |
Option A — Name provided:
User: "1on1 followup with Brad"
→ Look in 04-workspace/ceo-office/1on1s/brad/transcripts/ for latest file
→ If not found, fetch from Amie using fetch_1on1s.py --person Brad --since [today]
Option B — No name:
User: "1on1 followup"
→ AI asks: "Who was the 1-on-1 with?"
Option C — Fetch fresh: If the transcript isn't saved yet, run:
python3 02-projects/Beam/10-1on1-excellence/02-resources/scripts/fetch_1on1s.py --person [name] --since [today's date]
Load the transcript from 04-workspace/ceo-office/1on1s/{person}/transcripts/.
Output this format — short, sharp, actionable:
═══════════════════════════════════════
1ON1 FOLLOW-UP — {Person}, {Date}
═══════════════════════════════════════
⏱ {Duration} min | {1-line topic summary}
────────────────────────────────────────
📋 COMMITMENTS
────────────────────────────────────────
YOUR commitments:
- [ ] {What you promised} — by {date if mentioned, else "TBD"}
- [ ] {What you promised}
THEIR commitments:
- [ ] {What they promised} — by {date if mentioned, else "TBD"}
- [ ] {What they promised}
⚠️ OPEN LOOPS (mentioned but no owner/deadline):
- {Topic that was discussed but not resolved}
────────────────────────────────────────
💡 3 COACHING NOTES
────────────────────────────────────────
✅ WORKED: {One specific thing you did well — with quote}
⚠️ IMPROVE: {One specific thing to do differently next time — with concrete alternative}
❓ ASK NEXT TIME: {One specific question to open the next 1-on-1 with this person}
────────────────────────────────────────
✉️ SEND TO {Person}
────────────────────────────────────────
{Short follow-up message to send directly to the person.
Casual, warm, their tone. Summarizes what was agreed,
lists their commitments, and sets the next checkpoint.
No coaching language — this is peer-to-peer, not manager notes.
2-4 short paragraphs max. Ready to paste into Slack/chat.}
────────────────────────────────────────
Save to: 04-workspace/ceo-office/1on1s/{person}/followups/{date}-followup.md
If the followups/ subfolder doesn't exist, create it.
Keep each note to 1-2 sentences max. Be specific — quote the transcript.
WORKED — Pick ONE moment. Not generic praise. Reference what was said.
IMPROVE — Pick ONE thing. Give the alternative phrasing.
ASK NEXT TIME — Based on unresolved topics or commitments from THIS meeting.
SEND MESSAGE — A short message to send to the person after the meeting.
User: "1on1 followup with Brad"
AI: [Fetches latest Brad transcript]
═══════════════════════════════════════
1ON1 FOLLOW-UP — Brad, 2026-02-05
═══════════════════════════════════════
⏱ 9 min | Repeatable recruitment workflow, beachhead strategy
────────────────────────────────────────
📋 COMMITMENTS
────────────────────────────────────────
YOUR commitments:
- [ ] Figure out landing page / funnel / "makeup" for recruitment suite — TBD
- [ ] Chat tomorrow re: meetings to set up
THEIR commitments:
- [ ] Identify the ONE recruitment workflow to sell 100 times — TBD
- [ ] Complete messaging/materials for UNLEASH — TBD
- [ ] Coordinate with Accenture on finance/banking needs — TBD
⚠️ OPEN LOOPS:
- No deadline on "the ONE thing" — when does Brad decide?
- UNLEASH timeline not specified — what's the event date?
────────────────────────────────────────
💡 3 COACHING NOTES
────────────────────────────────────────
✅ WORKED: Direct challenge — "Sell me resume screening 100 times.
That's all I care about." Clear, specific, no hedging.
⚠️ IMPROVE: You took the "makeup" work onto yourself ("I'll figure
out the makeup part"). Push it down: "You own the positioning.
Show me a one-pager by Thursday."
❓ ASK NEXT TIME: "What's the ONE product? Show me the plan."
— This is your barrel test.
────────────────────────────────────────
✉️ SEND TO Brad
────────────────────────────────────────
Hey, good chat. So the play is clear — you pick the ONE
workflow we can sell 100 times. Resume screening, whatever
it is, but pick it. I'll sort the landing page and funnel
so we look the part.
Your side:
• Decide the one repeatable product
• UNLEASH messaging/materials
• Accenture — scope what finance/banking needs
Let's regroup Thursday — show me what you've got.
────────────────────────────────────────
Micro-skill: Capture fast, coach in 3 bullets, send the message, move on.
tools
Build a Palantir-shape, PDF-native use-case proposal document for a sophisticated enterprise account: research-grounded use cases (each with description, challenge, impact, value), an operating-graph ontology page, a recommended PoC with a week-by-week plan, and a closing page that asks for one decision. Load when a client asks us to 'propose high-impact use cases', requests a use-case presentation/catalog for a function (finance, HR, ops), or when a technical evaluation team will review candidates to pick a PoC. NOT for single-account cold outreach (use prospect-brief), full process diagnostics (use operating-diagnostic), or priced proposals (use proposal-creation).
development
Convert Beam Figma slide designs into high-fidelity, editable HTML presentation decks. Use when Codex is asked to audit Figma slides, extract slide templates, rebuild Beam slides as HTML decks, decide whether Figma imagery should be exported or rebuilt in HTML/CSS, create Beam/Prism-compatible deck templates, or improve fidelity of existing Beam HTML slide rebuilds.
development
Use the Beam AI reusable slide library: individual HTML slide templates extracted from Beam Figma rebuilds, kept separate from deck themes and full deck templates. Load when the user asks for a slide library, specific Beam slide patterns, reusable Figma-inspired slides, Prism slide-library items, or slide-level HTML templates.
development
Use Beam AI deck and report design packs, HTML templates, and curated examples to create sales decks, customer intro decks, RPO decks, and DIN A4 use-case proposal reports. Load when the user asks for Beam-branded presentation templates, Prism-compatible deck templates, Beam report templates, customer intro decks, commercial proposals, or reusable HTML deck/report examples.