Update to Sitelas
Snapshot Nov 1, 2026 · 18:10 UTC · version 3.0.0
Collection source: downloaded plugin package.
Instructions updated for build-a-website
Skill instructions — Now says: `find_templates` with what you parsed: `audience`, plus `register_hint` (the mood) and `conversion_goal` when you know them. It returns the templates ranked...
Observed in instructions or declared skills. Runtime behavior has not been tested.
Up to 10 plugins free · no card required.
All fields and original values.
Skill instructions
Oct 26, 2026 · 12:07 UTC
`select_template_for_brief` with what you parsed: `audience`, plus `register_hint` (the mood) and `conversion_goal` when you know them. - If the person wants to browse, use `list_site_templates`. With no arguments it gives an overview. P...
Nov 1, 2026 · 18:10 UTC
`find_templates` with what you parsed: `audience`, plus `register_hint` (the mood) and `conversion_goal` when you know them. It returns the templates ranked for this brief. - If the person wants to browse, call `find_templates` with `mod...
Compare saved observations
Download comparison JSONSKILL.md text changes
− removed · + added
--- before +++ after @@ -17,23 +17,23 @@ ## 2. Pick the template -Call `select_template_for_brief` with what you parsed: `audience`, plus `register_hint` (the mood) and `conversion_goal` when you know them. +Call `find_templates` with what you parsed: `audience`, plus `register_hint` (the mood) and `conversion_goal` when you know them. It returns the templates ranked for this brief. - 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, use `list_site_templates`. With no arguments it gives an overview. Pass `audience` to see one shelf, and `slugs` for the full detail of a shortlist. +- 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. ## 3. Create the draft Call `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". -The result includes a `manifest` listing every editable piece of text and every image. Work from it. Don't call `get_site`, `get_site_overview` or `list_site_copy` straight after creating. +The 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. ## 4. Customize in one pass - **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. -- **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, upload it with `upload_image_from_data`. -- **Palette:** if the brief's mood is very different from the template's, call `apply_palette` as well. +- **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`. +- **Palette:** if the brief's mood is very different from the template's, call `set_theme` with the new `colors` as well. - **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. ## 5. Check your work @@ -44,7 +44,7 @@ Share 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. -Then ask whether to publish. Publish only on a clear yes, using `publish_site`, and never describe the site as live until that call has returned. Publishing is free and can be undone with `revert_site`. +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"`). ## How to talk while you work
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 `select_template_for_brief` with what you parsed: `audience`, plus `register_hint` (the mood) and `conversion_goal` when you know them.\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, use `list_site_templates`. With no arguments it gives an overview. Pass `audience` to see one shelf, and `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`, `get_site_overview` or `list_site_copy` 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, upload it with `upload_image_from_data`.\n- **Palette:** if the brief's mood is very different from the template's, call `apply_palette` 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_site`, and never describe the site as live until that call has returned. Publishing is free and can be undone with `revert_site`.\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`, plus `register_hint` (the mood) and `conversion_goal` when you know them. It returns the templates ranked for this brief.\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"
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`, plus `register_hint` (the mood) and `conversion_goal` when you know them. It returns the templates ranked for this brief.\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"
}SHA-256 of public snapshot: d0c39097940aff2ee250424b66e58b74892bcfc6ff106e5d9a6227dc6c250049