@xevy/skills 0.1.19 → 0.1.20
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. Cloud (server Web Agent) by default; '-here' variants run locally in this Claude Code session. Claude reviews and corrects the result after every action.",
|
|
5
|
-
"version": "0.1.
|
|
5
|
+
"version": "0.1.20",
|
|
6
6
|
"author": {
|
|
7
7
|
"name": "Xevy"
|
|
8
8
|
},
|
package/package.json
CHANGED
|
@@ -0,0 +1,28 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: create-note
|
|
3
|
+
description: Create a personal note in the current Xevy workspace — a quick jotting, meeting note, snippet, or draft. Notes are private to you by default; you can publish one to a stable public, no-login link. Use when the user asks to "jot down", "take a note", "make a note", "save this as a note", or "create a shareable note". For a project-scoped doc/RFC/runbook, prefer /xevy:create-document instead.
|
|
4
|
+
argument-hint: "[title or topic] [--publish]"
|
|
5
|
+
disable-model-invocation: true
|
|
6
|
+
allowed-tools: "Read mcp__xevy__get_current_user mcp__xevy__list_workspaces mcp__xevy__create_note mcp__xevy__publish_note"
|
|
7
|
+
---
|
|
8
|
+
|
|
9
|
+
# /xevy:create-note — create a personal note
|
|
10
|
+
|
|
11
|
+
Create a note in the current Xevy workspace and return a link. Notes are **personal and workspace-scoped** (not project-scoped, unlike documents): `private` to you by default, or **published** to a stable no-login URL (`<XEVY_BASE>/n/<publicId>`). Optional argument `$ARGUMENTS` may carry the title/topic and a `--publish` flag.
|
|
12
|
+
|
|
13
|
+
## 1. Resolve the workspace
|
|
14
|
+
- Prefer `.xevy/project.json` for `workspaceIdentifier`. If it's missing, call `mcp__xevy__list_workspaces` and ask the user which workspace to use when there's more than one.
|
|
15
|
+
- Confirm `mcp__xevy__get_current_user` succeeds so the note is owned by the right account. Notes are strictly owner-only — you never see or touch another user's notes.
|
|
16
|
+
|
|
17
|
+
## 2. Decide title and body
|
|
18
|
+
- **Title:** from `$ARGUMENTS` or the user's request. Keep it concise and descriptive. Ask if it's unclear.
|
|
19
|
+
- **Body (markdown):** draft `contentMd` from the conversation/request. Don't fabricate facts — if the user only gave a title, create a short stub and say so. Use real markdown (headings, lists, code fences).
|
|
20
|
+
|
|
21
|
+
## 3. Create it
|
|
22
|
+
- Call `mcp__xevy__create_note` with `workspaceIdentifier`, `title`, and `contentMd` (markdown). Notes are created **private** — there is no visibility parameter.
|
|
23
|
+
- **Publish only on request:** if the user asked for a public/shareable link or passed `--publish`, call `mcp__xevy__publish_note` with the returned `noteId` afterwards. Confirm first — a published note is readable by anyone with the link, no login. The public id is stable (minted once), so the link never changes on later edits or re-publishes.
|
|
24
|
+
|
|
25
|
+
## 4. Report
|
|
26
|
+
- Give the user the note **title** and whether it's private or published.
|
|
27
|
+
- If **published**, share the no-login URL from the tool's returned `publicUrl` (shape: `<XEVY_BASE>/n/<publicId>`, e.g. `https://xevy.ai/n/<publicId>`). Use the URL the tool returns — do not construct it yourself. Otherwise tell them it's in their Notes app.
|
|
28
|
+
- Never print secrets or paste private content into third-party tools.
|
|
@@ -0,0 +1,33 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: manage-notes
|
|
3
|
+
description: Manage your personal Xevy notes end to end — list, find, read, edit, publish/unpublish, and delete. Use when the user wants to review their notes, update a note's body/title, publish a note to a public link or unpublish it, or remove a note. Notes are personal and workspace-scoped. For creating a brand-new note, prefer /xevy:create-note.
|
|
4
|
+
argument-hint: "[what to do, e.g. 'list my notes', 'publish the standup note', 'delete the scratch note']"
|
|
5
|
+
disable-model-invocation: true
|
|
6
|
+
allowed-tools: "Read mcp__xevy__get_current_user mcp__xevy__list_workspaces mcp__xevy__list_notes mcp__xevy__get_note mcp__xevy__create_note mcp__xevy__update_note mcp__xevy__delete_note mcp__xevy__publish_note mcp__xevy__unpublish_note"
|
|
7
|
+
---
|
|
8
|
+
|
|
9
|
+
# /xevy:manage-notes — manage your personal notes
|
|
10
|
+
|
|
11
|
+
Full lifecycle management of Xevy notes. Notes are **personal and workspace-scoped** (NOT project-scoped, unlike documents): `private` to you by default, or **published** to a stable no-login URL (`<XEVY_BASE>/n/<publicId>`). You can only ever see and act on your own notes. `$ARGUMENTS` describes what to do.
|
|
12
|
+
|
|
13
|
+
## 1. Resolve context
|
|
14
|
+
- Prefer `.xevy/project.json` for `workspaceIdentifier`. If missing, call `mcp__xevy__list_workspaces` and ask which workspace when there's more than one.
|
|
15
|
+
- `mcp__xevy__get_current_user` confirms whose notes you're working with (notes are strictly owner-only).
|
|
16
|
+
|
|
17
|
+
## 2. Find the note(s)
|
|
18
|
+
- **List:** `mcp__xevy__list_notes` with `workspaceIdentifier` → your own notes, newest-updated first. Pass `search` for a case-insensitive filter over title + body.
|
|
19
|
+
- **Read one:** `mcp__xevy__get_note` with the `noteId` for the full markdown `contentMd`.
|
|
20
|
+
- Match the user's description (title/topic) to a note; if several match, list the candidates and ask which one. Never guess at a destructive action.
|
|
21
|
+
|
|
22
|
+
## 3. Apply the change
|
|
23
|
+
- **Edit body / title** — `mcp__xevy__update_note`: set `contentMd` (markdown) and/or `title`. When revising, read the current `contentMd` first and preserve content the user didn't ask to change. Pass a `metadata` object to merge arbitrary keys.
|
|
24
|
+
- **Publish** — `mcp__xevy__publish_note`: makes the note readable by anyone with the link, no login. **Confirm first.** The public id is minted once and never changes, so re-publishing keeps the SAME link.
|
|
25
|
+
- **Unpublish** — `mcp__xevy__unpublish_note`: the public link stops resolving. The id is retained, so a later re-publish reuses the same URL.
|
|
26
|
+
|
|
27
|
+
## 4. Delete
|
|
28
|
+
- `mcp__xevy__delete_note` (soft delete). This is destructive — confirm the exact title with the user first. You can only delete your own notes.
|
|
29
|
+
|
|
30
|
+
## 5. Report
|
|
31
|
+
- State what changed (title, published/unpublished) and, when a note is **published**, give the no-login link from the tool's returned `publicUrl` (shape: `<XEVY_BASE>/n/<publicId>`). Use the URL the tool returns — never construct or guess it.
|
|
32
|
+
- For lists, show title · updated date · (public) — concise, scannable.
|
|
33
|
+
- Never paste private note content into third-party tools, and never print secrets.
|