Track public document changes for teaching updates

An educator used a Dot to watch public documents, rank likely teaching impacts, and compare draft notation with linked pages before suggesting edits.

Done with Dots· Intermediate

What they did
They set up a Dot, an always-on agent with its own cloud computer, to handle two possible jobs. First, it would watch selected public documents for changes and list which teaching materials those changes might affect, with source links. Second, it would compare an article draft’s notation with the pages it links to. The example request kept the agent in suggestion mode only: it could not overwrite, publish, send, or pay, and any unclear item had to stay marked unconfirmed.
How it went
The checking and revision roles were only proposed, not actually run. After setup, they used the Dot for a few days and said it reached out on its own and pointed out items from Drive and Gmail.
Tips
Start with public documents and keep the access scope narrow. Once a Dot can see connected data, disconnecting it later does not erase what it already learned.

Try it yourself with Dots

Watch these public documents every [week] for any changes: [links to standards, syllabi, regulations, or other sources]. Compare the changes with my teaching materials about [topic], and rank the ones most likely to matter. Also check whether the notation in [article, handout, or draft] still matches the linked pages. Return only a list of revision candidates with the relevant passage and source URL; do not change any files, and do not send, submit, publish, delete, or pay for anything without asking me first. Mark anything you cannot confirm as unconfirmed and wait for my approval before any irreversible action.

Fill in the [brackets]. Agents can make mistakes, so review anything before it is sent, paid or deleted.

Read the original on note.com ↗

Get 3 agent uses like this every morning

With the day's top AI news. Free, and one click to unsubscribe.