Skip to content
skills-il

1:1 tracker for each report

Build a skill that keeps a rolling agenda, last week commitments, and what you owe each direct report.

The more specific the description, the higher the quality of the skill.240 / 2000

Don't paste passwords, API keys, ID numbers, account details, or real document content. Describe in general terms.

More generators

Why a custom skill beats a one-off prompt for 1:1 tracking

Running 1:1s is one of the most personal-team things there is. The skill needs to know your reports, the style each one likes, and the history between you. Another manager's setup looks completely different. A one-off prompt cannot carry the context that accumulates over months. A personal skill can.

What makes this skill specifically yours

  • Your direct-report roster: 3-12 people you manage. The skill keeps a small file on each, what you discussed, and what is still open.
  • Your management style: direct and crisp? patient and listening? generative with ideas? The skill picks up on your style and helps you stay consistent, even on busy weeks.
  • The commitments you make: as a manager you make promises to your reports, and sometimes you forget. The skill extracts them from the meeting and reminds you.

Three things to include in your description

  1. A people roster: name, role, current project, communication style, and topics worth being sensitive about.
  2. Your 1:1 structure: what do you typically ask? "What do you want to talk about?", "What is your biggest blocker this week?", or a fixed list. The skill will draft an agenda in your structure.
  3. Where the agenda lives: a Markdown file per report, Notion, or a Google Sheet. The skill reads, updates, and remembers.

What this skill is NOT

This is not a performance-management tool. It does not score, does not document evals, and is not a formal record for promotion calls. It is your small chief-of-staff, reminding you of what you promised and what is still open. Formal documentation stays in your HR system.

Drop our catalog a look first

If you want a generic management-comms skill maintained for everyone, check the agentskills.co.il/en/categories/communication catalog. The generator is for the parts that are uniquely yours.

FAQ

How does the skill know each report?
Describe each one in 2-3 lines in the seed: name, role, what they are working on, and how they like to communicate. You can also point the skill at a folder you maintain on each.
Where does the rolling agenda live?
Option one, a Markdown file per report that you maintain. Option two, Notion or Roam. The skill reads the file before each meeting and updates it after. I recommend Markdown, simple and version-able.
What about sensitive notes?
The skill should not see all your thoughts, only the agenda and follow-ups. Performance notes, promotion deliberations, keep those outside the file the skill reads.
How is this different from Notion or Granola?
Notion is an empty form. The skill actually asks you the right questions before each meeting: "You owed Dani feedback on the doc, did you send it?", "Shelly mentioned wanting growth, have you opened that conversation?" It behaves like a small chief-of-staff, not a spreadsheet.