← Back to library

Prepare a focused brief for your next skip-level 1:1

ehnruiz published an open-source leader-1-1-prep skill that has a coding agent read your past one-on-one notes, recent tickets, chat threads and pending drafts, mark each old item closed, open or dropped, then draft a fixed thirty-minute agenda for the next skip-level.

  • OutcomeBefore a recurring 1:1 with a senior leader, have an agent check what carried over from last time, gather what changed since and draft a short agenda with at most two asks, plus an after-meeting checklist.
  • SetupUnder an hour
  • LevelIntermediate
  • Creditehnruiz
View original
Works with
Claude CodeClaude Cowork

Published Oct 23, 2026Updated Oct 23, 2026AI dry run on sample input: passed Oct 23, 2026Source verified Oct 24, 2026

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?

  1. Install the skillAdd the skill from the repository to your agent and connect the notes, tracker and chat tools you are allowed to use.
  2. Run it the day beforeAsk the agent to prepare your brief for the named leader and keep the file open for edits.
  3. Narrow the asksCut the decisions section to the two items where you truly need the leader's action.
  4. 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)

Prompt3 variables
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?
No coding is involved, but you install the skill in an agent such as Claude Code and connect your work tools, which takes some setup.
Why a fixed agenda?
The skill uses the same five blocks every time so the meeting does not slide into a status report and people topics are never skipped.
What license is it under?
The repository is MIT licensed by Emmanuel Ruiz, so you can use and adapt it with the copyright notice kept.

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.

More in Operations & Admin

All 203 Operations & Admin playbooks →

Related playbooks

Operations & AdminSkill✓ AI dry run

Have Claude fill PDF forms, even ones with no fields

Give Claude the pdf skill so that when you hand it a form and the answers, it first checks whether the file has real form fields, fills those by their IDs if it does, places text by measured coordinates on flat or scanned forms if it does not, validates every box before writing, and renders the filled pages as images so you can see where each answer landed before you sign or send it.

Credit: Anthropic

Minutes
Operations & AdminWorkflow✓ AI dry run

Fill PDF forms from your own documents with an agent

Upload a fillable PDF and the documents that hold the answers; the agent stages a value for each field, shows you the pending edits and saves the filled form.

Credit: Jerry Liu (@jerryjliu0)

Under an hour
Operations & AdminWorkflow✓ AI dry run

Have a desktop agent learn your folder of work scripts

Point a desktop agent at the folder of small scripts you rely on and get a catalog it can use, so you can run them by asking in plain words.

Credit: Tomasz Tunguz (@ttunguz)

Under an hour
Operations & AdminWorkflow✓ AI dry run

Map the onboarding process before building an AI agent

A clear picture of where onboarding time actually goes, and the simplest fix, which may be plain automation rather than AI.

Credit: u/Actual-Struggle9480 on r/u_Actual-Struggle9480

An afternoon+
Operations & AdminRoutine✓ AI dry run

Run an AI executive assistant on Claude Code

Email triage, calendar booking, shared docs and a morning briefing from one agent setup.

Credit: Nelson Amenya (@amenya_nelson)

An afternoon+