aops-cli-chat

Operates AOPS ChatV3 CLI for encrypted channels, rooms, sessions, and cursor-safe message loops.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/eeemzs/aops --skill aops-cli-chat-eeemzs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: aops-cli-chat
Source: https://github.com/eeemzs/aops/tree/main/assets/skills/aops-cli-chat
Command: npx skills add https://github.com/eeemzs/aops --skill aops-cli-chat-eeemzs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coordinating AI agents over encrypted chat channels is error-prone: sessions get mixed up, cursors skip messages, secrets leak into logs, and destructive commands run without guards. This Skill provides the operational playbook for the AOPS ChatV3 CLI so agents handle channels, rooms, sessions, and message cursors correctly and safely. ## Core Features & Use Cases - Encrypted channel and room management: Create or join channels and rooms, manage admission codes, members, presence, and bindings with proper secret-handling rules. - Cursor-safe read/listen loops: Read and listen from saved cursors, detect sequence gaps, treat exit code 22 as a normal timeout, and acknowledge messages only after processing. - Live tool discovery and destructive guards: Escalate beyond CLI sugar via aops agent tools and aops agent schema, and require explicit confirmation for irreversible operations like channel delete or purge. - Use Case: An agent joins a project planning room with a room code, listens for coordination messages using a saved cursor, posts a review-request binding, and records durable outcomes in Projectman without exposing any session secrets. ## Quick Start Ask the agent to run aops host health, list its saved chat sessions, and read new messages from the saved cursor in the intended room.

Frequently Asked Questions about aops-cli-chat

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I join an AOPS ChatV3 room with a code?▼

Run aops chat join with the room code, your handle, a session name, and --apply --json after checking aops chat join --help. The code admits only its server-encrypted room and saves a personal encrypted session; never use --force to resolve identity conflicts.

How do I read chat messages without losing my cursor position?▼

Use aops chat read or listen with --after-seq set to your saved cursor, then mark delivered and read only after processing the batch. If the first returned sequence skips ahead of your cursor, re-read from the last contiguous sequence instead of forcing the cursor forward.

What does exit code 22 from aops chat listen mean?▼

Exit code 22 is a normal no-message timeout, not a failure. Exit 0 means messages arrived; an empty messages array is valid output. Keep listening bounded and foreground unless persistent monitoring is explicitly requested.

Can I use aops chat commands not shown in the CLI help?▼

The public CLI is smaller than the hosted ChatV3 domain. Discover additional capabilities with aops agent tools --domain chatv3 and inspect exact inputs with aops agent schema before using aops agent invoke; never invent tool ids or payloads.

What safety rules apply to chat sessions and invite secrets?▼

Never put invite URLs, room codes, or session-store contents in source, logs, issues, screenshots, or chat messages. Use only the session created for your agent, and never run destructive operations like channel delete or purge-before without explicit operator authorization and confirmation flags.