Skill

1:1 prep

Build a context dossier for an upcoming 1:1 — recent Slack with this person, their Notion pages, their shipped work, open items they own, last 1:1 notes. Read-only.

npx claudepluginhub sitloboi2012/team-marketplace --plugin role-ceo

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Assembles the context you need to walk into a 1:1 informed. Read-only — no outbound actions.

SKILL.md

Similar Skills

cache-components

139.3k

Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.

cache-components

mcp-builder

124.2k

Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).

9 files

anthropics-skills-13

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitApr 23, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

1:1 prep

Assembles the context you need to walk into a 1:1 informed. Read-only — no outbound actions.

Workflow

1. Identify the person

From $ARGUMENTS, resolve to a specific teammate. If there's ambiguity (two people with the same first name), ask.

2. Find the last 1:1

Search Notion under the CEO's 1:1 notes path (ask if not set). If found, use its date as the window start. If not, default to 2 weeks back.

3. Pull (in parallel)

Slack: direct messages with this person in the window. Also their activity in channels you're both in — look for things they shipped, things they were stuck on, notable debates.
Notion: pages this person owns or was last-edited-by in the window. Specs, decisions, retros.
GitHub (if MCP enabled): PRs they opened or reviewed.
Calendar: meetings they organized or you both attended (useful context for follow-ups).
Fathom: recent meetings they attended and any action items tagged to them.
Last 1:1 notes: action items from last time. Which got done, which didn't, which need to carry over.

4. Synthesize

Don't dump. Filter to what's worth 20-30 min of conversation.

# 1:1 prep — <person> — <today>

**Last 1:1:** <date, N days ago>

## Open from last time
- [ ] <action item> — status: <done | in flight | carryover>

## What they shipped / drove
- <one line>

## What they're working on now
<1-3 bullets. Focus on things you haven't already seen in public Slack or status updates.>

## Signals worth asking about
- <specific observation the user might not have tracked: stuck on X, changed tone on Y, went quiet in #channel>
- <relationship-type signal: is a peer friction showing up? a growth area?>

## Things they might raise
- <based on their Slack / Notion activity — what's top of mind for them>

## Suggested topics
<3-5 questions the CEO could lead with. Specific, not "how are things.">

## Don't forget
- <small personal context if you have it — last time they mentioned X, they were taking vacation Y, a recent birthday / work anniversary>

5. Don't

Don't present surveillance. This is to help the CEO be a good manager, not to catalog the person's day.
Don't speculate about feelings or motives. Report signals; let the CEO interpret.
Don't include anything from the person's DMs with other people. Stay within what the CEO already has access to.
Don't auto-write this to Notion. 1:1 notes go in Notion during or after the meeting, not before.