Update to Mondovo

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

Collection source: downloaded plugin package.

WHAT CHANGED

Instructions updated for build-a-website

Skill instructions — Now says: --- name: build-a-website description: Create a new website with Mondovo from a description of a business — gather a strong brief, generate three designs,...

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: build-a-website description: Create a new website with Mondovo from a description of a business — gather a strong brief, generate three designs, help the user choose one, and publish it. Use when the user wants a new site, la...

After

Oct 28, 2026 · 12:54 UTC

Compare saved observations

Download comparison JSON

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -1,60 +1,85 @@
----
-name: build-a-website
-description: Create a new website with Mondovo from a description of a business — gather a strong brief, generate three designs, help the user choose one, and publish it. Use when the user wants a new site, landing page or online presence.
----
-
-# Build a website
-
-There are two ways to make the design: Mondovo generates three designs from a
-brief, or you design it yourself and Mondovo checks, hosts and publishes it.
-`get_intake_questions` says which ones this connection offers.
-
-## 1. Check first
-Call `list_sites` if the user might already have a site for this business, so you
-do not create a duplicate.
-
-## 2. Gather the brief
-Call `get_intake_questions`. Pre-fill every answer you can infer from the
-conversation, then ask only the real gaps, a few at a time, and show your
-assumptions so the user can correct them. The quality of the site depends on the
-brief, so get: business name, what they sell, location, who the customers are,
-what makes them different, the tone of voice, and the one action the site should
-drive (the `goal`, for example "book a consultation").
-
-Leave colours and mood open unless the user has a clear taste — then the three
-designs come back genuinely different. If they want a site like one they have
-seen, pass its address as `design.source_url`.
-
-For a ready-made business (a directory, for instance), call `list_packs` and use
-a `pack_slug` instead of a brief.
-
-## 3. Create
-If `get_intake_questions` returned a `design_method` choice, ask the user which
-they prefer.
-
-**You design it.** Write the complete site from the brief (the `files` and
-`content` shapes are in the tool description), check it with `validate_design`
-and fix every issue it lists, then call `create_site_from_design`. Put the
-business's real facts in `content`, never invented ones.
-
-**Mondovo generates it** (or there was no choice): call `create_site`. It returns a `site_id` and starts building three designs.
-This takes 3 to 15 minutes; the progress card in the chat updates itself. Tell
-the user it is underway and roughly how long it takes. Poll `get_site` about
-every 10 seconds when you need to know it has finished; only `ready` means all
-three designs are done.
-
-## 4. Choose a design
-Call `list_variations` with the `site_id`. The designs appear as a picker with
-screenshots. Let the user choose — never choose for them. If screenshots are
-still rendering, call it again in about a minute.
-
-## 5. Publish
-Only when the user asks. Suggest a subdomain from the business name (lowercase,
-hyphens) and confirm it. Call `publish_site` with the chosen design's
-`variation_id`. Publishing turns that design into its own site and returns a new
-`site_id` — use it from then on. Poll `get_site` on the new id about every 15
-seconds until `published`, then share the live link. Never call `publish_site`
-again to check on a publish that is already running.
-
-If the response is `contact_info_needs_confirmation`, show the user the contact
-details on the site and ask whether they are right before continuing.
+---
+name: build-a-website
+description: Create a new website with Mondovo from a description of a business — gather a strong brief, generate three designs, help the user choose one, and publish it. Use when the user wants a new site, landing page or online presence.
+---
+
+# Build a website
+
+There are two ways to make the design: Mondovo generates three designs from a
+brief, or you design it yourself and Mondovo checks, hosts and publishes it.
+`get_intake_questions` says which ones this connection offers.
+
+## 1. Resolve an existing site only when needed
+For an explicitly new website, go straight to gathering the brief. Do not list
+sites as an automatic duplicate check. If the user asks to reuse or continue an
+existing site, reuse its known `site_id`; only when it is missing, call
+`list_sites` with a `query` for the named site.
+
+## 2. Gather the brief
+Call `get_intake_questions`. Pre-fill every answer you can infer from the
+conversation, then ask only the real gaps, a few at a time, and show your
+assumptions so the user can correct them. The quality of the site depends on the
+brief, so get: business name, what they sell, location, who the customers are,
+what makes them different, the tone of voice, and the one action the site should
+drive (the `goal`, for example "book a consultation").
+
+Leave colours and mood open unless the user has a clear taste — then the three
+designs come back genuinely different. If they want a site like one they have
+seen, pass its address as `design.source_url`.
+
+For a ready-made business (a directory, for instance), call `list_packs` and use
+a `pack_slug` instead of a brief.
+
+## 3. Create
+If `get_intake_questions` returned a `design_method` choice, ask the user which
+they prefer.
+
+**You design it.** Write the complete site from the brief (the `files` and
+`content` shapes are in the tool description), check it with `validate_design`
+and fix every issue it lists, then call `create_site_from_design`. Put the
+business's supplied facts in `content` exactly. Do not invent its name or
+contact details. When the owner supplied no proof or prices, plausible sample
+content is allowed for their review; keep every planned section.
+
+**Mondovo generates it** (or there was no choice): call `create_site`. It returns a `site_id` and starts building three designs.
+This takes 3 to 15 minutes; the progress card in the chat updates itself. Tell
+the user it is underway and roughly how long it takes. Poll `get_site` about
+every 10 seconds when you need to know it has finished; only `ready` means all
+three designs are done.
+
+## 4. Choose a design
+Call `list_variations` with the `site_id`. The designs appear as a picker with
+screenshots. Let the user choose — never choose for them. If screenshots are
+still rendering, call it again in about a minute.
+
+## 5. Build on the chosen design
+Adding pages (`add_page`, `add_pages`), a collection or appointments to a design
+draft first copies the chosen design into its working site. Pass the user's
+chosen `variation_id`. If a call returns `choose_design`, show the designs and
+ask which to use, then retry with that ID.
+
+Relay `build_transition.tell_user` and use the returned working `site_id` for
+every later tool call, including publication. Another addition to the same
+design reuses its working site. To build a different design as a separate site,
+use the original design site's ID and that other design's `variation_id`.
+
+If an edit returns `use_build_site`, continue on its `build_site_id`. Resolve
+variation IDs on the working site when needed rather than assuming that a
+source-design ID identifies the intended variation there.
+
+## 6. Publish
+Only when the user asks. Suggest a subdomain from the business name (lowercase,
+hyphens) and confirm it. Call `publish_site` with the chosen design's
+`variation_id` when publishing from the design draft. Publishing creates or
+reuses that design's working site and returns its `site_id` — use it from then
+on. If you already received a working site ID, publish that site directly.
+Poll `get_site` on the returned ID about every 15 seconds until `published`, then share the live link. Never call `publish_site`
+again to check on a publish that is already running.
+
+If the response is `contact_info_needs_confirmation`, show the user the contact
+details on the site and ask whether they are right before continuing.
+
+If `chosen_design_lacks_edits` is returned, explain which design holds the
+owner's work and ask how they want to proceed. Do not silently change their
+selection. The response explains the editor path for deliberately publishing
+an untouched alternative.

