Update to Sitelas
Snapshot Nov 19, 2026 · 12:11 UTC · version 4.1.0
Collection source: downloaded plugin package.
Instructions updated for build-a-website
Skill instructions — Now says: - **"No template", "from scratch", "custom design".** When the person asks for that, don't pick a template. Call `get_example_fixtures`, follow its...
Observed in instructions or declared skills. Runtime behavior has not been tested.
Up to 3 plugins free · no card required.
All fields and original values.
Skill instructions
Nov 10, 2026 · 12:08 UTC
Call `read_rendered_page` on each page you built. Look for names, prices, phone numbers, addresses, FAQ answers or form options that still belong to the template's sample business, and fix them. They are your unfinished work, not the per...
Nov 19, 2026 · 12:11 UTC
- **"No template", "from scratch", "custom design".** When the person asks for that, don't pick a template. Call `get_example_fixtures`, follow its `_design_brief` (it shows the header, section, grid, colour and photo shapes that hold up...
Compare saved observations
Download comparison JSONSKILL.md text changes
− removed · + added
--- before +++ after @@ -22,6 +22,7 @@ - Use the best match unless something in its `antiCases` describes this person. In that case, skip it. - A match score under about 50% means no template fits well. Say so, name the closest one and ask how to proceed. - If the person wants to browse, call `find_templates` with `mode: "browse"`. Add `audience` to see one shelf, or `slugs` for the full detail of a shortlist. +- **"No template", "from scratch", "custom design".** When the person asks for that, don't pick a template. Call `get_example_fixtures`, follow its `_design_brief` (it shows the header, section, grid, colour and photo shapes that hold up on phones), and create the site with `create_site_from_fixture`. If you do start from a template anyway, your reply names it. Never describe a template-based site as made from scratch or custom-built. ## 3. Create the draft @@ -38,7 +39,7 @@ ## 5. Check your work -Call `read_rendered_page` on each page you built. Look for names, prices, phone numbers, addresses, FAQ answers or form options that still belong to the template's sample business, and fix them. They are your unfinished work, not the person's problem. Use `screenshot_page` only when the question is about how the page looks. +Call `review_site` and fix every phone_layout and broken_widget issue it reports. Its score measures structure, not taste, so "no issues" is not a description of how the site looks. Then call `read_rendered_page` on each page you built. Look for names, prices, phone numbers, addresses, FAQ answers or form options that still belong to the template's sample business, and fix them. They are your unfinished work, not the person's problem. Use `screenshot_page` only when the question is about how the page looks. ## 6. Share the preview and ask @@ -46,6 +47,15 @@ Then ask whether to publish. Publish only on a clear yes, using `publish`, and never describe the site as live until that call has returned. Publishing is free and can be undone with `undo` (`what: "last_publish"`). +## 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. +- **Quizzes, calculators and other widgets.** One `embed` per widget, inside a section with a real heading and text. Widgets run in a secure sandbox with no browser storage, so they can't save anything between visits: don't offer "save your result and come back later"; offer to send results through a form instead. If a widget shows blank, its script has an error that `review_site` reports; fix the script. Never ask the person to switch off Sandboxed (Secure). +- **Their language and their photos.** Reply in the language the person writes in. When a stock photo stands in for their own work (their portfolio, team, products or premises), say it is a placeholder and offer to put their own photos in. + ## How to talk while you work Describe what you're making ("starting from a warm editorial layout that suits a bakery", "writing the menu section") and leave tool names out. If asked which template you started from, say so plainly.
Full technical diff · 1 changed fields
changed /skill_md_contents
"---\nname: build-a-website\ndescription: Use when someone asks for a new website, landing page, portfolio or one-page site on Sitelas, such as \"build me a site for my bakery\" or \"make a portfolio for my photography\". Picks a designer-made template that fits, customizes every word and image for this business, checks the result, and shares a private preview before anything goes live.\n---\n\n# Build a website\n\nSitelas sites start from a designer-made template and are then customized for this business. A site still showing the template's sample business looks to the person like nothing was built. So customizing and checking come before sharing.\n\nIf the person's own instructions conflict with anything below, follow the person. If they say \"just build it\", stop asking questions and build from what you have.\n\n## 1. Understand the brief\n\nYou need three things: what the business or person is, the look and feel they want, and the one thing a visitor should do (call, book, enquire, buy elsewhere, read).\n\nIf the request gives you almost nothing (\"a bakery\"), ask one or two short questions first. Otherwise, start building.\n\n## 2. Pick the template\n\nCall `find_templates` with what you parsed: `audience` and `keywords` (the business in the owner's words), plus `register_hint` (the mood) and `conversion_goal` when you know them. It returns the templates ranked for this brief (`audience` alone only browses).\n\n- Use the best match unless something in its `antiCases` describes this person. In that case, skip it.\n- A match score under about 50% means no template fits well. Say so, name the closest one and ask how to proceed.\n- If the person wants to browse, call `find_templates` with `mode: \"browse\"`. Add `audience` to see one shelf, or `slugs` for the full detail of a shortlist.\n\n## 3. Create the draft\n\nCall `create_site_from_template` with `template_slug`, `site_name` and `brand_overrides`. Carry the brief's colours, and its fonts when it names a mood. If the template comes from a different line of work (for example a law-firm template used for a coaching business), also pass `page_slugs` so page addresses don't say \"/attorneys\".\n\nThe result includes a `manifest` listing every editable piece of text and every image. Work from it. Don't call `get_site` or `get_page` straight after creating.\n\n## 4. Customize in one pass\n\n- **Words:** one `patch_nodes` call covering every piece of template copy on every page, plus the header brand name. Write specific copy that the brief supports. Where you'd have to invent a fact (founding year, prices, an address), use a clear placeholder like \"[your phone number]\" rather than making one up.\n- **Images:** one `replace_images_from_search` call for every image in the manifest. Start each query from its `suggested_query` and make it specific to this business. Never type an image URL from memory. If the person attached their own photo, put it in place with `place_attached_image`.\n- **Palette:** if the brief's mood is very different from the template's, call `set_theme` with the new `colors` as well.\n- **What they asked for:** build it on this first pass. If they named a contact form, prices or opening hours, they should be on the page you share.\n\n## 5. Check your work\n\nCall `read_rendered_page` on each page you built. Look for names, prices, phone numbers, addresses, FAQ answers or form options that still belong to the template's sample business, and fix them. They are your unfinished work, not the person's problem. Use `screenshot_page` only when the question is about how the page looks.\n\n## 6. Share the preview and ask\n\nShare the preview link (`preview-….sitelas.com`) and say that the real address stays empty until they choose to publish. Add a short list, at most four items, of guesses you made that the brief didn't settle, and invite corrections. Mention that they can also edit by hand at their site's `/edit` address.\n\nThen ask whether to publish. Publish only on a clear yes, using `publish`, and never describe the site as live until that call has returned. Publishing is free and can be undone with `undo` (`what: \"last_publish\"`).\n\n## How to talk while you work\n\nDescribe what you're making (\"starting from a warm editorial layout that suits a bakery\", \"writing the menu section\") and leave tool names out. If asked which template you started from, say so plainly.\n"
"---\nname: build-a-website\ndescription: Use when someone asks for a new website, landing page, portfolio or one-page site on Sitelas, such as \"build me a site for my bakery\" or \"make a portfolio for my photography\". Picks a designer-made template that fits, customizes every word and image for this business, checks the result, and shares a private preview before anything goes live.\n---\n\n# Build a website\n\nSitelas sites start from a designer-made template and are then customized for this business. A site still showing the template's sample business looks to the person like nothing was built. So customizing and checking come before sharing.\n\nIf the person's own instructions conflict with anything below, follow the person. If they say \"just build it\", stop asking questions and build from what you have.\n\n## 1. Understand the brief\n\nYou need three things: what the business or person is, the look and feel they want, and the one thing a visitor should do (call, book, enquire, buy elsewhere, read).\n\nIf the request gives you almost nothing (\"a bakery\"), ask one or two short questions first. Otherwise, start building.\n\n## 2. Pick the template\n\nCall `find_templates` with what you parsed: `audience` and `keywords` (the business in the owner's words), plus `register_hint` (the mood) and `conversion_goal` when you know them. It returns the templates ranked for this brief (`audience` alone only browses).\n\n- Use the best match unless something in its `antiCases` describes this person. In that case, skip it.\n- A match score under about 50% means no template fits well. Say so, name the closest one and ask how to proceed.\n- If the person wants to browse, call `find_templates` with `mode: \"browse\"`. Add `audience` to see one shelf, or `slugs` for the full detail of a shortlist.\n- **\"No template\", \"from scratch\", \"custom design\".** When the person asks for that, don't pick a template. Call `get_example_fixtures`, follow its `_design_brief` (it shows the header, section, grid, colour and photo shapes that hold up on phones), and create the site with `create_site_from_fixture`. If you do start from a template anyway, your reply names it. Never describe a template-based site as made from scratch or custom-built.\n\n## 3. Create the draft\n\nCall `create_site_from_template` with `template_slug`, `site_name` and `brand_overrides`. Carry the brief's colours, and its fonts when it names a mood. If the template comes from a different line of work (for example a law-firm template used for a coaching business), also pass `page_slugs` so page addresses don't say \"/attorneys\".\n\nThe result includes a `manifest` listing every editable piece of text and every image. Work from it. Don't call `get_site` or `get_page` straight after creating.\n\n## 4. Customize in one pass\n\n- **Words:** one `patch_nodes` call covering every piece of template copy on every page, plus the header brand name. Write specific copy that the brief supports. Where you'd have to invent a fact (founding year, prices, an address), use a clear placeholder like \"[your phone number]\" rather than making one up.\n- **Images:** one `replace_images_from_search` call for every image in the manifest. Start each query from its `suggested_query` and make it specific to this business. Never type an image URL from memory. If the person attached their own photo, put it in place with `place_attached_image`.\n- **Palette:** if the brief's mood is very different from the template's, call `set_theme` with the new `colors` as well.\n- **What they asked for:** build it on this first pass. If they named a contact form, prices or opening hours, they should be on the page you share.\n\n## 5. Check your work\n\nCall `review_site` and fix every phone_layout and broken_widget issue it reports. Its score measures structure, not taste, so \"no issues\" is not a description of how the site looks. Then call `read_rendered_page` on each page you built. Look for names, prices, phone numbers, addresses, FAQ answers or form options that still belong to the template's sample business, and fix them. They are your unfinished work, not the person's problem. Use `screenshot_page` only when the question is about how the page looks.\n\n## 6. Share the preview and ask\n\nShare the preview link (`preview-….sitelas.com`) and say that the real address stays empty until they choose to publish. Add a short list, at most four items, of guesses you made that the brief didn't settle, and invite corrections. Mention that they can also edit by hand at their site's `/edit` address.\n\nThen ask whether to publish. Publish only on a clear yes, using `publish`, and never describe the site as live until that call has returned. Publishing is free and can be undone with `undo` (`what: \"last_publish\"`).\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- **Quizzes, calculators and other widgets.** One `embed` per widget, inside a section with a real heading and text. Widgets run in a secure sandbox with no browser storage, so they can't save anything between visits: don't offer \"save your result and come back later\"; offer to send results through a form instead. If a widget shows blank, its script has an error that `review_site` reports; fix the script. Never ask the person to switch off Sandboxed (Secure).\n- **Their language and their photos.** Reply in the language the person writes in. When a stock photo stands in for their own work (their portfolio, team, products or premises), say it is a placeholder and offer to put their own photos in.\n\n## How to talk while you work\n\nDescribe what you're making (\"starting from a warm editorial layout that suits a bakery\", \"writing the menu section\") and leave tool names out. If asked which template you started from, say so plainly.\n"
Full snapshot data
{
"description": "Use when someone asks for a new website, landing page, portfolio or one-page site on Sitelas, such as \"build me a site for my bakery\" or \"make a portfolio for my photography\". Picks a designer-made template that fits, customizes every word and image for this business, checks the result, and shares a private preview before anything goes live.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 107
}
],
"name": "build-a-website",
"skill_md_contents": "---\nname: build-a-website\ndescription: Use when someone asks for a new website, landing page, portfolio or one-page site on Sitelas, such as \"build me a site for my bakery\" or \"make a portfolio for my photography\". Picks a designer-made template that fits, customizes every word and image for this business, checks the result, and shares a private preview before anything goes live.\n---\n\n# Build a website\n\nSitelas sites start from a designer-made template and are then customized for this business. A site still showing the template's sample business looks to the person like nothing was built. So customizing and checking come before sharing.\n\nIf the person's own instructions conflict with anything below, follow the person. If they say \"just build it\", stop asking questions and build from what you have.\n\n## 1. Understand the brief\n\nYou need three things: what the business or person is, the look and feel they want, and the one thing a visitor should do (call, book, enquire, buy elsewhere, read).\n\nIf the request gives you almost nothing (\"a bakery\"), ask one or two short questions first. Otherwise, start building.\n\n## 2. Pick the template\n\nCall `find_templates` with what you parsed: `audience` and `keywords` (the business in the owner's words), plus `register_hint` (the mood) and `conversion_goal` when you know them. It returns the templates ranked for this brief (`audience` alone only browses).\n\n- Use the best match unless something in its `antiCases` describes this person. In that case, skip it.\n- A match score under about 50% means no template fits well. Say so, name the closest one and ask how to proceed.\n- If the person wants to browse, call `find_templates` with `mode: \"browse\"`. Add `audience` to see one shelf, or `slugs` for the full detail of a shortlist.\n- **\"No template\", \"from scratch\", \"custom design\".** When the person asks for that, don't pick a template. Call `get_example_fixtures`, follow its `_design_brief` (it shows the header, section, grid, colour and photo shapes that hold up on phones), and create the site with `create_site_from_fixture`. If you do start from a template anyway, your reply names it. Never describe a template-based site as made from scratch or custom-built.\n\n## 3. Create the draft\n\nCall `create_site_from_template` with `template_slug`, `site_name` and `brand_overrides`. Carry the brief's colours, and its fonts when it names a mood. If the template comes from a different line of work (for example a law-firm template used for a coaching business), also pass `page_slugs` so page addresses don't say \"/attorneys\".\n\nThe result includes a `manifest` listing every editable piece of text and every image. Work from it. Don't call `get_site` or `get_page` straight after creating.\n\n## 4. Customize in one pass\n\n- **Words:** one `patch_nodes` call covering every piece of template copy on every page, plus the header brand name. Write specific copy that the brief supports. Where you'd have to invent a fact (founding year, prices, an address), use a clear placeholder like \"[your phone number]\" rather than making one up.\n- **Images:** one `replace_images_from_search` call for every image in the manifest. Start each query from its `suggested_query` and make it specific to this business. Never type an image URL from memory. If the person attached their own photo, put it in place with `place_attached_image`.\n- **Palette:** if the brief's mood is very different from the template's, call `set_theme` with the new `colors` as well.\n- **What they asked for:** build it on this first pass. If they named a contact form, prices or opening hours, they should be on the page you share.\n\n## 5. Check your work\n\nCall `review_site` and fix every phone_layout and broken_widget issue it reports. Its score measures structure, not taste, so \"no issues\" is not a description of how the site looks. Then call `read_rendered_page` on each page you built. Look for names, prices, phone numbers, addresses, FAQ answers or form options that still belong to the template's sample business, and fix them. They are your unfinished work, not the person's problem. Use `screenshot_page` only when the question is about how the page looks.\n\n## 6. Share the preview and ask\n\nShare the preview link (`preview-….sitelas.com`) and say that the real address stays empty until they choose to publish. Add a short list, at most four items, of guesses you made that the brief didn't settle, and invite corrections. Mention that they can also edit by hand at their site's `/edit` address.\n\nThen ask whether to publish. Publish only on a clear yes, using `publish`, and never describe the site as live until that call has returned. Publishing is free and can be undone with `undo` (`what: \"last_publish\"`).\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- **Quizzes, calculators and other widgets.** One `embed` per widget, inside a section with a real heading and text. Widgets run in a secure sandbox with no browser storage, so they can't save anything between visits: don't offer \"save your result and come back later\"; offer to send results through a form instead. If a widget shows blank, its script has an error that `review_site` reports; fix the script. Never ask the person to switch off Sandboxed (Secure).\n- **Their language and their photos.** Reply in the language the person writes in. When a stock photo stands in for their own work (their portfolio, team, products or premises), say it is a placeholder and offer to put their own photos in.\n\n## How to talk while you work\n\nDescribe what you're making (\"starting from a warm editorial layout that suits a bakery\", \"writing the menu section\") and leave tool names out. If asked which template you started from, say so plainly.\n"
}SHA-256 of public snapshot: 84aae04cb0fbff429039bd034873a70cecb18ff0ef5d74b5e0a8f9fef9115d5f