@xevy/skills 0.1.28 → 0.1.30

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. Work runs locally by default; pass --cloud to use the server Web Agent. The coding agent reviews and corrects the result after every action.",
5
- "version": "0.1.28",
5
+ "version": "0.1.30",
6
6
  "author": {
7
7
  "name": "Xevy"
8
8
  },
package/README.md CHANGED
@@ -104,7 +104,11 @@ with `codex mcp add`.
104
104
 
105
105
  | Skill | Purpose |
106
106
  |-------|---------|
107
- | `setup` | Link repo, `.xevy/project.json`, deploy defaults, env sync |
107
+ | `create-artifact` | Build a self-contained interactive HTML artifact and save it in Drive |
108
+ | `create-document` | Create a project document with private/shared/public visibility |
109
+ | `create-note` | Create a private personal note, optionally published on request |
110
+ | `generate-image` | Generate an image and save it in the project Gallery |
111
+ | `xevy-setup` | Link repo, `.xevy/project.json`, deploy defaults, env sync |
108
112
  | `analyze [task] [--cloud]` | Task analysis (local by default) |
109
113
  | `plan [task] [--cloud]` | Planning + review (local by default) |
110
114
  | `execute [task] [--cloud]` | Build, verify, and open a PR (local by default) |
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@xevy/skills",
3
- "version": "0.1.28",
3
+ "version": "0.1.30",
4
4
  "description": "Install Xevy agent skills and secure per-agent MCP transports for Cursor, Claude Code, Codex, and other coding agents.",
5
5
  "type": "module",
