Update to Data

{
  "name": "convert-to-doc",
  "description": "Create a polished DOCX or Google Doc from an existing Data app.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 242
    }
  ],
  "skill_md_contents": "---\nname: convert-to-doc\ndescription: \"Create a polished DOCX or Google Doc from an existing Data app.\"\n---\n\n# Convert To Doc\n\nCreate a polished DOCX or Google Doc from an existing Data app.\n\n## Overall Instructions\n\n- Follow the [shared Data instructions](../../shared/shared-skill-instructions.md) throughout this workflow.\n- When converting a Data report or dashboard to a document, follow the [Data App Contract](../../shared/data-app.md) for source preservation and export.\n\n## Dependencies\n\nApply the shared [dependency resolution policy](../../shared/shared-skill-instructions.md#dependency-resolution) to the categories below.\n\n- Knowledge & Files: Source artifacts, document templates, style references, and requested cloud-document destinations.\n\n## Route\n\n- For a local app, use its `dist/index.html` and `src/data.json` directly.\n- For a published app, use its exact HTTPS `.chatgpt.site` or `.chatgpt-team.site` URL, the reviewed snapshot from `/api/snapshot`, and the saved presentation state from `/api/presentation` as the equivalent verified source. Follow [Published Site authentication](../../shared/data-app.md#published-site-authentication) before declaring a `401` blocked.\n- Preserve its visible content, charts, filters, presentation state, and reviewed source data. Do not create an intermediate report or rebuild the app.\n- Create a DOCX file with the [@documents](plugin://documents@openai-primary-runtime) plugin and match the final output format to the request.\n\n## Workflow\n\n1. **Preflight capabilities.** Confirm that the canonical Documents skill is available before conversion. For a native Google Doc, also confirm Google Drive document import or supported native image insertion. If a required capability is unavailable, explain the blocker and retain any verified local DOCX; do not claim delivery to Google Docs.\n2. **Resolve the existing app.** For a local app, verify its `dist/index.html` and use `src/data.json`. For a published app, verify the exact HTTPS `.chatgpt.site` or `.chatgpt-team.site` source URL, load the compiled app from that URL, and fetch its reviewed snapshot and saved presentation state from the source origin's `/api/snapshot` and `/api/presentation` endpoints. Reject other remote sources or a hosted source whose app, snapshot, or presentation endpoint cannot be read. Use the resolved app, presentation state, and referenced evidence to preserve visible content, charts, filters, exact claims, definitions, caveats, freshness, source labels, links, tables, and reviewed data.\n3. **Determine a starting style.** If a template or reference was not provided, ask the user what to base the document's layout and style on. If strong candidates exist in memory or user context, suggest them and include a link. If none exist, use the Documents plugin's built-in `google_docs_default` preset for a clean, neutral DOCX or Google Doc. Use another built-in preset only when the user requests a different document style.\n4. **Author with the Documents plugin.** Read and follow the canonical Documents skill. Only create a cover page, title page, or introductory page if the selected template includes one. Use native headings, paragraphs, lists, links, tables, and editable content wherever practical. If using a template, preserve its layout and formatting unless the user explicitly asks for changes. Copy template sections as needed and delete unused sections only when the document is complete. Keep raw SQL in source notes unless the user asked to see it; never use a whole-app screenshot.\n5. **Render, inspect, and repair.** Inspect every page at full size. Fix clipping, overlap, overflow, unresolved placeholders, missing chart marks, illegible text, missing table-header semantics, and missing meaningful image alt text.\n6. **Validate and deliver.** Confirm the DOCX opens cleanly and contains the required title, claims, metrics, caveats, freshness, and provenance. For Google Docs, import the verified DOCX. If import is blocked but native image insertion is supported, use the same PNGs with native document text as described in the shared workflow. Read back image counts and inspect the rendered pages before returning the link; report an import failure separately from a successful native insertion.\n\n## Chart images\n\n- Prefer the open Data app's read-only WebMCP tools for chart images: discover exact IDs with `list_data_app_cards({})`, then use `get_data_app_card_image({ cardId, scale: 3 })` or `get_data_app_card_images({ cardIds, scale: 3 })`. Read [Card images for slides and documents](../../shared/data-app.md#card-images-for-slides-and-documents) for browser discovery, PNG decoding, scope checks, and capture limits. Pass the saved PNG files to the Documents plugin; do not print base64 image bytes.\n- Follow the shared [capture priority](../../shared/data-app.md#capture-priority) and [image-preservation workflow](../../shared/data-app.md#preserve-chart-images-across-non-pdf-exports), including native Download PNG, same-card capture, and connector image insertion. Rebuild from existing reviewed data only after all three capture paths fail or are unavailable; validate the result and report the capture blockers and recreated charts only in the final response to the user. Styling, generic editable-document requirements, or import/MIME failures alone must not trigger reconstruction.\n- Card captures include rendered titles and text. Avoid duplicating those headings; keep surrounding captions, caveats, and source notes editable. Preserve the original image even when the document uses a different template.\n- Preserve aspect ratio and fit the whole image without cropping. Use the returned pixel dimensions to size placement at roughly 200 pixels per inch or better. Prefer scale 3 for card captures; if size limits require a lower scale, recheck legibility rather than enlarging a low-resolution image. Inspect every embedded chart at full size for sharp text, complete marks, accurate colors, and the intended filters and local chart selections.\n\n## Hard gates\n\n- The Documents plugin was selected and available before conversion.\n- Either the local app's verified `dist/index.html` and reviewed `src/data.json`, or the published app's verified HTTPS `.chatgpt.site` or `.chatgpt-team.site` URL with successful `/api/snapshot` and `/api/presentation` responses, was used directly as the reference for the document.\n- Every page passes full-page visual inspection and accessibility checks.\n- The document contains native structure rather than a flattened report image.\n- Charts use the app's exported PNGs or the validated last-resort capture fallback, reported only in the final response; all match its selected view, including signs and units.\n- Required claims, definitions, caveats, freshness, and provenance survive conversion.\n- The delivered destination matches the request.\n\nIf a hard gate fails, stop and report the failure.\n"
}