@taloswork/ose-shared 0.1.15 → 0.1.17

package/skills/expert-create/bin/expert-create.cjs

@@ -0,0 +1,96 @@
+#!/usr/bin/env node
+// expert-create — thin client for the Talos app's local expert service.
+// All validation and every file write happen in the app; this only forwards.
+//
+//   expert-create list
+//   expert-create show <id>
+//   expert-create create <draft.json>   (Talos asks the user to confirm)
+//   expert-create update <id> <patch.json>   (Talos asks the user to confirm)
+//   expert-create delete <id>          (Talos asks the user to confirm)
+"use strict";
+const { readFileSync } = require("node:fs");
+const http = require("node:http");
+
+function die(message, code) { process.stderr.write(`expert-create: ${message}\n`); process.exit(code); }
+const USAGE = "usage: expert-create list | show <id> | create <draft.json> | update <id> <patch.json> | delete <id>";
+
+function readJson(path) {
+  let raw;
+  try { raw = readFileSync(path, "utf8"); } catch (e) { die(`cannot read ${path}: ${e.message}`, 66); }
+  try { return JSON.parse(raw); } catch (e) { die(`${path} is not valid JSON: ${e.message}`, 65); }
+}
+
+function request(argv) {
+  const [action, a, b] = argv;
+  switch (action) {
+    case "list": return { action };
+    case "show": case "delete": if (!a) die(USAGE, 64); return { action, id: a };
+    case "create": if (!a) die(USAGE, 64); return { action, draft: readJson(a) };
+    case "update": if (!a || !b) die(USAGE, 64); return { action, id: a, patch: readJson(b) };
+    default: die(USAGE, 64);
+  }
+}
+
+// What a refused or unanswered confirmation left undone, per action.
+const UNDONE = {
+  create: ["creation", "created"],
+  update: ["edit", "changed"],
+  delete: ["deletion", "deleted"],
+};
+
+function errorCode(text) {
+  try { return JSON.parse(text).error; } catch { return undefined; }
+}
+function messageOf(text) {
+  try { const m = JSON.parse(text).message; return typeof m === "string" ? m : undefined; } catch { return undefined; }
+}
+
+// node:http, not global fetch: fetch (undici) drops a response whose headers
+// take over 300 s, and a create, update or delete waits on the user's
+// confirmation for up to 5 minutes. The app ends that wait itself (HTTP 408).
+function post(url, token, body) {
+  return new Promise((resolve, reject) => {
+    const payload = Buffer.from(JSON.stringify(body));
+    const req = http.request(`${url}/expert`, {
+      method: "POST",
+      headers: { authorization: `Bearer ${token}`, "content-type": "application/json", "content-length": payload.length },
+    }, (res) => {
+      const chunks = [];
+      res.on("data", (c) => chunks.push(c));
+      res.on("end", () => resolve({ status: res.statusCode ?? 0, text: Buffer.concat(chunks).toString("utf8") }));
+      res.on("error", reject);
+    });
+    req.on("error", reject);
+    req.end(payload);
+  });
+}
+
+async function main() {
+  const body = request(process.argv.slice(2));
+  const url = process.env.TALOS_EXPERT_URL;
+  const token = process.env.TALOS_EXPERT_TOKEN;
+  // Talos hands these only to a conversation with the user; a scheduled task,
+  // a sub-agent or a channel session never has them.
+  if (!url || !token) die("this needs the Talos app and a conversation with the user (TALOS_EXPERT_URL is not set). Scheduled tasks and sub-agents cannot change experts; do not write expert files yourself.", 69);
+  let res;
+  try {
+    res = await post(url, token, body);
+  } catch (e) { die(`cannot reach the Talos app: ${e.message}`, 69); }
+  const { status, text } = res;
+  const undone = UNDONE[body.action];
+  const error = errorCode(text);
+  if (undone && status === 409 && error === "cancelled_by_user") die(`the user cancelled the ${undone[0]}; nothing was ${undone[1]}`, 3);
+  if (undone && status === 408) die(`confirmation timed out; nothing was ${undone[1]}`, 4);
+  // The update would leave the expert as it is: the app wrote nothing and
+  // asked the user nothing.
+  if (status === 422 && error === "no_change") die(`${messageOf(text) ?? "the patch changes nothing"}; nothing was changed`, 5);
+  // Talos itself is not ready (no runtime yet, or the profile changed while
+  // the dialog was open). Not the request's fault, so not exit 1 ("fix the
+  // field and retry"): a retry would ask the user again about a runtime that
+  // is not the one they were shown.
+  if (status === 503 && error === "not_ready") die(`the Talos app is not ready (it is starting or switched profile); nothing was ${undone ? undone[1] : "done"}. Do not retry; tell the user.`, 69);
+  if (status < 200 || status >= 300) die(`HTTP ${status}${text ? `: ${text}` : ""}`, 1);
+  process.stdout.write(`${text}\n`);
+}
+
+main();

