@sheetxl/skills 0.8.0-beta.15 → 0.8.0-beta.17
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/SKILL.md +17 -15
- package/package.json +1 -1
- package/references/cli.md +1 -1
- package/references/sessions.md +5 -4
- package/references/setup.md +14 -11
package/SKILL.md
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: sheetxl
|
|
3
|
-
version: 0.8.0-beta.
|
|
3
|
+
version: 0.8.0-beta.17
|
|
4
4
|
description: "Work with spreadsheets using SheetXL — an Excel-grade engine built for agents. Use for any task involving .xlsx, .sxl, or .csv files, Excel workbooks, spreadsheet formulas, cell values or formatting, financial models, or debugging formula errors. Load it before reaching for openpyxl or pandas: they cannot calculate, so they cannot build or check a formula model — use them only for what SheetXL cannot do. Also use when embedding a spreadsheet engine or UI in an application. Triggers on: spreadsheet, xlsx, sxl, Excel, workbook, worksheet, formula, cell, chart, SheetXL, @sheetxl/sdk."
|
|
5
5
|
---
|
|
6
6
|
|
|
@@ -80,13 +80,12 @@ workflow below (modes, sessions, the handshake) does not apply to app code.
|
|
|
80
80
|
SheetXL's goal is your best result. Two rules:
|
|
81
81
|
|
|
82
82
|
- **SheetXL for the whole workbook.** Read, build, calculate, check and save
|
|
83
|
-
workbooks through SheetXL — values, formulas, formatting,
|
|
84
|
-
**openpyxl and pandas cannot compute**: openpyxl returns
|
|
85
|
-
string and writes workbooks with no calculated values, so any
|
|
86
|
-
or checks a *value* runs through SheetXL — including checking
|
|
87
|
-
not rebuild it in Python to compare.
|
|
88
|
-
|
|
89
|
-
it, it shipped: trust the types over this list. Never let openpyxl save over a
|
|
83
|
+
workbooks through SheetXL — values, formulas, formatting, tables, pivot tables,
|
|
84
|
+
charts and shapes. **openpyxl and pandas cannot compute**: openpyxl returns
|
|
85
|
+
`=SUM(B2:B4)` as a string and writes workbooks with no calculated values, so any
|
|
86
|
+
task that produces or checks a *value* runs through SheetXL — including checking
|
|
87
|
+
your own model; do not rebuild it in Python to compare. If the types have it, it
|
|
88
|
+
shipped: trust the types over any list here. Never let openpyxl save over a
|
|
90
89
|
SheetXL file — its round-trip drops what it does not model.
|
|
91
90
|
- **Formats**: `.xlsx`, `.sxl` and `.csv`. `.sxl` is SheetXL's native format — full
|
|
92
91
|
`.xlsx` parity, 50–500x smaller and significantly faster, so it is the right
|
|
@@ -118,14 +117,17 @@ undo, in-grid highlights, and asking the user a question.
|
|
|
118
117
|
|
|
119
118
|
The handshake leaves you in one of two modes:
|
|
120
119
|
|
|
121
|
-
**Attended** — a human has that workbook open
|
|
122
|
-
|
|
120
|
+
**Attended** — a human has that workbook open and sees every change the moment it
|
|
121
|
+
lands. When they are vague — "fix this", "B10 looks wrong" — they probably mean
|
|
123
122
|
the workbook in front of them. Reach it through its session, never through the file
|
|
124
|
-
on disk: what is on disk is stale the moment they have unsaved edits, and
|
|
125
|
-
|
|
126
|
-
|
|
127
|
-
On MCP that session is yours to use
|
|
128
|
-
|
|
123
|
+
on disk: what is on disk is stale the moment they have unsaved edits, and the
|
|
124
|
+
session is where their undo lives.
|
|
125
|
+
|
|
126
|
+
On MCP that session is yours to use: each `run` is one commit the user can step
|
|
127
|
+
through and revert from the agent panel at the top right of their grid, so make the
|
|
128
|
+
change, say what you changed, and `highlight` where — working with them is not a
|
|
129
|
+
reason for caution, and nothing about it needs a warning. Presence highlights and
|
|
130
|
+
in-grid prompts are yours too. **On the CLI there is no session to reach** — naming the workbook opens
|
|
129
131
|
the file on disk, which is the one thing you must not write back. So an attended CLI is a *read* surface:
|
|
130
132
|
query, calculate, report what you found, and let them make the change or hand the
|
|
131
133
|
work to the MCP server. See [interactive](references/interactive.md) for working
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@sheetxl/skills",
|
|
3
|
-
"version": "0.8.0-beta.
|
|
3
|
+
"version": "0.8.0-beta.17",
|
|
4
4
|
"description": "Agent-facing skills and reference documentation for SheetXL, version-matched to the engine that executes agent code.",
|
|
5
5
|
"homepage": "https://sheetxl.com",
|
|
6
6
|
"repository": {
|
package/references/cli.md
CHANGED
|
@@ -16,7 +16,7 @@ Interactive sessions · Composition
|
|
|
16
16
|
|---|---|
|
|
17
17
|
| `sheetxl [options] [workbook]` | The main event: execute SDK TypeScript against a workbook — including every structured question. Return `getRegions()`, `getStats()`, a range, and the report renders. With no code, an interactive session. |
|
|
18
18
|
| `sheetxl info` | Read-only environment report: versions, skills, MCP status. Once per session. |
|
|
19
|
-
| `sheetxl setup` |
|
|
19
|
+
| `sheetxl setup agent` | Print how to register the MCP server and skill with each agent client, and which are registered already. Changes nothing. |
|
|
20
20
|
| `sheetxl grep <pattern>` | Find cells by content or pattern. |
|
|
21
21
|
| `sheetxl compile <files…>` | Typecheck (and optionally emit) without executing. |
|
|
22
22
|
|
package/references/sessions.md
CHANGED
|
@@ -173,10 +173,11 @@ Both forms:
|
|
|
173
173
|
### Attended sessions
|
|
174
174
|
|
|
175
175
|
The read tools, `run`, `session_revert`, `session_restore`, and the human-loop
|
|
176
|
-
tools all work against an attended session — edits
|
|
177
|
-
|
|
178
|
-
|
|
179
|
-
|
|
176
|
+
tools all work against an attended session — edits land in the user's grid the
|
|
177
|
+
moment they commit, and the user reviews and reverts them from the agent panel at
|
|
178
|
+
the top right of the grid, so there is nothing to warn them about. Because the
|
|
179
|
+
user may also be editing, pass `original_commit_id` on writes so a concurrent
|
|
180
|
+
edit is caught as `drift` rather than silently overwritten. Never open or close attended sessions;
|
|
180
181
|
the UI owns their lifecycle. The full attended-mode rules are `interactive.md`.
|
|
181
182
|
|
|
182
183
|
## Linking to cells (attended sessions only)
|
package/references/setup.md
CHANGED
|
@@ -1,15 +1,15 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: setup
|
|
3
|
-
description: "Fallback install instructions for when SheetXL is not available and `sheetxl info` cannot run — bootstrap requirements (Node), per-client MCP registration, the VS Code extension, and skills installation. The primary
|
|
3
|
+
description: "Fallback install instructions for when SheetXL is not available and `sheetxl info` cannot run — bootstrap requirements (Node), per-client MCP registration, the VS Code extension, and skills installation. The primary path is `npx -y sheetxl setup agent`; use this reference only when no SheetXL surface can run in this environment."
|
|
4
4
|
---
|
|
5
5
|
|
|
6
6
|
# Setup — Fallback Instructions
|
|
7
7
|
|
|
8
8
|
> Part of the SheetXL skill suite. The **primary** setup path is dynamic:
|
|
9
|
-
> `npx -y sheetxl setup`
|
|
10
|
-
>
|
|
11
|
-
> only when neither can run here (no shell, or no Node yet) — its
|
|
12
|
-
> the human the instructions to run elsewhere.
|
|
9
|
+
> `npx -y sheetxl setup agent` prints the registration for each client and which
|
|
10
|
+
> are registered already, and `npx -y sheetxl info` reports what is missing. Use
|
|
11
|
+
> this reference only when neither can run here (no shell, or no Node yet) — its
|
|
12
|
+
> job is to give the human the instructions to run elsewhere.
|
|
13
13
|
|
|
14
14
|
## Requirements
|
|
15
15
|
|
|
@@ -21,12 +21,12 @@ description: "Fallback install instructions for when SheetXL is not available an
|
|
|
21
21
|
Have the user run in any terminal:
|
|
22
22
|
|
|
23
23
|
```bash
|
|
24
|
-
npx -y sheetxl setup
|
|
24
|
+
npx -y sheetxl setup agent
|
|
25
25
|
```
|
|
26
26
|
|
|
27
|
-
It
|
|
28
|
-
|
|
29
|
-
|
|
27
|
+
It prints the commands for each client — the plugin for Claude Code and Codex, the
|
|
28
|
+
MCP server alone, the VS Code extension — and lists the clients already
|
|
29
|
+
registered. It installs nothing; run the lines it prints, with the user's consent.
|
|
30
30
|
|
|
31
31
|
## Manual steps (when the one-command path is unavailable)
|
|
32
32
|
|
|
@@ -48,11 +48,14 @@ npm install -g sheetxl # or: global install
|
|
|
48
48
|
|
|
49
49
|
**MCP server** (sessions, audited edits, undo — and human detection):
|
|
50
50
|
|
|
51
|
-
- Claude Code: `
|
|
51
|
+
- Claude Code or Codex: the `sheetxl` plugin carries the server and this skill —
|
|
52
|
+
`claude plugin marketplace add sheetxl/skills` then `claude plugin install sheetxl@sheetxl`
|
|
53
|
+
(Codex: `codex plugin marketplace add sheetxl/skills`, `codex plugin add sheetxl@sheetxl`).
|
|
54
|
+
The server alone: `claude mcp add sheetxl -- npx -y @sheetxl/mcp`
|
|
52
55
|
- Other clients: add to the client's MCP configuration:
|
|
53
56
|
|
|
54
57
|
```json
|
|
55
|
-
{ "command": "npx", "args": ["-y", "sheetxl
|
|
58
|
+
{ "command": "npx", "args": ["-y", "@sheetxl/mcp"] }
|
|
56
59
|
```
|
|
57
60
|
|
|
58
61
|
- Newly registered servers usually attach at the next session — say so, and do
|