@perkos/perkos-a2a 0.3.1 → 0.4.0
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.
- package/README.md +76 -574
- package/dist/index.d.ts +2 -2
- package/dist/index.d.ts.map +1 -1
- package/dist/index.js +71 -7
- package/dist/index.js.map +1 -1
- package/dist/server.d.ts +12 -1
- package/dist/server.d.ts.map +1 -1
- package/dist/server.js +85 -20
- package/dist/server.js.map +1 -1
- package/dist/types.d.ts +1 -0
- package/dist/types.d.ts.map +1 -1
- package/openclaw.plugin.json +17 -30
- package/package.json +7 -2
- package/skills/perkos-a2a/SKILL.md +68 -0
|
@@ -0,0 +1,68 @@
|
|
|
1
|
+
# PerkOS A2A - Agent Skill Guide
|
|
2
|
+
|
|
3
|
+
## Overview
|
|
4
|
+
|
|
5
|
+
The PerkOS A2A plugin enables communication between OpenClaw agents using Google's Agent-to-Agent (A2A) protocol. Use these tools to delegate work, discover peers, and track task progress.
|
|
6
|
+
|
|
7
|
+
## Tools
|
|
8
|
+
|
|
9
|
+
### a2a_discover
|
|
10
|
+
|
|
11
|
+
Discover all peer agents in the council. Returns each agent's online/offline status, description, and skills.
|
|
12
|
+
|
|
13
|
+
**When to use:** Before sending a task, to check which agents are available and what they can do.
|
|
14
|
+
|
|
15
|
+
**Parameters:** None
|
|
16
|
+
|
|
17
|
+
**Example:**
|
|
18
|
+
```
|
|
19
|
+
Use a2a_discover to see which agents are online.
|
|
20
|
+
```
|
|
21
|
+
|
|
22
|
+
### a2a_send_task
|
|
23
|
+
|
|
24
|
+
Send a task to a specific peer agent. The task is delivered via JSON-RPC and queued for processing.
|
|
25
|
+
|
|
26
|
+
**When to use:** When you need another agent to perform work -- research, code generation, data processing, etc.
|
|
27
|
+
|
|
28
|
+
**Parameters:**
|
|
29
|
+
- `target` (required): Name of the peer agent (must match a key in the peers config)
|
|
30
|
+
- `message` (required): The task description/instructions to send
|
|
31
|
+
|
|
32
|
+
**Example:**
|
|
33
|
+
```
|
|
34
|
+
Use a2a_send_task to ask "mimir" to "Research the latest A2A protocol specification changes"
|
|
35
|
+
```
|
|
36
|
+
|
|
37
|
+
### a2a_task_status
|
|
38
|
+
|
|
39
|
+
Check the status of a previously sent task by its ID.
|
|
40
|
+
|
|
41
|
+
**When to use:** After sending a task, to poll for completion or check progress.
|
|
42
|
+
|
|
43
|
+
**Parameters:**
|
|
44
|
+
- `target` (required): Name of the agent that received the task
|
|
45
|
+
- `taskId` (required): The task ID returned from a2a_send_task
|
|
46
|
+
|
|
47
|
+
**Task states:** submitted, working, completed, failed, canceled
|
|
48
|
+
|
|
49
|
+
## Workflows
|
|
50
|
+
|
|
51
|
+
### Delegate and check back
|
|
52
|
+
|
|
53
|
+
1. `a2a_discover` -- see who's online
|
|
54
|
+
2. `a2a_send_task` -- send the task to a capable peer
|
|
55
|
+
3. `a2a_task_status` -- check on progress (may need to poll)
|
|
56
|
+
|
|
57
|
+
### Multi-agent coordination
|
|
58
|
+
|
|
59
|
+
1. Discover available agents
|
|
60
|
+
2. Send different subtasks to different agents based on their skills
|
|
61
|
+
3. Collect results via task status checks
|
|
62
|
+
4. Combine outputs for the user
|
|
63
|
+
|
|
64
|
+
## Notes
|
|
65
|
+
|
|
66
|
+
- Tasks are asynchronous. After sending, the peer agent processes independently.
|
|
67
|
+
- If the plugin is in client-only mode, you can send tasks but peers cannot send tasks to you.
|
|
68
|
+
- Peer URLs must be configured in the plugin config before you can communicate with them.
|