A few places to begin

Less blank page.
More next step.

A useful brief gives your agent something to work toward. Explore these examples, adapt the details, and decide what a good result should include.

Illustrative briefs, not recorded results. Execution depends on the configured models, tools, and sandbox. Check current capabilities.

6 examples shown.

Example · Research

A question.
A better-informed choice.

Compare the paths ahead.

Bring a decision into focus with a sourced comparison, clear trade-offs, and the questions that still need an answer.

“Compare three open-source tools for scheduling background jobs. Cover setup, retries, and monitoring. Link the sources and save a short comparison.”

Ask for: source links, the date of time-sensitive facts, assumptions, and a recommendation tied to your constraints.
Check: whether the sources support the claims and what remains uncertain.

Example · Data

A messy file.
A clearer picture.

Make sense of the spreadsheet.

Start with a supplied CSV, inspect the structure, and turn the important patterns into a summary you can question and verify.

“Review the CSV I attach. Check the columns and missing values, summarize the main patterns, and save a clean copy with your assumptions.”

Ask for: a data-quality check, explicit transformations, relevant totals, and a downloadable output file.
Check: calculations, units, and whether important records were removed or changed.

Example · Code

An everyday task.
A useful little tool.

Build something small and practical.

Give the task clear inputs and expected behavior. Ask for code, instructions, and evidence from the checks that actually ran.

“Build a small CSV validation script. Explain the inputs, write the code, add useful checks, and give me clear instructions for running it.”

Ask for: source files, dependency notes, sample inputs, and test results with any skipped checks.
Check: behavior on valid and invalid data before using it for important work.

Example · Vision

Another pair of eyes.
A more useful review.

Review the picture in front of you.

Use a supplied screenshot as the reference for a concrete critique. Keep observations grounded in what is actually visible.

“Review the screenshot I attach. Describe the layout, flag the unclear parts, and suggest specific improvements without guessing hidden details.”

Ask for: specific observations, the reason each issue matters, and a practical order for improvements.
Check: whether the model read the image correctly. Requires a vision-capable route.

Example · Image creation

A visual brief.
Something to react to.

Explore a visual direction.

Describe the subject, composition, colors, and output requirements. A verified image route can bring a first direction back as a file.

“Create a simple product illustration with a warm ivory background and a teal subject. Keep room for a headline, use soft 3D lighting, and avoid adding text.”

Ask for: the desired composition, dimensions, reference material, and an image file you can inspect.
Check: visual consistency and any unwanted details. Generation and editing require separately verified services.

Example · Recurring work

A standing question.
A regular check-in.

Give repeatable work a routine.

Turn a carefully scoped brief into an interval-based schedule. Keep related runs in the project and review the outputs over time.

“Review the public sources saved in this project. Summarize relevant updates, link the evidence, and clearly flag when information cannot be verified.”

Ask for: a clear scope and output format. Configure the schedule interval and per-run allowance in the workspace.
Check: worker availability and each run's evidence. Current schedules use intervals rather than calendar rules.

A good brief is a starting point. Add your actual constraints, upload the material the task needs, and review the result before relying on it. These examples do not run an agent or represent completed work. The hosted interface preview has no connected execution service. Read the workflow guide.