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.
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.
development
--- name: taste-skill type: skill version: '1.0' author: Leonxlnx (packaged by Zhichao Li) category: general tags: - frontend - design - anti-slop - landing-page updated: '2026-06-11' visibility: public description: Anti-slop frontend skill for landing pages, portfolios, and redesigns. The agent reads the brief, infers the right design direction, and ships interfaces that do not look templated. Real design systems when applicable, audit-first on redesigns, strict pre-flight check. license: MIT.
development
Use when communicating quantitative information in any form — Slack updates, emails, reports, decks, dashboards, landing pages, product UI, public talks. Covers two integrated layers: (1) making numbers semantically meaningful (translation, anchoring, simplification, story-pairing) and (2) showing numbers cleanly (chart vs table vs prose, chart-by-message, pre-attentive emphasis, color discipline, decluttering). Distilled and integrated from *Show Me the Numbers* (Stephen Few) and *Make Numbers Count* (Chip Heath & Karla Starr). Not for raw data analysis or statistics — this is about communication of numbers, not their derivation.
development
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.
tools
Stateful multi-session tutor adapted for Beam — teach a stakeholder to understand, trust, and operate a specific agent, or teach a Solution Engineer a client's business process for delivery. Grounds every lesson in Knowledge Hub sources (real agent graphs, real tasks, transcripts, Linear) before any web resource. Also works for any general topic. Trigger on "teach me", "beam teach", "教我", "onboard <person> on <agent>", "help <stakeholder> understand the agent", "learn this client's process".