Update to Accessibility Checks & Fixes

{
  "description": "Fix supported accessibility issues in an attached Word (DOCX) or PowerPoint (PPTX) file with Inkable, retrieve the completed remediation, and offer the updated file with remaining issues. Use for Word/PowerPoint accessibility fixes and their status, not PDF remediation or general document editing.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 491
    }
  ],
  "name": "fix-office-accessibility",
  "skill_md_contents": "---\nname: fix-office-accessibility\ndescription: Fix supported accessibility issues in an attached Word (DOCX) or PowerPoint (PPTX) file with Inkable, retrieve the completed remediation, and offer the updated file with remaining issues. Use for Word/PowerPoint accessibility fixes and their status, not PDF remediation or general document editing.\n---\n\n# Fix Word and PowerPoint accessibility\n\nUse the packaged `inkable-docs` MCP connection at `https://inkabledocs.com/mcp`. Fix the file only when requested; a check-only request belongs to `check-document-accessibility`.\n\n## Choose the matching tools\n\n| Original format | Start remediation              | Retrieve status and file |\n| --------------- | ------------------------------ | ------------------------ |\n| DOCX            | `remediate_docx_accessibility` | `get_docx_remediation`   |\n| PPTX            | `remediate_pptx_accessibility` | `get_pptx_remediation`   |\n\nRequire the original DOCX or PPTX attachment. If it is missing or ambiguous, ask for the file or clarification. PDF remediation is unsupported: explain that limit and offer a check instead. Do not convert a PDF or another unsupported format to bypass the limit.\n\n## Start or resume the job\n\n- Pass the original attachment in `file` using ChatGPT's `openai/fileParams` flow: `download_url` and `file_id` are required; preserve the provided filename and MIME when available. Do not fabricate attachment metadata, rebuild a file from text, or use the Claude upload-token workflow.\n- For an existing remediation, retain its `requestId` and format, and use the matching retrieval tool. Do not start duplicate work when the user asks whether a job is ready. Never send a remediation ID to `get_accessibility_check`.\n- Report queued and running states honestly. If asked to wait or retrieve until completion, poll conservatively and honor retry guidance. Stop on a terminal result or an access/rate-limit error and explain the observed state. A failed or pending job is not a completed file.\n\n## Deliver the completed file\n\n- Retrieve the completed result with the dedicated DOCX or PPTX retrieval tool. Present the returned embedded binary MCP file resource as a usable download in the matching Office format. The updated file is separate; preserve the original attachment.\n- If the client cannot materialize or download the resource, report the presentation problem instead of claiming delivery. Do not invent a link or substitute a reconstructed file. If a tool is missing, explain that the connection's tool set needs updating.\n- Report the returned before/after scores, applied fixes, remaining active/deferred checks, and warnings without claiming all issues are resolved. Label those scores as remediation results; do not claim an independent recheck unless it actually ran. Describe an email notification only as returned by the tool.\n- Explain that the output supports the user's accessibility workflow; it is not a guarantee of WCAG conformance. Keep check names/categories intact and expose neither attachment credentials nor operation capabilities in prose.\n\nAn independent post-remediation check is a separate action: run it when requested, using the actual output file and the check workflow. Do not silently add it or claim certification based on the remediation score.\n"
}