← SitelasCONTENT HISTORY

Update to Sitelas

Snapshot Nov 19, 2026 · 12:11 UTC · version 4.1.0

Collection source: downloaded plugin package.

WHAT CHANGED

Instructions updated for edit-and-publish

Skill instructions — Now says: Several of a kind go in one call: `edit_content_item` with `edits` for many items, `delete_page` with `slugs`, `delete_collection` with `content_types`,...

Observed in instructions or declared skills. Runtime behavior has not been tested.

Save Sitelas and check future changes in Following.

Up to 3 plugins free · no card required.

All fields and original values.

Skill instructions

Before

Nov 1, 2026 · 18:10 UTC

Use `delete_page`, `delete_content_item` and `delete_site` only when the person has asked for that deletion. Confirm before deleting a whole site.

After

Nov 19, 2026 · 12:11 UTC

Several of a kind go in one call: `edit_content_item` with `edits` for many items, `delete_page` with `slugs`, `delete_collection` with `content_types`, `remove_nodes` with every id. Use `delete_page`, `delete_content_item` and `delete_s...

Compare saved observations

Download comparison JSON

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -33,7 +33,16 @@
 
 A new page doesn't appear in the menu on its own. Add a menu link with `insert_nodes`, or tell the person it isn't linked yet. Rename a page's address only with `update_page`, which also updates links and redirects the old address.
 
-Use `delete_page`, `delete_content_item` and `delete_site` only when the person has asked for that deletion. Confirm before deleting a whole site.
+Several of a kind go in one call: `edit_content_item` with `edits` for many items, `delete_page` with `slugs`, `delete_collection` with `content_types`, `remove_nodes` with every id. Use `delete_page`, `delete_content_item` and `delete_site` only when the person has asked for that deletion. Confirm before deleting a whole site.
+
+## Pictures, payments and other sites' looks
+
+- **Pictures of the site.** When a tool answer has `preview_image`, that is the site's own main photo: use it if your reply shows a picture of the site, or show none. Never illustrate the site with an image from web search. It is another business's photo, and the person will take it for theirs.
+- **Payments.** This app doesn't add payment, deposit, donation or checkout buttons or links (Stripe, PayPal, Square and similar), and Sitelas refuses those changes. If the person asks, say so plainly and offer an enquiry or booking form instead. Taking money stays with their own provider, outside the site.
+- **Bookings and appointments.** Sitelas has no booking calendar: a site can't show free slots, take a reservation or stop double bookings. Say that first, before describing any booking flow. Then offer what it can do: a booking-request form (the visitor asks for a time, the owner confirms), or the scheduler they already use (Calendly, Cal.com, Doctolib and similar) placed on the page or linked from a button.
+- **"Make it look like this site."** When they give a website address to match, call `capture_url` on it. It reads that site's colours, fonts and layout, so you don't have to guess them from web search.
+- **Colour changes.** `set_theme` recolours what follows the theme. Elements with a fixed colour don't follow it, and `review_site` counts them. After a colour change, take a `screenshot_page` and confirm the new colour actually shows before saying it changed; patch the elements that kept the old colour.
+- **Widgets.** A blank quiz or calculator has a script error that `review_site` reports as broken_widget; fix the script with `patch_nodes`. Widgets can't save anything between visits. Never ask the person to switch off Sandboxed (Secure).
 
 ## Show the change, then ask
 
Full technical diff · 1 changed fields

changed /skill_md_contents

BEFORE
"---\nname: edit-and-publish\ndescription: Use when someone wants to change a website they already have on Sitelas — copy, images, colours, sections, pages, navigation or SEO — or wants to publish, unpublish or undo a publish. Every change lands on a private draft. The live site changes only when the person explicitly says to publish.\n---\n\n# Edit and publish a Sitelas site\n\nEvery edit writes to the site's draft. The live address keeps showing the last published version until `publish` runs. Publishing changes what the public sees, so it needs the person's explicit go-ahead every time.\n\nIf the person's own instructions conflict with anything below, follow the person.\n\n## Find the site and what's on it\n\n- Call `list_sites` if you don't know which site they mean. If they have several, ask which one.\n- Call `get_site` with `include: [\"brief\"]` before writing copy or changing the design, so new work matches the site's existing voice, colours and fonts.\n- Call `get_page` to find the exact pieces of text and images to change. Before any change to the header or footer structure, call `get_page` with `view: \"structure\"` to see how it's nested.\n\n## Make the change with the narrowest tool\n\n| They want                                          | Use                                                                              |\n| -------------------------------------------------- | -------------------------------------------------------------------------------- |\n| Change words, links, button text or an image       | `patch_nodes`, all changes in one call                                           |\n| Swap several photos                                | `replace_images_from_search`                                                     |\n| Use a photo they attached                          | `place_attached_image`, naming the spot from `get_page`                          |\n| Use their own photo that isn't attached            | `get_editor_link` with `image_target`: a one-time link that adds it to that spot |\n| Add a section                                      | `add_section`                                                                    |\n| Remove or reorder things                           | `remove_nodes`, `move_nodes`                                                     |\n| Add, copy, rename or delete a page                 | `add_page` (with `copy_of` to copy), `update_page`, `delete_page`                |\n| Change colours or fonts site-wide                  | `set_theme`                                                                      |\n| Blog posts, projects, team members and other lists | `list_content_items`, `add_content_item`, `edit_content_item`                    |\n| How a list of them shows: order, count, card look  | `patch_nodes` on the list (see `lists` in `get_page`), `set_card_design`         |\n| Search titles and descriptions                     | `update_seo`                                                                     |\n\nA new page doesn't appear in the menu on its own. Add a menu link with `insert_nodes`, or tell the person it isn't linked yet. Rename a page's address only with `update_page`, which also updates links and redirects the old address.\n\nUse `delete_page`, `delete_content_item` and `delete_site` only when the person has asked for that deletion. Confirm before deleting a whole site.\n\n## Show the change, then ask\n\n1. Call `read_rendered_page` on the page you changed and confirm the change is there.\n2. Share the preview link. Say plainly that the live site still shows the previous version.\n3. Ask whether to publish.\n\n## Publishing\n\n- Call `publish` only after a clear yes, such as \"publish it\" or \"make it live\". \"Change X\" is not permission to publish X.\n- To publish or take down a single page on a site that is already live, use `publish` or `unpublish` with its `page_slug`.\n- Use `unpublish` (take the site offline) and `undo` with `what: \"last_publish\"` (go back to the previous published version) only when the person asks for exactly that.\n- If `publish` is refused because of their plan (`billing_gate`), pass the message on as it is. Never take another site offline to make room.\n- After publishing, give the live address and stop. Don't publish again unless they ask.\n\nIf they'd rather make a small change themselves, `get_editor_link` gives them the visual editor for the right page.\n\nWhen you give someone a one-time photo link, Sitelas can't tell you when they have used it. When they say they're done, check the spot's image in `get_page` before saying it worked. If `place_attached_image` answers `placed: false`, the photo didn't come through: give them the link it returns instead of trying again.\n"
AFTER
"---\nname: edit-and-publish\ndescription: Use when someone wants to change a website they already have on Sitelas — copy, images, colours, sections, pages, navigation or SEO — or wants to publish, unpublish or undo a publish. Every change lands on a private draft. The live site changes only when the person explicitly says to publish.\n---\n\n# Edit and publish a Sitelas site\n\nEvery edit writes to the site's draft. The live address keeps showing the last published version until `publish` runs. Publishing changes what the public sees, so it needs the person's explicit go-ahead every time.\n\nIf the person's own instructions conflict with anything below, follow the person.\n\n## Find the site and what's on it\n\n- Call `list_sites` if you don't know which site they mean. If they have several, ask which one.\n- Call `get_site` with `include: [\"brief\"]` before writing copy or changing the design, so new work matches the site's existing voice, colours and fonts.\n- Call `get_page` to find the exact pieces of text and images to change. Before any change to the header or footer structure, call `get_page` with `view: \"structure\"` to see how it's nested.\n\n## Make the change with the narrowest tool\n\n| They want                                          | Use                                                                              |\n| -------------------------------------------------- | -------------------------------------------------------------------------------- |\n| Change words, links, button text or an image       | `patch_nodes`, all changes in one call                                           |\n| Swap several photos                                | `replace_images_from_search`                                                     |\n| Use a photo they attached                          | `place_attached_image`, naming the spot from `get_page`                          |\n| Use their own photo that isn't attached            | `get_editor_link` with `image_target`: a one-time link that adds it to that spot |\n| Add a section                                      | `add_section`                                                                    |\n| Remove or reorder things                           | `remove_nodes`, `move_nodes`                                                     |\n| Add, copy, rename or delete a page                 | `add_page` (with `copy_of` to copy), `update_page`, `delete_page`                |\n| Change colours or fonts site-wide                  | `set_theme`                                                                      |\n| Blog posts, projects, team members and other lists | `list_content_items`, `add_content_item`, `edit_content_item`                    |\n| How a list of them shows: order, count, card look  | `patch_nodes` on the list (see `lists` in `get_page`), `set_card_design`         |\n| Search titles and descriptions                     | `update_seo`                                                                     |\n\nA new page doesn't appear in the menu on its own. Add a menu link with `insert_nodes`, or tell the person it isn't linked yet. Rename a page's address only with `update_page`, which also updates links and redirects the old address.\n\nSeveral of a kind go in one call: `edit_content_item` with `edits` for many items, `delete_page` with `slugs`, `delete_collection` with `content_types`, `remove_nodes` with every id. Use `delete_page`, `delete_content_item` and `delete_site` only when the person has asked for that deletion. Confirm before deleting a whole site.\n\n## Pictures, payments and other sites' looks\n\n- **Pictures of the site.** When a tool answer has `preview_image`, that is the site's own main photo: use it if your reply shows a picture of the site, or show none. Never illustrate the site with an image from web search. It is another business's photo, and the person will take it for theirs.\n- **Payments.** This app doesn't add payment, deposit, donation or checkout buttons or links (Stripe, PayPal, Square and similar), and Sitelas refuses those changes. If the person asks, say so plainly and offer an enquiry or booking form instead. Taking money stays with their own provider, outside the site.\n- **Bookings and appointments.** Sitelas has no booking calendar: a site can't show free slots, take a reservation or stop double bookings. Say that first, before describing any booking flow. Then offer what it can do: a booking-request form (the visitor asks for a time, the owner confirms), or the scheduler they already use (Calendly, Cal.com, Doctolib and similar) placed on the page or linked from a button.\n- **\"Make it look like this site.\"** When they give a website address to match, call `capture_url` on it. It reads that site's colours, fonts and layout, so you don't have to guess them from web search.\n- **Colour changes.** `set_theme` recolours what follows the theme. Elements with a fixed colour don't follow it, and `review_site` counts them. After a colour change, take a `screenshot_page` and confirm the new colour actually shows before saying it changed; patch the elements that kept the old colour.\n- **Widgets.** A blank quiz or calculator has a script error that `review_site` reports as broken_widget; fix the script with `patch_nodes`. Widgets can't save anything between visits. Never ask the person to switch off Sandboxed (Secure).\n\n## Show the change, then ask\n\n1. Call `read_rendered_page` on the page you changed and confirm the change is there.\n2. Share the preview link. Say plainly that the live site still shows the previous version.\n3. Ask whether to publish.\n\n## Publishing\n\n- Call `publish` only after a clear yes, such as \"publish it\" or \"make it live\". \"Change X\" is not permission to publish X.\n- To publish or take down a single page on a site that is already live, use `publish` or `unpublish` with its `page_slug`.\n- Use `unpublish` (take the site offline) and `undo` with `what: \"last_publish\"` (go back to the previous published version) only when the person asks for exactly that.\n- If `publish` is refused because of their plan (`billing_gate`), pass the message on as it is. Never take another site offline to make room.\n- After publishing, give the live address and stop. Don't publish again unless they ask.\n\nIf they'd rather make a small change themselves, `get_editor_link` gives them the visual editor for the right page.\n\nWhen you give someone a one-time photo link, Sitelas can't tell you when they have used it. When they say they're done, check the spot's image in `get_page` before saying it worked. If `place_attached_image` answers `placed: false`, the photo didn't come through: give them the link it returns instead of trying again.\n"
Full snapshot data
{
  "description": "Use when someone wants to change a website they already have on Sitelas — copy, images, colours, sections, pages, navigation or SEO — or wants to publish, unpublish or undo a publish. Every change lands on a private draft. The live site changes only when the person explicitly says to publish.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 108
    }
  ],
  "name": "edit-and-publish",
  "skill_md_contents": "---\nname: edit-and-publish\ndescription: Use when someone wants to change a website they already have on Sitelas — copy, images, colours, sections, pages, navigation or SEO — or wants to publish, unpublish or undo a publish. Every change lands on a private draft. The live site changes only when the person explicitly says to publish.\n---\n\n# Edit and publish a Sitelas site\n\nEvery edit writes to the site's draft. The live address keeps showing the last published version until `publish` runs. Publishing changes what the public sees, so it needs the person's explicit go-ahead every time.\n\nIf the person's own instructions conflict with anything below, follow the person.\n\n## Find the site and what's on it\n\n- Call `list_sites` if you don't know which site they mean. If they have several, ask which one.\n- Call `get_site` with `include: [\"brief\"]` before writing copy or changing the design, so new work matches the site's existing voice, colours and fonts.\n- Call `get_page` to find the exact pieces of text and images to change. Before any change to the header or footer structure, call `get_page` with `view: \"structure\"` to see how it's nested.\n\n## Make the change with the narrowest tool\n\n| They want                                          | Use                                                                              |\n| -------------------------------------------------- | -------------------------------------------------------------------------------- |\n| Change words, links, button text or an image       | `patch_nodes`, all changes in one call                                           |\n| Swap several photos                                | `replace_images_from_search`                                                     |\n| Use a photo they attached                          | `place_attached_image`, naming the spot from `get_page`                          |\n| Use their own photo that isn't attached            | `get_editor_link` with `image_target`: a one-time link that adds it to that spot |\n| Add a section                                      | `add_section`                                                                    |\n| Remove or reorder things                           | `remove_nodes`, `move_nodes`                                                     |\n| Add, copy, rename or delete a page                 | `add_page` (with `copy_of` to copy), `update_page`, `delete_page`                |\n| Change colours or fonts site-wide                  | `set_theme`                                                                      |\n| Blog posts, projects, team members and other lists | `list_content_items`, `add_content_item`, `edit_content_item`                    |\n| How a list of them shows: order, count, card look  | `patch_nodes` on the list (see `lists` in `get_page`), `set_card_design`         |\n| Search titles and descriptions                     | `update_seo`                                                                     |\n\nA new page doesn't appear in the menu on its own. Add a menu link with `insert_nodes`, or tell the person it isn't linked yet. Rename a page's address only with `update_page`, which also updates links and redirects the old address.\n\nSeveral of a kind go in one call: `edit_content_item` with `edits` for many items, `delete_page` with `slugs`, `delete_collection` with `content_types`, `remove_nodes` with every id. Use `delete_page`, `delete_content_item` and `delete_site` only when the person has asked for that deletion. Confirm before deleting a whole site.\n\n## Pictures, payments and other sites' looks\n\n- **Pictures of the site.** When a tool answer has `preview_image`, that is the site's own main photo: use it if your reply shows a picture of the site, or show none. Never illustrate the site with an image from web search. It is another business's photo, and the person will take it for theirs.\n- **Payments.** This app doesn't add payment, deposit, donation or checkout buttons or links (Stripe, PayPal, Square and similar), and Sitelas refuses those changes. If the person asks, say so plainly and offer an enquiry or booking form instead. Taking money stays with their own provider, outside the site.\n- **Bookings and appointments.** Sitelas has no booking calendar: a site can't show free slots, take a reservation or stop double bookings. Say that first, before describing any booking flow. Then offer what it can do: a booking-request form (the visitor asks for a time, the owner confirms), or the scheduler they already use (Calendly, Cal.com, Doctolib and similar) placed on the page or linked from a button.\n- **\"Make it look like this site.\"** When they give a website address to match, call `capture_url` on it. It reads that site's colours, fonts and layout, so you don't have to guess them from web search.\n- **Colour changes.** `set_theme` recolours what follows the theme. Elements with a fixed colour don't follow it, and `review_site` counts them. After a colour change, take a `screenshot_page` and confirm the new colour actually shows before saying it changed; patch the elements that kept the old colour.\n- **Widgets.** A blank quiz or calculator has a script error that `review_site` reports as broken_widget; fix the script with `patch_nodes`. Widgets can't save anything between visits. Never ask the person to switch off Sandboxed (Secure).\n\n## Show the change, then ask\n\n1. Call `read_rendered_page` on the page you changed and confirm the change is there.\n2. Share the preview link. Say plainly that the live site still shows the previous version.\n3. Ask whether to publish.\n\n## Publishing\n\n- Call `publish` only after a clear yes, such as \"publish it\" or \"make it live\". \"Change X\" is not permission to publish X.\n- To publish or take down a single page on a site that is already live, use `publish` or `unpublish` with its `page_slug`.\n- Use `unpublish` (take the site offline) and `undo` with `what: \"last_publish\"` (go back to the previous published version) only when the person asks for exactly that.\n- If `publish` is refused because of their plan (`billing_gate`), pass the message on as it is. Never take another site offline to make room.\n- After publishing, give the live address and stop. Don't publish again unless they ask.\n\nIf they'd rather make a small change themselves, `get_editor_link` gives them the visual editor for the right page.\n\nWhen you give someone a one-time photo link, Sitelas can't tell you when they have used it. When they say they're done, check the spot's image in `get_page` before saying it worked. If `place_attached_image` answers `placed: false`, the photo didn't come through: give them the link it returns instead of trying again.\n"
}

SHA-256 of public snapshot: 50f34a69b844ddfe07154573bf40b2de82ee49ead4dda8d522309e0523c708a4