is-inboxlisted

# Direct Inbox Inbox is the person-accountable feedback loop around shared Content. A local agent may help compose and invoke it, but every read and send acts as the logged-in person. Never substitute a bare Agent credential or reproduce the flow with raw API calls. This skill invokes the CLI bundled with the plugin: ```bash CLI=(node "${CLAUDE_PLUGIN_ROOT}/cli/bundle/ideaspaces.js") ``` No separate install or native Inbox tool is required. ## Read Listing and reading are read-only and need no confirmation: ```bash "${CLI[@]}" inbox list "${CLI[@]}" inbox read "<thread-id>" ``` Use normal human output unless exact structured fields are needed; then append `--json`. Preserve the CLI's distinction between an empty Inbox and an unavailable one. A message is visible only to its two human parties. ## Choose the send coordinate A new inquiry needs: - one explicit person, as an email address or `@handle`; - one exact Content target coordinate (`n_…`) that the message is about; - a short name, dense summary, and Markdown message. For the current Space root, `"${CLI[@]}" status --json` exposes its declared root identity. A canonical `/repos/n_…` URL also carries the root coordinate. For a nested target, use an exact coordinate already supplied by the user, Map, or hosted reader; never guess one from a local path. Before sending, state the recipient, target, and message. Ask for confirmation when any were inferred or composed beyond the user's request. A request that alrea