When should you use it?
- You meet a skip-level or senior leader on a regular schedule and the meetings drift into status updates
- Commitments from the last meeting tend to disappear
- You want one question about your own development ready each time
Not for: Performance reviews or formal HR conversations; Workspaces where you are not allowed to give an agent read access to notes, tickets or chat
What do you need, and what do you get?
You need
- Claude Code or another agent that loads skills, with the skill installed
- Read access to your 1:1 notes page, ticket tracker and chat with that leader
- The leader's name and the date of the meeting
You get
- A one-screen Markdown brief named for the leader and date
- Status of every item from the last meeting
- A five-part agenda with no more than two asks
- A list of topics deliberately left out and an after-meeting checklist
How does it work, step by step?
- Install the skillAdd the skill from the repository to your agent and connect the notes, tracker and chat tools you are allowed to use.
- Run it the day beforeAsk the agent to prepare your brief for the named leader and keep the file open for edits.
- Narrow the asksCut the decisions section to the two items where you truly need the leader's action.
- Close the loopWithin an hour after the meeting, log the decisions, turn commitments into tickets and write next time's growth question.
The prompt
Our adapted version, written to work in Claude Code and Claude Cowork. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
Use the leader-1-1-prep skill to get me ready for my 1:1 with {leader_name} on {meeting_date}. Sources you may read: {allowed_sources}. Do not read anything else and do not post or create anything. Tell me which sources you could not reach. Keep the brief to one screen and give me no more than two asks.
The original skill is published by ehnruiz on GitHub. Open it there to install or import it; the prompt above is our own adaptation.
What can go wrong?
- The agent can only report what it can reach; read its list of sources it could not check.
- Chat threads can hold sensitive people matters; keep the brief private and out of shared folders.
- A brief that runs past one screen usually means the asks are still too broad.
- Do not let the agent post updates or create tickets without your review.
Our take
Most meeting-prep prompts summarize; this skill is opinionated about what a good skip-level meeting contains, and that is why we picked it. It caps the asks at two, keeps a people block even when time is short, rotates a question about your own growth and makes you write down what you will not raise. The carry-forward check is the quiet win: every old item is marked closed, open or dropped, and something open twice in a row must be discussed or dropped on purpose. We exercised the skill with our own invocation prompt on a fictional engineering manager preparing for a meeting with a director, using a notes page with five items from last time, eight tickets, a chat thread and one pending design doc. The brief marked the roadmap item closed, the offsite idea dropped with a stated reason and three items open, moved the vendor renewal onto the agenda because it was open for a second meeting, proposed two asks (a backfill approval and a decision on that renewal), put a contractor's performance under people, listed tool-level updates under topics to leave out and fit on one screen. It also noted that the calendar was not connected. You need an agent with access to your work tools, so this suits people already using Claude Code or Cowork at work.
Where the time goes back: Gathering last meeting's notes, tickets and threads by hand takes a while before every 1:1; the agent assembles it and you spend the time sharpening the asks.
FAQ
Do I need to be a developer?
Why a fixed agenda?
What license is it under?
Source and credit
This playbook is based on work by ehnruiz. We summarize it and link to it and write our own adapted prompt.
- Original
- leader-1-1-prep skill (ehnruiz/claude-skills)
- Creator
- ehnruiz
- Published on
- GitHub
- Original date
- Oct 15, 2026
- License
- MIT
- Originally for
- Claude Code
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. Skill exercised via our invocation prompt; no posting or ticket creation.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 24, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
The original is licensed under the MIT License (Copyright (c) 2026 Emmanuel Ruiz). Modified: our adapted prompt and summary are our own wording; the original is unchanged at the source link.
Are you the creator? Claim or correct this page.