{"id":12401,"plugin_id":"plugin_asdk_app_6a32e6bb349c8191858ce2ca77104214","kind":"skill","collection_source":null,"comparison_source":null,"observed_at":"2026-09-30T23:01:26.893Z","digest":"d048a4bc809827ae29a0e55c46db47b3f225e6e0533e5017a8abf5f8571f9f64","against":null,"payload":{"name":"launch-dayalogs-fieldwork","description":"Prepare, test, launch, and monitor Dayalogs survey fieldwork through the Dayalogs MCP. Use when a user wants to publish a survey, create hosted links or LinkSets, configure an embed, import an audience, send a campaign, test delivery, apply quotas or dates, or monitor collection and campaign delivery.","included_files":[{"relative_path":"agents/openai.yaml","size_in_bytes":547}],"skill_md_contents":"---\nname: launch-dayalogs-fieldwork\ndescription: Prepare, test, launch, and monitor Dayalogs survey fieldwork through the Dayalogs MCP. Use when a user wants to publish a survey, create hosted links or LinkSets, configure an embed, import an audience, send a campaign, test delivery, apply quotas or dates, or monitor collection and campaign delivery.\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 Dayalogs-managed send to eligible audience contacts.\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. Preview the campaign and use `send_survey_campaign_test` before a real send when practical.\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- Campaigns freeze their survey version when the first real recipients are queued. Tests and unsent previews use the current version.\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"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}