← MondovoCONTENT HISTORY

Update to Mondovo

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

Collection source: downloaded plugin package.

WHAT CHANGED

Instructions updated for onboarding

Full description — Now says: Explain Mondovo when the user explicitly asks what it can do or how to get started. Do not invoke just because it was installed or connected, or before...

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.

Full description

Before

Oct 24, 2026 · 13:37 UTC

Welcome a person who just installed Mondovo, show what it can do, and get them to their first website. Use right after installation or when the user asks how to get started with Mondovo.

After

Oct 28, 2026 · 12:54 UTC

Explain Mondovo when the user explicitly asks what it can do or how to get started. Do not invoke just because it was installed or connected, or before handling a specific task.

Skill instructions

Before

Oct 24, 2026 · 13:37 UTC

--- name: onboarding description: Welcome a person who just installed Mondovo, show what it can do, and get them to their first website. Use right after installation or when the user asks how to get started with Mondovo. --- # Get ...

After

Oct 28, 2026 · 12:54 UTC

--- name: onboarding description: Explain Mondovo when the user explicitly asks what it can do or how to get started. Do not invoke just because it was installed or connected, or before handling a specific task. --- # Get started with M...

Compare saved observations

Download comparison JSON

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -1,27 +1,31 @@
----
-name: onboarding
-description: Welcome a person who just installed Mondovo, show what it can do, and get them to their first website. Use right after installation or when the user asks how to get started with Mondovo.
----
-
-# Get started with Mondovo
-
-1. Call `list_sites` to see whether this account already has websites. The result
-   appears as a gallery card, so do not list every site in prose.
-2. If they already have sites, say how many and offer the three most useful next
-   steps: change something on a site, add a page, or publish a draft. Mention once
-   that they can also keep the site current by asking — add to a menu, write a
-   blog post, update a product or price, or turn on appointment booking.
-3. If they have none, say in two or three sentences what Mondovo does — it designs
-   three complete websites from a description of the business, they pick one, ask
-   for changes in plain words, and publish when ready; building and editing are
-   free — then ask what business the first website is for. If the welcome card
-   appears, its buttons send these same starting points; let the person use them.
-4. When they answer, follow the `build-a-website` skill. Run the intake as a short
-   conversation: one or two questions per message, each with two to four
-   suggested answers to pick from (for tone: "warm and friendly", "premium",
-   "bold and modern"). State what you inferred for a quick yes, and start
-   building after a few exchanges rather than asking every question.
-
-Keep it short and friendly. Never invent business facts (prices, addresses,
-phone numbers, reviews) — ask, or leave them out. Never mention how
-Mondovo works internally (models, providers, infrastructure).
+---
+name: onboarding
+description: Explain Mondovo when the user explicitly asks what it can do or how to get started. Do not invoke just because it was installed or connected, or before handling a specific task.
+---
+
+# Get started with Mondovo
+
+1. Answer the getting-started or capability question conversationally. Installation,
+   connection, a greeting, or mentioning Mondovo is not a request to browse sites.
+   Do not call `list_sites` to personalize a welcome or check the connection.
+2. Briefly explain the capabilities relevant to their question. For websites,
+   Mondovo designs three complete websites from a business description, lets them
+   pick one and request changes in plain words, and publishes when ready;
+   building and editing are free. Ask what they want to do without assuming they
+   want a website or that their account is empty.
+3. For a specific task, go directly to its tools or skill. Call `list_sites` only
+   if they ask to browse or find their sites, or the task needs an existing
+   `site_id` that is missing from the conversation and returned records. Reuse
+   known IDs. Each call can open a gallery; never use it as a warm-up for a
+   keyword-demand check, image, video, or other task that needs no site lookup.
+4. If they choose to build a website, follow the `build-a-website` skill. Run the
+   intake as a short conversation: one or two questions per message, each with two to four
+   suggested answers to pick from (for tone: "warm and friendly", "premium",
+   "bold and modern"). State what you inferred for a quick yes, and start
+   building after a few exchanges rather than asking every question.
+
+Keep it short and friendly. Preserve owner-supplied facts exactly; never invent
+the business name or contact details. Generated sites may use plausible sample
+proof and prices for the owner to review when none were supplied. Keep planned
+sections. Never mention how Mondovo works internally (models, providers,
+infrastructure).
Full technical diff · 2 changed fields

changed /description

BEFORE
"Welcome a person who just installed Mondovo, show what it can do, and get them to their first website. Use right after installation or when the user asks how to get started with Mondovo."
AFTER
"Explain Mondovo when the user explicitly asks what it can do or how to get started. Do not invoke just because it was installed or connected, or before handling a specific task."

changed /skill_md_contents

BEFORE
"---\r\nname: onboarding\r\ndescription: Welcome a person who just installed Mondovo, show what it can do, and get them to their first website. Use right after installation or when the user asks how to get started with Mondovo.\r\n---\r\n\r\n# Get started with Mondovo\r\n\r\n1. Call `list_sites` to see whether this account already has websites. The result\r\n   appears as a gallery card, so do not list every site in prose.\r\n2. If they already have sites, say how many and offer the three most useful next\r\n   steps: change something on a site, add a page, or publish a draft. Mention once\r\n   that they can also keep the site current by asking — add to a menu, write a\r\n   blog post, update a product or price, or turn on appointment booking.\r\n3. If they have none, say in two or three sentences what Mondovo does — it designs\r\n   three complete websites from a description of the business, they pick one, ask\r\n   for changes in plain words, and publish when ready; building and editing are\r\n   free — then ask what business the first website is for. If the welcome card\r\n   appears, its buttons send these same starting points; let the person use them.\r\n4. When they answer, follow the `build-a-website` skill. Run the intake as a short\r\n   conversation: one or two questions per message, each with two to four\r\n   suggested answers to pick from (for tone: \"warm and friendly\", \"premium\",\r\n   \"bold and modern\"). State what you inferred for a quick yes, and start\r\n   building after a few exchanges rather than asking every question.\r\n\r\nKeep it short and friendly. Never invent business facts (prices, addresses,\r\nphone numbers, reviews) — ask, or leave them out. Never mention how\r\nMondovo works internally (models, providers, infrastructure).\r\n"
AFTER
"---\nname: onboarding\ndescription: Explain Mondovo when the user explicitly asks what it can do or how to get started. Do not invoke just because it was installed or connected, or before handling a specific task.\n---\n\n# Get started with Mondovo\n\n1. Answer the getting-started or capability question conversationally. Installation,\n   connection, a greeting, or mentioning Mondovo is not a request to browse sites.\n   Do not call `list_sites` to personalize a welcome or check the connection.\n2. Briefly explain the capabilities relevant to their question. For websites,\n   Mondovo designs three complete websites from a business description, lets them\n   pick one and request changes in plain words, and publishes when ready;\n   building and editing are free. Ask what they want to do without assuming they\n   want a website or that their account is empty.\n3. For a specific task, go directly to its tools or skill. Call `list_sites` only\n   if they ask to browse or find their sites, or the task needs an existing\n   `site_id` that is missing from the conversation and returned records. Reuse\n   known IDs. Each call can open a gallery; never use it as a warm-up for a\n   keyword-demand check, image, video, or other task that needs no site lookup.\n4. If they choose to build a website, follow the `build-a-website` skill. Run the\n   intake as a short conversation: one or two questions per message, each with two to four\n   suggested answers to pick from (for tone: \"warm and friendly\", \"premium\",\n   \"bold and modern\"). State what you inferred for a quick yes, and start\n   building after a few exchanges rather than asking every question.\n\nKeep it short and friendly. Preserve owner-supplied facts exactly; never invent\nthe business name or contact details. Generated sites may use plausible sample\nproof and prices for the owner to review when none were supplied. Keep planned\nsections. Never mention how Mondovo works internally (models, providers,\ninfrastructure).\n"
Full snapshot data
{
  "description": "Explain Mondovo when the user explicitly asks what it can do or how to get started. Do not invoke just because it was installed or connected, or before handling a specific task.",
  "included_files": [],
  "name": "onboarding",
  "skill_md_contents": "---\nname: onboarding\ndescription: Explain Mondovo when the user explicitly asks what it can do or how to get started. Do not invoke just because it was installed or connected, or before handling a specific task.\n---\n\n# Get started with Mondovo\n\n1. Answer the getting-started or capability question conversationally. Installation,\n   connection, a greeting, or mentioning Mondovo is not a request to browse sites.\n   Do not call `list_sites` to personalize a welcome or check the connection.\n2. Briefly explain the capabilities relevant to their question. For websites,\n   Mondovo designs three complete websites from a business description, lets them\n   pick one and request changes in plain words, and publishes when ready;\n   building and editing are free. Ask what they want to do without assuming they\n   want a website or that their account is empty.\n3. For a specific task, go directly to its tools or skill. Call `list_sites` only\n   if they ask to browse or find their sites, or the task needs an existing\n   `site_id` that is missing from the conversation and returned records. Reuse\n   known IDs. Each call can open a gallery; never use it as a warm-up for a\n   keyword-demand check, image, video, or other task that needs no site lookup.\n4. If they choose to build a website, follow the `build-a-website` skill. Run the\n   intake as a short conversation: one or two questions per message, each with two to four\n   suggested answers to pick from (for tone: \"warm and friendly\", \"premium\",\n   \"bold and modern\"). State what you inferred for a quick yes, and start\n   building after a few exchanges rather than asking every question.\n\nKeep it short and friendly. Preserve owner-supplied facts exactly; never invent\nthe business name or contact details. Generated sites may use plausible sample\nproof and prices for the owner to review when none were supplied. Keep planned\nsections. Never mention how Mondovo works internally (models, providers,\ninfrastructure).\n"
}

SHA-256 of public snapshot: ce5c74e76cff6a6c3b6522e2f71d77c0c2e7fd17c385852fde982b815a893969