How to Make Your AI Agent Actually Useful

Your AI can read your emails and check your calendar, yet its morning brief can still leave you wondering what to do first.

Access gives it information. Useful instructions explain how that information relates to your day. Start with three things: context, priorities, and rules.

This is the companion guide to How to Make Your AI Agent Actually Useful. You will turn a generic daily summary into a brief that identifies replies, meeting preparation, and the work that deserves your attention. The complete prompt below is the RULES template mentioned in the video.

Already have a daily briefing task? Update that task with these instructions. If you still need to connect your accounts and create one, start with Create an AI Daily Brief with Claude Cowork.

The three things your agent needs

1. Context: what should a good day look like?

Tell the agent your role, what you are working on, and the time you want to protect. A job title alone leaves too much open to interpretation.

In the video's example, the person is a content creator making AI educational videos. Their best focus hours are 9:00 AM to 12:00 PM, and they want uninterrupted time for writing and filming. Research, scripts, filming, editing, and publishing all belong to their work.

That context gives the agent a reason to suggest a morning focus block instead of treating every free slot as interchangeable. It does not make the calendar free: an existing meeting still has to be acknowledged.

Write your own version in three or four short lines:

• What is your role, and what are you trying to finish this week?

• Which activities need uninterrupted time?

• When do you usually do your best focused work?

• Which commitments are fixed?

Use details that change a decision. A current project and a real deadline are more useful here than a long biography.

2. Priorities: what deserves attention first?

“Summarize my inbox” describes a source. “Find urgent emails that require a reply from me” describes a decision the report should help you make.

The video focuses on three outputs:

1. Urgent replies: messages that need an action from you, with the reason they are time-sensitive.

2. Meeting preparation: today's meetings and anything you need to review or bring.

3. Top three tasks: a proposed order based on deadlines, commitments, and impact.

Make the ranking concrete. For example, put commitments due today first, work that blocks someone else next, and important upcoming work after that. Adjust that order to your role.

Ask for the reason behind each proposed priority. “Finish the script” is more useful when it explains that filming is booked tomorrow. If the source does not contain a deadline, the agent should say so. If only two tasks are supported, it should return two.

3. Rules: what may the agent do?

Rules define both the report and the boundary around it. For this daily brief:

• Keep the entire brief under 200 words.

• Include source references where available.

• Separate confirmed facts from recommendations.

• Never invent missing information.

• Report unavailable sources clearly.

• Do not send emails, edit tasks, or change calendar events.

The video says changes need your approval. The template below uses a stricter starting point: this task only produces a brief. A suggested reply is something for you to review; a suggested focus block is not a calendar booking.

Instructions do not change account permissions. Review the connector tools and permissions separately, and block write actions where supported if this task only needs reading. Claude's connector documentation explains how connected services and their permissions work.

Copy the complete RULES template

This is the complete prompt from the video's companion notes. It uses the content creator example; personalize it before relying on the result.

Every weekday at 7:00 AM, create my personalized Daily Brief using my connected Gmail, Calendar, and Notion.

CONTEXT
- I am a content creator working on AI educational videos.
- My best focus hours are 9:00 AM to 12:00 PM.
- I want to protect uninterrupted time for writing and filming.
- My typical tasks include research, scripts, filming, editing, and publishing.

PRIORITIES
1. Identify urgent emails that require a reply.
2. Show today's meetings and any preparation required.
3. Identify the top 3 tasks based on deadlines, commitments, and impact.
4. Highlight any schedule conflicts or urgent blockers.

RULES
- Keep the daily brief under 200 words.
- Include source links or references where available.
- Separate confirmed facts from your recommendations.
- Never invent missing information.
- Do not send emails, edit tasks, or change calendar events.
- If any connected source is unavailable, clearly say so.

OUTPUT
1. Urgent Emails
2. Today's Schedule
3. Top 3 Priorities
4. Suggested Focus Block
5. Risks or Blockers

Make the template yours

Step 1: replace the example context

Change the role, current project, focus hours, and typical tasks. Keep the reading and reporting boundary unless you deliberately design a different workflow.

For example, a project manager might protect an afternoon planning block and prioritize decisions that unblock the team. A student might focus on assignment deadlines and exam preparation. These are possible adaptations, not claims that the template has been tested for every role.

Step 2: name the sources and time zone

“My tasks” can mean several different lists. Add the exact Notion page or database, the calendars to check, and a bounded email lookback. Explain custom fields such as the task owner and completion status.

Copy this optional add-on after the complete template, then replace every bracketed field:

Use these details with the Daily Brief instructions above:

