threadnote 1.1.2 → 1.1.4

package/docs/agent-instructions.md

@@ -119,11 +119,12 @@ compact_context({"project":"my-repo","topic":"active-bug","dryRun":true})
 
 Never compact secrets, credentials, customer data, raw production logs, or checked-in canonical docs into memory.
 
-## Sharing memories with teammates
+## Sharing context with teammates
 
-Threadnote can publish a curated subset of durable memories into a team git repo so other engineers' agents can pull them.
-The mechanism lives under the `viking://user/<you>/memories/shared/<team>/...` subtree; only memories that are explicitly
-published leave the machine. Personal handoffs, preferences, and unpublished durable notes always stay local.
+Threadnote can publish a curated subset of durable memories and agent artifacts (Codex/Claude skills and Claude
+commands) into a team git repo so other engineers' agents can pull them. The mechanism lives under the
+`viking://user/<you>/memories/shared/<team>/...` subtree; only content that is explicitly published leaves the machine.
+Personal handoffs, preferences, and unpublished durable notes always stay local.
 
 Publish a durable memory when its content is useful to other engineers working on the same project (intended behavior,
 design decisions, API contracts, gotchas) and is safe to share. Do NOT publish:
@@ -136,6 +137,16 @@ The MCP tool `share_publish` runs the same scrubber as the CLI and refuses to pu
 patterns (PEM private keys, `sk-...`, `gh[pousr]_...`, `Bearer ...`, `AKIA...`, `xox[abprs]-...`). It writes and pushes
 the shared copy first, then removes the personal copy after the push succeeds.
 
+The MCP tool `share_skill` shares a local Codex/Claude `SKILL.md` file or Claude command markdown file into the team's
+`agent-artifacts/` catalog after the same scrubber checks. Shared artifacts are recallable after sync, but local
+installation remains opt-in with `threadnote share install-artifacts --apply`.
+
+When the user asks whether shared skills exist, call `list_shared_skills`. When the user asks to install one, call
+`install_shared_skill` with the selected `name`; include `agent` and `kind` from the list result when available.
+`list_shared_skills` syncs shared repos before listing and reports `not_installed`, `current`, `update_available`,
+`local_modified`, or `remote_changed_and_local_modified`. Install/update selected shared skills only when the user asks;
+use `force:true` only when the user explicitly accepts overwriting local modifications.
+
 Incoming shared memories are normally fetched and synced automatically before MCP `recall_context` / `read_context` and
 CLI `threadnote recall` / `threadnote read` return. If automatic sync reports a dirty worktree, a conflict, or another
 git issue, run `threadnote share sync` after resolving the local state to pull, reindex, and push explicitly.
@@ -144,9 +155,13 @@ git issue, run `threadnote share sync` after resolving the local state to pull,
 # MCP call shape
 share_publish({"uri":"viking://user/you/memories/durable/projects/foo/bar.md"})
 share_publish({"uri":"viking://user/you/memories/durable/projects/foo/bar.md","team":"friends","push":false})
+share_skill({"path":"~/.codex/skills/reviewer/SKILL.md"})
+list_shared_skills({})
+install_shared_skill({"name":"reviewer","agent":"codex","kind":"skill"})
 ```
 
-Before publishing, confirm with the user unless they have already instructed you to share durable memories autonomously.
+Before publishing, confirm with the user unless they have already instructed you to share durable memories or agent
+artifacts autonomously.
 
 ## Handoff
 
@@ -184,5 +199,7 @@ threadnote forget viking://user/example/memories/events/duplicate.md
 threadnote handoff --project example --topic active-issue --task "short task summary" --tests "checks run" --next-step "what to do next"
 threadnote share init git@github.com:org/team-memories.git
 threadnote share publish viking://user/example/memories/durable/projects/foo/bar.md
+threadnote share publish-artifact ~/.codex/skills/example/SKILL.md
+threadnote share install-artifacts --name example --agent codex --kind skill --apply
 threadnote share sync
 ```

package/docs/index.html

@@ -783,7 +783,7 @@
             team-shared decisions — recallable from any session, on any agent, in any worktree.
           </p>
           <div class="cta-row">
-            <span class="pill"><span id="version-tag">v0.6.1</span> · local-first · GPL-3.0-or-later</span>
+            <span class="pill"><span id="version-tag">v0.6.1</span> · local-first · AGPL-3.0-or-later</span>
           </div>
         </div>
         <div class="scroll-cue">scroll ↓ &nbsp;·&nbsp; <span class="kbd">↓</span> / <span class="kbd">j</span></div>
@@ -1585,7 +1585,7 @@ threadnote doctor --dry-run</code></pre>
           </div>
 
           <p class="colophon">
-            threadnote · GPL-3.0-or-later · built on OpenViking 0.3.24 · use <span class="kbd">↑</span>
+            threadnote · AGPL-3.0-or-later · built on OpenViking 0.3.24 · use <span class="kbd">↑</span>
             <span class="kbd">↓</span> / <span class="kbd">j</span> <span class="kbd">k</span> to navigate
           </p>
         </div>

package/docs/share.md

@@ -1,9 +1,9 @@
-# Sharing memories with teammates
+# Sharing context with teammates
 
-`threadnote share` lets a small team keep a curated set of durable memories in a
-git repository so every member's local agent can recall them. Personal handoffs,
-preferences, and unpublished durable notes stay local; only memories you
-explicitly publish leave your machine.
+`threadnote share` lets a small team keep curated durable memories and agent
+artifacts in a git repository so every member's local agent can recall them.
+Personal handoffs, preferences, and unpublished durable notes stay local; only
+content you explicitly publish leaves your machine.
 
 ## Model in one screen
 
@@ -34,7 +34,7 @@ threadnote share init --team friends git@github.com:you/friends-memories.git
 ```
 
 `share init` clones the remote into your local memory tree and ingests any
-existing markdown memories into OpenViking.
+existing shareable markdown into OpenViking.
 
 ### See what's configured
 
@@ -86,6 +86,95 @@ Threadnote rewrites the shared memory in place, strips local-only provenance
 headers, commits, and pushes the shared repo. You do not need to store a
 personal replacement and run `share publish` again.
 
+### Share a skill or command
+
+Shared agent artifacts live in the same team repo, but outside `durable/`:
+
+```text
+agent-artifacts/
+  skills/codex/<name>/SKILL.md
+  skills/claude/<name>/SKILL.md
+  commands/claude/<name>.md
+```
+
+Publish a local artifact:
+
+```bash
+threadnote share publish-artifact ~/.codex/skills/reviewer/SKILL.md
+threadnote share publish-artifact ~/.claude/skills/triage/SKILL.md
+threadnote share publish-artifact ~/.claude/commands/review-pr.md
+```
+
+Path inference handles the common Codex and Claude locations. If the file is
+somewhere else, pass metadata explicitly:
+
+```bash
+threadnote share publish-artifact ./SKILL.md --agent codex --kind skill --name reviewer
+```
+
+Useful flags:
+
+```bash
+threadnote share publish-artifact <path> --preview
+threadnote share publish-artifact <path> --redact
+threadnote share publish-artifact <path> --force
+threadnote share publish-artifact <path> --no-push
+```
+
+`publish-artifact` runs the same scrubber as memory publish, writes the artifact
+under `agent-artifacts/`, ingests it into OpenViking under the shared team
+namespace, commits, and pushes. Existing artifacts with different content are
+not overwritten unless `--force` is passed.
+
+Agents can do the same through MCP:
+
+```text
+share_skill({"path":"~/.codex/skills/reviewer/SKILL.md"})
+```
+
+Agents can also list and install shared artifacts through MCP:
+
+```text
+list_shared_skills({})
+install_shared_skill({"name":"reviewer","agent":"codex","kind":"skill"})
+```
+
+`list_shared_skills` syncs configured shared repos before listing and reports
+one of:
+
+- `not_installed`
+- `current`
+- `update_available`
+- `local_modified`
+- `remote_changed_and_local_modified`
+
+### Install shared artifacts locally
+
+Shared artifacts are recallable after sync, but they are not installed into
+agent-native locations automatically. Installation is opt-in:
+
+```bash
+threadnote share install-artifacts          # preview only
+threadnote share install-artifacts --apply  # write files locally
+threadnote share install-artifacts --name reviewer --agent codex --kind skill --apply
+```
+
+Install targets are namespaced by Threadnote team to avoid colliding with
+personal files:
+
+```text
+~/.codex/skills/threadnote/<team>/<name>/SKILL.md
+~/.claude/skills/threadnote/<team>/<name>/SKILL.md
+~/.claude/commands/threadnote/<team>/<name>.md
+```
+
+If a target already exists with different content, installation refuses to
+overwrite local modifications unless `--force` is passed. Remote updates are
+applied by running the same install command again; Threadnote tracks the last
+installed shared hash in a sidecar metadata file next to the installed
+artifact. Start a new agent session after installing if that agent snapshots
+skills or commands at startup.
+
 ### Keep teammates' updates current
 
 Threadnote does a periodic background `git fetch` for configured share teams.
@@ -176,10 +265,11 @@ updates the git `origin` URL and verifies it with `git fetch`.
   - linux home paths (`/home/<you>/...`) → `<local-path>`
 - The scrubber complements but does not replace human review. Strip the value,
   preview with `--preview`, and then publish.
-- Only the `durable/` kind is shareable. `handoffs/`, `preferences/`,
-  `incidents/`, and other lifecycle kinds stay local by construction — both
-  the initial ingest (`share init`) and the sync-pull reindex (`share sync`)
-  skip any file outside `durable/`.
+- Only `durable/` memories and `agent-artifacts/` markdown files are
+  shareable. `handoffs/`, `preferences/`, `incidents/`, and other lifecycle
+  kinds stay local by construction — both the initial ingest (`share init`) and
+  the sync-pull reindex (`share sync`) skip any file outside the shareable
+  top-level directories.
 - `share publish` deletes the personal copy after publishing. If you want to
   keep both, copy the memory to a new URI first (`ov read` then
   `threadnote remember`).

package/docs/troubleshooting.md

@@ -8,7 +8,9 @@ Run:
 threadnote install
 ```
 
-The installer prefers `uv`, then `pipx`, then `python3 -m pip install --user`.
+The installer prefers `uv`, then `pipx`, then `python3 -m pip install --user`. For `curl | sh` installs, the wrapper
+reattaches `threadnote install` to your terminal when possible so it can prompt to install `uv` and continue instead of
+falling straight through to the pip fallback.
 
 ## `uv` Fails With `UnknownIssuer`
 
@@ -83,8 +85,14 @@ For detached starts, logs are written to:
 ~/.openviking/logs/server.log
 ```
 
-If `start` reports that OpenViking did not become healthy, open that log. Certificate failures during the first embedding
-model download are covered above.
+If `start` reports that OpenViking did not become healthy, first check whether it finished shortly after the timeout:
+
+```bash
+threadnote doctor --dry-run
+```
+
+If it still is not healthy, open that log. Certificate failures during the first embedding model download are covered
+above.
 
 ## Port Already In Use
 

package/package.json

@@ -1,10 +1,10 @@
 {
   "name": "threadnote",
-  "version": "1.1.2",
+  "version": "1.1.4",
   "type": "commonjs",
   "main": "dist/threadnote.cjs",
   "description": "Shared local context and handoffs for development agents",
-  "license": "GPL-3.0-or-later",
+  "license": "AGPL-3.0-or-later",
   "homepage": "https://github.com/Kashkovsky/threadnote#readme",
   "bugs": {
     "url": "https://github.com/Kashkovsky/threadnote/issues"
@@ -35,6 +35,7 @@
     "dist/",
     "docs/",
     "LICENSE",
+    "THIRD_PARTY.md",
     "manager/",
     "README.md",
     "scripts/"
@@ -71,7 +72,7 @@
     "@types/react": "^19.2.16",
     "@types/react-dom": "^19.2.3",
     "@vitest/coverage-v8": "^4.1.7",
-    "commander": "^14.0.3",
+    "commander": "^15.0.0",
     "esbuild": "^0.27.7",
     "eslint": "^10.3.0",
     "globals": "^17.6.0",

package/scripts/install.sh

@@ -116,7 +116,11 @@ install_package "$runtime"
 threadnote_bin="$(find_threadnote "$runtime")" || die "Installed $PACKAGE, but could not find the threadnote command."
 
 say "Running threadnote install"
-"$threadnote_bin" install "$@"
+if { true </dev/tty; } 2>/dev/null; then
+  "$threadnote_bin" install "$@" </dev/tty
+else
+  "$threadnote_bin" install "$@"
+fi
 
 if ! have threadnote; then
   say ""