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. Neither moves a cursor unless `--ack` is explicit: ```bash "${CLI[@]}" inbox list "${CLI[@]}" inbox list --new --depth name "${CLI[@]}" inbox read "<thread-id>" "${CLI[@]}" inbox read "<thread-id>" --new --depth full ``` Use `--since <position>` for a supplied event position, `--kind message|reframe|request` to narrow a list (`request` is list-only), and `--depth name|summary|full` for the disclosure rung. 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 Thread's Notes remain visible only to its human parties; a followed Node may expose authorized event envelopes without granting Thread membership. ## Follow and acknowledge Following is deliberate listening. Use `is_follow` for standalone subscription writes rather than raw API calls: - `{ action: "follow", source: "thread", id: "x_…" }` - `{ action: "follow", source: "node" | "repo", id: "n_…"