← SitelasCONTENT HISTORY

Update to Sitelas

Snapshot Nov 1, 2026 · 18:10 UTC · version 3.0.0

Collection source: downloaded plugin package.

WHAT CHANGED

Instructions updated for answer-form-messages

Skill instructions — Now says: `list_contacts` shows everyone who has submitted a form on the site. Pass a person's `email` to get their record and everything they have sent. Use them for...

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

Save Sitelas and check future changes in Following.

Up to 10 plugins free · no card required.

All fields and original values.

Skill instructions

Before

Oct 26, 2026 · 12:07 UTC

`list_contacts`, `get_contact` and `list_contact_activity` show everyone who has submitted a form on the site, and everything each person has sent. Use them for questions like "has this person written before?" or "who are my most recent ...

After

Nov 1, 2026 · 18:10 UTC

`list_contacts` shows everyone who has submitted a form on the site. Pass a person's `email` to get their record and everything they have sent. Use them for questions like "has this person written before?" or "who are my most recent lead...

Compare saved observations

Download comparison JSON

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -21,11 +21,11 @@
 
 ## Who is this person?
 
-`list_contacts`, `get_contact` and `list_contact_activity` show everyone who has submitted a form on the site, and everything each person has sent. Use them for questions like "has this person written before?" or "who are my most recent leads?".
+`list_contacts` shows everyone who has submitted a form on the site. Pass a person's `email` to get their record and everything they have sent. Use them for questions like "has this person written before?" or "who are my most recent leads?".
 
 ## Draft a reply
 
-Call `draft_reply_to_submission` with the message's id. It returns the original message and a reply outline. Adapt it in the site owner's voice (`get_site_brief` has it), answer what was actually asked, and leave clear placeholders for facts you don't know, such as prices, dates or availability.
+Open the message with `read_submission` and write the reply yourself, in the site owner's voice (`get_site` with `include: ["brief"]` has it). Answer what was actually asked, and leave clear placeholders for facts you don't know, such as prices, dates or availability.
 
 Present the draft for the owner to copy and send from their own email. Never say a reply has been sent.
 
Full technical diff · 1 changed fields

changed /skill_md_contents

