skills/running-effective-1-1s/SKILL.md
Help users run effective one-on-one meetings. Use when someone is a new manager setting up 1:1s, struggling to make 1:1s productive, wants to improve career conversations with reports, or needs to handle difficult 1:1 situations.
npx skillsauth add cvillamarp-lgtm/skillspodcast running-effective-1-1sInstall 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.
Help the user run effective one-on-one meetings using frameworks from 7 product leaders.
When the user asks for help with 1:1s:
Rachel Lockett: "Great leaders know that when you try to advise and have the answer all the time, you're not actually equipping your team to go solve the hard problems. You're training your team to come to you with all of the hard problems." Shift energy into curiosity when a report brings a hard problem. Avoid the urge to provide the answer immediately.
Kim Scott: "I would have three separate 45 minute conversations, so one about their past, one about their future, and one about their present to create a plan." Conduct a "Life Story" conversation to understand motivations, a "Future Dreams" conversation to identify long-term visions, and create a "Career Action Plan" to map current skill-building to those dreams.
Hilary Gridley: "In my one on ones... I'm asking them, 'What do you do for joy? Are you doing something every single day that's bringing you joy in your life?' And if they say no, I'm like, 'That's a problem.'" Ask reports directly about what brings them joy outside of work. Treat a lack of daily joy as a performance risk that needs a plan.
Howie Liu: "I actually cut my one-on-one roster by default... Just having more standing one-on-ones actually precludes me from engaging in more timely topics." Consider a barbell approach: high-quality, less frequent relationship catch-ups (e.g., monthly walks) vs. urgent topical meetings scheduled as needed.
Matt Mochary: "With each and every person on the stay team, you have a one-on-one with their manager for one hour and all the manager does is say, 'I'd like to know your thoughts and feelings,' and the person shares and then all the manager does is make them feel heard." Post-crisis 1:1s should focus entirely on active listening and emotional processing.
The report should own the agenda. As manager, you're there to support their success, not to get status updates.
For all 10 insights from 7 guests, see references/guest-insights.md
testing
Help users communicate more effectively in writing. Use when someone is drafting memos, emails, strategy docs, announcements, or any written communication that needs to be clear, concise, and persuasive.
documentation
Help users write effective specs and design documents. Use when someone is creating technical specs, feature specs, design docs, or trying to communicate product requirements to engineering and design teams.
development
Help users write effective PRDs. Use when someone is documenting product requirements, preparing specs for engineering, writing feature briefs, or defining what to build for their team.
tools
Help users define their North Star metric. Use when someone is choosing their primary success metric, trying to align the team around a key measure, struggling with metric proliferation, or setting up their measurement strategy.