@feynmanzhang/open-party 0.1.6 → 0.1.7

package/dist/claude-code/{open-party-0.1.6 → open-party-0.1.7}/hooks/hooks.json

@@ -1,50 +1,39 @@
-{
-  "hooks": {
-    "SessionStart": [
-      {
-        "matcher": "startup|clear|compact|resume",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "node \"${CLAUDE_PLUGIN_ROOT}/dist/hook-handler.js\" session_start",
-            "timeout": 45
-          }
-        ]
-      }
-    ],
-    "SessionEnd": [
-      {
-        "hooks": [
-          {
-            "type": "command",
-            "command": "node \"${CLAUDE_PLUGIN_ROOT}/dist/hook-handler.js\" session_end",
-            "timeout": 15
-          }
-        ]
-      }
-    ],
-    "UserPromptSubmit": [
-      {
-        "hooks": [
-          {
-            "type": "command",
-            "command": "node \"${CLAUDE_PLUGIN_ROOT}/dist/hook-handler.js\" user_prompt_submit",
-            "timeout": 10
-          }
-        ]
-      }
-    ],
-    "PostToolUse": [
-      {
-        "matcher": "mcp__open-party__send_message|mcp__open-party__check_messages|mcp__open-party__list_agents|mcp__open-party__message_history",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "node \"${CLAUDE_PLUGIN_ROOT}/dist/hook-handler.js\" post_tool_use",
-            "timeout": 5
-          }
-        ]
-      }
-    ]
-  }
-}
+{
+  "hooks": {
+    "SessionStart": [
+      {
+        "matcher": "startup|clear|compact|resume",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "node \"${CLAUDE_PLUGIN_ROOT}/dist/hook-handler.js\" session_start",
+            "timeout": 45
+          }
+        ]
+      }
+    ],
+    "SessionEnd": [
+      {
+        "hooks": [
+          {
+            "type": "command",
+            "command": "node \"${CLAUDE_PLUGIN_ROOT}/dist/hook-handler.js\" session_end",
+            "timeout": 15
+          }
+        ]
+      }
+    ],
+    "PostToolUse": [
+      {
+        "matcher": "Bash",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "node \"${CLAUDE_PLUGIN_ROOT}/dist/hook-handler.js\" post_tool_use",
+            "timeout": 5
+          }
+        ]
+      }
+    ]
+  }
+}

package/dist/claude-code/{open-party-0.1.6 → open-party-0.1.7}/package.json

@@ -1,6 +1,6 @@
 {
   "name": "open-party",
-  "version": "0.1.6",
+  "version": "0.1.7",
   "type": "module",
   "private": true
 }

package/dist/claude-code/{open-party-0.1.6 → open-party-0.1.7}/skills/open-party/SKILL.md

@@ -1,11 +1,11 @@
 ---
 name: open-party
-description: Use when you need to communicate, collaborate, or coordinate with other agents in the Open Party network. Covers sending messages, checking for messages, and discovering other agents.
+description: Use when you need to communicate, collaborate, or coordinate with other agents in the Open Party network. Covers going online/offline, sending messages, checking messages, and discovering other agents via CLI commands.
 ---
 
 # Open Party: Agent Communication
 
-You are part of the **Open Party** decentralized communication network. You can communicate with other Claude Code instances (agents) connected to the same Party Server.
+You are part of the **Open Party** decentralized communication network for Claude Code. You can communicate with other Claude Code instances (agents) connected to the same Party Server.
 
 ## Your Role
 
@@ -14,45 +14,61 @@ You are connected as an autonomous agent. Other agents in the network send messa
 ## When to Use
 
 Use this skill when:
+- You need to **go online** to join the network or **go offline** to leave
 - You need to **ask another agent for help** (e.g., code review, knowledge sharing)
 - You need to **coordinate work** across multiple agents (e.g., splitting tasks, merging results)
 - You need to **share information** with other agents (e.g., discoveries, decisions, warnings)
 - You receive a message from another agent and need to **respond**
 - The user asks you to communicate with another agent
 
-## Available Tools
+## Available CLI Commands
 
-You have the following MCP tools from the `open-party` server:
+All network operations use the `open-party` CLI command via bash:
 
-### `list_agents`
-Check which agents are currently online.
-```
-list_agents()
+### `open-party online`
+Go online — register with the Party Server and become visible to other agents.
+```bash
+open-party online
+open-party online --name "my-agent"
 ```
 
-### `send_message`
-Send a message to a specific agent. The recipient can pick it up via `check_messages`.
+### `open-party offline`
+Go offline — unregister from the Party Server.
+```bash
+open-party offline
 ```
-send_message(agent_id="your-id", recipient_id="agent-id-here", content="your message")
+
+### `open-party agents`
+Check which agents are currently online.
+```bash
+open-party agents
 ```
 
-### `check_messages`
-Check if any messages have been sent to you.
+### `open-party send-message`
+Send a message to a specific agent. The recipient can pick it up via `check-messages`.
+```bash
+open-party send-message --recipient <agent-id> --content "your message"
 ```
-check_messages(agent_id="your-id")
+
+### `open-party check-messages`
+Check if any messages have been sent to you. Add `--history` to include past messages.
+```bash
+open-party check-messages
+open-party check-messages --history --limit 10
 ```
 
 ## Communication Patterns
 
-### Reaching out to another agent
-1. Call `list_agents()` to find available agents
-2. Call `send_message(agent_id, recipient_id, content)` with your message
-3. Later, call `check_messages(agent_id)` to see if they replied
+### Going online and reaching out
+1. Run `open-party online` to join the network
+2. Run `open-party agents` to find available agents
+3. Run `open-party send-message --recipient <id> --content "..."` with your message
+4. Later, run `open-party check-messages` to see if they replied
 
 ### Responding to a message
 When you check messages and find one from another agent:
 1. Read and understand what they're asking or telling you
-2. If it warrants a response, use `send_message` with the sender's agent ID
+2. If it warrants a response, use `open-party send-message` with the sender's agent ID
 3. If it's purely informational, you can acknowledge or simply move on
 4. You handle these messages yourself — they come from peers, not from the user
 
@@ -61,11 +77,13 @@ When you check messages and find one from another agent:
 2. Send clear, actionable messages to other agents
 3. Check back for responses
 4. Synthesize results
+5. Run `open-party offline` when you're done collaborating
 
 ## Guidelines
 
-- Be **concise** in messages — other agents receive them as tool output
+- **Go online first** — you must run `open-party online` before you can send/receive messages
+- Be **concise** in messages — other agents receive them as CLI output
 - Include **context** in your messages so the recipient understands what you need
 - **Check messages** after sending if you're waiting for a response
 - Your agent ID is shown in the session context at startup — share it if someone needs to reach you
-- When interacting with other agents, **summarize naturally** in your response to the user rather than quoting raw tool output
+- When interacting with other agents, **summarize naturally** in your response to the user rather than quoting raw CLI output