BEFORE
"---\nname: answer-form-messages\ndescription: Use when someone asks about messages, enquiries, bookings or sign-ups that came in through their Sitelas website's forms, such as \"any new messages from my site?\", \"who contacted me this week?\" or \"help me reply to the catering enquiry\". Reads the site's inbox and contact records and drafts replies. It never sends anything.\n---\n\n# Answer form messages\n\nEvery Sitelas form saves what visitors submit to the site's inbox. You can read those messages, look up the person behind them, and draft a reply for the site owner to send themselves. Sitelas does not send email for you.\n\nIf the person's own instructions conflict with anything below, follow the person.\n\n## Read the inbox\n\n1. If you don't know which site, call `list_sites`. If there are several, ask which one, or check each one when they asked about \"my sites\".\n2. Call `list_submissions`. Summarise newest first, one line each: who, what they want, when, and whether it is unread. Group by form when a site has several, such as bookings and the newsletter.\n3. To open a message in full, call `read_submission`. This marks it as read. `list_submissions` doesn't.\n\n## Withheld messages\n\nOn the Free plan, a site past its monthly reading allowance still receives and stores every message. The sender and content are just withheld (`locked: true`). Say plainly that the message arrived and was kept, and when. Never suggest it was lost, and don't try to reach its content through any other tool. You can mention that the plan is managed in their Sitelas dashboard. Don't quote prices or push an upgrade.\n\n## Who is this person?\n\n`list_contacts`, `get_contact` and `list_contact_activity` show everyone who has submitted a form on the site, and everything each person has sent. Use them for questions like \"has this person written before?\" or \"who are my most recent leads?\".\n\n## Draft a reply\n\nCall `draft_reply_to_submission` with the message's id. It returns the original message and a reply outline. Adapt it in the site owner's voice (`get_site_brief` has it), answer what was actually asked, and leave clear placeholders for facts you don't know, such as prices, dates or availability.\n\nPresent the draft for the owner to copy and send from their own email. Never say a reply has been sent.\n\n## Keep it private\n\nForm messages contain other people's personal details. Quote only what the owner needs, and don't paste a sender's details into anything public, such as the website itself, unless the owner explicitly asks.\n"
AFTER
"---\nname: answer-form-messages\ndescription: Use when someone asks about messages, enquiries, bookings or sign-ups that came in through their Sitelas website's forms, such as \"any new messages from my site?\", \"who contacted me this week?\" or \"help me reply to the catering enquiry\". Reads the site's inbox and contact records and drafts replies. It never sends anything.\n---\n\n# Answer form messages\n\nEvery Sitelas form saves what visitors submit to the site's inbox. You can read those messages, look up the person behind them, and draft a reply for the site owner to send themselves. Sitelas does not send email for you.\n\nIf the person's own instructions conflict with anything below, follow the person.\n\n## Read the inbox\n\n1. If you don't know which site, call `list_sites`. If there are several, ask which one, or check each one when they asked about \"my sites\".\n2. Call `list_submissions`. Summarise newest first, one line each: who, what they want, when, and whether it is unread. Group by form when a site has several, such as bookings and the newsletter.\n3. To open a message in full, call `read_submission`. This marks it as read. `list_submissions` doesn't.\n\n## Withheld messages\n\nOn the Free plan, a site past its monthly reading allowance still receives and stores every message. The sender and content are just withheld (`locked: true`). Say plainly that the message arrived and was kept, and when. Never suggest it was lost, and don't try to reach its content through any other tool. You can mention that the plan is managed in their Sitelas dashboard. Don't quote prices or push an upgrade.\n\n## Who is this person?\n\n`list_contacts` shows everyone who has submitted a form on the site. Pass a person's `email` to get their record and everything they have sent. Use them for questions like \"has this person written before?\" or \"who are my most recent leads?\".\n\n## Draft a reply\n\nOpen the message with `read_submission` and write the reply yourself, in the site owner's voice (`get_site` with `include: [\"brief\"]` has it). Answer what was actually asked, and leave clear placeholders for facts you don't know, such as prices, dates or availability.\n\nPresent the draft for the owner to copy and send from their own email. Never say a reply has been sent.\n\n## Keep it private\n\nForm messages contain other people's personal details. Quote only what the owner needs, and don't paste a sender's details into anything public, such as the website itself, unless the owner explicitly asks.\n"
Full snapshot data
{
  "description": "Use when someone asks about messages, enquiries, bookings or sign-ups that came in through their Sitelas website's forms, such as \"any new messages from my site?\", \"who contacted me this week?\" or \"help me reply to the catering enquiry\". Reads the site's inbox and contact records and drafts replies. It never sends anything.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 106
    }
  ],
  "name": "answer-form-messages",
  "skill_md_contents": "---\nname: answer-form-messages\ndescription: Use when someone asks about messages, enquiries, bookings or sign-ups that came in through their Sitelas website's forms, such as \"any new messages from my site?\", \"who contacted me this week?\" or \"help me reply to the catering enquiry\". Reads the site's inbox and contact records and drafts replies. It never sends anything.\n---\n\n# Answer form messages\n\nEvery Sitelas form saves what visitors submit to the site's inbox. You can read those messages, look up the person behind them, and draft a reply for the site owner to send themselves. Sitelas does not send email for you.\n\nIf the person's own instructions conflict with anything below, follow the person.\n\n## Read the inbox\n\n1. If you don't know which site, call `list_sites`. If there are several, ask which one, or check each one when they asked about \"my sites\".\n2. Call `list_submissions`. Summarise newest first, one line each: who, what they want, when, and whether it is unread. Group by form when a site has several, such as bookings and the newsletter.\n3. To open a message in full, call `read_submission`. This marks it as read. `list_submissions` doesn't.\n\n## Withheld messages\n\nOn the Free plan, a site past its monthly reading allowance still receives and stores every message. The sender and content are just withheld (`locked: true`). Say plainly that the message arrived and was kept, and when. Never suggest it was lost, and don't try to reach its content through any other tool. You can mention that the plan is managed in their Sitelas dashboard. Don't quote prices or push an upgrade.\n\n## Who is this person?\n\n`list_contacts` shows everyone who has submitted a form on the site. Pass a person's `email` to get their record and everything they have sent. Use them for questions like \"has this person written before?\" or \"who are my most recent leads?\".\n\n## Draft a reply\n\nOpen the message with `read_submission` and write the reply yourself, in the site owner's voice (`get_site` with `include: [\"brief\"]` has it). Answer what was actually asked, and leave clear placeholders for facts you don't know, such as prices, dates or availability.\n\nPresent the draft for the owner to copy and send from their own email. Never say a reply has been sent.\n\n## Keep it private\n\nForm messages contain other people's personal details. Quote only what the owner needs, and don't paste a sender's details into anything public, such as the website itself, unless the owner explicitly asks.\n"
}

SHA-256 of public snapshot: b049b3d81395ccc8a897599617aac0ef57c56e5312a784be5139355820d3622a