Time zone for the 7:00 AM weekday schedule and all dates/times: [YOUR NAMED TIME ZONE]
Notion task page or database: [LINK]
Task owner and incomplete-status fields: [FIELDS AND VALUES]
Calendars to check: [CALENDAR NAMES]
Current project or goal: [PROJECT OR GOAL]
Important senders or commitments: [NAMES OR COMMITMENTS]

Check emails from the past 24 hours and unresolved messages from the past 7 days that require a reply from me. Exclude newsletters and promotions unless they contain a relevant commitment.

Consider only my incomplete tasks. Rank commitments due today first, then blockers affecting other people, then important upcoming work. Give one short reason per priority. Return fewer than three if the sources support fewer. Do not invent deadlines.

Treat calendar events and explicit source deadlines as facts. Label proposed task rankings and preparation not requested in the source as recommendations. Check for conflicts before suggesting a focus block. If no suitable block is free, say so; do not move a meeting or create an event.

Keep all five output sections together under 200 words. If a source is unavailable, mark the brief as incomplete and identify what could not be checked. Missing access does not mean there are no tasks or meetings. Keep the original no-send, no-edit, no-calendar-change rules.

Choose a named time zone such as Asia/Shanghai or America/New_York. A travel day should not silently change which “today” the brief uses.

Step 3: update the saved task

Open the existing daily brief in Scheduled and edit its instructions. Replace the older briefing prompt with the complete template and your filled-in details. Keep one consistent word limit and one recurrence; if you used the setup guide's 400-word add-on, replace that limit with under 200 words.

Review the saved schedule as well as the prompt: 7:00 AM, weekdays, your chosen time zone. Editing the prose alone is not a reason to assume the recurrence changed. Updating the existing task also avoids creating two morning reports.

Claude supports editing a scheduled task's instructions and cadence, and running it on demand. See the current scheduled-task instructions if your interface looks different.

Step 4: run it once and check the evidence

Open the supporting emails, calendar events, and Notion tasks. Check whether the report identifies actions you actually own, represents deadlines accurately, and distinguishes requested preparation from a suggestion.

Also check the proposed focus block against your calendar. “Protect my mornings” should help the agent make a useful recommendation, not cause it to ignore a meeting.

Before and after: what changes?

Illustrative examples only. The names, meetings, and tasks below are fictional; these are not results from a connected account.

Before: a generic summary

You have several unread emails, a meeting this afternoon, and tasks in Notion. Consider planning your day and focusing on important work.

That tells you where information exists, but still leaves the decisions to you.

After: a brief you can act on

Urgent Emails

• Maya requests approval of the tutorial outline by noon. Reply after reviewing it. Source: email, “Outline approval.”

Today's Schedule

• 2:00 PM: production check-in. The agenda requests the draft shot list. Source: calendar event.

Top 3 Priorities — recommended order

1. Approve the outline: due noon, per email.

2. Finish the script: filming is tomorrow, per Notion.

3. Prepare the shot list: requested for today's meeting.

Suggested Focus Block

• 9:00–10:30 AM for the script. No event appears in that window in the checked calendar. No booking created.

Risks or Blockers

• The thumbnail task has no deadline in Notion. Its urgency is unconfirmed.

In a real brief, include links where available so each claim is easy to check. If a source cannot be read, the report should explain that gap rather than present an apparently complete day.

Fix the part that is still vague

The priorities still feel random

Add a ranking rule and the current project. Name what makes a message urgent: a decision due today, an explicit request from a client, or work blocking a colleague. Ask for one short reason per priority.

It lists too much email

Narrow the lookback or specify important senders. Require an action from you, and exclude informational messages unless they contain a relevant commitment.

It recommends time that is already booked

Check the calendar list and time zone. Require a conflict check and ask it to say when no suitable block is available. The recommendation should never silently move an existing event.

It invents details or hides missing access

Ask it to quote or reference the source for the disputed claim. Clarify the exact task database and fields. An unavailable source should be labelled as unchecked; a missing deadline should remain unknown.

It keeps producing a long report

Keep the 200-word cap in one consistent set of saved instructions. Ask for only actionable items and one-line explanations. Do not fill every section with invented work just to satisfy the format.

Your next morning checklist

• The context matches your actual role, current work, and focus hours.

• Every proposed priority has a supported reason.

• The brief uses the intended sources, date, and time zone.

• Facts, recommendations, and unavailable information are clearly separated.

• All five sections together stay under 200 words.

• The task reports and suggests; it does not send messages or change your apps.

After a few mornings, revise the instruction behind any repeated problem. The model can stay the same: clearer context, priorities, and rules give it a better definition of a useful result.