Update to Hostinger Connector

{
  "name": "email-marketing",
  "description": "Use when the user wants to work with Hostinger Reach, their email marketing product — listing and creating contacts, importing contacts in bulk, organising them into groups, building segments with custom criteria, reading segment membership, listing marketing profiles, and checking whether a sending domain's MX, SPF, DKIM and DMARC records are configured. Not for mailboxes or reading mail.",
  "included_files": [],
  "skill_md_contents": "---\nname: email-marketing\ndescription: Use when the user wants to work with Hostinger Reach, their email marketing product — listing and creating contacts, importing contacts in bulk, organising them into groups, building segments with custom criteria, reading segment membership, listing marketing profiles, and checking whether a sending domain's MX, SPF, DKIM and DMARC records are configured. Not for mailboxes or reading mail.\n---\n\n# Email marketing (Reach)\n\nBinary: **`hostinger-reach-mcp`** — every tool named `reach_*`.\n\nRun the `hostinger` router first. Its safety gates apply to everything here.\n\nThis is **marketing contacts and segments**, not email hosting. Creating a\nmailbox, forwarding, or an autoreply is a different product and is not covered by\nany skill in this plugin — say so rather than reaching for another binary.\n\n## Start from the profile\n\nEverything is scoped to a Reach profile. `reach_listProfilesV1` lists them; take\nthe identifier from there rather than guessing, and if there are several, ask\nwhich one before writing anything.\n\n`reach_getProfileDomainDNSStatusV1` reports the MX, SPF, DKIM and DMARC state for\nthe profile's sending domain. **Check this before the user sends anything to a\nreal list** — a domain missing SPF or DKIM gets its mail filtered as spam, and\nthat damages the domain's reputation in a way that is slow to undo. Fixing the\nrecords themselves is the `domains` skill.\n\n## Reading contacts, groups and segments\n\n- `reach_listContactsV1` — paginated, filterable by group and subscription\n  status. Respect the subscription status: an unsubscribed contact is a request\n  the user is legally obliged to honour, not a row to work around.\n- `reach_listContactGroupsV1` — groups the contacts are organised into.\n- `reach_listSegmentsV1`, `reach_getSegmentDetailsV1` — segments and one\n  segment's definition.\n- `reach_listSegmentContactsV1`, `reach_listProfileSegmentContactsV1` — who is\n  actually in a segment. Use these to show the user the size and shape of an\n  audience *before* they act on it.\n\n## Personal data — the constraint that shapes this whole skill\n\nContacts are named people with email addresses, and in many jurisdictions that\nis regulated personal data. Treat it accordingly:\n\n- **Never write contact data into project files, commits, deploy archives, or a\n  summary that could be pasted elsewhere.** Show it in the conversation to the\n  user who asked, and nowhere else.\n- **Never import a list the user cannot account for.** Before\n  `reach_createNewContactsV1`, ask where the addresses came from and confirm the\n  people consented to marketing email. If the answer is a scraped list, a\n  purchased list, or \"found it somewhere\", decline and say why: it is a legal\n  problem for the user and it will burn their sending domain.\n- **Never invent contacts.** Do not fabricate names or addresses to fill out a\n  test, and do not derive an address from a pattern (`firstname@company.com`).\n- **Do not enrich.** Adding data about a contact from another source is not what\n  the user asked for and is exactly what data protection rules restrict.\n\n## Writes\n\n- `reach_createANewContactV1` — one contact. Read back the name, email and group\n  before creating it.\n- `reach_createNewContactsV1` — bulk. State **how many** contacts, which group\n  they land in, and where the list came from, then take one confirmation. A bulk\n  import is the highest-volume write in this skill; a mistake here is visible to\n  every recipient.\n- `reach_createANewContactSegmentV1` — a segment definition. Show the criteria in\n  plain language and say roughly who it will match; a criterion the user misread\n  means the wrong audience gets the next campaign.\n\n## The destructive one\n\n`reach_deleteAContactV1` **permanently removes a contact** from the email\nmarketing system, by UUID. Two confirmations, never batched:\n\n1. First names the contact — email address and name, resolved from\n   `reach_listContactsV1`, not the raw UUID the user pasted. State that the\n   contact and their history cannot be restored.\n2. Second in a separate turn.\n\nNever delete more than one contact per approval, and never carry an approval\nforward to another contact. If the user wants a contact to stop receiving mail,\nunsubscribing is usually what they mean — check before deleting.\n\n## Full tool list\n\nProfiles: `reach_listProfilesV1`, `reach_getProfileDomainDNSStatusV1`\n\nContacts: `reach_listContactsV1`, `reach_createANewContactV1`,\n`reach_createNewContactsV1`, `reach_deleteAContactV1`,\n`reach_listContactGroupsV1`\n\nSegments: `reach_listSegmentsV1`, `reach_createANewContactSegmentV1`,\n`reach_getSegmentDetailsV1`, `reach_listSegmentContactsV1`,\n`reach_listProfileSegmentContactsV1`\n"
}