skills/general/1on1-prep/SKILL.md
Prepare for an upcoming 1-on-1. Triggers: 'prep my 1on1 with [name]', '1on1 prep', 'prepare for my meeting with [name]', 'what should I cover with [name]', 'get ready for 1on1'.
npx skillsauth add beam-ai-team/beam-next-skills 1on1-prepInstall 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.
Generate a sharp prep sheet before a 1-on-1. Pulls open commitments, unresolved loops, and patterns from prior meetings so you walk in with a plan, not an improvisation.
Before reading prior transcripts, follow-ups, or coaching reviews, show the person, context folders, date range, and whether sensitive feedback will be included. Require explicit user approval in the current turn before writing a prep sheet or updating any commitment tracker. Do not send agenda notes, create tasks, or share prep externally from this skill.
When to use: 5-10 minutes before a 1-on-1 Time: ~2 minutes Output: 1-page prep sheet with opener, accountability check, and push topics Inputs: Prior transcripts, follow-ups, coaching reviews for that person
User: "prep my 1on1 with Brad"
→ Look in 04-workspace/ceo-office/1on1s/brad/
If no name: ask "Who's the 1-on-1 with?"
Pull from these sources in order:
Latest follow-up: 04-workspace/ceo-office/1on1s/{person}/followups/ — most recent file
Last 2-3 transcripts: 04-workspace/ceo-office/1on1s/{person}/transcripts/ — most recent 2-3 files
Latest coaching review (if exists): 02-projects/Beam/10-1on1-excellence/04-outputs/{person}/
═══════════════════════════════════════
1ON1 PREP — {Person}, {Date}
═══════════════════════════════════════
Last meeting: {date} ({days} days ago) | {1-line summary}
────────────────────────────────────────
🎯 OPEN WITH
────────────────────────────────────────
"{Specific opening question — based on their biggest
open commitment from last time. Not 'how are things?'
but 'Show me X that you committed to.'}"
Why this opener: {1 sentence — what it tests or unblocks}
────────────────────────────────────────
📋 ACCOUNTABILITY CHECK
────────────────────────────────────────
THEIR open commitments (from last meeting):
- [ ] {Commitment} — status: {Unknown/Overdue/Due}
- [ ] {Commitment} — status: {Unknown/Overdue/Due}
YOUR open commitments (from last meeting):
- [ ] {Commitment} — have you done this? {Yes/No/Partial}
- [ ] {Commitment}
💀 DEAD ITEMS (committed but never followed up):
- {Item from 2+ meetings ago that was never revisited}
────────────────────────────────────────
🔥 PUSH TOPICS
────────────────────────────────────────
1. {Topic to push on} — Why: {context from transcripts}
→ Ask: "{Specific question}"
2. {Topic to push on} — Why: {context}
→ Ask: "{Specific question}"
3. {Topic to push on} — Why: {context}
→ Ask: "{Specific question}"
────────────────────────────────────────
⚡ COACHING FOCUS (for yourself)
────────────────────────────────────────
Based on your last review/follow-up, focus on:
• {One behaviour to practice in THIS meeting}
Avoid:
• {One pattern to break — from prior coaching notes}
────────────────────────────────────────
Save to: 04-workspace/ceo-office/1on1s/{person}/preps/{date}-prep.md
If the preps/ subfolder doesn't exist, create it.
The opener is the most important line. It sets the tone for the entire meeting.
BEFORE meeting: 1on1-prep ← you are here
AFTER meeting: 1on1-followup ← capture commitments + coaching notes
WEEKLY/BIWEEKLY: 1on1-review ← deep expert analysis
The prep skill feeds from follow-up outputs. The follow-up feeds into the next prep. The review catches patterns the cycle misses.
┌─────────┐ ┌──────────────┐ ┌─────────────┐
│ PREP │────→│ MEETING │────→│ FOLLOW-UP │
│ (before)│ │ (the 1on1) │ │ (after) │
└────▲────┘ └──────────────┘ └──────┬──────┘
│ │
└───────────────────────────────────────┘
feeds into
┌─────────────┐
│ REVIEW │ (weekly/biweekly deep dive)
│ (5 experts) │
└─────────────┘
User: "prep my 1on1 with Brad"
AI: [Loads brad/followups/2026-02-05-followup.md]
[Loads last 2 brad transcripts]
[Loads brad coaching review if exists]
═══════════════════════════════════════
1ON1 PREP — Brad, 2026-02-10
═══════════════════════════════════════
Last meeting: 2026-02-05 (5 days ago) | ONE repeatable product, makeup/funnel
────────────────────────────────────────
🎯 OPEN WITH
────────────────────────────────────────
"Last time I asked you to pick the ONE workflow we sell
100 times. What is it? Show me the plan."
Why: This was the central commitment. If he doesn't
have it, nothing else matters.
────────────────────────────────────────
📋 ACCOUNTABILITY CHECK
────────────────────────────────────────
THEIR open commitments:
- [ ] Pick the ONE repeatable product — status: Unknown
- [ ] UNLEASH messaging/materials — status: Unknown
- [ ] Accenture finance/banking scoping — status: Unknown
YOUR open commitments:
- [ ] Landing page / funnel / "makeup" — have you done this?
- [ ] Chat about meetings to set up — did this happen?
💀 DEAD ITEMS: None (first follow-up cycle)
────────────────────────────────────────
🔥 PUSH TOPICS
────────────────────────────────────────
1. The ONE product — Why: Brad agreed but didn't explicitly
name it. He drifted to "suite" thinking multiple times.
→ Ask: "Name it. One sentence. What do we sell 100x?"
2. UNLEASH prep — Why: Event date unknown, materials unstarted
→ Ask: "When is UNLEASH? What's ready? What's not?"
3. Pipeline — Why: Brad said most prospects are "middle of
nowhere America." NYC is covered.
→ Ask: "How many meetings this week? Show me the list."
────────────────────────────────────────
⚡ COACHING FOCUS (for yourself)
────────────────────────────────────────
Practice: End every commitment with a deadline. Don't let
"I'll do it" fly without "by when?"
Avoid: Taking work onto yourself. Last time you said
"I'll figure out the makeup part." Push it down.
────────────────────────────────────────
Micro-skill: Walk in with a plan. Open with accountability. Push on 3 things. Get out.
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.