Examples
Three realistic jobs, start to finish: a news post, a new page from blocks, a change across many pages.
On this page
Three jobs people give an assistant, told the way they go: what you say, what the assistant does with the tools, and what you do at the end. The site is a bakery called example; the assistant is connected as in Connect your assistant.
1. A news post from a few words
You say: "Write a news post that we open at 8 from Monday 3 November, friendly tone, two short paragraphs. Don't publish."
The assistant calls describe_site to learn what the key allows and which collections exist, then get_schema to see what a news record needs: a title, a date, a summary, a body, maybe a photo. It writes the post and saves it with create_draft in news under an id like earlier-opening. If it forgot a required field, the server says so and it fills it in. Then it calls preview_link and gives you the address.
You open the link, read the post, fix a word if you like (in the admin, as usual), and press Publish. In History the post's first version is signed by the key's name, the second by you.
What it needed: a key with Read and Save drafts.
2. A new page built from blocks
You say: "Make a page at /wholesale for cafés that want to stock our bread: a hero with a short intro, three cards (sourdough, rye, baguettes) and a contact band. Use photos we already have."
The assistant calls describe_site (is this a Clear Blocks site? yes) and describe_kit to see which blocks exist and what words each takes. It calls list_media to find photos, then create_draft in pages for a page with the title and address, add_block three times (a hero, a cards block with three cards, a contact block) with the words shaped like the kit's examples and the photos' addresses in the photo slots. The cards look crowded, so it calls update_block with a style step to give the block more room. It finishes with preview_link.
You look at the page on the preview link. The page is not in the menu yet; add it under Site settings → Menu if you want it there, then Publish.
What it needed: Read, Save drafts and Pages and blocks. If it had to fetch a photo from your supplier's website, Files too (add_photo).
3. A change across many pages
You say: "Our phone number changed from 555 0100 to 555 0199. Find every place it appears and fix it, but tell me what you found before changing anything."
The assistant calls search_records for the old number, then get_record with version: "draft" on each hit (so it sees the latest text, including drafts you have not published yet). It lists the pages and records it found: the contact page, the footer in the site record, two news posts. You say go. It saves each with create_draft, changing only the field that holds the number and leaving the rest as it was, and uses update_block for a block on the contact page. Then a preview_link.
You check the preview, then Publish. The site's search is published content only, so if the number also sits in a draft nobody published, mention that page to the assistant.
What it needed: Read, Save drafts and, for the block on the contact page, Pages and blocks.
Prompts that work well
- Say what not to do: "don't publish", "don't touch the home page", "ask before deleting".
- Ask for a look first: "tell me what you'd change before you change it".
- Ask for a preview link at the end; it is the quickest way to check.
- Name the collection or page when you know it; the assistant finds it faster and makes fewer calls.
- Give facts in the prompt (dates, prices, names). The assistant is told not to invent them.