rshow 0.0.1 → 0.0.3

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "rshow",
-  "version": "0.0.1",
+  "version": "0.0.3",
   "description": "Publish static artifacts to rshow",
   "license": "MIT",
   "homepage": "https://rslib.github.io/rshow",
@@ -21,7 +21,7 @@
   ],
   "type": "module",
   "engines": {
-    "node": ">=26"
+    "node": ">=22"
   },
   "bin": {
     "rshow": "dist/main.js"
@@ -38,7 +38,8 @@
     "test": "node --test test/",
     "build": "node scripts/build.mjs",
     "typecheck": "tsc --noEmit",
-    "prepack": "node scripts/assemble.mjs"
+    "prepack": "node scripts/assemble.mjs",
+    "sea": "node scripts/sea.mjs"
   },
   "devDependencies": {
     "@types/node": "^26.6.6",

package/skills/rshow/SKILL.md

@@ -96,7 +96,7 @@ Only the owner can share, rename or delete.
 
 On 2, fix the command and do not retry the same line.
 On a config error (`no server configured`, no token, or a config file that will not load), run `rshow doctor` and show its output to the person.
-On 4, or on exit 2 with `no token`, never ask for a token in chat. Tell the person to run `rshow login` in their own terminal, which saves the token in the Keychain.
+On 4, or on exit 2 with `no token`, never ask for a token in chat. Tell the person to run `rshow login` in their own terminal, which saves the token where only their account can read it.
 On 5, retry once and then report the message verbatim.
 On 6, fix the page, never `--no-check` past it.
 

package/skills/rshow/reference/cli.md

@@ -10,6 +10,7 @@
 - projects
 - tags and list
 - theme, show, delete
+- skills
 - handoff and compare
 - Config files
 - Exit codes
@@ -26,7 +27,7 @@ This file is the whole surface, both config files and the exit codes.
 | `rshow publish <file-or-dir>` | upload a folder, or one file as `index.html`, as a new version |
 | `rshow config [dir] [--offline]` | print the merged config as JSON, with `theme` resolved to its current version, such as `default@3` |
 | `rshow init --url <admin-url> --art <viewer-url>` | write the global config file, with `--theme` and `--force` |
-| `rshow doctor [dir]` | check node, config, token, api, art and theme, one `ok\|warn\|fail` line each |
+| `rshow doctor [dir]` | check node, config, token, api, art, theme and skills, one `ok\|warn\|fail` line each |
 | `rshow list` | list artifacts you own or that are shared with you, with `--project`, `--tag` and `--q` filters |
 | `rshow show <slug>` | print the artifact, its versions, its shares, its project and its tags |
 | `rshow share <slug>` | set the mode, or add and remove shares |
@@ -41,7 +42,10 @@ This file is the whole surface, both config files and the exit codes.
 | `rshow theme preview <dir>` | build the theme, then serve its preview page on `127.0.0.1` |
 | `rshow theme publish <dir>` | publish a theme folder as `theme-<name>` and set it public |
 | `rshow theme list` | list theme artifacts and the version each one serves |
-| `rshow login` | read a token from the terminal with no echo, check it and save it in the macOS Keychain. The person runs it, never the agent |
+| `rshow skills install [target ...]` | link or copy the three skills into `~/.claude/skills`, `~/.pi/agent/skills` or `~/.codex/skills` |
+| `rshow skills uninstall [target ...]` | remove the skill links and copies rshow made |
+| `rshow skills status [target ...]` | print `link`, `copy v<version>`, `missing` or `foreign` per target and skill |
+| `rshow login` | read a token from the terminal with no echo, check it and save it in the macOS Keychain, the Linux keyring or a 0600 file. The person runs it, never the agent |
 | `rshow logout` | remove the saved token |
 
 `--help` on its own prints the general usage, and `--help` after a command prints that command.
@@ -188,6 +192,23 @@ It names an unknown token, a colour value that is not `#hex`, `rgb()` or `var(--
 `theme preview` builds the preset on its base in a temporary folder and serves it on `127.0.0.1`, with the same offline theme lookup, local `_data` store and live reload as `rshow preview`, and prints the URL of `index.html`; the temporary folder goes when the server stops.
 `theme publish` runs the check first on a preset, then publishes the built folder, so `--no-check` skips both.
 
+## skills
+
+```bash
+rshow skills install [target ...] [--link|--copy] [--dry-run]
+rshow skills uninstall [target ...] [--dry-run]
+rshow skills status [target ...] [--json]
+```
+
+The three skills, `rshow`, `rshow-slides` and `rshow-implement`, teach an agent to publish; `rshow skills install` puts them where claude, pi and codex read them.
+A target is `claude` (`~/.claude/skills`), `pi` (`~/.pi/agent/skills`) or `codex` (`~/.codex/skills`), and with no target every one whose parent folder exists is used.
+The default is a symlink to the skills folder rshow reads from; `--copy` copies it and writes a `.rshow-skill` marker with the version, which a link does not need.
+The default copies in an npx cache, because npm may delete that folder under a live link.
+Each skill prints `ok`, `installed`, `updated` or `removed`, then a summary line.
+A folder, a file or a link that rshow did not make is left alone, with `skip <dst>: exists and is not from rshow` on stderr and exit 6 on the run.
+`rshow skills uninstall` removes only what rshow made: a link into a skills folder that holds rshow skills, or a copy with the marker.
+`rshow doctor` reports the skills on one `skills` line, which warns and never fails.
+
 ## handoff and compare
 
 ```bash
@@ -226,8 +247,10 @@ Later files win, and the environment beats both.
 
 `RSHOW_URL` overrides `url` and `RSHOW_ART` overrides `art`.
 `rshow init --url <admin-url> --art <viewer-url>` writes the global file with both, keeps its other fields, and prints the next step, `rshow login`.
-`rshow doctor [dir]` checks node, both config files, the token, the API, the art host and the theme, one line each, and exits 6 when a check failed. Run it on a config error and show its output to the person.
-The token comes from `RSHOW_TOKEN`, else from the macOS Keychain, where `rshow login` saves it. It is never read from a file or from a flag.
+`rshow doctor [dir]` checks node, both config files, the token, the API, the art host, the theme and the skills, one line each, and exits 6 when a check failed. Run it on a config error and show its output to the person.
+The token comes from `RSHOW_TOKEN`, else from the macOS Keychain, the Linux keyring or the 0600 credentials file, where `rshow login` put it. It is never read from a flag, and you never ask for one in chat: the person runs `rshow login`.
+On a cluster, rshow trusts the system certificate store and any PEM file in `RSHOW_EXTRA_CA_FILE`, and `RSHOW_SYSTEM_CA=0` keeps the store out; `https_proxy` is used by the binary, and by an npm install with `NODE_USE_ENV_PROXY=1`.
+`rshow login` needs no keychain on Linux: it uses the keyring, or writes `${XDG_CONFIG_HOME:-$HOME/.config}/rshow/credentials` with mode 600.
 `XDG_CONFIG_HOME` moves the global config file away from `~/.config`.
 
 ## Exit codes
@@ -238,5 +261,5 @@ The token comes from `RSHOW_TOKEN`, else from the macOS Keychain, where `rshow l
 | 2 | usage, which covers a bad flag, a bad slug, a missing `index.html` and a missing token |
 | 4 | auth, which covers an expired token, a revoked token and a token without the scope the command needs |
 | 5 | api or a failed build, which covers a taken slug, a refused request and a build command that exited non-zero |
-| 6 | `rshow check` found an error in the page |
+| 6 | `rshow check` found an error in the page, or a skill folder in the way is not from rshow |
 | 7 | `rshow compare` found a screen that drifted from the handoff |