An assignment that leaves less to guess#
For work inside applications, specify permissions and review criteria as well as the goal. Adapt this original template; replace the brackets with concrete details.
Outcome: [what should be finished] Sources: [specific files, URLs or source application] Scope: [date range, folder, number of items] You may: [read the selected data and create a new working output] Before my approval, do not: [send, publish, buy, delete or change original data] Deliverable: [file type, columns, length, evidence links] Acceptance criteria: [how I will assess correctness] If information is missing: mark the gap; do not invent a replacement. Budget: do not use a paid service or make purchases without approval. Process a small sample first. Finish by separating completed actions, proposals awaiting approval and unresolved items.
Two separate controls: a prompt describes your intent; application settings also determine actual permissions and billing. Writing “stay within budget” does not create a technical spending cap. See usage and approvals.
Four useful assignments to copy#
These are original example assignments. Supply your own material and start with a small scope. A particular service requires an available connection and appropriate permissions.
1. Research you can make a decision from
Useful for comparing tools, services or public offers. Supply three specific URLs first.
Compare the offers on these three official pages: [URL 1], [URL 2], [URL 3]. My need is [specific requirement]. Return a table: provider, suitability, price and currency, billing period, main limitation, direct source, time checked. Mark missing prices “not published”. Distinguish monthly from annual billing. Do not create accounts or buy anything. Recommend at most two options and explain what still needs checking.
2. Email drafts ready for your review
Connect the correct mailbox first. Choose a narrow label or folder.
In the connected mailbox, review at most 10 messages labelled [label] from the last 7 days. Group them into reply needed, my decision needed and information only. For at most three messages, prepare drafts in this conversation: recipient, subject, body and a link to the original. Do not send, delete, archive or change labels. If a reply needs information you do not have, write a question for me.
3. Compare two spreadsheets
Attach two practice copies. Name the column that identifies matching items.
I attached old.csv and new.csv. Compare them using the ID column. Create changes.csv with columns ID,change_type,column,old_value,new_value. List added, removed and changed items separately. Do not silently merge duplicate or blank IDs: report them as issues. Preserve the original files. Finish with the row count of each input and the number of differences found.
4. Review a website before publishing
Provide a public or accessible preview. Specify the pages and screen widths.
Review this website preview: [URL]. Visit the homepage and these three pages: [URLs]. Check navigation, language switching, links and readability at widths of 390 and 1365 pixels. Return at most 8 concrete findings: page, reproduction steps, expected and actual behaviour, severity and a screenshot. Separate verified defects from improvement suggestions. Do not deploy anything or change hosting settings. Mark anything you could not verify.
Review questions: Did the Bot open the cited source? Does the attachment contain every row? Does each link support the specific claim? Is “done” backed by an output you can inspect yourself?
From a good example to recurring work#
For your first automation, we recommend public sources and results delivered only to the conversation. Request and refine a one-off result first. Then adapt this assignment:
Save our verified news-checking process as a skill called “Weekly changes”. Propose a routine for this Bot every Monday at 08:30 in Europe/Bratislava. Sources: [three specific official URLs]. Track only changes since the last successful check. Output in this conversation: at most five material updates, each with its date, direct link and explanation of its impact. If nothing material changed, do not invent an update. If a source is unavailable, mark it and do not present old information as new. Do not send anything elsewhere or modify the websites. Show me the schedule, time zone and proposed next run. Do not create the routine yet. Create it after my approval, then confirm its state.
Before enabling it, check: the URLs, Bratislava time zone, output destination and missing-data behaviour. After its first real run, check for repeated items. Pause the routine when you want a break; closing the app does not tell it to stop.
If Teach a task is available, you can demonstrate a workflow. Review the resulting procedure anyway. The mobile guide says routine schedule/instruction edits and test runs require desktop.
What belongs in a saved skill
State when it applies, required inputs, steps, validation and the output. Include what to do when a source is missing. The skills documentation describes private skills as shared across your Bots; another Bot still needs the relevant connection or login.
Review the saved skill before its next use. List its inputs, steps, result checks, output destination and actions requiring my approval. Compare it with the last successful run. Do not run or overwrite it yet.