@tanagram/lore 0.1.62 → 0.1.64

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tanagram/lore",
-  "version": "0.1.62",
+  "version": "0.1.64",
   "description": "Lore CLI",
   "type": "module",
   "bin": {

package/skills/lore-read/SKILL.md

@@ -6,16 +6,16 @@ description: >-
   threads by filepath, author, or time range. Examples: "show me that Lore
   thread", "what did my coworker share on Lore last week", "find Lore
   threads that touched src/foo.ts", "list recent Lore sessions". Shells out
-  to the `tanagram lore get` and `tanagram lore list` CLI commands.
+  to the `lore threads get` and `lore threads list` CLI commands.
 allowed-tools: Bash
 ---
 
 # Read from Lore
 
-Fetches data from Lore via the `tanagram` CLI. Two underlying commands:
+Fetches data from Lore via the `lore` CLI. Two underlying commands:
 
-- `tanagram lore get <thread-id-or-url>` — fetch a single thread by ID or session URL.
-- `tanagram lore list [flags]` — list/search threads with optional filters.
+- `lore threads get <thread-id-or-url>` — fetch a single thread by ID or session URL.
+- `lore threads list [flags]` — list/search threads with optional filters.
 
 Both print a JSON payload on stdout. Parse the JSON and summarize for the user; only show raw JSON if they ask for it.
 
@@ -36,7 +36,7 @@ Do NOT run proactively. Only on explicit request.
 When the user gives a thread ID (`th_...`) or a Lore session URL (`https://lore.tanagram.ai/session/th_...`):
 
 ```bash
-tanagram lore get <thread-id-or-url>
+lore threads get <thread-id-or-url>
 ```
 
 The argument can be either form — the CLI extracts the thread ID from a URL automatically.
@@ -44,18 +44,18 @@ The argument can be either form — the CLI extracts the thread ID from a URL au
 ## Listing / Searching Threads
 
 ```bash
-tanagram lore list [--before <cursor>] [--after <cursor>] \
-                   [--author-ids <id1,id2,...>] \
-                   [--created-at <unix> | <start>...<end>] \
-                   [--filepath-prefixes <prefix1,prefix2,...>]
+lore threads list [--before <cursor>] [--after <cursor>] \
+                  [--author_ids <id1,id2,...>] \
+                  [--created_at <unix> | <start>...<end>] \
+                  [--filepath_prefixes <prefix1,prefix2,...>]
 ```
 
 Flag reference:
 
-- `--filepath-prefixes` — comma-separated filepath prefixes. Matches threads whose sessions touched files under any of those prefixes. Use this for "threads about <some path>".
-- `--author-ids` — comma-separated **Lore user IDs** (not names or emails). If the user names a coworker, you need their Lore user ID; if you don't have it, ask the user or fetch a recent unfiltered list and look for their ID in the results before filtering.
-- `--created-at` — either a single Unix timestamp (seconds) or a `<start>...<end>` range of Unix timestamps. Convert any human time range ("last week", "since Monday") into Unix seconds before passing. Today is provided in the system context.
-- `--before` / `--after` — pagination cursors returned in a previous list response. Use these to page through large result sets, not for time filtering (that's `--created-at`).
+- `--filepath_prefixes` — comma-separated filepath prefixes. Matches threads whose sessions touched files under any of those prefixes. Use this for "threads about <some path>".
+- `--author_ids` — comma-separated **Lore user IDs** (not names or emails). If the user names a coworker, you need their Lore user ID; if you don't have it, ask the user or fetch a recent unfiltered list and look for their ID in the results before filtering.
+- `--created_at` — either a single Unix timestamp (seconds) or a `<start>...<end>` range of Unix timestamps. Convert any human time range ("last week", "since Monday") into Unix seconds before passing. Today is provided in the system context.
+- `--before` / `--after` — pagination cursors returned in a previous list response. Use these to page through large result sets, not for time filtering (that's `--created_at`).
 
 Combine flags freely — they AND together server-side.
 
@@ -70,9 +70,9 @@ Both commands emit a single JSON object/array on stdout. After running:
 
 ## Failure Modes
 
-- **Not logged in**: command returns `not logged in - run 'tanagram login' first`. Tell the user to run `tanagram login`.
-- **Bad thread ref**: `tanagram lore get` requires either a `th_...` ID or a Lore session URL. If the user passes something else, ask them to clarify or provide the URL.
-- **Unknown author**: `--author-ids` only accepts Lore user IDs. If the user gives a name/email and you don't have a mapping, run `tanagram lore list` without the author filter (optionally narrowed by `--created-at` or `--filepath-prefixes`) and find the ID from the results, or ask the user.
+- **Not logged in**: command returns `not logged in — run 'lore login' first`. Tell the user to run `lore login`.
+- **Bad thread ref**: `lore threads get` requires either a `th_...` ID or a Lore session URL. If the user passes something else, ask them to clarify or provide the URL.
+- **Unknown author**: `--author_ids` only accepts Lore user IDs. If the user gives a name/email and you don't have a mapping, run `lore threads list` without the author filter (optionally narrowed by `--created_at` or `--filepath_prefixes`) and find the ID from the results, or ask the user.
 - **Empty results**: not an error — tell the user no threads matched and suggest loosening filters.
 
 ## What This Does NOT Do