@wji.ai/cli 0.3.0 → 0.5.0

package/skill/wji/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: wji
-description: Drive the WJI AI platform from the terminal with the `wji` CLI — sign in, manage workspaces and the fsnode/dataset tree, upload assets, generate images/video/audio and poll the results, and work on Infinite Canvas nodes (read the user's selected nodes, create generate nodes, connect references), and manage models, agents, prompt presets and your profile. Use whenever a task mentions WJI, wji-backend, a WJI workspace, canvas, fsnode, dataset node, or asks to generate media on WJI.
+description: Drive the WJI AI platform from the terminal with the `wji` CLI — sign in, manage workspaces and the fsnode/dataset tree, upload assets, generate images/video/audio and poll the results, and work on Infinite Canvas nodes (read the user's selected nodes, create generate nodes, connect references), manage workspace members, invitations and canvas owners, manage NPC City NPCs (profile, work history, soul, character document) and Backreel posts (drafts, publishing, cast and crew credits), and manage models, agents, prompt presets and your profile. Use whenever a task mentions WJI, wji-backend, a WJI workspace, canvas, fsnode, dataset node, NPC City, an NPC / resident, Backreel, or asks to generate media on WJI.
 ---
 
 # WJI CLI
@@ -302,6 +302,15 @@ System keys currently include `image`, `document`, `workspace-dataset`,
 When authoring, edit a pulled folder and `skill push` it again, or
 `skill update <id> --dir ./my-skill` to replace its files.
 
+**Crews** are skill packs with agent seats (a `crew.json` + `agents/<seat>.md`
+next to `skills/`). `wji crew install <name> --for claude|codex|openclaw|grok|all`
+installs one into the host (Claude Code: `~/.claude/skills` + `~/.claude/agents`;
+Codex: `~/.agents/skills` + `~/.codex/agents/*.toml`; OpenClaw: workspaces under
+`~/.openclaw/workspaces/<crew>/` plus a JSON5 fragment to merge by hand; Grok bot:
+an import zip). `--dry-run` shows the plan, `--from <dir|zip|url>` bypasses the
+registry, `wji crew status` / `uninstall` track what was written, and
+`wji crew check <dir>` validates a pack. The `short-drama` crew is the known one.
+
 Bundle limits: at most 200 markdown files, 2MB per file, 20MB in total and a
 5MB zip; 50 user skills per account. `skill update --dir` sends files in the
 request body, where each file is capped far lower, at **200,000 characters** —
@@ -323,6 +332,19 @@ A workspace's InfiniteCanvas app can hold several canvases (`wji canvas list`);
 `wji canvas create <name>` adds an empty one — e.g. one canvas per episode or
 per character set.
 
+**Ownership.** A canvas can have an owner (a workspace member) and a
+visibility: `members` (everyone in the workspace sees it) or `owner` (only
+the owner and the workspace owner). `wji canvas list` shows both;
+`wji canvas owner <canvasId> <member> --visibility owner` sets them — the
+workspace owner only. Visibility hides, it does not lock: on a `members`
+canvas any editor can edit. For a class of students (one canvas each, copy
+work to all, collect results) use `wji class` — see the `wji-classroom` skill.
+
+**Color tags.** `wji canvas tag red <nodeIds…> -l HW1` tags nodes and names
+the color on that canvas; `--tag HW1` then filters `canvas nodes`,
+`class status` and `class results`. `wji canvas copy <nodeIds…> --to
+<canvasId…>` copies nodes with their connections and tags to other canvases.
+
 **The link.** The user opens a canvas in the browser and presses the link
 button in its top bar. That stores the open workspace, canvas and **the nodes
 they have selected** on their account for 5 minutes (the tab renews it while
@@ -332,12 +354,17 @@ open). Every `wji canvas` command then targets that canvas; pass
 ```bash
 wji canvas status                     # linked canvas + selected nodes (ids, asset URLs, settings)
 wji canvas nodes                      # every node; * marks generate nodes
+wji canvas nodes --tag C01            # nodes with the color tag labelled C01 (or --tag red, --untagged)
+wji canvas nodes -n '^C0[1-3] '       # nodes whose name matches a regex (case-insensitive); combines with --tag/-k
+wji canvas tags                       # color tags on the canvas: color, label, node count
 wji canvas get <nodeId>               # full detail incl. references
 wji asset download <assetId…> -o <dir>   # then look at the images yourself
 
 wji canvas create E01 -w <workspaceId>  # new empty canvas; then --canvas <id>
 wji canvas add video --from <imgNode> <imgNode> -m <model> -r 16:9 -d 8 -p "@image1 … @image2 …"
 wji canvas add text -t "shot list…" --at 0,600
+wji canvas add text --text-file prompt.txt --plain --size 600,900   # plain text keeps its line breaks; node 600×900
+wji canvas set <nodeId> --text-file notes.md --size 520,700           # replace the text, resize
 wji canvas add image --asset <assetId> -n "Ada sheet"     # display node for an existing asset
 wji canvas add dataset --dataset <fsnodeId>                # card bound to a workspace dataset
 wji canvas set <nodeId> -p "new prompt"        # merges: other settings stay
@@ -387,6 +414,10 @@ wji canvas rm <nodeId…>                        # destructive — see Rules
 - Take new ids from the command's own output (`wji --json canvas add … | jq
   -r .id`), not by searching names — names repeat on a canvas. In zsh a
   variable holding several ids is not word-split; pass the ids literally.
+- Text, title and comment nodes are **Markdown** on the web: a single line break
+  joins the lines into one paragraph (the CLI warns). For prompts and other plain
+  text pass `--plain` (line breaks become Markdown hard breaks); `--size w,h`
+  sets the node's box so a long prompt is readable without scrolling.
 - Changes show up live in the user's open canvas; there's no need to ask them
   to reload.
 - `canvas gen` sends exactly what the canvas's own Generate button sends
@@ -396,6 +427,55 @@ wji canvas rm <nodeId…>                        # destructive — see Rules
 
 See `reference/canvas-recipes.md` for end-to-end examples.
 
+## NPC City and Backreel
+
+**NPC City NPCs** (residents) belong to you, or to an organization when you
+pass `--org`. Refer to one by id, `@handle` or name; an `@handle` that isn't
+yours resolves in the public directory (read-only for you).
+
+```bash
+wji npc list                                   # yours; --public for the directory
+wji npc get @mika                              # profile + numbered work history
+wji npc create "Mika" --role Singer --genre "City pop" --handle mika.npc   # private draft
+wji npc set @mika --tagline "…" --tag tier=Rising --social ig=https://…
+wji npc publish @mika                          # visibility public (unpublish = private)
+wji npc job add @mika -t concert --title "Neon Night" --date 2026-10-01 --location Taipei
+wji npc job set @mika 2 --detail "sold out" ; wji npc job rm @mika 3 -y
+wji npc soul get @mika > soul.json ; wji npc soul set @mika '{"voice":{…}}'
+wji npc doc export @mika -o mika.md            # whole character in one file
+wji npc doc apply @mika @mika.md --dry-run     # see the diff, then without --dry-run
+```
+
+- **Jobs** are the NPC's work history (concert, release, collaboration, brand,
+  event, ad, appearance) shown on its public page. They have no ids: the CLI
+  numbers them 1…n and rewrites the whole list, so list again before `job
+  set` / `job rm` if anything else may have changed it.
+- `soul set` merges top-level keys only; a nested object you pass replaces
+  that whole key. Memories and albums are not part of the soul.
+- `npc create` needs NPC City spawn permission on the account (a 403 says so);
+  only an admin can grant it. Admin actions — spawn permission, featured / hero
+  slider, moderation — are not in `wji`.
+- `npc transfer send <npc> --to <email>` offers the NPC to someone; they
+  `npc transfer accept <id>` within 7 days. You lose it on acceptance.
+
+**Backreel posts** are your film / project pages. `create` always makes a
+draft; publishing needs a cover, media or an episode.
+
+```bash
+wji backreel list                              # yours, drafts included; --all for published posts
+wji backreel create "Harbour" -d @synopsis.txt --tags drama,short --cover <assetId>
+wji backreel set <postId> --project-status in_production
+wji backreel credit add <postId> --kind creative --name "Wayne" --role 導演
+wji backreel credit add <postId> --npc @mika --role "飾 阿明" --job appearance
+wji backreel publish <postId>                  # unpublish takes it offline
+```
+
+- Credits (max 30) are rewritten whole in order; `credit rm` goes by number.
+- `--npc` casts an NPC (the credit's `npcId`, name and avatar come from it);
+  `--job <type>` also adds the work to that NPC's history — only for your own
+  NPCs.
+- `--description` takes plain text (turned into paragraphs) or HTML.
+
 ## Everything else
 
 ```bash
@@ -413,7 +493,9 @@ wji org list && wji org use <orgId>
   These commands delete, revoke or overwrite, and none can be undone from the
   CLI: `ws rm`, `ws app rm`, `ws member rm`, `fs rm`, `dataset rm`,
   `asset rm`, `history rm`, `preset rm`, `skill rm`, `skill update --dir`,
-  `agent rm`, `auth key rm`, `auth key revoke`, `config rm`, `canvas rm`.
+  `agent rm`, `auth key rm`, `auth key revoke`, `config rm`, `canvas rm`,
+  `ws member link` (revokes the current share link), `npc rm`, `npc job rm`,
+  `npc doc apply`, `npc transfer send`, `backreel rm`, `backreel credit rm`.
   They prompt `[y/N]` in a terminal, but when you run them there is no
   terminal, so they refuse unless you pass `--yes`. **The user's reply in the
   chat is the only confirmation there is.** Before running one:

package/skill/wji/reference/commands.md

@@ -73,7 +73,11 @@ switch endpoint.
 | `ws favorite <id> [--off]` | `PUT /workspace/list/:id/favorite` |
 | `ws fs [id] [-a appId]` | `GET /workspace/list/:id/fs[/:appid]` |
 | `ws app list\|add <app> [-n]\|rm <appId> [-y]` | `POST/DELETE /workspace/list/:id/apps` |
-| `ws member list\|add <userId> [-r role]\|role <memberId> <role>\|rm <memberId> [-y]` | `/workspace/list/:id/member/*` |
+| `ws member list [id] [-r role]` | members from `GET /workspace/list/:id` (there is no member-list endpoint): name, email, role, user id, membership id |
+| `ws member add <userIds...> [-r editor\|viewer] [-w]` | `POST .../member/add-batch {users, role}` (≤50; existing members skipped). Org workspaces accept only org members |
+| `ws member invite <emails...> [-r editor\|viewer] [-w]` | `POST /invitation/workspace/:id/invite-emails` (owner only, ≤50; commas/spaces split). Registered users are **added at once**, others get an emailed invitation — which also revokes the current share link. Reports added / invited / skipped / invalid |
+| `ws member link [id] [-r role] [--show]` | `POST /invitation/create {targetType:'workspace', targetId, role}` (owner only; valid 7 days — the server rejects any `expiredAt`). One active link per workspace — a new one revokes the old. `--show` lists the active link (`GET /invitation/workspace/:id`) |
+| `ws member role <member> <editor\|viewer> [-w]` / `ws member rm <members...> [-w] [-y]` | `PUT .../member/:memberId/role`, `DELETE .../member/:memberId`. `<member>` is a name, email, user id or membership id (ambiguous names are an error); the owner is refused. A removed member's canvases stay |
 | `ws quota [id] [--set k=v]` | `GET .../quota-usage`, `PUT .../quota` |
 | `ws stats [id]` | `GET /workspace/list/:id/stats` |
 | `ws templates` / `ws clone <templateId>` | `GET /workspace/start/templates`, `POST /workspace/create/:id` |
@@ -160,13 +164,17 @@ updates live.
 | --- | --- |
 | `canvas status` (`link`) | `GET /canvas-link`, then the selected nodes read fresh from the canvas |
 | `canvas unlink` | `DELETE /canvas-link`; the tab turns its button off at its next heartbeat (≤ 60s) |
-| `canvas list [-w]` | canvases under each InfiniteCanvas app: `GET /workspace/list/:id/fs/:appId` → `workspace-v2/canvases` children |
-| `canvas create <name> [-w] [--app]` | `POST /fsnode/create` a `workspace-v2/canvas` folder under that `canvases` folder with the web's initial content (`{data:{viewport, backgroundMode:'dots'}, metadata:{}}`) |
-| `canvas nodes [-c] [-k kind]` | `GET /fsnode/list/:canvasId/children?limit=-1` + `POST /assets/check-status` |
+| `canvas list [-w] [-o member\|none]` | canvases under each InfiniteCanvas app: `GET /workspace/list/:id/fs/:appId` → `workspace-v2/canvases` children, with owner and visibility from `content.metadata`. Owner-only canvases of others are hidden unless you own the workspace |
+| `canvas create <name> [-w] [--app] [-o member] [--visibility owner\|members]` | `POST /fsnode/create` a `workspace-v2/canvas` folder under that `canvases` folder with the web's initial content (`{data:{viewport, backgroundMode:'dots'}, metadata:{ownerUserId?, visibility?}}`) |
+| `canvas owner <canvasId> [member] [--visibility owner\|members] [--none]` | without options shows owner + visibility; otherwise `PATCH /fsnode/list/:id` with the whole envelope `{data, metadata}` and `baseUpdatedAt` (retried on 409). **Workspace owner only** (403 otherwise). `owner` visibility = only the owner and the workspace owner see the canvas; it hides, it does not lock — with `members` any editor can edit it |
+| `canvas tag <tag> [nodeIds...] [-c] [-l label] [--selected]` | sets `content.colorTag {colorId}` on the nodes (`contentPatch`); `none` removes it. `<tag>` is a color, color id or existing label. `-l` writes the color's label to the canvas folder `content.data.colorTagNames` (`""` clears) |
+| `canvas copy [nodeIds...] --to <canvasIds...> [-c] [--selected] [--at x,y] [--same-position] [-y]` | the canvas's own copy-paste: new nodes (no position, `generate.historyId/pendingAssetId` dropped, finished asset shared via `file`), edges among them re-created oldest first so `@image1…` numbering holds, color tags kept and a missing label carried to the target. Edges from nodes outside the copy are left out. Default placement: right of what is already on the target |
+| `canvas nodes [-c] [-k kind] [-n regex] [--tag tags…\|--untagged]` | `GET /fsnode/list/:canvasId/children?limit=-1` + `POST /assets/check-status`. `-n` matches the node name as a case-insensitive regex (`/re/flags` to set flags yourself). `--tag` takes a label (`C01`, case-insensitive), a color (`red`) or a color id (`rose`); several values match any. Filters combine (AND) |
+| `canvas tags [-c] [-a]` | the canvas's color tags: color, label, node count (`-a` also unused, unlabelled colors) |
 | `canvas get <nodeId> [-c]` | same load; one node with references (`@image1 ← id`) and frame slots |
 | `canvas edges [-c] [--node]` | the `canvas/edge` children |
-| `canvas add <kind> [-c] [-n] [-t\|--text-file] [--asset] [--dataset] [-p\|--prompt-file] [-m] [-r] [--resolution] [-d] [--set] [--from ids…] [--at x,y]` | `POST /fsnode/create` (`canvas/node/<kind>`), then one `canvas/edge` per `--from`. Kinds: text, title, comment, image, video, audio, dataset. `add dataset --dataset <fsnodeId>` writes `content {datasetId, datasetName, datasetType, datasetParentName, description}` from the dataset node (must be `workspace/dataset`); it takes no `--from` |
-| `canvas set <nodeId> [-c] [-n] [-t] [--move x,y] [-p] [-m] [-r] [--resolution] [-d] [--set]` | read → merge → `PATCH /fsnode/list/:id` |
+| `canvas add <kind> [-c] [-n] [-t\|--text-file] [--plain] [--size w,h] [--asset] [--dataset] [-p\|--prompt-file] [-m] [-r] [--resolution] [-d] [--set] [--from ids…] [--at x,y]` | `POST /fsnode/create` (`canvas/node/<kind>`), then one `canvas/edge` per `--from`. Kinds: text, title, comment, image, video, audio, dataset. `add dataset --dataset <fsnodeId>` writes `content {datasetId, datasetName, datasetType, datasetParentName, description}` from the dataset node (must be `workspace/dataset`); it takes no `--from`. Text kinds are Markdown on the web; `--plain` turns every single line break into a Markdown hard break (`"  \n"`, fenced code untouched), and without it the CLI warns when a single break would be joined. `--size` writes `content.width/height` |
+| `canvas set <nodeId> [-c] [-n] [-t\|--text-file] [--plain] [--move x,y] [--size w,h] [-p] [-m] [-r] [--resolution] [-d] [--set]` | read → merge → `PATCH /fsnode/list/:id` with `contentPatch` of only the top-level keys that changed, so a concurrent browser edit of another key survives (falls back to a whole-content write on a backend without `contentPatch`) |
 | `canvas connect <from> <to> [-c]` | `POST /fsnode/create` (`canvas/edge`); a first/last-frame video model gets `videoFrameSlot` start, then end |
 | `canvas disconnect <from> <to> [-c]` | `DELETE /fsnode/list/:edgeId` |
 | `canvas rm <nodeIds...> [-c] [-y]` | deletes the nodes' edges, then the nodes; refuses nodes still generating |
@@ -179,6 +187,12 @@ Storage format (what the web canvas writes):
   `generate` with `content.generate {prompt, model, ratio, resolution,
   duration, values, improvePromptEnabled, historyId?, pendingAssetId?}`. Width
   and height are not stored.
+- Color tag: the node stores only `content.colorTag {colorId}`, one of
+  `rose` (red), `orange`, `amber` (yellow), `lime` (green), `teal`, `sky`
+  (blue), `violet` (purple), `fuchsia` (pink). The label is per color per
+  canvas, on the canvas folder: `content.colorTagNames {rose: "C01", …}`, so
+  every red node on a canvas shares one label. A `name` left on an old node's
+  `colorTag` is ignored, as on the web.
 - Edge: `mimetype canvas/edge`, name `连线`, `content {fromNodeId, toNodeId,
   sourceHandle, targetHandle, videoFrameSlot?}`. References are incoming edges
   sorted by `sort` then id, numbered per source kind.
@@ -202,6 +216,71 @@ viewport, url}` on toggle (`takeover: true`), on selection change and every
 60s. A non-takeover `PUT` from a tab that no longer owns the link gets
 `409 canvas-link-gone`, which switches that tab's button off.
 
+## class
+
+A class is a workspace the teacher owns; students are members (editors) and
+each student's canvas is the one whose `metadata.ownerUserId` is them. Every
+command takes `-w` (defaults to the linked workspace, then the profile's).
+
+| Command | API / behaviour |
+| --- | --- |
+| `class roster` | members minus the owner, with role and owned canvases |
+| `class canvases [--create] [--visibility owner\|members] [--update] [--name '{name}'] [--student …] [--app]` | lists each student's canvas; `--create` makes the missing ones (`POST /fsnode/create`, owner = student, default visibility `owner`); `--update` applies `--visibility` to existing ones. Idempotent |
+| `class copy [nodeIds...] [-c] [--selected] [--student …] [--at x,y] [--same-position] [-y]` | `canvas copy` into every student canvas (default: the linked selection); 4 canvases at a time; failures reported per student with a rerun hint, exit 1 |
+| `class status [--tag …] [-k kind] [--student …] [-s name\|recent\|progress]` | per student: nodes, generate nodes done / running / failed / not run, `GET /ai/assets/history/search?scope=canvas&scopeId=<canvas>&limit=1&sort[createdAt]=desc` for count + last generation, credits from `GET .../quota-usage` `byUserTotal` |
+| `class results [--student …] [--tag …] [-k kind] [-n regex] [--since 2h] [--all] [-s recent\|name] [-l n] [-d dir]` | finished media on student canvases (generate nodes; `--all` adds display nodes), newest first; `-d` saves `<dir>/<student>/<node>-<id>.<ext>` |
+
+`--tag` matches each canvas's own label (a label a canvas lacks matches nothing
+there); `--student` takes names, emails or user ids.
+
+## npc
+
+`<npc>` is an id, `@handle` or name among your NPCs (org NPCs with `--org`); an
+unknown `@handle` falls back to `GET /npc-city/residents/by-handle/:h` (public).
+
+| Command | API |
+| --- | --- |
+| `npc list [--public] [-k] [--status active\|debut\|hiatus] [--visibility] [--page] [--limit]` | `GET /npc-city/residents/mine` (`--public`: `GET /npc-city/residents`) |
+| `npc get <npc>` | `GET /npc-city/residents/:id` |
+| `npc create <name> --role --genre [--handle] [--tagline] [--bio] [--image url\|assetId] [--hero-image] [--color] [--status] [--visibility] [--social k=url…] [--tag k=v…] [--set k=v…]` | `GET …/handle-available`, then `POST /npc-city/residents` (needs profile `canSpawn`; private by default; name is uppercased) |
+| `npc set <npc> [-n] [--role] [--genre] [same flags]` | `PATCH /npc-city/residents/:id` with only the given fields; `--social` / `--tag` merge into the current objects |
+| `npc publish <npc>` / `npc unpublish <npc>` | `PATCH … {visibility}` |
+| `npc rm <npc> [-y]` | `DELETE /npc-city/residents/:id` (soft delete) |
+| `npc handle <handle> [--exclude <npc>]` | `GET /npc-city/residents/handle-available` |
+| `npc job list <npc>` | the resident's `jobs[]`, numbered 1…n |
+| `npc job add <npc> -t <type> --title --date YYYY-MM-DD [--detail] [--location] [--url]` | read, append, `PATCH {jobs}` |
+| `npc job set <npc> <n> [same flags]` | read, merge into #n, `PATCH {jobs}` |
+| `npc job rm <npc> <n...> [-y]` | read, drop, `PATCH {jobs}`; refuses if the list changed meanwhile |
+| `npc soul get <npc>` | `GET /npc-city/residents/:id/soul` |
+| `npc soul set <npc> <json\|@file\|->` | `PATCH /npc-city/residents/:id/soul {soulConfig}` (shallow merge) |
+| `npc doc export <npc> [--format md\|json] [-o file]` | `GET /npc-city/residents/:id/document?format=` |
+| `npc doc apply <npc> <@file\|-> [--dry-run] [-y]` | `POST …/document/preview`, confirm, `POST …/document` |
+| `npc transfer send <npc> --to <email\|userId> [-y]` | `POST /npc-city/residents/:id/transfer` |
+| `npc transfer list` | `GET /npc-city/transfers/incoming` + `/outgoing` |
+| `npc transfer accept\|reject\|cancel <transferId>` | `POST /npc-city/transfers/:id/<action>` |
+
+Job types: concert, release, collaboration, brand, event, ad, appearance. The
+server drops jobs without a title or date and turns unknown types into `event`;
+the CLI rejects both up front.
+
+## backreel
+
+| Command | API |
+| --- | --- |
+| `backreel list [--all] [-k] [--page] [--limit]` | `GET /backreel/post/search/my` (`--all`: `GET /backreel/post/search`) |
+| `backreel get <postId>` | `GET /backreel/post/list/:id` |
+| `backreel create <title> [--kind showcase\|crowdfunding] [--category] [--project-status] [--tags a,b] [-d text\|@file] [--cover assetId] [--cover-portrait] [--trailer] [--body json]` | `POST /backreel/post/create` (always a draft) |
+| `backreel set <postId> [--title] [same flags]` | `PUT /backreel/post/list/:id` with only the given fields |
+| `backreel publish\|unpublish <postId>` | `POST /backreel/post/list/:id/publish\|unpublish` (publish needs a cover, media or an episode) |
+| `backreel rm <postId> [-y]` | `DELETE /backreel/post/list/:id` |
+| `backreel credit list <postId>` | the post's `credits[]`, numbered |
+| `backreel credit add <postId> --role [--name] [--kind cast\|crew\|creative] [--npc] [--user] [--link] [--job <type>]` | read, append, `PUT {credits}`; `--job` then appends to the NPC's `jobs` (own NPCs only, checked first) |
+| `backreel credit rm <postId> <n...> [-y]` | read, drop, `PUT {credits}` |
+
+Project status: planning, pre_production, in_production, post_production,
+completed. `-d` plain text becomes `<p>` paragraphs; HTML passes through and
+is sanitized server-side. Admin routes (`/api/backreel/*`) reject `sk_` keys.
+
 ## gen
 
 Shared flags: `-m/--model` (required), `-p/--prompt`, `-n/--n`, `-w/--workspace`,
@@ -339,6 +418,17 @@ Only `.md` files persist (the importer drops everything else); scripts belong to
 | `skill update <id> [-n] [-d] [--visibility] [--dir] [-y]` | `PUT /ai/skill/:id` — metadata, or replace **all** files from `--dir` (confirms first) |
 | `skill rm <id> [-y]` | `DELETE /ai/skill/:id` |
 
+## crew
+
+Crew packs are local or remote folders (`crew.json`, `agents/<seat>.md`, `skills/<name>/SKILL.md`, `AGENTS.md`) — no WJI API involved.
+
+| Command | Behaviour |
+| --- | --- |
+| `crew install [name] --for <claude,codex,openclaw,grok\|all> [--from dir\|zip\|tar.gz\|url] [--ref] [--project dir] [--link] [--out zip] [--no-register] [--dry-run] [-y]` | fetches the pack (registry → GitHub tarball, cached under `~/.wji/crews/`), validates it, prints the plan, then per host: **claude** copies `skills/*` → `~/.claude/skills/` and `agents/*.md` → `~/.claude/agents/`; **codex** copies skills → `~/.agents/skills/` and writes `~/.codex/agents/<seat>.toml` (`developer_instructions` = persona body, `sandbox_mode` from capabilities, `[[skills.config]]` per skill); **openclaw** shares `~/.agents/skills/`, writes `~/.openclaw/workspaces/<crew>/<seat>/{AGENTS.md,SOUL.md,skills→}` + `openclaw.agents.json5` and runs `openclaw agents add` when the binary exists; **grok** writes `<crew>-export.zip` (`skills/`, `bots/*.json`, `bots/crew-manifest.json`, `channels/*.json`, sibling links rewritten to `sand-workflow:`). `--project` targets `<dir>/.claude`, `.agents`, `.codex`, `openclaw` instead of `$HOME` |
+| `crew status [name]` | reads `~/.wji/crews/installed.json`; per path ✓ / ↗ symlink / ✗ missing |
+| `crew uninstall <name> [--for targets] [-y]` | removes exactly the recorded paths; reminds you to clean `openclaw.json` by hand |
+| `crew check <dir>` | validates `crew.json` ↔ `agents/*.md` (names, skills, tools vs capabilities), every `SKILL.md` (name == folder, description ≤ 1024) and that relative links resolve |
+
 Import rules: the zip must contain `SKILL.md` at its root (or one folder deep — a
 single common root folder is stripped). `SKILL.md` frontmatter `name:` is
 required; `description:` is read too. Visibility is `private` (default) or

package/skill/wji-classroom/SKILL.md

@@ -0,0 +1,161 @@
+---
+name: wji-classroom
+description: Run a class on WJI with the `wji` CLI — a teacher's workspace where every student has their own Infinite Canvas. Set up the class workspace, invite students by email or share link, create one private canvas per student, hand out preset prompts and starter nodes (copy the teacher's selected nodes into every student's canvas), then check each student's progress and collect their generated results by name, recency or color tag. Use when a teacher / instructor / 老師 / 講師 mentions a class, course, workshop, students / 學生 / 学员, assignments / homework / 作業, or wants to manage members' canvases on WJI.
+---
+
+# WJI classroom
+
+This skill sits on top of the `wji` skill — read that one for sign-in,
+models, generation and the canvas basics. Everything here is the `wji`
+CLI; the class-wide commands live under `wji class`.
+
+## How a class maps onto WJI
+
+| Class | WJI |
+| --- | --- |
+| the class | a workspace the teacher **owns** |
+| a student | a workspace member with role **editor** (viewers cannot generate) |
+| a student's desk | a canvas whose owner is that student, visibility `owner` — only they and the teacher see it |
+| handouts | workspace prompt presets, and starter nodes copied into every canvas |
+| an assignment | nodes carrying a color tag with a label, e.g. red = `HW1` |
+
+Only the workspace **owner** can invite, create share links and set canvas
+owners. Check first:
+
+```bash
+wji auth whoami
+wji ws member list <workspaceId>        # your row must say owner
+```
+
+## 1. Create the class workspace
+
+```bash
+wji ws create "Art 101 — Spring" -a canvas     # the canvas app is all a class needs
+wji ws use <workspaceId>                        # later commands default to it
+```
+
+## 2. Invite students
+
+```bash
+wji ws member invite amy@school.edu, ben@school.edu     # ≤50 per call; commas or spaces
+wji ws member link                                       # or a join link (valid 7 days) to post in the class chat
+wji ws member link --show                                # the active link
+wji class roster                                         # who has joined, role, canvas
+```
+
+- Registered emails join immediately (`added`); the others get an invitation
+  email and join after signing up (`invited`). Rerun `class roster` later.
+- There is **one** active link per workspace. `member link` — and any
+  `member invite` that emails someone — revokes the previous link. Tell the
+  teacher before replacing a link they already shared.
+- Late joiners via the link join as the link's role (default editor).
+- Wrong role: `wji ws member role "Ben" editor`. Remove: `wji ws member rm "Ben"`.
+
+## 3. One canvas per student
+
+```bash
+wji class canvases --create                    # named after each student, private
+wji class canvases --create --name "{name} · Art 101"
+wji class canvases --visibility members --update   # let the class see each other's canvases
+```
+
+It only creates what is missing, so rerun it after new students join. The
+teacher (workspace owner) sees every canvas; each student sees only theirs
+(plus any canvas with visibility `members`, e.g. a shared "Class board").
+Individual canvases: `wji canvas owner <canvasId> "Amy" --visibility owner`.
+
+## 4. Preset prompts, so students don't have to type
+
+Two ways, often both:
+
+**Workspace presets** — a prompt library for the class. Students press `/`
+on their canvas (the *workspace* tab) and the prompt becomes a text node, or
+`/` inside a generate node's prompt box to insert it.
+
+```bash
+wji preset create "Watercolor portrait" -w <workspaceId> -c utility -t hw1 \
+  -p "A soft watercolor portrait of @image1, loose brush strokes, paper texture"
+wji preset workspace                          # what the class sees
+```
+
+**Starter nodes** — a ready-to-run generate node (prompt, model, settings,
+reference images already wired) that students only have to press Generate on.
+Build it once on the teacher's canvas, then copy it to everyone (step 5):
+
+```bash
+wji canvas add image -c <teacherCanvas> -n "HW1 portrait" -m <model> \
+  -p "@image1 as a watercolor portrait" --from <referenceImageNode>
+```
+
+Pick the model with `wji models list --feature image` / `wji models get`.
+
+## 5. Copy nodes into every student's canvas
+
+The usual way: the teacher selects the nodes in the browser and presses the
+link button in the canvas top bar. Then:
+
+```bash
+wji canvas status                              # confirm what is selected
+wji canvas tag red --selected -l HW1           # optional: mark it as an assignment
+wji class copy -y                              # the selection → every student canvas
+wji class copy <nodeId> <nodeId> -c <canvasId> --student "Amy" "Ben" -y
+```
+
+- Connections between the copied nodes come along with their `@image1…`
+  order; finished images/videos are shared (not regenerated); generate nodes
+  keep prompt, model and settings but start un-generated.
+- The group lands to the right of what is already on each canvas (`--at x,y`
+  or `--same-position` to choose).
+- Color tags come along; the label (`HW1`) is added to a student's canvas if
+  that color has no label there yet.
+- Failures are reported per student with a `--student …` rerun hint.
+
+## 6. Check progress and gather results
+
+```bash
+wji class status                               # every student: nodes, done / running / failed / not run, gens, last gen, credits
+wji class status --tag HW1 --sort progress     # just the assignment, least done first
+wji class status --sort recent                 # who generated most recently
+wji class results --tag HW1                    # finished work, newest first
+wji class results --student "Amy" --since 2h
+wji class results --tag HW1 -d ./hw1           # download: ./hw1/<student>/<node>-<id>.png
+wji class results --tag HW1 --all              # also display nodes students uploaded
+```
+
+To review, download and look at the files, then leave feedback on the
+student's canvas:
+
+```bash
+wji canvas list --owner "Amy"
+wji canvas add comment -c <amyCanvas> -t "Lovely colors — try a warmer background" --at 0,-200
+```
+
+## Rules
+
+- **Emails go out in the teacher's name.** Show the exact address list and
+  role and get a yes in the chat before `ws member invite`. Same for
+  `ws member link` when a link is already active (it stops working).
+- **Copying writes into every student's canvas.** Say what will be copied
+  (node names, count of students) and get a yes, then pass `-y`.
+- **Don't generate on students' canvases** unless the teacher asks — it
+  spends the teacher's credits and replaces what the student would do. When
+  asked, follow the `wji` skill's cost rules (show the total for N students).
+- **Deleting in a student's canvas** (`canvas rm`) follows the `wji`
+  confirm-before-destroying rule, one canvas at a time.
+- Look students up by name or email (`--student "Amy"`); if a name is
+  ambiguous the CLI says so — ask, don't guess.
+
+## Good to know
+
+- Private (`owner`) visibility hides a canvas; it does not lock it. On a
+  `members` canvas any editor can edit anything.
+- Students can edit or delete workspace presets (the backend has no role
+  check there). Keep the canonical prompts in the teacher's own presets too
+  (`wji preset create` without `-w`) and re-copy with `wji preset copy`.
+- Generation history in a workspace is readable by every member, so students
+  can technically list each other's generations through the API even when
+  canvases are private.
+- Organization admins who are not the workspace owner cannot invite or set
+  canvas owners — the workspace owner must.
+- Credits in `class status` are what each student spent in this workspace
+  (all time); `wji ws quota` sets a workspace spending cap.