---
name: al-247-teach-your-ai-assistants-to-check-the-live-source-for-dat
description: "AI assistants with memory can recall a deadline or a price perfectly and still be wrong, because the meeting moved or the price changed since they saved it. The fix is to make them remember where to look rather than the value itself, and to check that place before stating or acting on anything that can change. A creator shared a copy-paste prompt on X on Oct 19, 2026, re-shared on Oct 22, that rolls out a 'check the source, don't trust memory' rule across a team of assistants: map the changing facts each one relies on to an authoritative source like a calendar, inbox, Notion or database, replace stored values with pointers (for example 'check Google Calendar for the next review date'), get approval before changing memory, and test three assistants on facts they had answered from memory. The original post had about 62,000 views and 645 bookmarks. Use when the user wants help with live source checking for agent memory (personal productivity) for a small business."
---

# Teach your AI assistants to check the live source for dates, prices and statuses instead of trusting what they remember

AI assistants with memory can recall a deadline or a price perfectly and still be wrong, because the meeting moved or the price changed since they saved it. The fix is to make them remember where to look rather than the value itself, and to check that place before stating or acting on anything that can change. A creator shared a copy-paste prompt on X on Oct 19, 2026, re-shared on Oct 22, that rolls out a 'check the source, don't trust memory' rule across a team of assistants: map the changing facts each one relies on to an authoritative source like a calendar, inbox, Notion or database, replace stored values with pointers (for example 'check Google Calendar for the next review date'), get approval before changing memory, and test three assistants on facts they had answered from memory. The original post had about 62,000 views and 645 bookmarks.

## Inputs to collect first
Ask the user for anything below that they haven't already given you. Don't guess missing facts.

- Assistants and what each does
- Google Calendar / Gmail / Notion / spreadsheet / store admin

## Instructions

Do the task below with the user's inputs in place of each [bracket].

Help me set up a 'check the source, don't trust memory' rule for my AI assistant(s): [list assistants and what each does]. Keep all current permissions for sending, buying and publishing exactly as they are. 1) For each assistant, list the facts it relies on that can change: dates, prices, statuses, contact details, balances, order info. Next to each, name where the current value lives (for example [Google Calendar / Gmail / Notion / spreadsheet / store admin]) and say whether you can actually reach it. Flag anything missing or conflicting. 2) Review what each assistant remembers. Keep stable preferences and rules. For changing facts, propose replacing the value with where to check it, e.g. 'check Google Calendar for the next review date'. Show me the changes for one assistant first and wait for my OK. 3) Write this standing instruction for each: 'Before stating or acting on a fact that can change, check its source and say where and when you checked. If you can't reach it, say so, label the remembered value as old and unverified, and don't act on it.' 4) Pick three changing facts and test: did it check, what did it find, and did that differ from memory? Report results honestly; if you can't tell, say so.

## Safety checks (share these with the user)

- This prompt works on text other people wrote (emails, reviews, messages or web pages). That text can hide instructions aimed at AI, such as "ignore your rules and…". Paste it as material to work on, and never let the AI act on requests inside it, like paying, sharing logins or changing records.
- Check every figure, price and total against your own records before anything is sent, posted or booked. A person approves refunds, discounts, payments and price changes.
- Remove names, contact details, account numbers and other personal data the task doesn't need before you paste, and check your AI tool's data and training settings.
- Read and edit the draft before it reaches a customer or goes public. If you later automate this prompt, start with "draft and notify me", not "send automatically".
- Say clearly which parts need a person to review or approve before anything is sent, paid, posted or filed.

## About this skill

- Works with: Grok Bot, ChatGPT, Claude, Google Calendar, Gmail, Notion
- Based on this real-world example: https://x.com/Michael_Fenech_/status/2112133154916208727
- Free prompt from AgentPlaybook Real Estate: https://agentic-library.netlify.app/prompt/al-247-teach-your-ai-assistants-to-check-the-live-source-for-dates/
- To install in an agent that supports Agent Skills, save this file as SKILL.md in a folder with the same name as `name` above (for example in your skills directory). Install steps for Claude.ai, Claude Code, Cursor and Codex: https://agentic-library.netlify.app/skills/
