Update to Dayalogs

{
  "description": "Create, revise, validate, preview, publish, and share Dayalogs Reports through the Dayalogs MCP. Use for reports built from an Analysis Result, charts, trends, comparisons, filters, themes, cover images, print layouts, share links, or report email delivery. Keep report authoring distinct from raw response inspection and Analysis Recipe changes.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 590
    }
  ],
  "name": "create-dayalogs-report",
  "skill_md_contents": "---\nname: create-dayalogs-report\ndescription: Create, revise, validate, preview, publish, and share Dayalogs Reports through the Dayalogs MCP. Use for reports built from an Analysis Result, charts, trends, comparisons, filters, themes, cover images, print layouts, share links, or report email delivery. Keep report authoring distinct from raw response inspection and Analysis Recipe changes.\n---\n\n# Create Dayalogs Reports\n\nBuild a Report over the selected Analysis Result, with consistent data, readable charts and deliberate delivery.\n\n## Choose the data and draft\n\n1. Check the account's capabilities and actual available tools. If Reporting tools are unavailable, explain the limitation rather than claiming that a Report was saved or published.\n2. Read `survey_authoring_help` at `reporting/workflow/help.md` and the relevant topic under `reporting/`. Use `get_report_context` for the chosen Survey or Report and `get_report_schema` for the current definition contract.\n3. Identify the intended audience, questions, population, unit and exact Analysis Result. Obtain its supported `dataset_source` from `get_analysis_project_reports`. Never guess a pin or substitute current raw Survey responses for an unavailable Result.\n4. A definition-only draft may omit its data connection. Real-data preview, charts, totals, print and publication require an admitted, applied Result. If it is missing, use the Analysis workflow first; drafting does not authorize acquisition or Apply.\n5. For an approved connection, use `connect_analysis_project_report` with the exact returned source and current Report revision when updating. Connecting a Result does not publish the Report.\n6. Draft using field identifiers and typed choices from context. Keep fixed population selection distinct from allowed viewer filters. Specify measures, denominators, missing-value handling, comparisons and periods explicitly; multiple-answer percentages may exceed 100%.\n\n## Validate and preview\n\n1. Reuse the chosen theme, branding and owned gallery images. Read `reporting/themes/help.md` for reusable theme changes. Keep each concept's color consistent across charts, legends and periods; respect the author's palette.\n2. Run `validate_report`, resolve errors, then `save_report_draft` with explicit create/update intent and the current `expected_revision_id` for updates. On conflict, reconcile deliberately; never retry by silently replacing the revision.\n3. Give the returned preview URL. Inspect web and prepared print output when browser access is available, including cover contrast, chart labels, page breaks and filters. Otherwise state clearly that visual checking remains pending.\n4. Explain the Result pin, filters, unit, unweighted bases and weighting. Keep interpretation supported by data. Generated written comments have their own availability and explicit request boundary; consult `reporting/dynamic-comments/help.md` only when needed. Audio narration is outside this workflow.\n\n## Publish and deliver only when requested\n\n- After explicit approval, `publish_report` targets the expected current revision. Publication, share-link creation and email sending are distinct steps.\n- Use the share-link tools only for the requested scope and validity. Treat link URLs as access-bearing data. Unpublishing withdraws all access without deleting draft/history; individual revocation is permanent for that link.\n- For email, first use `get_report_email_options` and `preview_report_email` for an existing published link. Show the selected sender, copy, unique eligible recipients, link scope and exact cost. Only after approval, call `send_report_email` with unchanged settings and the returned unexpired `preview_token`, `confirmed=true` and a unique `request_key` inside the `email` object. If the preview expires or changes, obtain a new approval.\n- Retry an unknown send outcome with that same key and payload. Monitor the returned batch; transport acceptance is not confirmed receipt and opens remain estimates. A shared link does not create recipient-specific filters.\n\nReturn the draft or published revision, preview or requested share URL, data provenance and actual delivery state. Do not describe an unreviewed preview, a queued email or an incomplete calculation as complete.\n"
}