Update to OrbitPage

{
  "name": "orbitpage-manage-page",
  "description": "Review, preview, edit, publish, and restore the OAuth-connected OrbitPage page. Use when a user asks to inspect their workspace or page, check publication status or plan capabilities, propose page changes, apply an approved preview, publish an exact revision, or restore a retained version.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 444
    }
  ],
  "skill_md_contents": "---\nname: orbitpage-manage-page\ndescription: \"Review, preview, edit, publish, and restore the OAuth-connected OrbitPage page. Use when a user asks to inspect their workspace or page, check publication status or plan capabilities, propose page changes, apply an approved preview, publish an exact revision, or restore a retained version.\"\n---\n\n# Manage an OrbitPage page\n\nOperate only on the workspace connected through OrbitPage OAuth. Use the MCP tools for live state and controlled changes; never infer page contents, permissions, revisions, or publication state.\n\n## Choose the workflow\n\n- For workspace identity or publication questions, call `get_workspace` and `get_publication_status`.\n- For page-content questions, call `get_page`. Call `get_page_capabilities` before recommending edits whose availability may depend on role or plan.\n- For requested edits, follow the preview, approval, apply, and optional publish sequence below.\n- For rollback requests, follow the version-restore sequence below.\n- Do not activate for unrelated calendar, messaging, image-generation, domain-purchase, DNS, billing, or general web-development requests.\n\n## Read current state\n\n1. Call only the minimum read tools needed.\n2. Treat returned public URLs, revision numbers, permissions, limits, and content as authoritative.\n3. Report whether the draft is published, has unpublished changes, or is still awaiting publication.\n4. Do not expose OAuth tokens, credentials, internal identifiers, or debug payloads.\n\n## Preview and apply changes\n\n1. Call `get_page` for every section the request may affect.\n2. Call `get_page_capabilities` when the requested fields, block types, or limits may depend on the connected plan or role.\n3. Preserve all unspecified content. Do not silently rewrite links, theme, menu, subpages, consent settings, or text files.\n4. Call `preview_page_changes` and retain its preview token, expected draft revision, and expiry exactly as returned.\n5. Show a concise proposal with the affected fields and make clear that neither the draft nor the public page has changed.\n6. Stop for explicit approval. Do not interpret silence, a topic change, or an earlier general request as approval of the displayed proposal.\n7. After approval, call `apply_page_changes` with the exact preview token and expected revision. Set `publish=false` so the approved result is saved as a private draft.\n8. Report the saved draft revision and whether it differs from the published revision.\n9. If the preview expired or the revision changed, read the current page again and create a new preview. Never force or reconstruct a stale mutation.\n\n## Publish safely\n\n1. Publish only after the user explicitly confirms that the saved revision should become public.\n2. Call `publish_page` with the exact saved revision as the expected revision.\n3. Call `get_publication_status` after publishing.\n4. Confirm the public URL, draft revision, published revision, and whether unpublished changes remain.\n5. If publication is pending, say so without claiming the public page is already current.\n\n## Restore a retained version\n\n1. Call `list_page_versions` and summarize the available retained versions without choosing one for the user.\n2. Ask the user to select a specific version and explicitly confirm restoration.\n3. Call `restore_page_version` only for the selected version and use the current expected draft revision when available.\n4. Keep the restored result private. Never publish a restored version automatically.\n5. Report the new draft revision and make clear that the public page remains unchanged until separately confirmed and published.\n\n## Response requirements\n\n- Distinguish clearly between a proposal, a saved private draft, a pending publication, and a completed publication.\n- State the affected sections and preserve information the tools did not return.\n- Use the connected workspace only; do not ask the user for tenant IDs, page IDs, OAuth tokens, or passwords.\n- Ask a focused clarification when the target content or requested outcome is ambiguous.\n- Decline unsupported actions and explain the nearest supported OrbitPage workflow without invoking unrelated tools.\n"
}