Aveiro

View saved version →

---
name: draft-newsletters-and-social-posts
description: Draft newsletters and social media posts in Aveiro for a person to review and send, for example to announce a new blog post. Use when the user asks to write or revise a newsletter, an email campaign, or social posts.
---

# Draft newsletters and social posts

Aveiro never sends a newsletter or publishes a social post from here: a person approves, schedules and sends it in the Aveiro dashboard. If the user asks to send or post now, say so and offer to prepare the draft. Explicit instructions from the user take priority over these steps.

## Source material

If the draft is about the user's own content, read it first: find the page with `aveiro_list_pages` and read it with `aveiro_get_page`. Use only facts from the source or from the user. Don't invent news, numbers, dates or quotes.

## Newsletter

1. Call `aveiro_newsletter_list_campaigns` to see recent campaigns and avoid repeating one. To match an earlier campaign's tone or structure, read it with `aveiro_newsletter_get_campaign`.
2. Call `aveiro_newsletter_create_draft` with a subject, preview text and the body in `html_content`.
3. Revise it with `aveiro_newsletter_update_draft` when the user asks for changes.
4. Tell the user the draft is ready to review and send from the Aveiro dashboard.

## Social posts

1. Call `aveiro_social_list_accounts`. If no accounts are connected, ask the user to connect them in the Aveiro dashboard and stop.
2. Ask which accounts to post to, unless the user already said.
3. Write a caption that fits the strictest platform you target, or give a platform its own caption in `platform_overrides`. Put links in `first_comment` when a platform handles links in captions badly. A Reddit target needs a subreddit, and the post needs a Reddit title in `platform_titles`.
4. For images, reuse an asset from `aveiro_social_list_media` or `aveiro_social_list_org_media`, or register a public image or video URL with `aveiro_social_register_media`. `aveiro_social_generate_media` and `aveiro_video_create_mockup` use AI credits: ask before calling them, and for `aveiro_video_create_mockup` pass `estimate_only` true first and share the cost.
5. Call `aveiro_social_create_draft` with the targets and media. Use `submit_for_review` false while the user is still editing. Revise with `aveiro_social_update_draft`.
6. Tell the user a person approves and schedules the post in the Aveiro dashboard.

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: get-started
description: Check the Aveiro connection and help the user choose a site and a task. Use right after Aveiro is connected, or when the user asks what Aveiro can do or which sites it can reach.
---

# Get started with Aveiro

This workflow only reads data. Explicit instructions from the user take priority over these steps.

1. Call `aveiro_me` to confirm the connection. Tell the user, in plain words, what the connection allows (for example writing pages, publishing, media, social drafts, newsletters) and how many sites it can reach. If the call fails with an authorization error, ask the user to reconnect Aveiro and stop.
2. Call `aveiro_list_sites` and show the sites by name. Use the site IDs it returns; never guess one.
3. If there are no sites, offer to create one. Call `aveiro_list_templates`, let the user pick a template and a name, and call `aveiro_create_site` only after they confirm.
4. Ask which site to work on and what they want to do. Suggest only tasks the connection allows, such as:
   - draft a blog post or update a page,
   - review unpublished changes and publish them,
   - draft a newsletter or social posts about recent content.
5. Continue with the matching workflow: `write-and-publish-pages` for pages, `draft-newsletters-and-social-posts` for newsletters and social posts.

Do not create, change or publish anything in this workflow except a site the user asked for in step 3.

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: write-and-publish-pages
description: Write, edit and publish pages on an Aveiro website, such as blog posts, docs pages and landing pages. Use when the user asks to draft a page, change an existing page, add images to a page, or publish site changes.
---

# Write and publish pages

Pages are drafts until they are published. Explicit instructions from the user take priority over these steps.

## Before writing

1. Find the site with `aveiro_list_sites`, unless its ID is already known in this conversation.
2. Call `aveiro_authoring_guide` once per conversation, before the first `aveiro_create_page` or `aveiro_update_page`, and follow it. Pages use Aveiro's MDX dialect: content pages are headings and prose with registered components only where they help; landing pages are built from page sections. Never write raw HTML layout.
3. Ask for what you can't know: the topic, the audience, key facts, links. Don't invent product details, numbers, quotes or dates.

## Change an existing page

1. Find it with `aveiro_list_pages`, then read it with `aveiro_get_page`.
2. Call `aveiro_update_page` with the complete new body in `content`; it replaces the whole body, so keep every part the user didn't ask to change. Pass the revision from `aveiro_get_page` as `if_match`, so an edit made in the meantime isn't overwritten.
3. To change only the title, summary, tag, image or display date, send `metadata` and leave `content` out. `publishedAt` must be a real date (YYYY-MM-DD).

## Add a page

1. Pick a path inside the right folder, for example `/blog/spring-update.mdx`. If the folder doesn't exist, create it with `aveiro_create_collection` first.
2. Call `aveiro_create_page` with the path, the MDX body and metadata (at least a title and a summary).

## Images

- Check `aveiro_list_media` first and reuse an existing image's URL.
- For a new image from a public HTTPS URL, call `aveiro_import_media_from_url` and embed the `mdx` it returns.
- For a screenshot of a real web page, call `aveiro_media_create_screenshot` with `estimate_only` true first, tell the user the credit cost, and render only after they agree. Then poll `aveiro_media_get_screenshot` until it is done.
- Never invent an image URL.

## Publish

1. Show what is waiting with `aveiro_list_changes` and summarize the changes.
2. Call `aveiro_publish_site` only when the user has asked to publish in this conversation. Name the pages that will go live, and pass their `content_ids` so nothing else is published by accident.
3. If the site has translations, ask whether to publish them too and set `locale_scope` to match.

Delete a page (`aveiro_delete_page`) only when the user asks for it and confirms which page.

Referenced files: 1 — file references are metadata, not package contents.