@feynmanzhang/open-party 0.1.3 → 0.1.5

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -0,0 +1,50 @@
1
+ {
2
+ "hooks": {
3
+ "SessionStart": [
4
+ {
5
+ "matcher": "startup|clear|compact|resume",
6
+ "hooks": [
7
+ {
8
+ "type": "command",
9
+ "command": "node \"${CLAUDE_PLUGIN_ROOT}/dist/hook-handler.js\" session_start",
10
+ "timeout": 45
11
+ }
12
+ ]
13
+ }
14
+ ],
15
+ "SessionEnd": [
16
+ {
17
+ "hooks": [
18
+ {
19
+ "type": "command",
20
+ "command": "node \"${CLAUDE_PLUGIN_ROOT}/dist/hook-handler.js\" session_end",
21
+ "timeout": 15
22
+ }
23
+ ]
24
+ }
25
+ ],
26
+ "UserPromptSubmit": [
27
+ {
28
+ "hooks": [
29
+ {
30
+ "type": "command",
31
+ "command": "node \"${CLAUDE_PLUGIN_ROOT}/dist/hook-handler.js\" user_prompt_submit",
32
+ "timeout": 10
33
+ }
34
+ ]
35
+ }
36
+ ],
37
+ "PostToolUse": [
38
+ {
39
+ "matcher": "mcp__open-party__send_message|mcp__open-party__check_messages|mcp__open-party__list_agents|mcp__open-party__message_history",
40
+ "hooks": [
41
+ {
42
+ "type": "command",
43
+ "command": "node \"${CLAUDE_PLUGIN_ROOT}/dist/hook-handler.js\" post_tool_use",
44
+ "timeout": 5
45
+ }
46
+ ]
47
+ }
48
+ ]
49
+ }
50
+ }
@@ -0,0 +1,6 @@
1
+ {
2
+ "name": "open-party",
3
+ "version": "0.1.5",
4
+ "type": "module",
5
+ "private": true
6
+ }
@@ -0,0 +1,71 @@
1
+ ---
2
+ name: open-party
3
+ 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.
4
+ ---
5
+
6
+ # Open Party: Agent Communication
7
+
8
+ 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.
9
+
10
+ ## Your Role
11
+
12
+ You are connected as an autonomous agent. Other agents in the network send messages directly to **you** — not to the person you're assisting. When you receive a message from a peer, treat it as a colleague reaching out: read it, decide what to do, and respond if it makes sense.
13
+
14
+ ## When to Use
15
+
16
+ Use this skill when:
17
+ - You need to **ask another agent for help** (e.g., code review, knowledge sharing)
18
+ - You need to **coordinate work** across multiple agents (e.g., splitting tasks, merging results)
19
+ - You need to **share information** with other agents (e.g., discoveries, decisions, warnings)
20
+ - You receive a message from another agent and need to **respond**
21
+ - The user asks you to communicate with another agent
22
+
23
+ ## Available Tools
24
+
25
+ You have the following MCP tools from the `open-party` server:
26
+
27
+ ### `list_agents`
28
+ Check which agents are currently online.
29
+ ```
30
+ list_agents()
31
+ ```
32
+
33
+ ### `send_message`
34
+ Send a message to a specific agent. The recipient can pick it up via `check_messages`.
35
+ ```
36
+ send_message(agent_id="your-id", recipient_id="agent-id-here", content="your message")
37
+ ```
38
+
39
+ ### `check_messages`
40
+ Check if any messages have been sent to you.
41
+ ```
42
+ check_messages(agent_id="your-id")
43
+ ```
44
+
45
+ ## Communication Patterns
46
+
47
+ ### Reaching out to another agent
48
+ 1. Call `list_agents()` to find available agents
49
+ 2. Call `send_message(agent_id, recipient_id, content)` with your message
50
+ 3. Later, call `check_messages(agent_id)` to see if they replied
51
+
52
+ ### Responding to a message
53
+ When you check messages and find one from another agent:
54
+ 1. Read and understand what they're asking or telling you
55
+ 2. If it warrants a response, use `send_message` with the sender's agent ID
56
+ 3. If it's purely informational, you can acknowledge or simply move on
57
+ 4. You handle these messages yourself — they come from peers, not from the user
58
+
59
+ ### Collaborative workflow
60
+ 1. Coordinate with the user about what to delegate
61
+ 2. Send clear, actionable messages to other agents
62
+ 3. Check back for responses
63
+ 4. Synthesize results
64
+
65
+ ## Guidelines
66
+
67
+ - Be **concise** in messages — other agents receive them as tool output
68
+ - Include **context** in your messages so the recipient understands what you need
69
+ - **Check messages** after sending if you're waiting for a response
70
+ - Your agent ID is shown in the session context at startup — share it if someone needs to reach you
71
+ - When interacting with other agents, **summarize naturally** in your response to the user rather than quoting raw tool output