Update to Mondovo

Snapshot Oct 28, 2026 · 12:54 UTC · version 1.0.11

Collection source: downloaded plugin package.

WHAT CHANGED

Instructions updated for edit-a-website

Skill instructions — Now says: --- name: edit-a-website description: Change an existing Mondovo website — text, prices, images, layout, styling, new pages — and undo changes. Use when the...

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

Save Mondovo and check future changes in Following.

Up to 10 plugins free · no card required.

All fields and original values.

Skill instructions

Before

Oct 24, 2026 · 13:37 UTC

--- name: edit-a-website description: Change an existing Mondovo website — text, prices, images, layout, styling, new pages — and undo changes. Use when the user wants to update, fix, redesign part of, or add to a site they already hav...

After

Oct 28, 2026 · 12:54 UTC

Compare saved observations

Download comparison JSON

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -1,30 +1,41 @@
----
-name: edit-a-website
-description: Change an existing Mondovo website — text, prices, images, layout, styling, new pages — and undo changes. Use when the user wants to update, fix, redesign part of, or add to a site they already have.
----
-
-# Edit a website
-
-Find the site with `list_sites` (or use the `site_id` already in the
-conversation). Then pick the lightest tool that does the job:
-
-| The user wants | Use |
-|---|---|
-| Different words, prices, FAQ answers, links or image addresses | `patch_variation_content` — instant, no redesign |
-| A layout, style or section change ("make the hero darker", "add testimonials") | `refine_site` with the request in plain words |
-| A new page (About, Services, Contact…) | `add_page`, or `add_pages` for several |
-| To go back to how it was | `list_versions`, then `restore_version` |
-
-- `refine_site`, `add_page` and `add_pages` return a `job_id`. The chat shows a
-  progress card that updates itself; poll `get_job` about every 10 seconds when
-  you need the result. A finished job can still list items in `failed` — tell the
-  user about each one.
-- To show a reference image for a change, upload it with `upload_asset` and pass
-  the returned address in `image_urls`.
-- If a site is busy with another change you get `site_busy` with that job's id —
-  wait for it, then try again.
-- Every change is saved in the site's version history and can be undone. If a
-  response carries `history_warning`, tell the user the change saved but was not
-  recorded before making more edits.
-- Changes are not live until the site is published again. Offer to publish after
-  a round of edits (see the `build-a-website` skill, step 5).
+---
+name: edit-a-website
+description: Change an existing Mondovo website — text, prices, images, layout, styling, new pages — and undo changes. Use when the user wants to update, fix, redesign part of, or add to a site they already have.
+---
+
+# Edit a website
+
+Reuse the `site_id` already in the conversation or returned records. Only if it
+is missing, find the site with `list_sites`, using a `query` for its name.
+Then pick the lightest tool that does the job:
+
+| The user wants | Use |
+|---|---|
+| Different words, prices, FAQ answers, links or image addresses | `patch_variation_content` — instant, no redesign |
+| A layout, style or section change ("make the hero darker", "add testimonials") | `refine_site` with the request in plain words |
+| A new page (About, Services, Contact…) | `add_page`, or `add_pages` for several |
+| To go back to how it was | `list_versions`, then `restore_version` |
+
+- On a design draft, adding pages, a collection or appointments first builds
+  the chosen design into its working site. Pass its `variation_id`; on
+  `choose_design`, show the designs and ask the user which to build from.
+  Relay `build_transition.tell_user` and use its returned working `site_id`
+  for every later call, including publish. Repeated additions reuse that site.
+- If an edit returns `use_build_site`, retry on its `build_site_id`. Read that
+  site's designs when a variation ID is needed rather than assuming that a
+  source-design ID identifies the intended variation there.
+- `refine_site`, generated `add_page` calls and `add_pages` return a `job_id`.
+  An `add_page` call with authored `code` saves immediately without a job.
+  For generated changes, the chat shows a
+  progress card that updates itself; poll `get_job` about every 10 seconds when
+  you need the result. A finished job can still list items in `failed` — tell the
+  user about each one.
+- To show a reference image for a change, upload it with `upload_asset` and pass
+  the returned address in `image_urls`.
+- If a site is busy with another change you get `site_busy` with that job's id —
+  wait for it, then try again.
+- Every change is saved in the site's version history and can be undone. If a
+  response carries `history_warning`, tell the user the change saved but was not
+  recorded before making more edits.
+- Changes are not live until the site is published again. Offer to publish after
+  a round of edits (see the `build-a-website` skill, step 6).

Full technical diff · 1 changed fields

changed `/skill_md_contents`

BEFORE

"---\r\nname: edit-a-website\r\ndescription: Change an existing Mondovo website — text, prices, images, layout, styling, new pages — and undo changes. Use when the user wants to update, fix, redesign part of, or add to a site they already have.\r\n---\r\n\r\n# Edit a website\r\n\r\nFind the site with `list_sites` (or use the `site_id` already in the\r\nconversation). Then pick the lightest tool that does the job:\r\n\r\n| The user wants | Use |\r\n|---|---|\r\n| Different words, prices, FAQ answers, links or image addresses | `patch_variation_content` — instant, no redesign |\r\n| A layout, style or section change (\"make the hero darker\", \"add testimonials\") | `refine_site` with the request in plain words |\r\n| A new page (About, Services, Contact…) | `add_page`, or `add_pages` for several |\r\n| To go back to how it was | `list_versions`, then `restore_version` |\r\n\r\n- `refine_site`, `add_page` and `add_pages` return a `job_id`. The chat shows a\r\n  progress card that updates itself; poll `get_job` about every 10 seconds when\r\n  you need the result. A finished job can still list items in `failed` — tell the\r\n  user about each one.\r\n- To show a reference image for a change, upload it with `upload_asset` and pass\r\n  the returned address in `image_urls`.\r\n- If a site is busy with another change you get `site_busy` with that job's id —\r\n  wait for it, then try again.\r\n- Every change is saved in the site's version history and can be undone. If a\r\n  response carries `history_warning`, tell the user the change saved but was not\r\n  recorded before making more edits.\r\n- Changes are not live until the site is published again. Offer to publish after\r\n  a round of edits (see the `build-a-website` skill, step 5).\r\n"

AFTER

"---\nname: edit-a-website\ndescription: Change an existing Mondovo website — text, prices, images, layout, styling, new pages — and undo changes. Use when the user wants to update, fix, redesign part of, or add to a site they already have.\n---\n\n# Edit a website\n\nReuse the `site_id` already in the conversation or returned records. Only if it\nis missing, find the site with `list_sites`, using a `query` for its name.\nThen pick the lightest tool that does the job:\n\n| The user wants | Use |\n|---|---|\n| Different words, prices, FAQ answers, links or image addresses | `patch_variation_content` — instant, no redesign |\n| A layout, style or section change (\"make the hero darker\", \"add testimonials\") | `refine_site` with the request in plain words |\n| A new page (About, Services, Contact…) | `add_page`, or `add_pages` for several |\n| To go back to how it was | `list_versions`, then `restore_version` |\n\n- On a design draft, adding pages, a collection or appointments first builds\n  the chosen design into its working site. Pass its `variation_id`; on\n  `choose_design`, show the designs and ask the user which to build from.\n  Relay `build_transition.tell_user` and use its returned working `site_id`\n  for every later call, including publish. Repeated additions reuse that site.\n- If an edit returns `use_build_site`, retry on its `build_site_id`. Read that\n  site's designs when a variation ID is needed rather than assuming that a\n  source-design ID identifies the intended variation there.\n- `refine_site`, generated `add_page` calls and `add_pages` return a `job_id`.\n  An `add_page` call with authored `code` saves immediately without a job.\n  For generated changes, the chat shows a\n  progress card that updates itself; poll `get_job` about every 10 seconds when\n  you need the result. A finished job can still list items in `failed` — tell the\n  user about each one.\n- To show a reference image for a change, upload it with `upload_asset` and pass\n  the returned address in `image_urls`.\n- If a site is busy with another change you get `site_busy` with that job's id —\n  wait for it, then try again.\n- Every change is saved in the site's version history and can be undone. If a\n  response carries `history_warning`, tell the user the change saved but was not\n  recorded before making more edits.\n- Changes are not live until the site is published again. Offer to publish after\n  a round of edits (see the `build-a-website` skill, step 6).\n"

Full snapshot data

{
  "description": "Change an existing Mondovo website — text, prices, images, layout, styling, new pages — and undo changes. Use when the user wants to update, fix, redesign part of, or add to a site they already have.",
  "included_files": [],
  "name": "edit-a-website",
  "skill_md_contents": "---\nname: edit-a-website\ndescription: Change an existing Mondovo website — text, prices, images, layout, styling, new pages — and undo changes. Use when the user wants to update, fix, redesign part of, or add to a site they already have.\n---\n\n# Edit a website\n\nReuse the `site_id` already in the conversation or returned records. Only if it\nis missing, find the site with `list_sites`, using a `query` for its name.\nThen pick the lightest tool that does the job:\n\n| The user wants | Use |\n|---|---|\n| Different words, prices, FAQ answers, links or image addresses | `patch_variation_content` — instant, no redesign |\n| A layout, style or section change (\"make the hero darker\", \"add testimonials\") | `refine_site` with the request in plain words |\n| A new page (About, Services, Contact…) | `add_page`, or `add_pages` for several |\n| To go back to how it was | `list_versions`, then `restore_version` |\n\n- On a design draft, adding pages, a collection or appointments first builds\n  the chosen design into its working site. Pass its `variation_id`; on\n  `choose_design`, show the designs and ask the user which to build from.\n  Relay `build_transition.tell_user` and use its returned working `site_id`\n  for every later call, including publish. Repeated additions reuse that site.\n- If an edit returns `use_build_site`, retry on its `build_site_id`. Read that\n  site's designs when a variation ID is needed rather than assuming that a\n  source-design ID identifies the intended variation there.\n- `refine_site`, generated `add_page` calls and `add_pages` return a `job_id`.\n  An `add_page` call with authored `code` saves immediately without a job.\n  For generated changes, the chat shows a\n  progress card that updates itself; poll `get_job` about every 10 seconds when\n  you need the result. A finished job can still list items in `failed` — tell the\n  user about each one.\n- To show a reference image for a change, upload it with `upload_asset` and pass\n  the returned address in `image_urls`.\n- If a site is busy with another change you get `site_busy` with that job's id —\n  wait for it, then try again.\n- Every change is saved in the site's version history and can be undone. If a\n  response carries `history_warning`, tell the user the change saved but was not\n  recorded before making more edits.\n- Changes are not live until the site is published again. Offer to publish after\n  a round of edits (see the `build-a-website` skill, step 6).\n"
}

SHA-256 of public snapshot: 3004094aecb70bb3ed3c5201e1cd530459bf8b9a3265d4bfd02f42b64440aa2c