Full technical diff · 1 changed fields

changed `/skill_md_contents`

BEFORE

"---\r\nname: build-a-website\r\ndescription: Create a new website with Mondovo from a description of a business — gather a strong brief, generate three designs, help the user choose one, and publish it. Use when the user wants a new site, landing page or online presence.\r\n---\r\n\r\n# Build a website\r\n\r\nThere are two ways to make the design: Mondovo generates three designs from a\r\nbrief, or you design it yourself and Mondovo checks, hosts and publishes it.\r\n`get_intake_questions` says which ones this connection offers.\r\n\r\n## 1. Check first\r\nCall `list_sites` if the user might already have a site for this business, so you\r\ndo not create a duplicate.\r\n\r\n## 2. Gather the brief\r\nCall `get_intake_questions`. Pre-fill every answer you can infer from the\r\nconversation, then ask only the real gaps, a few at a time, and show your\r\nassumptions so the user can correct them. The quality of the site depends on the\r\nbrief, so get: business name, what they sell, location, who the customers are,\r\nwhat makes them different, the tone of voice, and the one action the site should\r\ndrive (the `goal`, for example \"book a consultation\").\r\n\r\nLeave colours and mood open unless the user has a clear taste — then the three\r\ndesigns come back genuinely different. If they want a site like one they have\r\nseen, pass its address as `design.source_url`.\r\n\r\nFor a ready-made business (a directory, for instance), call `list_packs` and use\r\na `pack_slug` instead of a brief.\r\n\r\n## 3. Create\r\nIf `get_intake_questions` returned a `design_method` choice, ask the user which\r\nthey prefer.\r\n\r\n**You design it.** Write the complete site from the brief (the `files` and\r\n`content` shapes are in the tool description), check it with `validate_design`\r\nand fix every issue it lists, then call `create_site_from_design`. Put the\r\nbusiness's real facts in `content`, never invented ones.\r\n\r\n**Mondovo generates it** (or there was no choice): call `create_site`. It returns a `site_id` and starts building three designs.\r\nThis takes 3 to 15 minutes; the progress card in the chat updates itself. Tell\r\nthe user it is underway and roughly how long it takes. Poll `get_site` about\r\nevery 10 seconds when you need to know it has finished; only `ready` means all\r\nthree designs are done.\r\n\r\n## 4. Choose a design\r\nCall `list_variations` with the `site_id`. The designs appear as a picker with\r\nscreenshots. Let the user choose — never choose for them. If screenshots are\r\nstill rendering, call it again in about a minute.\r\n\r\n## 5. Publish\r\nOnly when the user asks. Suggest a subdomain from the business name (lowercase,\r\nhyphens) and confirm it. Call `publish_site` with the chosen design's\r\n`variation_id`. Publishing turns that design into its own site and returns a new\r\n`site_id` — use it from then on. Poll `get_site` on the new id about every 15\r\nseconds until `published`, then share the live link. Never call `publish_site`\r\nagain to check on a publish that is already running.\r\n\r\nIf the response is `contact_info_needs_confirmation`, show the user the contact\r\ndetails on the site and ask whether they are right before continuing.\r\n"

