@xevy/skills 0.1.45 → 0.1.47
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.
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
"name": "xevy",
|
|
3
3
|
"displayName": "Xevy",
|
|
4
4
|
"description": "Native /xevy:* SDLC workflow commands driven through the Xevy MCP server. Analyze, plan, execute, fix, and move-to-qa run locally by default and accept --cloud for the server Web Agent. Merge stays local; merge-pull-request evaluates and lands the remote PR.",
|
|
5
|
-
"version": "0.1.
|
|
5
|
+
"version": "0.1.46",
|
|
6
6
|
"author": {
|
|
7
7
|
"name": "Xevy"
|
|
8
8
|
},
|
package/package.json
CHANGED
package/skills/computer/SKILL.md
CHANGED
|
@@ -15,6 +15,8 @@ Start an `agent` session with `computer_start`, associating the current project/
|
|
|
15
15
|
|
|
16
16
|
Inspect existing sessions before changing control. Human take-over advances the generation and stops agent sessions. Continue only when control is explicitly returned; refresh session metadata before further input. Send the captured generation with pause/resume/stop, including cleanup, so an old agent cannot stop a new controller. Stop only the session this run owns; stopping one agent session leaves other agents connected. For owned cleanup, call `computer_control({computerId, sessionId, generation, transition: 'stop'})` with the captured generation. On the public surface, start with `computer_start({computerId, mode: 'agent', projectId, taskId})` using relevant context; the internal server surface takes only `computerId` and inherits its task, so follow the active tool schema.
|
|
17
17
|
|
|
18
|
+
For parallel work, start a separate agent session for each agent and keep its session ID with its generation. Agents on the same Computer can share a generation; a generation alone establishes no ownership. Keep browser tabs and file-transfer IDs scoped to the creating session. Submit independent work concurrently, then poll each command ID to its terminal result. The companion bounds simultaneous execution and queues additional work. Native desktop input uses an exclusive focus lease; release it after the observed sequence so another agent can act. A busy desktop lease requires waiting or using an independent browser tab. It provides no reason to pause, stop, or take over another agent. Xevy's Computer view lists connected sessions; “Stop my session” releases only the viewer session created by that view, while “Take over agents” explicitly ends agent control.
|
|
19
|
+
|
|
18
20
|
## Browser control
|
|
19
21
|
|
|
20
22
|
For browser work, use tab-scoped browser actions when the companion advertises them. Start an agent session, then call `browser.discover` through `computer_action` and read its `computer_command` result. Select the browser and profile named by the user; otherwise use the relevant open browser/profile shown by discovery. Do not infer a profile from a window title alone.
|
|
@@ -25,7 +27,7 @@ Create a task-owned tab with `browser.newTab {url}` before parallel browser work
|
|
|
25
27
|
|
|
26
28
|
## Observe, act, verify
|
|
27
29
|
|
|
28
|
-
For shell work, queue `shell.run {executable,args?,cwd?,timeoutMs?}`. Pass an executable and an argument array; each invocation has a 30-second timeout and
|
|
30
|
+
For shell work, queue `shell.run {executable,args?,cwd?,timeoutMs?}`. Pass an executable and an argument array; each invocation has a maximum 30-second timeout and 128 KiB of output per stream. Read the terminal command result, `exitCode`, and returned stdout/stderr. A terminal command with a nonzero exit code has failed. A timeout or output-limit error leaves any preceding writes uncertain; inspect the relevant files or application before repeating the command. Use short commands that return their verification output, such as reading a test file or printing a focused test's result. Break independent checks into separate commands. The current surface supplies no long-running job handle or streamed shell session; report an unsupported long-running check as incomplete. Verify the effect of any write before repeating it. Shell commands may change many files or external records, so keep one focused invocation per operation and describe the intended effect in the operation completion. Block rules can target `shell.run`, executable names, and the working directory. A file-path rule governs structured `file.*` actions; block `shell.run` when shell access to that path must also be prevented. Command arguments and output stay out of durable audit summaries.
|
|
29
31
|
|
|
30
32
|
For file transfer, use absolute paths and chunks of at most 192 KiB. Download with `file.stat {path}` followed by `file.readChunk {path,offset,length}` until `eof`; verify each chunk's SHA-256 and the assembled file locally. Upload by calculating the full file's SHA-256, then call `file.uploadStart {path,size,sha256,replace?}`, send ordered `file.uploadChunk {transferId,offset,dataBase64}` actions, and finish with `file.uploadCommit {transferId}`. Use `file.uploadCancel` if abandoning a transfer. The companion stages at most 100 MiB across transfers and removes stale uploads after one hour. Transfer IDs belong to the creating agent session. Path block rules apply to reads and uploads, including chunk and commit steps. Treat the transferred bytes and shell output as ephemeral results; keep them out of operation summaries.
|
|
31
33
|
|
|
@@ -34,11 +36,13 @@ For file transfer, use absolute paths and chunks of at most 192 KiB. Download wi
|
|
|
34
36
|
3. Queue bounded actions with the current generation: focus, launch a supported application, click, drag, scroll, type, or press a key. Use observations to choose the next dependent action.
|
|
35
37
|
4. Read each command until a terminal result, then take a fresh screenshot and check the expected app result. For a transaction, verify its final state, such as the saved file, submitted record, or visible deletion confirmation. Native input success establishes that the action executed; business success requires observed application evidence.
|
|
36
38
|
5. A timeout or lost acknowledgement leaves the result uncertain. Inspect command status and the desktop before retrying a write. Resume from the observed state; avoid repeating a submit, payment, send, or delete whose outcome is unresolved.
|
|
37
|
-
6. After the final
|
|
39
|
+
6. After the final desktop observation, queue `desktop.release {}` when you used native desktop input and wait for its terminal result. This releases the desktop focus lease so another agent can act. Browser tabs remain independent during the lease. Then call `computer_complete_operation` using the same `operationId`, current generation, and `completed`, `submitted`, `deleted`, or `failed`. Summarize the result actually verified. Stop owned control when finished.
|
|
38
40
|
|
|
39
41
|
Use the actual tool argument names and response envelope. Queue `const {command} = await computer_action({computerId, sessionId, generation, action: 'desktop.snapshot', payload: {}, operationId, summary: 'Verify the test record'})`, then read `await computer_command({computerId, commandId: command.id})`. The action response is `{command: {...}}`; take the ID from its nested `command`, while MCP clients parse the response's JSON text content. Read each action's current payload schema before constructing inputs.
|
|
40
42
|
|
|
41
|
-
|
|
43
|
+
Screenshot command responses include an image block and JSON text with the command envelope, including its ID, session ID, generation, action, status, and result metadata. Inspect both: the image establishes the visible outcome and the envelope associates it with the command being verified. Image bytes are omitted from the JSON text. Shell and file responses remain JSON command results; decode file chunks locally and verify their checksums. A tool transport response alone proves neither a completed command nor a completed app transaction.
|
|
44
|
+
|
|
45
|
+
Only after reading terminal operation commands and the relevant final evidence, record the verified result with:
|
|
42
46
|
|
|
43
47
|
```javascript
|
|
44
48
|
computer_complete_operation({
|
|
@@ -53,6 +57,10 @@ computer_complete_operation({
|
|
|
53
57
|
|
|
54
58
|
The completion argument is `outcome`; command responses expose execution `status`.
|
|
55
59
|
|
|
60
|
+
For desktop changes, a later `desktop.snapshot` or `desktop.windows` result can establish the final state. For browser changes, use a later `browser.snapshot`, `browser.inspect`, or `browser.tabs` result. `desktop.release` and `browser.disconnect` do not invalidate that evidence. A successful `shell.run`, `file.uploadCommit`, or `file.uploadCancel` can complete a technical operation; an unfinished upload cannot. `file.stat` and `file.readChunk` can prove read-only file operations. A terminal failed or blocked command can support `failed`. Use `submitted` or `deleted` only after observing the application outcome, and verify shell or file writes separately when their effect matters.
|
|
61
|
+
|
|
62
|
+
Verify every affected target in an operation. Observe the desktop after desktop input and the same browser tab after its input. A different tab's observation or a later shell success establishes no outcome for that tab. A successful `browser.closeTab` establishes terminal cleanup for that tab. Finish or cancel every upload before completing its operation. Preserve the operation ID for retries on the same target. If target evidence expires, start a new operation and gather fresh verification; a remaining unrelated result cannot establish completion.
|
|
63
|
+
|
|
56
64
|
Keep a stable `operationId` for one outcome across clicks, waits, retries, and screenshots. Use summaries such as “Save the test customer in the CRM” or “Export the monthly worksheet.” Start a new operation for a distinct transaction. Native audit segments retain cumulative counts per segment; the logical activity groups distinct segments and a separate verified completion. Record errors and blocked outcomes honestly.
|
|
57
65
|
|
|
58
66
|
## Blocks, data, and evidence
|
|
@@ -7,7 +7,7 @@
|
|
|
7
7
|
"expected_output": "One verified save transaction with stable operation ID, final observed persisted text, completion record, and generation-fenced owned-session cleanup.",
|
|
8
8
|
"files": [],
|
|
9
9
|
"expectations": [
|
|
10
|
-
"Calls list/get and starts
|
|
10
|
+
"Calls list/get and starts an agent session with current project/task when relevant; records S and generation 7, with native input using an exclusive focus lease.",
|
|
11
11
|
"Inspects monitor/window and screenshot results before dependent input and uses physical global coordinates from the current image.",
|
|
12
12
|
"Uses one operationId for edit/save/reopen/final snapshot and reads terminal command status.",
|
|
13
13
|
"Completion reports completed only after inspecting the reopened exact text and final screenshot; native input success alone is insufficient.",
|
|
@@ -42,6 +42,33 @@
|
|
|
42
42
|
"Drive failure is reported with a retained local guide/evidence path; no viewer URL or stored-artifact success is fabricated.",
|
|
43
43
|
"Protected data stays out of logs; only selected safe guide screenshots persist, audit cap/blocks remain enforced, and owned cleanup is generation-fenced."
|
|
44
44
|
]
|
|
45
|
+
},
|
|
46
|
+
{
|
|
47
|
+
"id": 4,
|
|
48
|
+
"prompt": "This is a scripted evaluation. Computer WIN has two active agents, A and B, both at generation 12. You are B. A owns browser tab tab-A and holds the desktop lease. You need to check a test page, upload a fixture and finish while A keeps working. Describe action and cleanup calls. B receives a screenshot command result with an image block and JSON containing command.sessionId=B, generation=12, action=browser.snapshot, status=succeeded. Do not claim a live test.",
|
|
49
|
+
"expected_output": "Independent agent work with session-owned tab/transfer and generation-fenced cleanup; A remains connected.",
|
|
50
|
+
"files": [],
|
|
51
|
+
"expectations": [
|
|
52
|
+
"Uses B with generation 12 and treats the session ID as ownership; sharing a generation grants no ownership of A.",
|
|
53
|
+
"Creates a B-owned browser tab and transfer; never mutates tab-A or transfer IDs owned by A.",
|
|
54
|
+
"Uses separate command IDs to read terminal results and examines the image and command envelope together.",
|
|
55
|
+
"Waits for the busy native lease or uses browser control; never stops, pauses or takes over A to obtain the desktop.",
|
|
56
|
+
"Releases a desktop lease only if used, and stops only B with captured generation 12; preserves A.",
|
|
57
|
+
"Clearly labels the evidence as scripted and makes no claim of newly performed live testing."
|
|
58
|
+
]
|
|
59
|
+
},
|
|
60
|
+
{
|
|
61
|
+
"id": 5,
|
|
62
|
+
"prompt": "This is a scripted Computer shell/file evaluation. shell.run has a maximum 30-second timeout. A fixture creation command times out after it may have written C:\\Temp\\fixture.txt. A later file.stat succeeds and file.readChunk returns the expected content with a valid SHA-256. A separate test command returns exitCode=7 with stdout and stderr; the user also requests a 90-second test. State the verified outcomes and next actions without executing tools.",
|
|
63
|
+
"expected_output": "Evidence-based recovery of the uncertain write, failed test reporting and honest long-running limitation.",
|
|
64
|
+
"files": [],
|
|
65
|
+
"expectations": [
|
|
66
|
+
"Checks the file before retrying the timed-out write and avoids duplicating it once its exact content and checksum are observed.",
|
|
67
|
+
"Reads terminal command status and exitCode; reports the test returning 7 as failed.",
|
|
68
|
+
"Uses short commands that return verification output and keeps output/fixture content out of durable audit summaries.",
|
|
69
|
+
"Reports the 90-second test as incomplete because the current shell surface has no supported long-running job handle; invents neither a higher timeout nor completed proof.",
|
|
70
|
+
"Completes only the verified file/technical operation using relevant final evidence and keeps the failing test outcome separate."
|
|
71
|
+
]
|
|
45
72
|
}
|
|
46
73
|
]
|
|
47
74
|
}
|