6
6
  "keywords": [
@@ -12,9 +12,11 @@ Local analysis is the default. Pass the exact standalone `--cloud` flag to deleg
12
12
 
13
13
  ## 0. Choose the engine
14
14
 
15
- - Parse `$ARGUMENTS` for the exact standalone `--cloud` token and remove that token before resolving the task. Do not treat similar text such as `--cloudy` as the flag.
16
- - Without `--cloud`, follow the **Local workflow** and do not call `start_ai_action`.
17
- - With `--cloud`, follow the **Cloud workflow**.
15
+ - Parse `$ARGUMENTS` for the exact standalone `--cloud` token and remove that token before resolving the task. Do not treat similar text such as `--cloudy`, `cloud`, or `--cloud=true` as the flag.
16
+ - Without `--cloud`, follow the **Local workflow** and do not call `start_ai_action`. The missing flag is an explicit instruction to stay local: for the whole run, `mcp__xevy__start_ai_action`, `mcp__xevy__get_ai_execution`, and `mcp__xevy__list_ai_executions` are forbidden, and so is any other way of handing the work to the Xevy server agent.
17
+ - Never infer the cloud engine from context. Task status, an earlier cloud run, an open pull request, an existing execution record, an idle local worktree, urgency, or a local step that turns out to be slow or hard are **not** consent. Only the literal flag selects the Cloud workflow.
18
+ - If the Local workflow cannot be completed, stop and report exactly what is blocking it, then let the user decide whether to rerun with `--cloud`. Never switch engines mid-run and never run both.
19
+ - With `--cloud`, follow the **Cloud workflow** and do not duplicate the work locally beyond the review-and-correct step it defines.
18
20
 
19
21
  ## 1. Resolve the task
20
22
 
@@ -0,0 +1,61 @@
1
+ ---
2
+ name: create-artifact
3
+ description: Create a self-contained interactive HTML artifact and save it in Xevy Drive. Use for interactive prototypes, dashboards, calculators, diagrams, visual explainers, mini tools, and polished HTML presentations. Artifacts are private by default and open in Xevy's sandboxed /file/ viewer. This initial version supports HTML only; use generate-image for static images and create-document for prose-first project documents.
4
+ argument-hint: "[what to build] [--note <note-id>] [--public]"
5
+ ---
6
+
7
+ # Create an HTML artifact
8
+
9
+ Turn the user's request into one polished, self-contained HTML file and save it as an **Artifact** in Xevy Drive. HTML is the only artifact format supported by this skill for now.
10
+
11
+ ## 1. Resolve where it belongs
12
+
13
+ - Read `.xevy/project.json` when available and use its `workspaceIdentifier` and `projectIdentifier`. Otherwise use the Xevy discovery tools available in the host, or ask for the project only when it cannot be inferred safely.
14
+ - If the user explicitly asks to attach the artifact to a personal note, obtain the note UUID from the request or current context and use `create_note_attachment`. That route stores the artifact in Personal Drive and inserts it into the note.
15
+ - Otherwise use `create_attachment` so the artifact appears in the selected project's Drive.
16
+ - If the request references a task code, resolve it with `find_task` and pass the returned UUID as `taskId` when creating the project artifact.
17
+
18
+ ## 2. Build a self-contained HTML document
19
+
20
+ Return a complete document with `<!doctype html>`, `<html>`, `<head>`, viewport metadata, and `<body>`. Put all CSS and JavaScript inline because the sandbox deliberately blocks network access.
21
+
22
+ Design around the requested job rather than a generic template:
23
+
24
+ - Make the primary information or interaction immediately clear.
25
+ - Use semantic HTML, visible keyboard focus, labelled controls, sufficient contrast, and responsive layout.
26
+ - Keep interactions usable with keyboard and pointer. Honour `prefers-reduced-motion` when motion is present.
27
+ - Use system fonts, inline SVG, CSS, and data URLs only. Do not reference CDNs, remote fonts, scripts, stylesheets, images, APIs, iframes, or forms that submit to a server; the viewer's content policy blocks them.
28
+ - Keep state local to the page. Do not assume cookies, same-origin access, parent-page DOM access, or unrestricted storage.
29
+ - Escape or safely encode any user-supplied text inserted into markup or JavaScript.
30
+ - Include real requested content. Do not leave placeholder buttons, lorem ipsum, TODOs, or controls that appear functional but do nothing.
31
+
32
+ Before saving, check that the HTML is complete, that every visible control has a working local behaviour, and that the document remains understandable at narrow and wide widths.
33
+
34
+ ## 3. Save it as an Artifact
35
+
36
+ Choose a concise kebab-case filename ending in `.html` and a one-sentence description.
37
+
38
+ For a project artifact, call `create_attachment` with:
39
+
40
+ - the resolved `workspaceIdentifier` and `projectIdentifier`
41
+ - `textContent`: the complete HTML document
42
+ - `mimeType`: `text/html`
43
+ - `fileName`: the `.html` filename
44
+ - `description`: what the artifact does
45
+ - optional resolved `taskId`
46
+ - `public: false`, unless the user explicitly requested a public/shareable artifact
47
+
48
+ For a personal-note artifact, call `create_note_attachment` with:
49
+
50
+ - `noteId`
51
+ - `textContent`: the complete HTML document
52
+ - `mimeType`: `text/html`
53
+ - `fileName` and `description`
54
+
55
+ Note attachments are always created private. Publishing the note is a separate, explicit action outside this skill.
56
+
57
+ ## 4. Report the result
58
+
59
+ Return the artifact name and the exact viewer URL from the tool response. Say where it was saved (project Drive or the named personal note) and whether it is private or public. Do not construct a URL yourself, expose storage keys, or claim success if Xevy did not store the artifact.
60
+
61
+ If the user asks for a non-HTML artifact format, explain briefly that `create-artifact` currently supports HTML only and offer the closest existing capability instead of silently changing formats.
@@ -0,0 +1,41 @@
1
+ {
2
+ "skill_name": "create-artifact",
3
+ "evals": [
4
+ {
5
+ "id": 1,
6
+ "prompt": "Create an interactive break-even calculator for a subscription product. Let me change price, monthly fixed costs, and cost per customer, and show the customer count needed to break even. Save it in this project's Drive.",
7
+ "expected_output": "A responsive, accessible, self-contained HTML calculator saved privately as an Artifact in the current project's Drive, with a returned /file/ viewer URL.",
8
+ "files": [],
9
+ "expectations": [
10
+ "The HTML contains working local controls and recalculates the break-even customer count.",
11
+ "The artifact has no external scripts, styles, fonts, images, frames, or network requests.",
12
+ "create_attachment is called with textContent, mimeType text/html, an .html filename, and public false.",
13
+ "The final response uses the viewer URL returned by Xevy."
14
+ ]
15
+ },
16
+ {
17
+ "id": 2,
18
+ "prompt": "Make a compact interactive HTML explainer of our release flow: draft → ready → in progress → review → done. Clicking each stage should reveal who owns it and the exit criteria. Attach it to note 2be7c3e8-1d14-4de1-9463-4a4f8f0995e9.",
19
+ "expected_output": "A keyboard-accessible, self-contained HTML flow explainer stored in Personal Drive and inserted inline into the specified note.",
20
+ "files": [],
21
+ "expectations": [
22
+ "The artifact presents all five stages and lets keyboard and pointer users reveal stage details.",
23
+ "The page is responsive and honours reduced-motion preferences.",
24
+ "create_note_attachment is called with the supplied noteId, textContent, mimeType text/html, and an .html filename.",
25
+ "The final response states that the artifact is private and attached to the note."
26
+ ]
27
+ },
28
+ {
29
+ "id": 3,
30
+ "prompt": "Build a public one-page HTML status dashboard for task VI42-07 with three service indicators, an incident timeline, and a button that switches between current status and maintenance details.",
31
+ "expected_output": "A self-contained HTML status dashboard linked to the resolved task, explicitly public because the user requested it, and saved as an Artifact in Drive.",
32
+ "files": [],
33
+ "expectations": [
34
+ "find_task is used to resolve VI42-07 before artifact creation.",
35
+ "The HTML includes three service indicators, an incident timeline, and a working local view switch.",
36
+ "create_attachment receives the resolved taskId and public true.",
37
+ "The result is reported with Xevy's returned viewer URL and public state."
38
+ ]
39
+ }
40
+ ]
41
+ }
@@ -12,9 +12,11 @@ Local implementation is the default. Pass the exact standalone `--cloud` flag to
12
12
 
13
13
  ## 0. Choose the engine
14
14
 
15
- - Parse `$ARGUMENTS` for the exact standalone `--cloud` token and remove that token before resolving the task. Do not treat similar text such as `--cloudy` as the flag.
16
- - Without `--cloud`, follow the **Local workflow** and do not call `start_ai_action`.
17
- - With `--cloud`, follow the **Cloud workflow**.
15
+ - Parse `$ARGUMENTS` for the exact standalone `--cloud` token and remove that token before resolving the task. Do not treat similar text such as `--cloudy`, `cloud`, or `--cloud=true` as the flag.
16
+ - Without `--cloud`, follow the **Local workflow** and do not call `start_ai_action`. The missing flag is an explicit instruction to stay local: for the whole run, `mcp__xevy__start_ai_action`, `mcp__xevy__get_ai_execution`, and `mcp__xevy__list_ai_executions` are forbidden, and so is any other way of handing the work to the Xevy server agent.
17
+ - Never infer the cloud engine from context. Task status, an earlier cloud run, an open pull request, an existing execution record, an idle local worktree, urgency, or a local step that turns out to be slow or hard are **not** consent. Only the literal flag selects the Cloud workflow.
18
+ - If the Local workflow cannot be completed, stop and report exactly what is blocking it, then let the user decide whether to rerun with `--cloud`. Never switch engines mid-run and never run both.
19
+ - With `--cloud`, follow the **Cloud workflow** and do not duplicate the work locally beyond the review-and-correct step it defines.
18
20
 
19
21
  ## 1. Resolve and apply common gates
20
22
 
@@ -12,9 +12,11 @@ Local rework is the default. Pass the exact standalone `--cloud` flag to delegat
12
12
 
13
13
  ## 0. Choose the engine
14
14
 
15
- - Parse `$ARGUMENTS` for the exact standalone `--cloud` token and remove that token before resolving the task. Do not treat similar text such as `--cloudy` as the flag.
16
- - Without `--cloud`, follow the **Local workflow** and do not call `start_ai_action`.
17
- - With `--cloud`, follow the **Cloud workflow**.
15
+ - Parse `$ARGUMENTS` for the exact standalone `--cloud` token and remove that token before resolving the task. Do not treat similar text such as `--cloudy`, `cloud`, or `--cloud=true` as the flag.
16
+ - Without `--cloud`, follow the **Local workflow** and do not call `start_ai_action`. The missing flag is an explicit instruction to stay local: for the whole run, `mcp__xevy__start_ai_action`, `mcp__xevy__get_ai_execution`, and `mcp__xevy__list_ai_executions` are forbidden, and so is any other way of handing the work to the Xevy server agent.
17
+ - Never infer the cloud engine from context. Task status, an earlier cloud run, an open pull request, an existing execution record, an idle local worktree, urgency, or a local step that turns out to be slow or hard are **not** consent. Only the literal flag selects the Cloud workflow.
18
+ - If the Local workflow cannot be completed, stop and report exactly what is blocking it, then let the user decide whether to rerun with `--cloud`. Never switch engines mid-run and never run both.
19
+ - With `--cloud`, follow the **Cloud workflow** and do not duplicate the work locally beyond the review-and-correct step it defines.
18
20
 
19
21
  ## 1. Resolve
20
22
 
@@ -12,9 +12,11 @@ Local-only merge is the default. Pass the exact standalone `--cloud` flag to hav
12
12
 
13
13
  ## 0. Choose the engine
14
14
 
15
- - Parse `$ARGUMENTS` for the exact standalone `--cloud` token and remove that token before resolving the task. Do not treat similar text such as `--cloudy` as the flag.
16
- - Without `--cloud`, follow the **Local workflow** and do not call `start_ai_action`.
17
- - With `--cloud`, follow the **Cloud workflow**.
15
+ - Parse `$ARGUMENTS` for the exact standalone `--cloud` token and remove that token before resolving the task. Do not treat similar text such as `--cloudy`, `cloud`, or `--cloud=true` as the flag.
16
+ - Without `--cloud`, follow the **Local workflow** and do not call `start_ai_action`. The missing flag is an explicit instruction to stay local: for the whole run, `mcp__xevy__start_ai_action`, `mcp__xevy__get_ai_execution`, and `mcp__xevy__list_ai_executions` are forbidden, and so is any other way of handing the work to the Xevy server agent.
17
+ - Never infer the cloud engine from context. Task status, an earlier cloud run, an open pull request, an existing execution record, an idle local worktree, urgency, or a local step that turns out to be slow or hard are **not** consent. Only the literal flag selects the Cloud workflow.
18
+ - If the Local workflow cannot be completed, stop and report exactly what is blocking it, then let the user decide whether to rerun with `--cloud`. Never switch engines mid-run and never run both.
19
+ - With `--cloud`, follow the **Cloud workflow** and do not duplicate the work locally beyond the review-and-correct step it defines.
18
20
 
19
21
  ## 1. Resolve
20
22
 
@@ -32,7 +34,11 @@ Run verification for the merged scope: inspect `git status`, then run the projec
32
34
 
33
35
  ### Local safety rules
34
36
 
35
- - The merge is local only. Do not push and do not change task status; in particular, do not move the task to `done`. The user pushes manually from the main worktree.
37
+ - The merge stays in this working copy. Do not `git push` anything — not the base branch, not the feature branch, not tags.
38
+ - Do not open, update, or merge a pull request, and do not call the GitHub merge API, `gh pr merge`, or `gh pr create`. Landing the branch on the remote is the Cloud workflow's job and requires `--cloud`.
39
+ - Do not change task status; in particular, do not move the task to `done`.
40
+ - Do not deploy main, and do not "land it through a PR first" to make the merge visible remotely. If the user wants main updated, say the merge is local and unpushed, and let them decide what to do next.
41
+ - The user pushes manually from the main worktree.
36
42
  - Keep the task worktree for iteration; do not delete it.
37
43
 
38
44
  ## 2B. Cloud workflow (`--cloud`)
@@ -51,6 +57,8 @@ The server agent verifies the open-subtasks gate, syncs the base into the featur
51
57
  - If conflicts remain or tests fail, fix them on the feature branch; never push a protected branch directly. Re-verify before finishing.
52
58
  - Report PASS/PARTIAL/FAIL with evidence. Merge mode must not move the task to `done`.
53
59
 
54
- ## 3. Main deploy (optional, policy-aware)
60
+ ## 3. Main deploy — cloud workflow only (optional, policy-aware)
55
61
 
56
- If the user wants main updated, `mcp__xevy__deploy_main` deploys the project's remote default branch. Never push protected branches (`master`, `main`, `develop`, `staging`) to make main reflect local work; land changes through a PR first and warn that main shows the remote/PR-merged state. In the local workflow, an unpushed merge will not appear in main. Report the main URL.
62
+ This step does not apply to the Local workflow. After a local merge, report that the merge is local and unpushed, so main cannot reflect it, and stop there.
63
+
64
+ In the Cloud workflow, if the user wants main updated, `mcp__xevy__deploy_main` deploys the project's remote default branch. Never push protected branches (`master`, `main`, `develop`, `staging`) to make main reflect local work, and warn that main shows the remote/PR-merged state. Report the main URL.
@@ -12,9 +12,11 @@ Local QA handoff is the default. Pass the exact standalone `--cloud` flag to del
12
12
 
13
13
  ## 0. Choose the engine
14
14
 
15
- - Parse `$ARGUMENTS` for the exact standalone `--cloud` token and remove that token before resolving the task. Do not treat similar text such as `--cloudy` as the flag.
16
- - Without `--cloud`, follow the **Local workflow** and do not call `start_ai_action`.
17
- - With `--cloud`, follow the **Cloud workflow**.
15
+ - Parse `$ARGUMENTS` for the exact standalone `--cloud` token and remove that token before resolving the task. Do not treat similar text such as `--cloudy`, `cloud`, or `--cloud=true` as the flag.
16
+ - Without `--cloud`, follow the **Local workflow** and do not call `start_ai_action`. The missing flag is an explicit instruction to stay local: for the whole run, `mcp__xevy__start_ai_action`, `mcp__xevy__get_ai_execution`, and `mcp__xevy__list_ai_executions` are forbidden, and so is any other way of handing the work to the Xevy server agent.
17
+ - Never infer the cloud engine from context. Task status, an earlier cloud run, an open pull request, an existing execution record, an idle local worktree, urgency, or a local step that turns out to be slow or hard are **not** consent. Only the literal flag selects the Cloud workflow.
18
+ - If the Local workflow cannot be completed, stop and report exactly what is blocking it, then let the user decide whether to rerun with `--cloud`. Never switch engines mid-run and never run both.
19
+ - With `--cloud`, follow the **Cloud workflow** and do not duplicate the work locally beyond the review-and-correct step it defines.
18
20
 
19
21
  ## 1. Resolve
20
22
 
@@ -12,9 +12,11 @@ Local planning is the default. Pass the exact standalone `--cloud` flag to deleg
12
12
 
13
13
  ## 0. Choose the engine
14
14
 
15
- - Parse `$ARGUMENTS` for the exact standalone `--cloud` token and remove that token before resolving the task. Do not treat similar text such as `--cloudy` as the flag.
16
- - Without `--cloud`, follow the **Local workflow** and do not call `start_ai_action`.
17
- - With `--cloud`, follow the **Cloud workflow**.
15
+ - Parse `$ARGUMENTS` for the exact standalone `--cloud` token and remove that token before resolving the task. Do not treat similar text such as `--cloudy`, `cloud`, or `--cloud=true` as the flag.
16
+ - Without `--cloud`, follow the **Local workflow** and do not call `start_ai_action`. The missing flag is an explicit instruction to stay local: for the whole run, `mcp__xevy__start_ai_action`, `mcp__xevy__get_ai_execution`, and `mcp__xevy__list_ai_executions` are forbidden, and so is any other way of handing the work to the Xevy server agent.
17
+ - Never infer the cloud engine from context. Task status, an earlier cloud run, an open pull request, an existing execution record, an idle local worktree, urgency, or a local step that turns out to be slow or hard are **not** consent. Only the literal flag selects the Cloud workflow.
18
+ - If the Local workflow cannot be completed, stop and report exactly what is blocking it, then let the user decide whether to rerun with `--cloud`. Never switch engines mid-run and never run both.
19
+ - With `--cloud`, follow the **Cloud workflow** and do not duplicate the work locally beyond the review-and-correct step it defines.
18
20
 
19
21
  ## 1. Resolve the task
20
22