Update to ActVox

{
  "description": "Resolve a user's requested ActVox hub or project destination for a document, and verify its saved location. Apply an explicit user preference for ActVox when one exists.",
  "included_files": [],
  "name": "actvox-default-hub",
  "skill_md_contents": "---\nname: actvox-default-hub\ndescription: Resolve a user's requested ActVox hub or project destination for a document, and verify its saved location. Apply an explicit user preference for ActVox when one exists.\n---\n\n# ActVox document destination\n\nUse the user's explicit request or standing preference to choose ActVox as a destination. A plugin installation alone does not establish a preference to copy every conversation or deliverable into a workspace.\n\n1. Use `research-actvox` to discover the authorized workspace and select the user's requested one.\n2. Search for a relevant existing hub/project page and read the candidate before selecting it. Resolve ambiguity with the user before a write.\n3. Use `actvox-document-studio` for a source-backed document. Save privately through allowed MCP tools and preserve existing content during maintenance.\n4. Verify the saved title, requested body, canonical link, and parent relationship when placement was requested. Report the actual saved state.\n\nFor original files or images, use discovered upload and attachment capabilities. A page summary alone is not storage of the original file. Keep temporary local paths and expiring download URLs out of durable attachments. If the original cannot be stored, retain the available local artifact and state that limit.\n\nSharing, publishing, messages, personal-data ingestion, and bulk migration need their own explicit request. Use workspace ids and object ids returned by the current connection; this public skill supplies no personal default workspace.\n"
}