@taloswork/ose-shared 0.1.3 → 0.1.5

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@taloswork/ose-shared",
-  "version": "0.1.3",
+  "version": "0.1.5",
   "description": "Talos cross-OSE shared library — skills + MCP servers auto-loaded into every OSE (P93 2026-07-27).",
   "type": "module",
   "files": [
@@ -10,6 +10,6 @@
   "publishConfig": {
     "access": "public"
   },
-  "_talosPublishHash": "sha256-RfTV3yagoQYs34T0xBwaQJ1l6PXSqIzzesBbFROxxaA",
-  "_talosPublishedAt": "2026-09-03T06:44:08.968Z"
+  "_talosPublishHash": "sha256-KOvhlr3qgAcQLbNL6vcsxL_bzNJOy5irYClssKyPFS8",
+  "_talosPublishedAt": "2026-09-05T10:13:14.516Z"
 }

package/skills/document/SKILL.md

@@ -40,53 +40,60 @@ script only when:
   document files via these scripts — never hand-write a python / ReportLab /
   LibreOffice script for document output.
   **Any deck/presentation(路演/汇报/评审/宣讲/pitch/roadshow/介绍 PPT)**:
-  **CLARIFY FIRST — HARD GATE (applies to EVERY deck).** Before authoring
-  anything, UNLESS the user already gave them or said "你决定/you decide", you
-  MUST ask — in **ONE AskUserQuestion call with these FOUR questions** — and wait
-  for answers (the tool allows up to 4 questions per call — use all four; do NOT
-  split into a second call and do NOT drop the style question):
-  **(1) content source** (提供材料 / 联网调研 / 自由创作); **(2) scenario** (pitch /
-  内审 / 销售 / 讲座 / 发布会 / 培训 / 大会 — sets tone, density, required sections);
-  **(3) style — pick ONE 风格。两级选择，名单一律读 `catalog.json`，本文件不列族名。**
-  第一级（放在这次四问里）：展示 `catalog.json` 的 **`groups`** 作为 image-card 选项，
-  `{ label: group.name_cn, description: <该 group 的 scenarios 前两项，用 " · " 连接>,
-  imagePath: <skill 目录下 group.sample 的绝对路径> }`。大类顺序按 Q2 的场景答案匹配
-  `group.scenarios`，最贴合的排前面。**外加一张卡放在最后**：
-  `{ label: "使用我的模板文件", description: "复用现成 PPT 的版式/风格", filePick: "file" }`
-  （无 imagePath，渲染成文件夹卡）。选中它 → 走 `pptx-tokenize`/`pptx-theme` 复用路径
-  （rewrite.md B2），不进下面的第二级。
-
-  第二级（四问返回后**单独发一次单问题调用**）：把所选 group 下的 `entries` 展示为
-  image-card，`{ label: entry.name_cn, description: entry.oneliner（**逐字照抄，不得改写、
-  不得加"风"/"首选"之类的尾巴**）, imagePath: <entry.sample 的绝对路径> }`。
-  **该 group 只有一个 entry 时跳过第二级，直接用它。** 用户在别处已经点名族 id 的，
-  两级全跳过。
-
-  样图都是**预渲染**的 WebP，随 skill 一起分发 —— 直接把路径传过去，**不要在提问时渲染任何东西**。
-
-  选中的 `entry.id` 即 `--style` 的取值：`html2pptx deck.html out.pptx --style <id>`。
-  entry 是 skin 还是 pack 由 `catalog.json` 决定，渲染命令**完全相同**，不需要分情况处理。
-  **(4) slide count.**
-  **Keep the call LEAN — it streams in full before the panel becomes interactive,
-  so every extra token is dead wait.** Questions (1)(2)(4) pass options as **bare
-  label strings** (e.g. `["提供材料","联网调研","自由创作"]`) — NO per-option
-  `description`/`detail` objects; each question stem is ONE short sentence. The ONLY
-  descriptions in the whole call are Q3's group descriptions (第二级的族 one-liner 在
-  单独那次调用里，不算进这次的四问). Skip any chat
-  preamble before the tool (or keep it to a single short line) — the questions speak
-  for themselves.
-  Every question carries an implicit "其他/自定义" free-text escape (the panel adds
-  it). If they respond with a question/correction instead of a pick, answer it,
-  then re-ask. Do NOT drop the style question or waive the gate by judging the deck
-  "small/quick" — only an explicit user spec or "你决定" skips it.
-
-  **Pick the skin** (in this order): a remembered deck-skin preference → user named
-  a style → 按 Q2 的场景去匹配 `catalog.json` 里 group/entry 的 `scenarios`（要 clean/
-  formal/light 的就再按 `entry.mode === "light"` 收窄）→ 仍并列时取最贴合那个 group 的
-  第一个 entry。**本文件不写死任何族 id** —— 名单只有 `catalog.json` 一份，写在这里的
-  默认族会在下一次增删族时静默过期，而没有任何闸门抓得住。`styles/README.md` 是同一份
-  名单的人读版，用来理解各族的气质，不作为选择依据。Never unstyled. After the user
-  confirms, save the preference to memory.
+  **CLARIFY FIRST — HARD GATE (applies to EVERY deck).** Before authoring, collect
+  three brief fields: **(1) content source** (提供材料 / 联网调研 / 自由创作);
+  **(2) scenario** (pitch / 内审 / 销售 / 讲座 / 发布会 / 培训 / 大会 — sets tone,
+  density, required sections); **(3) slide count.** Ask only for fields the user did
+  not already supply, in **ONE AskUserQuestion call with at most THREE questions**, and
+  wait for the answers. If all three are already known, do not ask them again.
+
+  **STYLE PICKER — ONE RESULT PER IMAGE, SCENARIO-RANKED.** After the scenario is
+  known, read the skill directory's **current `catalog.json` from disk immediately
+  before building the picker**. Never reuse a catalog listing from earlier conversation
+  context and never infer pack availability by scanning `packs/`. If the current catalog
+  cannot be read or parsed, stop and report that exact error instead of presenting stale
+  options.
+
+  Unless the user already named an entry id/name, supplied a template file, or explicitly
+  said **"无需展示模板，直接替我选定风格"**, send one single-question image-card picker:
+
+  - Rank **entries**, not groups, against the confirmed scenario and the user's requested
+    tone. Show at most 8 recommended entries. A scenario-matching `kind === "pack"` ranks
+    before matching skins; include at least one matching pack whenever one exists.
+  - Every image card maps to exactly one final entry and uses
+    `{ label: entry.kind === "pack" ? "PACK · " + entry.name_cn : entry.name_cn,
+    description: entry.oneliner, imagePath: <skill目录下entry.sample的绝对路径> }`.
+    Copy `entry.oneliner` verbatim. Never use `group.sample` in this default picker.
+  - Append `{ label: "查看全部风格", description: "一次查看全部模板" }`, then
+    `{ label: "使用我的模板文件", description: "复用现成 PPT 的版式/风格",
+    filePick: "file" }` as the final option.
+
+  **"按场景推荐/你推荐" means rank the cards and still ask.** It does NOT waive the
+  picker. Only the explicit no-picker wording above authorizes automatic selection.
+  Do not waive this gate because the deck is small or quick.
+
+  If the user chooses **查看全部风格**, immediately show **every current
+  `catalog.entries` item in one single-question image-card picker** using the same label,
+  description, and imagePath rule above. Preserve catalog order, keep `PACK ·` visible,
+  and append the custom-template file card. Do not ask for a group, paginate, or return to
+  any category/second-level picker; the browse-all action must expose final selectable
+  templates directly.
+
+  Samples are pre-rendered WebP files shipped with the skill: pass their absolute paths
+  directly and do not render anything during the question. The selected `entry.id` is the
+  `--style` value: `html2pptx deck.html out.pptx --style <id>`. Skin and pack use the same
+  render command; `catalog.json` resolves their different asset directories.
+
+  **Keep both calls LEAN.** The content/scenario/count questions use bare label strings,
+  no per-option descriptions; every question stem is one short sentence. Skip chat
+  preambles or keep one short line. Every question has the panel's implicit custom-text
+  escape. If the user responds with a correction or question, handle it and re-ask.
+
+  **Automatic choice, only when explicitly authorized:** rank by a remembered preference,
+  an exact user-named style, scenario match, a matching pack before a matching skin, then
+  `entry.mode` when the user asked for clean/formal/light/dark. Never hardcode a family id:
+  `catalog.json` is the only roster; `styles/README.md` is explanatory only. Never render
+  unstyled. After the user confirms, save the preference to memory.
 
   **Custom style (user picked 其他/自定义 on Q3)** — clarify which route, **prefer B
   (derive a bespoke look)**: