@tanagram/lore 0.1.217 → 0.1.219

package/README.md

@@ -14,6 +14,15 @@ npm install -g @loredotlink/cli
 lore
 ```
 
+On npm 11.16 or newer, npm may ask you to approve global install scripts
+before it considers them reviewed. If you see an `allow-scripts` warning, run
+the install with npm's global allowlist flag so the Lore postinstall migration
+and background-binary refresh are explicitly approved:
+
+```sh
+npm install -g --allow-scripts=@loredotlink/cli @loredotlink/cli
+```
+
 `lore` opens a dashboard in your terminal. Sign in there once and, on
 macOS, background uploads start immediately. On Linux, run `lore configure`
 to pick which directories upload.
@@ -220,7 +229,12 @@ Esc to return to the sidebar, and q to exit.
   non-interactive and pipe-friendly: if the target `SKILL.md` already exists but
   is managed by Lore (the same `sk_…`), it is overwritten with the remote body;
   if it exists and is *not* managed by Lore, the install errors instead of
-  clobbering it. Use `lore skills sync` for conflict-preserving updates.
+  clobbering it. For now, downloaded `claude_project` skills are installed to
+  `~/.claude/skills/<name>/SKILL.md` and downloaded `agents_project` skills are
+  installed to `~/.config/agents/skills/<name>/SKILL.md` instead of a
+  project-local directory; this is temporary until Lore can store project skills
+  without making the user pick a project during install. Use `lore skills sync`
+  for conflict-preserving updates.
 - `lore skills uninstall <skill-id>` — removes the managed local skill file and
   clears the installation record.
 - `lore skills publish <local-name-or-skill-id>` — publishes an authored skill