Build a guide with an agent

A guide is a set of spots the creator has been to, grouped into chapters, with the practical facts buyers need (how to get there, hours, fees, places to stay and eat) and the creator's own photos. The agent gives the creator's material structure. It never replaces their experience: every coordinate, fact and photo comes from the creator or from a source the agent names.

Before the first call

Ask the creator for five minutes: which region, which spots, where their map links and tracks live, which photos exist and who took them, the price, the language. Load the rules with get_authoring_guide (or install the SKILL.md) and call whoami to see the key's scopes and limits.

The steps

1. Pick or make the guide. list_guides; edit a matching draft, or create_guide when the creator wants a new one.
2. Define the properties first. create_property for what every spot should carry (Best time, Difficulty, Facilities, Elevation). Read them back with list_properties: spots store option ids, never labels.
3. Add the spots. create_spot makes a complete spot in one call. For many spots, or a build you will run again, use upsert_spots with your own ref: re-running never duplicates. Leave lat and lon empty rather than guessing.
4. Add the facts the creator has. Arrival, hours, fees, status notices, links, extra pins, rules on site. Planning facts explains each shape.
5. Group the spots. create_chapter and set_chapter_members: a chapter carries prose (a region, a day), a collection is a plain set (top picks).
6. Add routes and places where the creator has them: create_route with the line from their GPX, create_facility for stays, transport, tours, food and parking.
7. Photos. Ask for the files and who took each one; upload them over REST. Photos has the details.
8. Region, price, settings. set_guide_region, set_guide_price with the number the creator gave, update_guide for the headline, tags and country.
9. The sales page draft. get_sales_page, then save_sales_page_draft. Testimonials only from real quotes the creator gives; never promise updates.
10. Check the links. check_links, a minute later get_link_report. See Links and link health.
11. Run readiness and hand back. get_guide_readiness: fix what you can, list the rest, send the creator the reviewUrl. See Readiness.

Handing back

Tell the creator in plain words what you created or changed (counts), what you could not fill and why, the links you could not verify, the facts with a review date, and your review notes. Then the clicks that are theirs: putting the guide on sale and publishing the sales page happen in the studio. Never describe the guide as written by AI in buyer-facing copy; the creator's name is on it.