Update to Dayalogs

{
  "description": "Prepare, test, launch, and monitor Dayalogs survey fieldwork through the Dayalogs MCP. Use for hosted links, LinkSets, embeds, audiences, email campaigns, continuous surveys, file mappings, canonical row batches, quotas, collection dates, delivery tests, collection progress and attributable campaign conversion. Keep preparation, activation and real sending separate.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 580
    }
  ],
  "name": "launch-dayalogs-fieldwork",
  "skill_md_contents": "---\nname: launch-dayalogs-fieldwork\ndescription: Prepare, test, launch, and monitor Dayalogs survey fieldwork through the Dayalogs MCP. Use for hosted links, LinkSets, embeds, audiences, email campaigns, continuous surveys, file mappings, canonical row batches, quotas, collection dates, delivery tests, collection progress and attributable campaign conversion. Keep preparation, activation and real sending separate.\n---\n\n# Launch Dayalogs Fieldwork\n\nMove a reviewed draft into the correct collection channel without accidental publication or sending.\n\n## Choose The Channel\n\n- Hosted link: one reusable entry point for anonymous or metadata-driven access.\n- LinkSet: a managed set of individual links, often linked to audience contacts or intended for export to another delivery channel.\n- Embed: a modal placement on an approved website origin, backed by an eligible reusable share link.\n- Email campaign: a one-off send from a static contact LinkSet, or an explicitly selected continuous campaign with its own invitation list fed by files/external events. A continuous Report does not imply a continuous campaign.\n\nExplain the choice if the user's request could reasonably use more than one channel.\n\n## Workflow\n\n1. Read the current survey and confirm it is the intended version. Preview it before any public action.\n2. Check collection dates, quota behavior, link metadata, audience rules, and survey compatibility for the chosen channel.\n3. For audiences, use repeatable imports and inspect import status. Do not treat a transport error as proof that a chunk failed; verify the persisted import state before retrying.\n4. Create or configure the channel:\n   - Use share-link and LinkSet tools for hosted access and personalized links.\n   - Use embed compatibility and embed tools for website placements. Restrict origins deliberately.\n   - Use campaign tools for email. Call `list_sender_identities` and pass the\n     selected `sender_identity` key; never invent a From address. Preview the\n     campaign and use `send_survey_campaign_test` before a real send when\n     practical. For continuous campaigns, read `survey_authoring_help` path\n     `operations/continuous-campaigns/help.md`, create a continuous draft, map the\n     current input schema, and obtain explicit approval before activation or real\n     invitation admission. Use the single trigger or `add_continuous_survey_campaign_batch`\n     with already-mapped canonical rows; browser file mapping is a separate UI path.\n5. Ask for explicit confirmation immediately before each public or outbound action: starting collection, creating a real link when guarded, sending a campaign, retrying failed recipients, or another irreversible operation.\n6. Start collection only after confirmation. Do not infer approval from the user asking for a preview, link design, or campaign draft.\n7. Monitor the resulting channel. Use campaign events and campaign state for queued, sent, delivered, delayed, bounced, complaint, and failed counts.\n\n## Delivery Rules\n\n- Permanent email delivery failures exclude contacts from Dayalogs email campaign queues, but not from LinkSets or link exports that may be delivered through SMS, messaging, or offline channels.\n- Explain excluded-recipient counts when a campaign audience is smaller than its source segment.\n- Do not expose provider names as user-facing delivery statuses.\n- Do not claim click tracking is active when `tracking_available` is false. Report click totals as unavailable, not zero.\n- One-off campaigns freeze their survey version when the first real recipients are queued. Continuous invitation attempts pin the applicable version at validated signed Start, not introduction display; importer compatibility guards can retain a previous renderable version. Tests and unsent previews are separate.\n- Continuous `idEvent` is optional and literal. An existing ID returns the original invitation without mutation/resend even with changed input; an invalid attempt consumes nothing. Null/omitted means always new. Do not automatically retry an unknown-outcome ID-less MCP/API call. Reopening/explicitly resuming the same browser import operation is a separate retry identity.\n- Continuous file imports show only a first-100-row mapping sample before full apply; distinguish it from final whole-file counts and correct/reimport only rejected rows. Pause/close stops new admission, not already queued sends or issued links.\n\n## Completion\n\nReport what was created, whether collection is active, the concrete channel, audience and exclusion totals, and current delivery state. Include identifiers useful for later monitoring, but do not expose access tokens or secrets.\n"
}