AnyShare

View saved version →

---
name: get-started
description: Set up AnyShare and choose a first document-sharing or engagement task after installation.
---

# Get started with AnyShare

Explain that AnyShare can share an original document with a protected link, organize documents in an existing data room, or report recorded engagement. Offer those choices if the user has not already chosen a task. Continue an existing request without asking them to repeat it.

Use the host's AnyShare OAuth connection when a task needs account access. The user signs in and selects one organization and permissions in AnyShare; never request passwords, tokens or verification codes in chat. Check `get_connection` when beginning the chosen task and identify the connected organization. A dashboard organization switch does not retarget a connection.

Installation alone authorizes no upload, new share link, room placement or private engagement lookup. Once the user requests a supported task, follow `../share-documents/SKILL.md` with the actual available tools. Files must preserve their original bytes and be no larger than 5,242,880 bytes. New links require verified email and disable downloads by default.

When reporting the connection, identify the organization and explain any billing restriction using the returned `billing` details. State the known reason and relevant date, the affected actions, what remains available, and the recovery step. For an expired trial, explain that uploads, new share links and adding documents to rooms are paused while existing documents and engagement reports remain readable with the required permissions. `can_use: false` does not mean the connection failed or all AnyShare usage is unavailable. If billing details are absent, state that the reason is unavailable; do not invent a trial expiry or payment failure. Follow the access-and-errors guidance in `../share-documents/SKILL.md` for other billing states and failures.

Direct billing questions to the organization owner or https://share.anysoft.ai/support. Do not promote subscriptions or lead to checkout. Disconnecting in AnyShare Settings → AI connections stops future assistant access; existing documents and recipient links remain.

View saved version →

---
name: share-documents
description: Upload original documents to AnyShare, create protected recipient links, organize existing data rooms, or review recorded document engagement.
---

# Share documents with AnyShare

Use the connected AnyShare tools and their current schemas. Client namespaces may prefix names. Check `get_connection` for the organization and permissions; use only that organization. Resolve names with `list_documents`, `get_document`, `list_data_rooms` and `get_data_room`. Ask for a selection when multiple documents or destinations match. Use returned IDs; never silently reconnect to another organization.

## Explain access and errors

Use `billing.state`, `reason`, `message`, `trial_ends_at` and `access_until` from `get_connection` or a failed action. Explain the specific known cause, relevant date in the user's timezone, affected action, remaining capabilities, and next step. Billing dates and subscription status come from the server; never infer them from `can_use` alone.

- **Trial or paid access active:** the requested writes may proceed with the required permissions. If cancellation is scheduled or renewal is past due but access remains active, explain that access continues through `access_until`; do not call it already blocked.
- **Renewal grace:** sharing still works until `access_until`. Explain the temporary grace period without claiming a payment failed unless `subscription_status` confirms it.
- **Paused:** explain the returned reason: expired trial, canceled/paused/unpaid subscription, past-due renewal, incomplete activation, ended paid access, or unverified access. Use `trial_ends_at` for trial expiry and only returned dates for other deadlines. Uploads, new share links and adding documents to rooms are blocked. Existing document browsing and recorded engagement reports remain readable with their required scopes. Continue the user's requested read task; do not stop merely because `can_use` is false. Existing recipient-link availability is a separate matter; do not promise those links remain usable.
- **Missing billing details:** refresh `get_connection` once. If only `can_use: false` is available or the refresh fails, explain which writes are restricted and that the exact reason could not be retrieved. Ask the organization owner or AnyShare support to review it; do not guess that a trial expired, a card failed, or a subscription was canceled.

For a `402` / `billing_access_required` failure, explain its billing details and leave the write pending. Reconnecting does not resolve a billing restriction. If the returned current billing state now permits the action, refresh the connection and retry once with the original idempotency key. For `401`, explain that sign-in/reconnection is needed; for `403`, explain the missing permission. Treat validation errors, rate limits, processing failures and service errors according to their actual returned details, without blaming billing. Do not repeatedly retry blocked writes, bypass access controls or change billing state. Direct billing questions to the organization owner or the returned support URL; never promote a plan, upgrade, subscription or checkout.

## Upload original bytes

The limit is 5,242,880 bytes. Supported formats are PDF, DOC/DOCX, PPT/PPTX, XLS/XLSX, CSV, ODT/ODP/ODS. Use only the original file selected or authorized for this task. Never replace it with extracted text, screenshots, a summary, a reconstruction, a truncated file or another format.

Choose exactly one upload path:

- **Host file reference available:** call `upload_document` directly with the actual `download_url` and stable `file_id`, plus `file_name`/`mime_type` when supplied. Supply the original filename if absent. Do not reserve a separate upload first. A local path or invented URL is not a host file reference.
- **Exact-byte transfer or browser handoff:** call `request_document_upload` with the original filename and byte size. Transfer only with a capability already author

Preview of the first 4,000 characters. Read full instructions →