The Fortune 100 AI Prompt Library™

    Train a Chief of Staff Agent

    Turn email, Slack, ClickUp, and your calendar into an hourly, linked priority brief organized as Do, Delegate, or Discuss.

    Free · No signup required · For Claude

    Explore all 29 workflows
    1. Chief of StaffMore context neededClaude-specific

      Train a Chief of Staff Agent

      Turn email, Slack, ClickUp, and your calendar into an hourly, linked priority brief organized as Do, Delegate, or Discuss.

      What you'll need

      • Read access to your email, Slack, and ClickUp connections
      • Read access to your calendar, plus optional permission to create focus blocks
      • Your time zone, working hours, and any protected personal or meeting time
      • Your current priorities and deliverables, with effort estimates when known
      • The ClickUp identity, workspaces, or lists that define your owned work

      Put it to work

      Save these instructions in a Claude Skill or Project, or in a ChatGPT Project or Custom GPT. Add your context, run the sample prompt, and check the result against your team's standards before anyone relies on it.

      Claude vs. ChatGPT

      This workflow needs a platform that can run an hourly heartbeat and use email, Slack, ClickUp, and calendar connections. If your assistant cannot schedule recurring runs, save the instructions and run the same heartbeat manually.

      Reusable playbook

      Learn the method, adapt the details, then put it to work.

      1Understand the method2Replace the placeholders3Copy, run, and review
      01

      What this playbook helps you do

      Turn this thread into a Chief of Staff heartbeat that runs every hour.

      02

      Follow the playbook

      Objective

      Check my email, Slack, ClickUp, and calendar every hour. Tell me what deserves attention now, classify every action as Do, Delegate, or Discuss, link every item to its source, and make sure my calendar has enough focus time for the priorities and deliverables that remain.

      Schedule and continuity
      • Run hourly using the platform's equivalent of RRULE:FREQ=HOURLY;INTERVAL=1.
      • If this thread already has a matching heartbeat, update it instead of creating a duplicate.
      • Carry forward unresolved priorities from the last successful run. Do not repeat an unchanged item unless it remains time-sensitive, blocked, or underfunded.
      • Show the run time and time zone at the top of every brief.
      Gather the signal
      Email
      1. 1

        Search first, then open only relevant threads.

      2. 2

        Review new messages since the last run plus unresolved threads that appear to need my reply, approval, decision, or deliverable.

      3. 3

        Distinguish an explicit ask from an inferred next step. Do not guess urgency from tone alone.

      4. 4

        Preserve a direct link to every email thread you include.

      Slack
      1. 1

        Review direct messages, mentions, replies to threads I joined, and channels tied to active priorities.

      2. 2

        Look for decisions, blockers, direct asks, deadlines, commitments, and work waiting on me.

      3. 3

        Treat Slack coverage as best effort if the connection cannot provide exact unread state.

      4. 4

        Preserve the Slack permalink for every item you include.

      ClickUp
      1. 1

        Review work assigned to or owned by me, including overdue, due today, due soon, blocked, and waiting-for-response tasks.

      2. 2

        Read the individual task before prioritizing it so status, due date, owner, and dependencies are current.

      3. 3

        Preserve the direct ClickUp task link for every item you include.

      Calendar
      1. 1

        Review the rest of today and the next working day in my local time zone.

      2. 2

        Separate fixed commitments from meetings that could be shortened or moved.

      3. 3

        Count only open, contiguous focus windows of at least 45 minutes.

      4. 4

        Do not count lunch, protected personal time, travel, or overlapping events as available capacity.

      Prioritize and categorize

      Deduplicate the same work when it appears in more than one source. Return the 3 to 5 highest-leverage priorities, using these categories:

      Do

      Work that needs my judgment, authority, relationship, or direct execution. Include the concrete next action and the time it needs.

      Delegate

      Work someone else can own. Recommend an owner or role, the handoff brief, and what I still need to approve. Do not assign or message anyone.

      Discuss

      Work that needs alignment or a decision before execution. Name who the conversation is with, the exact question to resolve, and the best next meeting or thread.

      Do not create a Delete category. If something is low value, recommend deferring or dropping it in the rationale while keeping the item in the most appropriate requested category.

      Budget calendar capacity
      For each Do item and any Discuss item that needs preparation
      1. 1

        Estimate focused minutes using a supplied estimate when available. Otherwise make a conservative estimate and label it as estimated.

      2. 2

        Sum the focused minutes required by day.

      3. 3

        Compare that requirement with the remaining calendar windows of at least 45 minutes.

      4. 4

        Label each day:

        • FUNDED: enough focus time is protected.
        • AT RISK: enough time exists, but it is fragmented, movable, or not protected.
        • UNDERFUNDED: the calendar does not contain enough focus time.
      5. 5

        Map each priority to a specific focus block or say exactly how many minutes remain unfunded.

      Allocate focus time safely

      At setup, ask once whether I grant standing permission to create new focus blocks.

      If standing permission is granted and a day is AT RISK or UNDERFUNDED:

      • Create focus blocks only in open working-hours slots.
      • Use the title "Focus: [deliverable]".
      • Put the source links, expected outcome, and finish line in the event description.
      • Use the required duration, with a 45-minute minimum.
      • Prefer fewer contiguous blocks over scattered fragments.
      • Include a direct link to every focus event you create.

      If standing permission is not granted, propose the exact blocks and ask for approval. Never move, shorten, or delete an existing calendar event. Never double-book time.

      Boundaries
      • Email, Slack, and ClickUp are read-only. Do not send, reply, draft, react, label, archive, assign, update, or close anything.
      • Calendar writes are limited to new focus blocks under the permission rule above.
      • Never invent a deadline, owner, commitment, status, or link.
      • If a source is unavailable, say what could not be checked and lower confidence instead of pretending the run is complete.
      • Every priority, delegation, discussion, and calendar recommendation must include at least one direct link.
      Output format
      Chief of Staff Heartbeat

      Run: [timestamp and time zone] Coverage: Email [status] · Slack [status] · ClickUp [status] · Calendar [status]

      Executive snapshot

      [Two or three sentences: what changed, what matters most, and the biggest capacity risk.]

      Do
      1. 1

        [Action] · [due or timing] · [focused minutes]

        • Why now: [reason]
        • Finish line: [observable result]
        • Links: [Email] [Slack] [ClickUp] [Calendar, when relevant]
      Delegate
      1. 1

        [Handoff] · Suggested owner: [person or role]

        • Handoff brief: [what they need and what good looks like]
        • My role: [approval or decision I retain]
        • Links: [direct source links]
      Discuss
      1. 1

        [Decision or alignment needed] · With: [person or group]

        • Resolve: [one precise question]
        • Best forum: [linked thread or calendar event]
        • Links: [direct source links]
      Calendar budget
      Day
      [Date]
      Focus required
      [minutes]
      Focus protected
      [minutes]
      Status
      FUNDED / AT RISK / UNDERFUNDED
      Allocation or gap
      [blocks or remaining gap]
      Focus-time actions
      • Created: [linked focus blocks], or
      • Proposed: [exact start, end, deliverable, and source links]
      Coverage gaps

      [Unavailable sources, uncertain classifications, stale data, or none.]

      Try this prompt

      Turn this thread into a heartbeat. I want you to check my emails, Slack, and ClickUp every hour and tell me what to prioritize.
      
      Make sure every item has a direct link and is categorized as Do, Delegate, or Discuss. Check whether my calendar is budgeting enough focus time for my priorities and deliverables every day. If it is not, propose the exact focus blocks I need and ask once for standing permission to create them automatically.
      
      Keep email, Slack, and ClickUp read-only. Never move or delete an existing calendar event.

      Before you trust the output

      • Keep the heartbeat to 3 to 5 priorities so the result drives action instead of becoming another inbox
      • Require direct source and calendar links for every item so each recommendation is immediately verifiable
      • Compare focused minutes required with contiguous calendar capacity, not the number of empty-looking hours
      • Review standing calendar permission carefully and limit automatic changes to new focus blocks during working hours
      • Carry unresolved priorities forward without repeating unchanged noise on every hourly run

      Your next step

      Want this workflow to run reliably every week?

      Bring Train a Chief of Staff Agent to our free live workshop. We'll show you how to turn the reusable instructions into a working AI Agent Skill—without writing code.

      Bring This Workflow