Choosing for everyday and difficult tasks#
Start with your account’s ordinary option for rewriting a short text. If several choices are available and you are dealing with interacting constraints, source comparison or programming, try the option designed for deeper work. Compare the same request for requirements met, errors and time, not just the name.
Treat labels such as Fast or multi-agent as entries in a particular product’s menu, not a permanent button list. The public page confirmed Fast; the full selection for a signed-in Slovak account remains unverified. Multiple agents or a longer answer do not by themselves establish correctness.
Research you can verify#
Try a small task: find official instructions for a service you already know. Supply a precise question, country and time period. Enable search if your account offers it; otherwise explicitly ask for research and check that the response contains real sources.
Find current official instructions for [specific task] for a user in [European country]. Use and open primary sources. Give a direct link for each important step and the source date when available. Separate country-specific rules from general information. Say when you cannot read a page. Output: concise steps, sources and unverified points.
- Open at least two key links yourself. Check the publisher, date and relevant passage.
- Check whether the link actually supports the claim. A homepage often is not enough.
- Distinguish publication date, event date and the date you checked the information.
- For a conflict, return to the original document and state what remains uncertain.
An answer without sources is not a verified research result. Request the direct source for a specific sentence. Read Grok on X for handling posts and their context.
Connect a source and start with reading#
A connector links another service. For a first test, prepare a harmless document with a unique title, such as “Summary test — three points”. Review what the connection can read and change before allowing access. If you only need a summary, do not grant write access when you can choose.
In Google Drive, find the document with the exact title “Summary test — three points”. Give its title and link, then summarise it in three points. If several documents match, list them first. Do not create, move or edit anything in Drive.
Check that the link opens the right file and compare the three points with the original. On failure, check the connected Google account, document permissions and organisational restrictions. “File not found” is not proof that the file does not exist. You can disconnect after the test.
One successful task before automation#
Automate a task only after checking a successful one-off result. Prepare exact sources, a timezone and a rule for when you want a notification.
- Open Automations or request a task in chat.
- Set its name, instructions, trigger, sources and notification. Check the timezone.
- Save and select Run now. Verify the result’s sources.
- Check the first scheduled run in history too.
- On failure, pause the task and revise its instructions.
Every Monday at 08:00 Europe/Bratislava, check these official pages: [links]. Look for changes since the last successful run. For each change, give the previous and new state, source and date. Mark uncertainty. Send no notification if nothing changed. Prepare the result only; do not publish anything.
This is a proposed request. This guide has not enabled an automation in your account. Continue with a workflow for difficult tasks.