AFTER

"---\nname: build-a-website\ndescription: Create a new website with Mondovo from a description of a business — gather a strong brief, generate three designs, help the user choose one, and publish it. Use when the user wants a new site, landing page or online presence.\n---\n\n# Build a website\n\nThere are two ways to make the design: Mondovo generates three designs from a\nbrief, or you design it yourself and Mondovo checks, hosts and publishes it.\n`get_intake_questions` says which ones this connection offers.\n\n## 1. Resolve an existing site only when needed\nFor an explicitly new website, go straight to gathering the brief. Do not list\nsites as an automatic duplicate check. If the user asks to reuse or continue an\nexisting site, reuse its known `site_id`; only when it is missing, call\n`list_sites` with a `query` for the named site.\n\n## 2. Gather the brief\nCall `get_intake_questions`. Pre-fill every answer you can infer from the\nconversation, then ask only the real gaps, a few at a time, and show your\nassumptions so the user can correct them. The quality of the site depends on the\nbrief, so get: business name, what they sell, location, who the customers are,\nwhat makes them different, the tone of voice, and the one action the site should\ndrive (the `goal`, for example \"book a consultation\").\n\nLeave colours and mood open unless the user has a clear taste — then the three\ndesigns come back genuinely different. If they want a site like one they have\nseen, pass its address as `design.source_url`.\n\nFor a ready-made business (a directory, for instance), call `list_packs` and use\na `pack_slug` instead of a brief.\n\n## 3. Create\nIf `get_intake_questions` returned a `design_method` choice, ask the user which\nthey prefer.\n\n**You design it.** Write the complete site from the brief (the `files` and\n`content` shapes are in the tool description), check it with `validate_design`\nand fix every issue it lists, then call `create_site_from_design`. Put the\nbusiness's supplied facts in `content` exactly. Do not invent its name or\ncontact details. When the owner supplied no proof or prices, plausible sample\ncontent is allowed for their review; keep every planned section.\n\n**Mondovo generates it** (or there was no choice): call `create_site`. It returns a `site_id` and starts building three designs.\nThis takes 3 to 15 minutes; the progress card in the chat updates itself. Tell\nthe user it is underway and roughly how long it takes. Poll `get_site` about\nevery 10 seconds when you need to know it has finished; only `ready` means all\nthree designs are done.\n\n## 4. Choose a design\nCall `list_variations` with the `site_id`. The designs appear as a picker with\nscreenshots. Let the user choose — never choose for them. If screenshots are\nstill rendering, call it again in about a minute.\n\n## 5. Build on the chosen design\nAdding pages (`add_page`, `add_pages`), a collection or appointments to a design\ndraft first copies the chosen design into its working site. Pass the user's\nchosen `variation_id`. If a call returns `choose_design`, show the designs and\nask which to use, then retry with that ID.\n\nRelay `build_transition.tell_user` and use the returned working `site_id` for\nevery later tool call, including publication. Another addition to the same\ndesign reuses its working site. To build a different design as a separate site,\nuse the original design site's ID and that other design's `variation_id`.\n\nIf an edit returns `use_build_site`, continue on its `build_site_id`. Resolve\nvariation IDs on the working site when needed rather than assuming that a\nsource-design ID identifies the intended variation there.\n\n## 6. Publish\nOnly when the user asks. Suggest a subdomain from the business name (lowercase,\nhyphens) and confirm it. Call `publish_site` with the chosen design's\n`variation_id` when publishing from the design draft. Publishing creates or\nreuses that design's working site and returns its `site_id` — use it from then\non. If you already received a working site ID, publish that site directly.\nPoll `get_site` on the returned ID about every 15 seconds until `published`, then share the live link. Never call `publish_site`\nagain to check on a publish that is already running.\n\nIf the response is `contact_info_needs_confirmation`, show the user the contact\ndetails on the site and ask whether they are right before continuing.\n\nIf `chosen_design_lacks_edits` is returned, explain which design holds the\nowner's work and ask how they want to proceed. Do not silently change their\nselection. The response explains the editor path for deliberately publishing\nan untouched alternative.\n"

