@jive-sh/skill-sync 0.4.9 → 0.4.10-latest-darwin-arm64

package/multi-call-binary

@@ -0,0 +1,4 @@
+[diffend] Oversized file quarantined before diffing.
+name: package/multi-call-binary
+size: 91273442 bytes
+sha256: 7792981b4abcd585269c21ce10d621229bb99b555ee18511787e870982779872

package/package.json

@@ -1,48 +1,20 @@
 {
   "name": "@jive-sh/skill-sync",
-  "version": "0.4.9",
-  "license": "MIT",
+  "version": "0.4.10-latest-darwin-arm64",
   "type": "module",
+  "license": "MIT",
+  "os": [
+    "darwin"
+  ],
+  "cpu": [
+    "arm64"
+  ],
+  "files": [
+    "multi-call-binary"
+  ],
   "description": "Keeps one skills directory identical across every machine you work on.",
   "repository": {
     "type": "git",
     "url": "git+https://github.com/jive-sh/skill-sync.git"
-  },
-  "main": "./dist/index.js",
-  "module": "./dist/index.js",
-  "types": "./src/index.ts",
-  "exports": {
-    ".": {
-      "types": "./src/index.ts",
-      "import": "./dist/index.js"
-    }
-  },
-  "files": [
-    "README.md",
-    "dist",
-    "src",
-    "bin",
-    "install.cjs"
-  ],
-  "scripts": {
-    "postinstall": "node ./install.cjs"
-  },
-  "bin": {
-    "skill-sync": "./bin/skill-sync",
-    "skill-sync-daemon": "./bin/skill-sync-daemon"
-  },
-  "optionalDependencies": {
-    "@jive-sh/skill-sync-darwin-arm64": "npm:@jive-sh/skill-sync@0.4.9-latest-darwin-arm64",
-    "@jive-sh/skill-sync-darwin-x64": "npm:@jive-sh/skill-sync@0.4.9-latest-darwin-x64",
-    "@jive-sh/skill-sync-linux-arm64": "npm:@jive-sh/skill-sync@0.4.9-latest-linux-arm64",
-    "@jive-sh/skill-sync-linux-x64": "npm:@jive-sh/skill-sync@0.4.9-latest-linux-x64",
-    "@jive-sh/skill-sync-windows-x64": "npm:@jive-sh/skill-sync@0.4.9-latest-windows-x64"
-  },
-  "dependencies": {
-    "commander": "^13.1.0"
-  },
-  "peerDependencies": {
-    "effect": "^4.0.0",
-    "typescript": "^5.9.3"
   }
 }

package/README.md

