@mkterswingman/5mghost-wonder 0.0.4 → 0.0.6

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/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@mkterswingman/5mghost-wonder",
3
- "version": "0.0.4",
3
+ "version": "0.0.6",
4
4
  "description": "企微文档读取 CLI — WeCom document reader",
5
5
  "type": "module",
6
6
  "engines": {
@@ -33,6 +33,8 @@ wonder --version
33
33
 
34
34
  ## Step 2 — mkterswingman Auth Login
35
35
 
36
+ **Only use the CLI to check login state. Do not read `~/.mkterswingman/auth.json` directly** — that file is the auth SDK's internal storage (format may change, and OAuth completion → disk flush has a brief window where naive reads misjudge expiry). `wonder auth status` handles this correctly. The same rule applies to `~/.mkterswingman/5mghost-wonder/cookies.json` and the local telemetry SQLite file: always go through the corresponding `wonder` CLI command.
37
+
36
38
  Check current status:
37
39
 
38
40
  ```bash
@@ -0,0 +1,26 @@
1
+ ---
2
+ name: update-5mghost-wonder
3
+ description: Use this skill when the user wants to update or upgrade wonder, says "update wonder", "upgrade wonder", "更新 wonder", "升级 wonder", or invokes `/update-5mghost-wonder`. Also use when the user asks to check for a newer version of the WeCom document CLI.
4
+ ---
5
+
6
+ # Update wonder — 升级 5mghost-wonder CLI
7
+
8
+ Run the CLI's built-in updater. It reinstalls the latest published version globally via npm.
9
+
10
+ ```bash
11
+ wonder update
12
+ ```
13
+
14
+ When the command completes, verify the new version is in place:
15
+
16
+ ```bash
17
+ wonder --version
18
+ ```
19
+
20
+ After updating, **the bundled skills (`setup-5mghost-wonder`, `use-5mghost-wonder`, `update-5mghost-wonder`) on disk are refreshed by the package's `postinstall`**, but the AI session's already-loaded skill text is the old version. Tell the user to start a new session if they need the latest skill text — open a fresh chat / restart the CLI / `/exit` and re-enter.
21
+
22
+ If `wonder update` exits non-zero, the most common cause is npm permission or registry issues. Re-run with the user's terminal so they can see the npm error directly:
23
+
24
+ ```bash
25
+ npm install -g @mkterswingman/5mghost-wonder@latest
26
+ ```
@@ -96,6 +96,18 @@ Output is a structured JSON:
96
96
 
97
97
  Consume this JSON directly to answer the user's question.
98
98
 
99
+ ### ⚠️ Row/column indexing — JSON is 0-based, Excel is 1-based
100
+
101
+ In wonder's JSON output, `row` and `col` (and `startRow`/`endRow`/`startCol`/`endCol` in `merges`) are **0-based**. Excel addresses the user sees in the WeCom UI are **1-based**.
102
+
103
+ | JSON value | Excel address |
104
+ |---|---|
105
+ | `row: 0, col: 0` | A1 |
106
+ | `row: 9, col: 2` | C10 |
107
+ | `startRow: 1, startCol: 2, endRow: 9, endCol: 2` | C2:C10 (merged cell) |
108
+
109
+ **When talking to the user, always convert to 1-based Excel addresses.** The user thinks in Excel rows ("第 10 行"), not JSON indices. Internal calculations can stay 0-based; only what the user reads needs translation. Do not say "行 9" when you mean Excel row 10.
110
+
99
111
  ### Viewing embedded images
100
112
 
101
113
  Image cells have a `path` field pointing to the local extracted file. Use the Read tool to view:
@@ -31,6 +31,21 @@
31
31
  "workbuddy",
32
32
  "codebuddy"
33
33
  ]
34
+ },
35
+ {
36
+ "name": "update-5mghost-wonder",
37
+ "source": { "type": "local", "path": "./skills/update-5mghost-wonder" },
38
+ "targets": [
39
+ "claude",
40
+ "claude-internal",
41
+ "codex",
42
+ "codex-internal",
43
+ "gemini",
44
+ "gemini-internal",
45
+ "openclaw",
46
+ "workbuddy",
47
+ "codebuddy"
48
+ ]
34
49
  }
35
50
  ]
36
51
  }