@tanagram/lore 0.1.88 → 0.1.89

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tanagram/lore",
-  "version": "0.1.88",
+  "version": "0.1.89",
   "description": "Lore CLI",
   "type": "module",
   "bin": {
@@ -28,8 +28,8 @@
     "ink-testing-library": "^4.0.0",
     "tsx": "^4.20.6",
     "typescript": "^5.9.3",
-    "@lore/transcripts": "0.1.0",
-    "@lore/contracts": "0.1.0"
+    "@lore/contracts": "0.1.0",
+    "@lore/transcripts": "0.1.0"
   },
   "dependencies": {
     "@sentry/node": "^10.47.0",

package/skills/lore-read/SKILL.md

@@ -12,10 +12,11 @@ allowed-tools: Bash
 
 # Read from Lore
 
-Fetches data from Lore via the `lore` CLI. Two underlying commands:
+Fetches data from Lore via the `lore` CLI. Three underlying commands:
 
 - `lore threads get <thread-id-or-url>` — fetch a single thread by ID or Lore URL.
-- `lore threads list [flags]` — list/search threads with optional filters.
+- `lore threads list [flags]` — list/search threads with optional deterministic filters.
+- `lore threads ask --question=<question>` — search threads by semantic meaning; use when the user asks an open-ended question.
 
 Both print a JSON payload on stdout. Parse the JSON and summarize for the user; only show raw JSON if they ask for it.
 
@@ -59,9 +60,21 @@ Flag reference:
 
 Combine flags freely — they AND together server-side.
 
+## Searching Threads Semantically:
+
+```bash
+lore threads ask --question=<question>
+```
+
+Use this when asks about threads in a broad way that can't be entirely captured by the flags listed above. For example:
+
+- "what have we been thinking about our open-source strategy?"
+- "what did we say about running multiple fastify replicas in railway?"
+- "what are some recent decisions we've made about our Posthog setup?"
+
 ## Output
 
-Both commands emit a single JSON object/array on stdout. After running:
+All commands emit a single JSON object/array on stdout. After running:
 
 1. Parse the JSON.
 2. Summarize the relevant fields for the user (thread ID, title/topic, author, created time, URL, matching filepaths, etc.) instead of dumping raw JSON.

package/skills/share/SKILL.md

@@ -20,6 +20,8 @@ Run when the user asks to:
 
 Do NOT run this proactively. Only on explicit request.
 
+- "share to #channel" (share to Lore AND post to a Slack channel)
+
 ## Command
 
 **Always** pass `--session-id ${CLAUDE_SESSION_ID}` so the CLI exports _this_ session — the one the user just asked to share. Claude Code substitutes `${CLAUDE_SESSION_ID}` with the current session's ID; the CLI will not guess it for you.
@@ -68,6 +70,44 @@ The first command prints a single JSON object on stdout:
 - `highlight` — present only when `--highlight` was supplied. When `matched` is true, the `url` already includes the server-selected block anchor or range.
 - `clipboard_copied` — `true` when the URL was copied to the system clipboard (via `pbcopy` on macOS, `wl-copy`/`xclip`/`xsel` on Linux, `clip.exe` on Windows). `false` when no clipboard tool was available. Mention this to the user when `true` so they know they can paste it directly.
 
+## Slack Integration
+
+If the user says "share to #channel", "post to #eng", or includes a Slack channel name (with or without the `#` prefix), do the following **after** the Lore export succeeds:
+
+1. Extract the `thread_id` from the export output.
+2. Strip the leading `#` from the channel name if present.
+3. Read the auth token from `~/.lore/token` (prod) or `~/.lore-dev/token` (dev). If neither exists, tell the user to run `lore login` first.
+4. Determine the API base URL: use `LORE_API_URL` env var if set, otherwise `https://api.lore.tanagram.ai` for prod or `http://localhost:4000` for dev (check which token file exists).
+5. Post to Slack via the API directly:
+
+```bash
+TOKEN=$(cat ~/.lore/token 2>/dev/null || cat ~/.lore-dev/token 2>/dev/null)
+API_BASE="${LORE_API_URL:-https://api.lore.tanagram.ai}"
+curl -s -X POST "$API_BASE/api/slack/post" \
+  -H "Authorization: Bearer $TOKEN" \
+  -H "Content-Type: application/json" \
+  -d "{\"channel_name\": \"CHANNEL\", \"thread_id\": \"THREAD_ID\"}"
+```
+
+Replace `CHANNEL` with the channel name (no `#` prefix) and `THREAD_ID` with the `thread_id` from the export output.
+
+If `lore slack post` is available (check with `lore slack --help 2>/dev/null`), you may use that instead:
+
+```bash
+lore slack post CHANNEL --thread-id THREAD_ID
+```
+
+6. If the response contains `"ok":true`, confirm to the user that the thread was posted to the channel.
+7. If it fails with "No Slack installation", tell the user to connect Slack from Account Settings first.
+8. If it fails with a channel error, tell the user the bot may not be in that channel and suggest `/invite @Lore` in Slack.
+
+When Slack posting is requested, the response should look like:
+
+> Shared: https://lore.tanagram.ai/session/th_abc123 (copied to clipboard).
+> Posted to #eng in Slack.
+
+If the user just says "share" without mentioning a channel, skip the Slack step entirely.
+
 ## After Running
 
 Echo the session URL back to the user as a clickable link. If `clipboard_copied` is `true`, add a short note that the URL is on their clipboard. Do not list other threads, summarize the conversation, or take any additional action unless the user asks. A minimal response looks like: