@yahaha-studio/kichi-forwarder 0.1.1-beta.7 → 0.1.1-beta.9
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/openclaw.plugin.json
CHANGED
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
"id": "kichi-forwarder",
|
|
3
3
|
"name": "Kichi Forwarder",
|
|
4
4
|
"description": "Native OpenClaw plugin for Kichi World with direct avatar control, status sync, timers, notes, and music tools",
|
|
5
|
-
"version": "0.1.1-beta.
|
|
5
|
+
"version": "0.1.1-beta.9",
|
|
6
6
|
"author": "OpenClaw",
|
|
7
7
|
"skills": ["./skills/kichi-forwarder"],
|
|
8
8
|
"configSchema": {
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@yahaha-studio/kichi-forwarder",
|
|
3
|
-
"version": "0.1.1-beta.
|
|
3
|
+
"version": "0.1.1-beta.9",
|
|
4
4
|
"description": "Native OpenClaw plugin for Kichi World with direct avatar control, status sync, timers, notes, and music tools",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"main": "index.ts",
|
|
@@ -8,9 +8,9 @@ metadata: {"openclaw":{"skillKey":"kichi-forwarder","homepage":"https://github.c
|
|
|
8
8
|
|
|
9
9
|
Kichi Forwarder provides websocket tools for connecting an OpenClaw agent to Kichi, directly controlling the Kichi avatar, syncing companion status, and handling Kichi notes, timers, and music workflows.
|
|
10
10
|
|
|
11
|
-
##
|
|
11
|
+
## Pre-install Remote Discovery
|
|
12
12
|
|
|
13
|
-
|
|
13
|
+
The following URLs are only used when this skill is first loaded from a remote URL before local installation. After the plugin is installed locally, these URLs are not referenced and the local files take precedence:
|
|
14
14
|
|
|
15
15
|
- `SKILL.md`: `https://yahaha-studio.github.io/kichi-forwarder/SKILL.md`
|
|
16
16
|
- `install.md`: `https://yahaha-studio.github.io/kichi-forwarder/references/install.md`
|
|
@@ -30,7 +30,7 @@ Runtime data lives under the user home directory and is isolated per OpenClaw ag
|
|
|
30
30
|
|
|
31
31
|
## Remote URL Install Entry
|
|
32
32
|
|
|
33
|
-
When this skill is loaded from:
|
|
33
|
+
When this skill is first loaded from:
|
|
34
34
|
|
|
35
35
|
- `https://yahaha-studio.github.io/kichi-forwarder/SKILL.md`
|
|
36
36
|
|
|
@@ -40,13 +40,13 @@ The install and join flow is defined only in:
|
|
|
40
40
|
|
|
41
41
|
- `https://yahaha-studio.github.io/kichi-forwarder/references/install.md`
|
|
42
42
|
|
|
43
|
-
Read
|
|
43
|
+
Read that file once to complete the initial install. After local installation, the local `install.md` is used instead.
|
|
44
44
|
|
|
45
45
|
## Install Gate
|
|
46
46
|
|
|
47
47
|
For install/onboarding/connect requests:
|
|
48
48
|
|
|
49
|
-
- Read and follow `install.md` before
|
|
49
|
+
- Read and follow `install.md` before starting the install flow.
|
|
50
50
|
- Before continuing any install/onboarding/connect flow, check whether `kichi-forwarder` is already installed. If it is installed, ensure it is on the latest published version of `@yahaha-studio/kichi-forwarder`; if not, update it to that latest version first.
|
|
51
51
|
- If plugin installation fails with `429`, treat it as a ClawHub routing failure and switch to the non-ClawHub archive install path from `install.md`/`error.md`. Do not retry the same bare package command.
|
|
52
52
|
- Before calling `kichi_connection_status` or `kichi_join`, update workspace `HEARTBEAT.md` by following `heartbeat.md`. If the update fails, warn the user that heartbeat integration will be unavailable and continue the connection flow.
|
|
@@ -21,11 +21,11 @@ For "join Kichi World" onboarding requests:
|
|
|
21
21
|
|
|
22
22
|
## Workflow Boundary
|
|
23
23
|
|
|
24
|
-
|
|
24
|
+
The plugin code itself does not write to workspace files. The onboarding instructions above direct the agent to update `HEARTBEAT.md` on behalf of the user as part of the install flow.
|
|
25
25
|
|
|
26
26
|
If user wants recurring note board checks:
|
|
27
27
|
|
|
28
|
-
1.
|
|
28
|
+
1. Update workspace `HEARTBEAT.md`.
|
|
29
29
|
2. Keep the existing OpenClaw heartbeat cadence unless the user explicitly wants a different interval.
|
|
30
30
|
3. Do not claim the plugin edited `HEARTBEAT.md` automatically.
|
|
31
31
|
|
|
@@ -53,9 +53,9 @@ openclaw plugins install ./yahaha-studio-kichi-forwarder-<version>.tgz
|
|
|
53
53
|
|
|
54
54
|
You may also use the exact absolute or relative `.tgz` path that `npm pack` produced. The local archive path bypasses the preferred ClawHub lookup.
|
|
55
55
|
|
|
56
|
-
## Remote URL Install Command Path
|
|
56
|
+
## Remote URL Install Command Path
|
|
57
57
|
|
|
58
|
-
If the user asks:
|
|
58
|
+
This section only applies when the skill is first loaded from a remote URL before local installation. If the user asks:
|
|
59
59
|
|
|
60
60
|
```text
|
|
61
61
|
Read https://yahaha-studio.github.io/kichi-forwarder/SKILL.md and connect me to Kichi World with avatarId: {avatarId} and host: {host}
|
|
@@ -65,7 +65,7 @@ Read https://yahaha-studio.github.io/kichi-forwarder/SKILL.md and connect me to
|
|
|
65
65
|
|
|
66
66
|
When the user asks with one of the commands above, execute in this fixed order:
|
|
67
67
|
|
|
68
|
-
1.
|
|
68
|
+
1. If loaded from a remote URL, read `install.md` and `heartbeat.md` from the published skill URLs first. If installed locally, use the local files.
|
|
69
69
|
2. Parse `avatarId` from user text (`AvatarId`/`avatarId`, case-insensitive).
|
|
70
70
|
3. Resolve the host and write the current agent's `state.json`.
|
|
71
71
|
4. Check whether `@yahaha-studio/kichi-forwarder` is already installed.
|
|
@@ -95,4 +95,4 @@ If any box is unchecked, the onboarding remains incomplete.
|
|
|
95
95
|
|
|
96
96
|
If the `HEARTBEAT.md` update fails, warn the user that heartbeat integration will be unavailable but do not block the connection flow.
|
|
97
97
|
|
|
98
|
-
|
|
98
|
+
The plugin code does not write to workspace files directly. The agent updates `HEARTBEAT.md` as part of this onboarding flow.
|