@tanagram/lore 0.1.57 → 0.1.58

package/package.json

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

package/skills/fork/SKILL.md

@@ -0,0 +1,84 @@
+---
+name: fork
+description: >-
+  Distills a Lore thread into handoff context for continuing work. Use when the
+  user asks to "continue work from thread", "fork from thread", "pick up from
+  this Lore thread", or invokes /fork with a Lore thread URL/ID and forker
+  intent.
+argument-hint: "<lore-thread-url-or-id> <forker-intent>"
+allowed-tools: Bash
+---
+
+# Fork a Lore Thread
+
+Fetches an intent-conditioned handoff summary for a Lore thread and returns the
+`source_distilled` payload to the agent so it can continue from that context.
+
+## When to Use
+
+Run when the user asks to:
+
+- "continue work from thread <thread-url-or-id>"
+- "fork from thread <thread-url-or-id>"
+- "pick up from this Lore thread"
+- "use this thread as context for <intent>"
+- invoke `/fork <thread-url-or-id> <forker-intent>`
+
+Do not use this for merely reading or listing Lore threads. Use the `lore-read`
+skill for read-only thread inspection.
+
+## Inputs
+
+This skill needs two inputs:
+
+1. A Lore thread URL or ID. Accepted examples include `th_...`,
+   `https://lore.tanagram.ai/session/th_...`, and
+   `https://lore.tanagram.ai/thread/th_...`.
+2. Forker intent: what the user wants to do with the source thread.
+
+If either input is missing, ask one concise clarification question before
+running the command.
+
+## Command
+
+Run `lore threads fork` with the thread reference and intent. The command emits
+JSON; extract and return only `source_distilled`.
+
+```bash
+THREAD_REF='<lore-thread-url-or-id>'
+FORKER_INTENT='<what the user wants to do next>'
+
+lore threads fork "$THREAD_REF" --forker-intent "$FORKER_INTENT" \
+  | node -e 'let input = "";
+process.stdin.on("data", (chunk) => { input += chunk; });
+process.stdin.on("end", () => {
+  const parsed = JSON.parse(input);
+  if (typeof parsed.source_distilled !== "string" || parsed.source_distilled.length === 0) {
+    console.error("lore threads fork did not return source_distilled");
+    process.exit(1);
+  }
+  process.stdout.write(parsed.source_distilled);
+});'
+```
+
+Use shell-safe quoting for both values. Do not pass the full thread transcript to
+the model yourself; the CLI/API performs the intent-conditioned distillation.
+
+## After Running
+
+Treat the printed `source_distilled` text as the source-thread context for the
+current task. Use it to continue the requested work. Do not show raw JSON to the
+user unless they explicitly ask for it.
+
+If the user only asked to prepare the fork context, return the distilled text
+verbatim. If they asked to continue the work, briefly acknowledge that the fork
+context was loaded and proceed with the task using that context.
+
+## Failure Modes
+
+- **Not logged in**: the command returns a login error. Tell the user to run
+  `lore login` and retry.
+- **Thread not found or not visible**: tell the user the thread could not be
+  found or they do not have access, and ask for a visible Lore thread URL/ID.
+- **Missing `source_distilled`**: surface the error and do not invent fork
+  context.