@@ -1,93 +0,0 @@
-# @jive-sh/skill-sync
-
-Keeps the skills you choose identical across every Claude and Codex skills folder on every machine you
-work on.
-
-A daemon finds each agent home on the machine (Claude's `~/.claude` and every `~/.claude-<name>`, and
-Codex's `~/.agents`, counted as soon as either `~/.agents` or `~/.codex` exists; anything named `*.lock` is
-another program's lock and is ignored, as a home and as a file or folder inside a skills folder) and syncs the `skills`
-folder in each through a Cloudflare Worker: file index in D1, contents in R2 addressed by hash. `skill-sync login` asks the daemon to sign in and opens
-`skill-sync.jive.sh` in your browser, where you verify with your jive.sh passkey (from any passkey
-manager, such as Google Password Manager). The service hands a per-machine token straight to the daemon,
-never through the CLI. The daemon keeps it in `~/.jive/skill-sync-token.json` and starts syncing, and it
-stays signed in through restarts, reboots and upgrades until you run `skill-sync logout` or revoke the
-token.
-
-```
-skill-sync login     sign this machine in with your passkey; the daemon starts syncing
-skill-sync logout    revoke this machine's token and stop syncing
-skill-sync list      list the skills that sync, as the server holds them (needs a sign-in)
-skill-sync upgrade   upgrade with the package manager that installed it
-skill-sync version   print the installed version
-```
-
-Everything else — which folders and skills sync, renaming computers — is on the
-dashboard.
-
-The daemon registers itself to start at login when the package is installed. It also keeps skill-sync up
-to date: every 5 minutes it asks the package manager that installed it (bun, pnpm, yarn or npm, with that
-manager's own registry settings) whether a newer version is published, installs it the same way, and
-restarts on it, still signed in. `skill-sync upgrade` does the same at once.
-
-## The dashboard
-
-`https://skill-sync.jive.sh/` shows, live, the latest version published on npm, and:
-
-- **Synced skills**: the list, with the shared version of each skill and where it was last edited.
-- **Computers**: each machine (renameable), whether its daemon is running and which version it runs, its
-  skills folders, and the skills in each with their files. A daemon older than the published version is
-  marked "update pending"; it upgrades itself within 5 minutes.
-- **Accounts**, under each running computer: one line per Claude and Codex account on it, with how much of
-  each limit is used, when it resets, and when that reading was taken. See [Account usage](#account-usage).
-
-Every file shows the first 8 characters of its SHA-256, amber when a folder's copy differs from the synced
-one. The page reloads itself when a new version of the service is deployed.
-
-The server holds one list of skills to sync. Every enabled folder on every machine pushes and pulls
-exactly the skills on that list, and never touches any other skill. A skill's checkbox adds it to the
-list or removes it, for every machine at once. A folder's checkbox turns syncing on or off for that
-folder; a folder seen for the first time starts off, so nothing is written into a folder until you tick it. Both are stored on the server, so they apply at once
-and survive a reinstall.
-
-A folder that lacks a listed skill gets a copy. Deleting a listed skill in any folder deletes it in every
-folder and takes it off the list; unticking it instead stops syncing and leaves every copy where it is.
-
-## The latest edit wins
-
-Every file carries the time it was last edited: on a machine, its modification time; on the server, the
-edit time of the version it holds. Whenever two copies of a file differ, the one edited later replaces
-the other, on the server and in every folder. Nothing is merged and nothing is set aside. A deletion
-counts as an edit made when the daemon noticed it.
-
-Edit times come from each machine's clock, so a machine whose clock is far off can win or lose against
-edits it should not.
-
-## Account usage
-
-Every minute the daemon reads how much of its limits each account on the machine has used, and sends the
-numbers to the dashboard when they change. An account is a folder in your home directory: `~/.claude` and each
-`~/.claude-<name>` for Claude (each a `CLAUDE_CONFIG_DIR`), `~/.codex` and each `~/.codex-<name>` for Codex
-(each a `CODEX_HOME`).
-
-The numbers come only from files each tool writes for itself. No credential is read, nothing is fetched, and
-only the numbers leave the machine:
-
-- **Claude**: the plan usage Claude Code last fetched, which it keeps in the account's `.claude.json` (for
-  `~/.claude`, in `~/.claude.json`) and refreshes about every five minutes while a session runs. The 5-hour and
-  weekly limits, and usage credits spent when they are on.
-- **Codex**: the rate limits Codex recorded with its latest turn, in the account's session files under
-  `sessions/`. Its 5-hour and weekly limits.
-
-So a reading is as fresh as the tool's last use of that account, and the dashboard shows its age on every
-line. A limit whose reset time has passed since the reading shows no number, since the new window's use is not
-known yet. Neither file is a documented format: when a tool changes its format, the line says "usage unknown"
-and why, rather than showing a wrong number. Daemons before 0.4.9 send no usage, and their machines show no
-accounts.
-
-## Configuration
-
-`~/.jive/skill-sync.json` holds the endpoint and the machine name, written on first run.
-`~/.jive/skill-sync-token.json` holds this machine's token while it is signed in. It is an ordinary file,
-so anything that can read your home directory can copy the token; signing out, or the server rejecting the
-token, deletes it. The CLI reaches the daemon over `~/.jive/skill-sync.sock` (a named pipe on Windows),
-which only your user can open.

package/bin/package.json

@@ -1 +0,0 @@
-{"type":"commonjs"}