Update to Sitelas

Snapshot Nov 1, 2026 · 18:10 UTC · version 3.0.0

Collection source: downloaded plugin package.

WHAT CHANGED

Instructions updated for edit-and-publish

Skill instructions — Now says: `publish` runs. Publishing changes what the public sees, so it needs the person's explicit go-ahead every time. - Call `get_site` with `include: ["brief"]`...

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

Save Sitelas and check future changes in Following.

Up to 10 plugins free · no card required.

All fields and original values.

Skill instructions

Before

Oct 26, 2026 · 12:07 UTC

`publish_site` runs. Publishing changes what the public sees, so it needs the person's explicit go-ahead every time. - Call `get_site_brief` before writing copy or changing the design, so new work matches the site's existing voice, colou...

After

Nov 1, 2026 · 18:10 UTC

`publish` runs. Publishing changes what the public sees, so it needs the person's explicit go-ahead every time. - Call `get_site` with `include: ["brief"]` before writing copy or changing the design, so new work matches the site's existi...

Compare saved observations

Download comparison JSON

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -5,15 +5,15 @@
 
 # Edit and publish a Sitelas site
 
-Every edit writes to the site's draft. The live address keeps showing the last published version until `publish_site` runs. Publishing changes what the public sees, so it needs the person's explicit go-ahead every time.
+Every 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.
 
 If the person's own instructions conflict with anything below, follow the person.
 
 ## Find the site and what's on it
 
 - Call `list_sites` if you don't know which site they mean. If they have several, ask which one.
-- Call `get_site_brief` before writing copy or changing the design, so new work matches the site's existing voice, colours and fonts.
-- Call `get_site_manifest` to find the exact pieces of text and images to change. Before any change to the header or footer structure, call `get_site_tree` to see how it's nested.
+- 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.
+- 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.
 
 ## Make the change with the narrowest tool
 
@@ -21,13 +21,14 @@
 | -------------------------------------------------- | -------------------------------------------------------------------------------- |
 | Change words, links, button text or an image       | `patch_nodes`, all changes in one call                                           |
 | Swap several photos                                | `replace_images_from_search`                                                     |
-| Use a photo they attached                          | `place_attached_image`, naming the spot from `get_site_manifest`                 |
+| Use a photo they attached                          | `place_attached_image`, naming the spot from `get_page`                          |
 | Use their own photo that isn't attached            | `get_editor_link` with `image_target`: a one-time link that adds it to that spot |
 | Add a section                                      | `add_section`                                                                    |
 | Remove or reorder things                           | `remove_nodes`, `move_nodes`                                                     |
-| Add, copy, rename or delete a page                 | `add_page`, `duplicate_page`, `update_page`, `delete_page`                       |
-| Change colours or fonts site-wide                  | `apply_brand`, or `apply_palette` for a full palette change                      |
+| Add, copy, rename or delete a page                 | `add_page` (with `copy_of` to copy), `update_page`, `delete_page`                |
+| Change colours or fonts site-wide                  | `set_theme`                                                                      |
 | Blog posts, projects, team members and other lists | `list_content_items`, `add_content_item`, `edit_content_item`                    |
+| How a list of them shows: order, count, card look  | `patch_nodes` on the list (see `lists` in `get_page`), `set_card_design`         |
 | Search titles and descriptions                     | `update_seo`                                                                     |
 
 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.
@@ -42,12 +43,12 @@
 
 ## Publishing
 
-- Call `publish_site` only after a clear yes, such as "publish it" or "make it live". "Change X" is not permission to publish X.
-- To publish or take down a single page on a site that is already live, use `publish_page` or `unpublish_page`.
-- Use `unpublish_site` (take the site offline) and `revert_site` (go back to the previous published version) only when the person asks for exactly that.
-- If `publish_site` is refused because of their plan (`billing_gate`), pass the message on as it is. Never take another site offline to make room.
+- Call `publish` only after a clear yes, such as "publish it" or "make it live". "Change X" is not permission to publish X.
+- To publish or take down a single page on a site that is already live, use `publish` or `unpublish` with its `page_slug`.
+- 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.
+- 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.
 - After publishing, give the live address and stop. Don't publish again unless they ask.
 
 If they'd rather make a small change themselves, `get_editor_link` gives them the visual editor for the right page.
 
-When 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_site_manifest` 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.
+When 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.

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_site` 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_brief` before writing copy or changing the design, so new work matches the site's existing voice, colours and fonts.\n- Call `get_site_manifest` to find the exact pieces of text and images to change. Before any change to the header or footer structure, call `get_site_tree` 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_site_manifest`                 |\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`, `duplicate_page`, `update_page`, `delete_page`                       |\n| Change colours or fonts site-wide                  | `apply_brand`, or `apply_palette` for a full palette change                      |\n| Blog posts, projects, team members and other lists | `list_content_items`, `add_content_item`, `edit_content_item`                    |\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_site` 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_page` or `unpublish_page`.\n- Use `unpublish_site` (take the site offline) and `revert_site` (go back to the previous published version) only when the person asks for exactly that.\n- If `publish_site` 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_site_manifest` 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\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"

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\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"
}

SHA-256 of public snapshot: 50af29958086c2a37c979b93c23dbeed4c14b5d9ccb8d62108cc4db26672c084