Full snapshot data

{
"description": "Create a new website with Mondovo from a description of a business — gather a strong brief, generate three designs, help the user choose one, and publish it. Use when the user wants a new site, landing page or online presence.",
"included_files": [],
"name": "build-a-website",
"skill_md_contents": "---\nname: build-a-website\ndescription: Create a new website with Mondovo from a description of a business — gather a strong brief, generate three designs, help the user choose one, and publish it. Use when the user wants a new site, landing page or online presence.\n---\n\n# Build a website\n\nThere are two ways to make the design: Mondovo generates three designs from a\nbrief, or you design it yourself and Mondovo checks, hosts and publishes it.\n`get_intake_questions` says which ones this connection offers.\n\n## 1. Resolve an existing site only when needed\nFor an explicitly new website, go straight to gathering the brief. Do not list\nsites as an automatic duplicate check. If the user asks to reuse or continue an\nexisting site, reuse its known `site_id`; only when it is missing, call\n`list_sites` with a `query` for the named site.\n\n## 2. Gather the brief\nCall `get_intake_questions`. Pre-fill every answer you can infer from the\nconversation, then ask only the real gaps, a few at a time, and show your\nassumptions so the user can correct them. The quality of the site depends on the\nbrief, so get: business name, what they sell, location, who the customers are,\nwhat makes them different, the tone of voice, and the one action the site should\ndrive (the `goal`, for example \"book a consultation\").\n\nLeave colours and mood open unless the user has a clear taste — then the three\ndesigns come back genuinely different. If they want a site like one they have\nseen, pass its address as `design.source_url`.\n\nFor a ready-made business (a directory, for instance), call `list_packs` and use\na `pack_slug` instead of a brief.\n\n## 3. Create\nIf `get_intake_questions` returned a `design_method` choice, ask the user which\nthey prefer.\n\n**You design it.** Write the complete site from the brief (the `files` and\n`content` shapes are in the tool description), check it with `validate_design`\nand fix every issue it lists, then call `create_site_from_design`. Put the\nbusiness's supplied facts in `content` exactly. Do not invent its name or\ncontact details. When the owner supplied no proof or prices, plausible sample\ncontent is allowed for their review; keep every planned section.\n\n**Mondovo generates it** (or there was no choice): call `create_site`. It returns a `site_id` and starts building three designs.\nThis takes 3 to 15 minutes; the progress card in the chat updates itself. Tell\nthe user it is underway and roughly how long it takes. Poll `get_site` about\nevery 10 seconds when you need to know it has finished; only `ready` means all\nthree designs are done.\n\n## 4. Choose a design\nCall `list_variations` with the `site_id`. The designs appear as a picker with\nscreenshots. Let the user choose — never choose for them. If screenshots are\nstill rendering, call it again in about a minute.\n\n## 5. Build on the chosen design\nAdding pages (`add_page`, `add_pages`), a collection or appointments to a design\ndraft first copies the chosen design into its working site. Pass the user's\nchosen `variation_id`. If a call returns `choose_design`, show the designs and\nask which to use, then retry with that ID.\n\nRelay `build_transition.tell_user` and use the returned working `site_id` for\nevery later tool call, including publication. Another addition to the same\ndesign reuses its working site. To build a different design as a separate site,\nuse the original design site's ID and that other design's `variation_id`.\n\nIf an edit returns `use_build_site`, continue on its `build_site_id`. Resolve\nvariation IDs on the working site when needed rather than assuming that a\nsource-design ID identifies the intended variation there.\n\n## 6. Publish\nOnly when the user asks. Suggest a subdomain from the business name (lowercase,\nhyphens) and confirm it. Call `publish_site` with the chosen design's\n`variation_id` when publishing from the design draft. Publishing creates or\nreuses that design's working site and returns its `site_id` — use it from then\non. If you already received a working site ID, publish that site directly.\nPoll `get_site` on the returned ID about every 15 seconds until `published`, then share the live link. Never call `publish_site`\nagain to check on a publish that is already running.\n\nIf the response is `contact_info_needs_confirmation`, show the user the contact\ndetails on the site and ask whether they are right before continuing.\n\nIf `chosen_design_lacks_edits` is returned, explain which design holds the\nowner's work and ask how they want to proceed. Do not silently change their\nselection. The response explains the editor path for deliberately publishing\nan untouched alternative.\n"
}

SHA-256 of public snapshot: 2c7f129b2ae800c06644394120f62c1e182200d6c6faa5e92100e1f74c5c97e6