A blog hero image, rendered and delivered to Drive with a link that actually opens
A company-formation service needed a hero image for an article on forming a company in a specific market, rendered and saved to the client's Drive with an openable signed URL. AOS generated the image and delivered it as a working link — running image generation as a dedicated capability, deliberately kept separate from blog drafting.
01 Ground
Content for a company-formation service lives or dies partly on whether it looks finished. An article on registering a company in a specific market needs a hero image to anchor it — without one, the piece reads as a draft no matter how good the copy is. But producing that image is its own small production chore: generating something on-brand and on-topic, then getting it somewhere the team can actually use it, with a link that opens rather than a path that 404s.
The delivery half of this is where these tasks usually break. An image that exists only inside a run, or is saved to a private bucket behind a bare storage path, is effectively undelivered — the operator clicks the link and gets an access error instead of a picture. For a deliverable, 'rendered' and 'openable by the client' are two different milestones, and the second is the one that actually matters.
There is also a design temptation to fold image generation into the blog-drafting workflow so a single command produces text and art together. That sounds convenient and is fragile in practice: it couples two very different capabilities, makes both harder to reason about, and means a hiccup in one can compromise the other. The cleaner model treats image generation as a deliberate, standalone capability — which is the design choice this run reflects.
- Rendered blog hero image for a market-specific company-formation article, saved to the client's Drive AOS skill run 36b26d22 deliverable 90% confident
- Delivered with a working signed URL (openable link, not a bare storage path) AOS skill run 36b26d22 90% confident
- Run completed at approximately $0.21 AOS skill run 36b26d22 90% confident
02 Decide
Two decisions shape this run. The first is that image generation is a dedicated capability, deliberately kept separate from blog drafting rather than bolted onto it. Drafting an article and rendering art are different jobs with different failure modes, and isolating them keeps each one simple, debuggable, and independently usable — the service can ask for a hero image without invoking a whole content pipeline.
The second decision is about delivery: the image is handed over as an openable signed URL, not a bare storage path. A private bucket path is technically a 'save' but practically a dead end, because the client clicking it gets an access error. By delivering a working signed link, AOS makes the deliverable usable the moment the run finishes — the distinction between 'rendered' and 'actually openable by the recipient' is treated as part of the job, not an afterthought.
03 Deploy
AOS generated a hero image for the article on company formation in the specified market, then saved it into the client's Drive and produced a signed URL so the link opens rather than returning an access error. The delivery step — turning a private stored asset into something the client can actually click and view — was handled as part of the run, not left as a manual follow-up.
The capability was exercised on its own, not as a side effect of drafting the blog. That separation is intentional: image generation stands as its own dedicated skill, so it can be invoked precisely when an asset is needed. The pass cost roughly $0.21, making a finished, openable hero image a near-trivial line item against the value of shipping a piece that looks complete.