Update to Apsis Vega

{
  "description": "Agree, count, save or change an audience of contacts with Apsis Vega. Use when the user wants to find, target or count a group of contacts by their properties, events or subscriptions, save one as a segment, or change an existing segment.",
  "included_files": [],
  "name": "audience-building",
  "skill_md_contents": "---\nname: audience-building\ndescription: Agree, count, save or change an audience of contacts with Apsis Vega. Use when the user wants to find, target or count a group of contacts by their properties, events or subscriptions, save one as a segment, or change an existing segment.\n---\n\nApsis Vega works on the user's Apsis account. The company is Apsis, with a capital A and the rest in lower case, never in all capitals, and the product is Apsis Vega. Once the user has picked an account and a section, pass the same `account` and `section` to every later call. When a tool result asks for the user's go-ahead, say what the next call would do and wait for their answer in a new message. The user's explicit instructions take priority over this skill, and a tool's own refusals and notes always apply.\n\n## Start from what exists\n\n- A subscription, or a segment the account already has (`list_segments`), needs no interview. Reuse it.\n- For an audience built from conditions, call `describe_segment_target` first. It returns the section's attributes and events, each with its `name`, its type and the operators it allows. Match the marketer's words against those names.\n\n## Agree the audience before building it\n\n- Ask one question at a time, in plain, non-technical language, and wait for each answer.\n- Keep it proportional: an audience with one condition needs one confirming question.\n- Point out, as a choice the marketer can check, anything that quietly changes who is included:\n  - \"is not X\" on a field that can be empty also includes people with no value at all;\n  - \"contains\" or \"starts with\" catches more than the literal word;\n  - an open-ended or overlapping time window widens the group.\n\n## Describe it in plain words\n\n- No operators, parentheses, comparison symbols, \"&\" or \"+\", in replies, option labels and headings alike. Write \"and\" and \"or\" as words.\n- Phrase each condition in words: \"is\", \"contains\", \"more than\". Write a true or false field as a trait: \"marked as VIP\".\n- Only mixed or nested and/or logic gets an outline, indented under \"Match ALL of:\", \"Match at least ONE of:\" or \"Match NONE of:\".\n- Where a result carries `audienceDescription` or `audience_description`, relay it as written. It is rendered from the query itself, so it describes what was actually counted.\n\n## Count freely\n\n`count_profiles` saves nothing. Use it as often as refining needs, with `aql` for the conditions agreed so far or `segmentId` for an existing segment. Give the marketer the count with the plain-language description beside it. For how many people are subscribed to one subscription, `count_subscribed` is the count.\n\n## Saving is a separate decision\n\n- Most requests are answered by a count, or by sending to a subscription narrowed by a segment that already exists.\n- If the marketer may want the same group again, ask whether to keep it as a reusable segment or whether seeing who matches was enough. A saved segment can't be deleted, only hidden. Call `create_segment` only on a clear yes. A marketer who asked for a reusable segment has already answered.\n- `set_segment_visibility` hides or unhides a segment. Hiding is reversible and never changes who it targets.\n\n## Changing a segment\n\nBefore an `edit_segment` that changes conditions, restate the new audience in plain words and get a light confirm. A segment is re-evaluated each time it is used, so the edit also changes who any unsent or scheduled email using it will reach. Say so when such an email exists; it is allowed, not a reason to refuse. A rename alone changes nobody's membership.\n"
}