package/skills/expert-create/references/role-guide.md

@@ -0,0 +1,24 @@
+# Writing an expert's role
+
+The role is the first thing the model reads in every conversation with this
+expert, before Talos's own rules and tools. Keep it about the domain and the
+voice; Talos already explains its tools, files and safety rules — do not repeat
+or override them.
+
+Structure, in this order, as plain Markdown:
+
+1. **Who you are** — one or two sentences: the role, who it serves.
+2. **What you do** — the concrete jobs, as a short list.
+3. **How you work** — the method: what to check first, what to ask the user
+   before starting, the order of work, the quality bar.
+4. **What you deliver** — formats and shapes of the output (a PDF report, an
+   Excel model, a list of options with a recommendation).
+5. **Boundaries** — what this expert does not do, and when to say so.
+
+Rules:
+- Write instructions to the model ("Ask for the target market before…"), not a
+  description of a product.
+- Be specific to the domain; a generic "be helpful and accurate" adds nothing.
+- No tool names, file paths or claims about Talos features — they change and
+  the role would mislead.
+- Under ~600 words is usually enough; length is not quality.

package/skills/image-layout/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: image-layout
-description: "Use when EXISTING images (files already on disk) are combined or altered as pixels: 拼图 / 拼接 / 宫格 / 九宫格 / 长图 / 对比图 / 加水印 / 加标签 / 裁剪 / 圆角 / 缩放, stitch / combine / collage / contact sheet / side-by-side / before-after / watermark / label / crop / resize. The mechanical test: if the images do not exist as files yet, this is NOT the skill. Do NOT trigger for generating NEW images, INCLUDING when the request names a layout word ('生成一张九宫格的图' is one generated picture); documents (document skill); Xiaohongshu cards (talos-xhs-ops); or upscaling / background removal, which need a model."
+description: "Use when EXISTING images (files already on disk) are combined or altered as pixels: 拼图 / 拼接 / 宫格 / 九宫格 / 长图 / 对比图 / 加水印 / 加标签 / 裁剪 / 圆角 / 缩放, stitch / combine / collage / contact sheet / side-by-side / before-after / watermark / label / crop / resize. The mechanical test: if the images do not exist as files yet, this is NOT the skill. Do NOT trigger for generating NEW images, INCLUDING when the request names a layout word ('生成一张九宫格的图' is one generated picture); documents (document skill); social-post cards (social-cards); or upscaling / background removal, which need a model."
 license: Proprietary. LICENSE.txt has complete terms
 ---
 
@@ -146,7 +146,7 @@ tool.
   creates imagery, it only arranges what exists.
 - **A PDF / Word / PowerPoint deliverable** → the document skill (`doc-gen`,
   `html2pptx`). Do not build a "poster" here and call it a document.
-- **Xiaohongshu campaign cards** → `talos-xhs-ops` (`render-cards`), which owns
-  the 1080×1440 card format and its QA.
+- **Cards for a social post** → `social-cards` (`render`), which owns card
+  templates, every platform's card size and their QA.
 - **Pixel-level algorithms** — background removal, super-resolution,
   content-aware fill. CSS cannot do these; they need a model.