AI Agent Use Cases
Views —

AI Agent Use Cases

Added today

44All 189

Prompt to Prepare a Shopping Cart from a Recipe Photo

The author reports that Grok Bot receives a recipe photo, organizes the ingredients and quantities, and creates a shopping list by excluding ingredients already available at home.

Grok Bot
Life & Hobbies

1–20 of 189

DevShared prompt

Requesting Notification When a New Version Is Registered

Someone requested to check every hour if a new version of Python for automated testing has been registered.

ChatGPT

How it works

  1. The author asked ChatGPT to clone the 'actions/python-versions' repository, which contains the list of Python versions.
  2. They requested to run 'git pull' every hour to get the latest list and check if the stable Python 3.15 version had been added.
  3. They also included a condition to notify them when the desired version appeared in the list.

Results

At the time the post was made, the new version had been registered, so the Python 3.15 version could be used in GitHub Actions, an automated testing service. There is no information about whether ChatGPT actually performed repeated checks or sent notifications.

Notes

This is a post introducing the request message shared by the author. Since the periodic execution settings and execution logs are not public, it cannot be confirmed from this request alone whether the notification actually worked.

Source

Simon Willison’s Weblog Original post ↗

Example prompt · ChatGPT

Create a monitoring task that periodically checks whether a stable Python version for use in GitHub Actions has been registered.

Input: Target version [e.g., 3.15], check interval [frequency], notification destination [connection]. First, check whether the current execution environment can maintain scheduled execution and notifications after the chat ends. If not supported, suggest a possible scheduler setup and distinguish between completed and incomplete configurations.

Read the current version list from the official actions/python-versions repository to determine the exact version and whether it is a stable release. Do not mistake pre-releases for stable versions, and distinguish lookup failures from unregistered versions. Record the check time and the source of the list used.

Notify only when the desired version is found for the first time, including the version, check time, and source link. Save the state so that repeated runs or retries after failures do not send duplicate notifications.

Deliverables: Execution code or scheduling setup, state storage method, and how to stop the process. Test for unregistered, pre-release only, stable version found, lookup failure, and duplicate execution cases. Do not claim the monitoring is verified until you have checked actual scheduled execution logs.