[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ME4FCJZJ3NPYW1D04XWJRM":3,"skill-same:01M6ME4FCJZJ3NPYW1D04XWJRM":84},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":57,"repositoryHtmlUrl":58,"repositoryHomepageUrl":59,"ownerHtmlUrl":60,"ownerBlogUrl":61,"ownerDescription":62,"updatedAt":63,"install":64,"resources":77},"01M6ME4FCJZJ3NPYW1D04XWJRM","jimeng-script-intake",null,"Use when 新剧本入库即梦分镜师工作空间并拆集。","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fandreamzhang\u002Fjimeng-skills\u002F.agents\u002Fskills\u002Fjimeng-script-intake\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000002","文档处理","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37],"intake","script","jimeng script intake","docx","macos","linux","windows","assets","use","character","剧本","分镜","短剧","when","2026-11-10 10:12:30",false,"---\nname: jimeng-script-intake\ndescription: Use when 新剧本入库即梦分镜师工作空间并拆集。\nversion: 1.1.0\nauthor: 即梦分镜师工作台\nlicense: MIT\nplatforms: [windows, linux, macos]\nmetadata:\n  codex:\n    tags: [短剧, 剧本入库, 拆集, 即梦分镜师]\n    related_skills: [jimeng-character-assets, docx]\n---\n\n# 短剧剧本入库与拆集（即梦分镜师工作空间）\n\n## When to Use\n\n- 用户丢来一本新剧本（.docx\u002F.txt\u002F.doc\u002F.pdf）说「这是新剧本，放在他应该在的位置」「开始处理这部」。\n- 需要在即梦分镜师工作空间新建一部剧的剧本仓库（骨架 + 源稿存档 + 分集 txt）。\n- 已入库剧本的场景行\u002F叙述行格式被质疑、或下游脚本报「未命名场景（场景标题缺失）」、终审伪报台词「改写」时（看 `references\u002Fscript-format-contract.md` 定位是哪条格式规则）。\n\n不适用：已经在跑的剧本单集分镜生产（那是 AGENTS.md 的阶段一～八）。\n\n**工作区根**：Codex 项目根（AGENTS.md 所在目录；所有 `scripts\u002F…`、`tools\u002F…` 相对该根，可用环境变量 `JIMENG_ROOT` 显式指定）。\n**权威规则**：工作区根 `AGENTS.md`（阶段零前 \u002F 文件结构 \u002F 硬约束）。本技能只补它没写的操作细节与解析器坑。\n\n## 目标位置（放错＝后续全流程读不到剧本）\n\n```\nscripts\u002F\u003C剧名>\u002F\n├── \u003C剧名> 1-N.docx         # 源稿存档，原字节不动（既有各剧源稿都放这一层）\n├── script\u002F\n│   ├── 00-剧本概要.txt      # 剧名 + 人物简表等「第1集」标题之前的前言\n│   ├── ep01.txt … epNN.txt  # ★ 分镜全流程唯一读的剧本形态\n│   ├── assets\u002F  config\u002F  outputs\u002F\n```\n\n`.codex\u002Fmemory\u002F\u003C剧名>-\u003Crole>.md` 五份身份文件必须在首次派子代理前存在，否则子代理按派遣契约 abort。\n\n## 步骤\n\n1. **定剧名**：取剧本首行标题去掉《》或用户给的名字，作为 `scripts\u002F` 目录名（不含《》、标点）。\n2. **建骨架＋身份文件**（一条命令）：`python tools\u002Fnew_drama_memory.py \"\u003C剧名>\" --dirs`\n3. **存档源稿**：把用户上传件原样复制为 `scripts\u002F\u003C剧名>\u002F\u003C剧名> 1-N.docx`（N=总集数），`md5sum` 与上传件比对确认字节一致；不转码、不另存、不改内容。通用的 `剧本(2).docx` 这类文件名要换成「剧名 1-N」再入库。\n4. **拆集**：`python tools\u002Fsplit_script_episodes.py \"scripts\u002F\u003C剧名>\u002F\u003C剧名> 1-N.docx\" --name \"\u003C剧名>\"`\n   产出 `script\u002Fep01.txt …` + `script\u002F00-剧本概要.txt`；重复执行幂等（覆盖同名文件）。\n   - **整本多集、纯中文** → 用上面这条。\n   - **单集稿 \u002F 中韩对照（双语）稿** → 用 `python tools\u002Fdocx_script_import.py \"\u003Cdocx路径>\" \"\u003C剧名>\" --ep N`：一次落 `script\u002FepNN.txt`（中文正文）+ `epNN-中韩对照.txt`（双语留档）+ `00-剧本概要.txt` + `_source\u002F` 源稿。**别拿 `split_script_episodes.py` 处理双语稿**：它按行保留韩文，韩文台词会被当成中文台词进台词本与终审对照。\n   - 双语稿落库后把 `_source\u002F` 里的源稿按本节约定挪到剧根、命名成 `\u003C剧名> 1-N.docx`（全库一致，换新版时能一键重跑）。\n5. **验证**（必做，不要只信脚本自报）：见下节。\n6. **报告**：产出清单＋验证数字＋下一步。\n   - **阶段零（`config\u002Fglobal-style.md`）**：风格 A-D 选项必须交用户敲定，不得代定；**画幅也必须先问**（短剧默认 9:16 竖屏，别写成 16:9）。用户偏好：**光线从句从简**（写「日间自然光，室内光线柔和」「夜晚，室内以油灯烛火作局部照明」这种粒度，不写光源方向与明暗细节）、**不加角色与面孔强化子句**——面孔铁律\u002F画内文字这类纪律改记在人物资产条目里，不在 config 重复。\n   - 人物资产（阶段零点五）走 `jimeng-character-assets` 技能。\n\n## 台词正文一字不改，只做标记类规范化\n\n四项都由 `tools\u002Fsplit_script_episodes.py` 默认完成（`--no-fix` 关闭，仅用于排查）：\n\n1. **场景行**去行首「场」、非断字连字符(U+2010‑2014)统一为 ASCII `-`：`场12‑3 青云宗山门 日 外` → `12-3 青云宗山门 日 外`。\n   why：`gen_dialogue_list.is_scene_title()` 要求行首是数字编号；否则整集台词被归入「未命名场景（场景标题缺失）」，而 `check_dialogue` 还会把该场景行并进上一条台词 → 终审伪报「改写」。\n2. **无标记叙述行补 `△`**（原稿多数叙述行本来就带 △，属标记不一致）。\n   why：`check_dialogue` 把任何无法识别的行并进上一条台词，且空行不重置合并状态 → 台词被污染。\n3. **台词后紧贴的【…】行（钩子\u002F字幕）前补空行**。\n   why：`gen_dialogue_list` 把紧贴上一句的普通文本行当作台词折行续接。\n4. **前言（剧名\u002F人物简表）独立成 `script\u002F00-剧本概要.txt`，绝不并入 ep01**。\n   why：人物简表每行都形如 `角色：介绍`，会被解析成 ep01 的台词，污染台词本与终审对照。\n\n## 拆集（整本 → 分集）与人物清点\n\n- 拆集：`python tools\u002Fsplit_script_episodes.py \"scripts\u002F\u003C剧名>\u002F\u003C剧名> 1-N.docx\" --name \"\u003C剧名>\"`（章节见下）。\n- 人物清点：`python tools\u002Fgen_character_inventory.py \"\u003C剧名>\" --alias assets\u002F_character-aliases.json` —— 阶段零点五 第 1 步，逐集出场表 + 有台词\u002F无台词分列；别名表按剧维护。\n  新剧首次清点时最常见的漏项是**「角色名 + 动作描述」的台词行**（`弟子甲厉声反驳：…`、`清月收回手掌面向众人：…`）与**单字序号简写**（`人物：守山弟子甲、乙、丙`），两者不并回角色名就会多出几个幽灵角色，后续分镜 @引用名分裂。\n\n## 验证（两步，都真跑）\n\n- **逐行回环比对**：源稿非空行数 == 写出行数，且序列逐行相等（用 `normalize()` 重算期望序列），只允许上面三类标记差异 —— 证明没有丢字\u002F串行。\n- **镜像试跑台词本**：把 `script\u002Fep*.txt` 复制到 scratch 的 `\u003C剧名>\u002Fscript\u002F` 下，对每集跑 `.agents\u002Fskills\u002Fjimeng-storyboard\u002Fscripts\u002Fgen_dialogue_list.py`，然后核对：全部集解析成功、台词总条数 == 源稿独立计数（减去人物简表行数）、0 集出现「未命名场景」、无台词含 `△` 或异常长（>90 字多为被叙述\u002F钩子污染）。\n  在 scratch 里跑，别直接生成项目 `outputs\u002F`（那是分镜生产产物）。\n  现成片段与解析器契约见 `references\u002Fscript-format-contract.md`。\n\n## 坑\n\n- **自写 docx 段落抽取正则：用 `\u003Cw:t(?:\\s[^>]*)?>(.*?)\u003C\u002Fw:t>`**（`w:t` 后必须是空白或 `>`）。写成 `\u003Cw:t[^>]*>` 会连 `\u003Cw:textAlignment ...\u002F>` 一起匹配，把大段 XML 当成正文抽出来，表现为「剧本里混进了标签」，排查半天。`tools\u002Fsplit_script_episodes.py` 已按前者实现。\n- **集号标题与场景行格式两大类都要容错**：正文标题可能是「第N集」或「第N集」（阿拉伯\u002F中文数字），解析器两都收；场景编号可能是 `1-1 地点 日 内`、`场1‑1 …`、`36-1 地点｜午后｜外`，去「场」+连字符统一后都满足「行首数字」契约。\n- **native python 读不了 MSYS 的 `\u002Ftmp\u002F...`**：`$TMPDIR` 在 bash 里可能展开成 `\u002Ftmp\u002F...`，直接传给 python 会 `file not found`。scratch 一律用原生路径 `C:\u002FUsers\u002F\u003Cuser>\u002FAppData\u002FLocal\u002FTemp\u002Fjimeng-scratch\u002F...`。\n- **中韩对照 \u002F 双语稿**：进流水线的 `epXX.txt` 只留中文行，韩文行另存 `epXX-中韩对照.txt`。韩文台词行同样满足 `角色(情绪): 台词` 形态（半角括号与冒号也在正则里），混进 `epXX.txt` 会让台词本与终审对照凭空多出一整套「缺失\u002F改写」。双语档案同时是后续韩国本地化（人名\u002F称谓\u002F物件）的依据。\n- **台词本总时长异常（约为合理值的两倍）、且某说话人台词后粘着一整段叙述** = 那段叙述没打 `△`（解析器把无法识别的行并进上一条台词）。入库后先核总秒数与逐条字数，别只看「N 条台词」。\n- 逐字校验要**对着源稿算**：把源 docx 抽出的（角色, 台词）序列与 `script\u002FepXX.txt` 的序列**逐对**比较，只有这样才能证明「只加标记、没改一个字」；只比行数证明不了。片段见 `references\u002Fscript-format-contract.md` §5。\n- **别把源稿只留在 `docs\u002F`**：`docs\u002F` 是暂存区，管道只读 `scripts\u002F\u003C剧名>\u002Fscript\u002FepXX.txt`。\n- **不要手改 `script\u002FepXX.txt`** 的台词文字来「修格式」；只加标记（△\u002F空行\u002F场景行前缀），台词逐字是终审硬判据。\n- 拆集规则（规范化项）改动后，要在旧剧上跑一次 `tools\\py.cmd tools\u002Frun_all_checks.py \u003C剧名> epXX` 回归对比。\n","# 短剧剧本入库与拆集（即梦分镜师工作空间）\n\n## When to Use\n\n- 用户丢来一本新剧本（.docx\u002F.txt\u002F.doc\u002F.pdf）说「这是新剧本，放在他应该在的位置」「开始处理这部」。\n- 需要在即梦分镜师工作空间新建一部剧的剧本仓库（骨架 + 源稿存档 + 分集 txt）。\n- 已入库剧本的场景行\u002F叙述行格式被质疑、或下游脚本报「未命名场景（场景标题缺失）」、终审伪报台词「改写」时（看 `references\u002Fscript-format-contract.md` 定位是哪条格式规则）。\n\n不适用：已经在跑的剧本单集分镜生产（那是 AGENTS.md 的阶段一～八）。\n\n**工作区根**：Codex 项目根（AGENTS.md 所在目录；所有 `scripts\u002F…`、`tools\u002F…` 相对该根，可用环境变量 `JIMENG_ROOT` 显式指定）。\n**权威规则**：工作区根 `AGENTS.md`（阶段零前 \u002F 文件结构 \u002F 硬约束）。本技能只补它没写的操作细节与解析器坑。\n\n## 目标位置（放错＝后续全流程读不到剧本）\n\n```\nscripts\u002F\u003C剧名>\u002F\n├── \u003C剧名> 1-N.docx         # 源稿存档，原字节不动（既有各剧源稿都放这一层）\n├── script\u002F\n│   ├── 00-剧本概要.txt      # 剧名 + 人物简表等「第1集」标题之前的前言\n│   ├── ep01.txt … epNN.txt  # ★ 分镜全流程唯一读的剧本形态\n│   ├── assets\u002F  config\u002F  outputs\u002F\n```\n\n`.codex\u002Fmemory\u002F\u003C剧名>-\u003Crole>.md` 五份身份文件必须在首次派子代理前存在，否则子代理按派遣契约 abort。\n\n## 步骤\n\n1. **定剧名**：取剧本首行标题去掉《》或用户给的名字，作为 `scripts\u002F` 目录名（不含《》、标点）。\n2. **建骨架＋身份文件**（一条命令）：`python tools\u002Fnew_drama_memory.py \"\u003C剧名>\" --dirs`\n3. **存档源稿**：把用户上传件原样复制为 `scripts\u002F\u003C剧名>\u002F\u003C剧名> 1-N.docx`（N=总集数），`md5sum` 与上传件比对确认字节一致；不转码、不另存、不改内容。通用的 `剧本(2).docx` 这类文件名要换成「剧名 1-N」再入库。\n4. **拆集**：`python tools\u002Fsplit_script_episodes.py \"scripts\u002F\u003C剧名>\u002F\u003C剧名> 1-N.docx\" --name \"\u003C剧名>\"`\n   产出 `script\u002Fep01.txt …` + `script\u002F00-剧本概要.txt`；重复执行幂等（覆盖同名文件）。\n   - **整本多集、纯中文** → 用上面这条。\n   - **单集稿 \u002F 中韩对照（双语）稿** → 用 `python tools\u002Fdocx_script_import.py \"\u003Cdocx路径>\" \"\u003C剧名>\" --ep N`：一次落 `script\u002FepNN.txt`（中文正文）+ `epNN-中韩对照.txt`（双语留档）+ `00-剧本概要.txt` + `_source\u002F` 源稿。**别拿 `split_script_episodes.py` 处理双语稿**：它按行保留韩文，韩文台词会被当成中文台词进台词本与终审对照。\n   - 双语稿落库后把 `_source\u002F` 里的源稿按本节约定挪到剧根、命名成 `\u003C剧名> 1-N.docx`（全库一致，换新版时能一键重跑）。\n5. **验证**（必做，不要只信脚本自报）：见下节。\n6. **报告**：产出清单＋验证数字＋下一步。\n   - **阶段零（`config\u002Fglobal-style.md`）**：风格 A-D 选项必须交用户敲定，不得代定；**画幅也必须先问**（短剧默认 9:16 竖屏，别写成 16:9）。用户偏好：**光线从句从简**（写「日间自然光，室内光线柔和」「夜晚，室内以油灯烛火作局部照明」这种粒度，不写光源方向与明暗细节）、**不加角色与面孔强化子句**——面孔铁律\u002F画内文字这类纪律改记在人物资产条目里，不在 config 重复。\n   - 人物资产（阶段零点五）走 `jimeng-character-assets` 技能。\n\n## 台词正文一字不改，只做标记类规范化\n\n四项都由 `tools\u002Fsplit_script_episodes.py` 默认完成（`--no-fix` 关闭，仅用于排查）：\n\n1. **场景行**去行首「场」、非断字连字符(U+2010‑2014)统一为 ASCII `-`：`场12‑3 青云宗山门 日 外` → `12-3 青云宗山门 日 外`。\n   why：`gen_dialogue_list.is_scene_title()` 要求行首是数字编号；否则整集台词被归入「未命名场景（场景标题缺失）」，而 `check_dialogue` 还会把该场景行并进上一条台词 → 终审伪报「改写」。\n2. **无标记叙述行补 `△`**（原稿多数叙述行本来就带 △，属标记不一致）。\n   why：`check_dialogue` 把任何无法识别的行并进上一条台词，且空行不重置合并状态 → 台词被污染。\n3. **台词后紧贴的【…】行（钩子\u002F字幕）前补空行**。\n   why：`gen_dialogue_list` 把紧贴上一句的普通文本行当作台词折行续接。\n4. **前言（剧名\u002F人物简表）独立成 `script\u002F00-剧本概要.txt`，绝不并入 ep01**。\n   why：人物简表每行都形如 `角色：介绍`，会被解析成 ep01 的台词，污染台词本与终审对照。\n\n## 拆集（整本 → 分集）与人物清点\n\n- 拆集：`python tools\u002Fsplit_script_episodes.py \"scripts\u002F\u003C剧名>\u002F\u003C剧名> 1-N.docx\" --name \"\u003C剧名>\"`（章节见下）。\n- 人物清点：`python tools\u002Fgen_character_inventory.py \"\u003C剧名>\" --alias assets\u002F_character-aliases.json` —— 阶段零点五 第 1 步，逐集出场表 + 有台词\u002F无台词分列；别名表按剧维护。\n  新剧首次清点时最常见的漏项是**「角色名 + 动作描述」的台词行**（`弟子甲厉声反驳：…`、`清月收回手掌面向众人：…`）与**单字序号简写**（`人物：守山弟子甲、乙、丙`），两者不并回角色名就会多出几个幽灵角色，后续分镜 @引用名分裂。\n\n## 验证（两步，都真跑）\n\n- **逐行回环比对**：源稿非空行数 == 写出行数，且序列逐行相等（用 `normalize()` 重算期望序列），只允许上面三类标记差异 —— 证明没有丢字\u002F串行。\n- **镜像试跑台词本**：把 `script\u002Fep*.txt` 复制到 scratch 的 `\u003C剧名>\u002Fscript\u002F` 下，对每集跑 `.agents\u002Fskills\u002Fjimeng-storyboard\u002Fscripts\u002Fgen_dialogue_list.py`，然后核对：全部集解析成功、台词总条数 == 源稿独立计数（减去人物简表行数）、0 集出现「未命名场景」、无台词含 `△` 或异常长（>90 字多为被叙述\u002F钩子污染）。\n  在 scratch 里跑，别直接生成项目 `outputs\u002F`（那是分镜生产产物）。\n  现成片段与解析器契约见 `references\u002Fscript-format-contract.md`。\n\n## 坑\n\n- **自写 docx 段落抽取正则：用 `\u003Cw:t(?:\\s[^>]*)?>(.*?)\u003C\u002Fw:t>`**（`w:t` 后必须是空白或 `>`）。写成 `\u003Cw:t[^>]*>` 会连 `\u003Cw:textAlignment ...\u002F>` 一起匹配，把大段 XML 当成正文抽出来，表现为「剧本里混进了标签」，排查半天。`tools\u002Fsplit_script_episodes.py` 已按前者实现。\n- **集号标题与场景行格式两大类都要容错**：正文标题可能是「第N集」或「第N集」（阿拉伯\u002F中文数字），解析器两都收；场景编号可能是 `1-1 地点 日 内`、`场1‑1 …`、`36-1 地点｜午后｜外`，去「场」+连字符统一后都满足「行首数字」契约。\n- **native python 读不了 MSYS 的 `\u002Ftmp\u002F...`**：`$TMPDIR` 在 bash 里可能展开成 `\u002Ftmp\u002F...`，直接传给 python 会 `file not found`。scratch 一律用原生路径 `C:\u002FUsers\u002F\u003Cuser>\u002FAppData\u002FLocal\u002FTemp\u002Fjimeng-scratch\u002F...`。\n- **中韩对照 \u002F 双语稿**：进流水线的 `epXX.txt` 只留中文行，韩文行另存 `epXX-中韩对照.txt`。韩文台词行同样满足 `角色(情绪): 台词` 形态（半角括号与冒号也在正则里），混进 `epXX.txt` 会让台词本与终审对照凭空多出一整套「缺失\u002F改写」。双语档案同时是后续韩国本地化（人名\u002F称谓\u002F物件）的依据。\n- **台词本总时长异常（约为合理值的两倍）、且某说话人台词后粘着一整段叙述** = 那段叙述没打 `△`（解析器把无法识别的行并进上一条台词）。入库后先核总秒数与逐条字数，别只看「N 条台词」。\n- 逐字校验要**对着源稿算**：把源 docx 抽出的（角色, 台词）序列与 `script\u002FepXX.txt` 的序列**逐对**比较，只有这样才能证明「只加标记、没改一个字」；只比行数证明不了。片段见 `references\u002Fscript-format-contract.md` §5。\n- **别把源稿只留在 `docs\u002F`**：`docs\u002F` 是暂存区，管道只读 `scripts\u002F\u003C剧名>\u002Fscript\u002FepXX.txt`。\n- **不要手改 `script\u002FepXX.txt`** 的台词文字来「修格式」；只加标记（△\u002F空行\u002F场景行前缀），台词逐字是终审硬判据。\n- 拆集规则（规范化项）改动后，要在旧剧上跑一次 `tools\\py.cmd tools\u002Frun_all_checks.py \u003C剧名> epXX` 回归对比。\n",{"name":5,"author":43,"license":15,"version":44,"metadata":45,"platforms":53,"description":7},"即梦分镜师工作台","1.1.0",{"codex":46},{"tags":47,"related_skills":51},[36,48,49,50],"剧本入库","拆集","即梦分镜师",[52,27],"jimeng-character-assets",[30,29,28],"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Fandreamzhang\u002Fjimeng-skills\u002F.agents\u002Fskills\u002Fjimeng-script-intake",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":65,"prompt":75,"zipAvailable":76},[66,69,72],{"tool":67,"command":68},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill jimeng-script-intake",{"tool":70,"command":71},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill jimeng-script-intake",{"tool":73,"command":74},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill jimeng-script-intake","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fandreamzhang\u002Fjimeng-skills\u002F.agents\u002Fskills\u002Fjimeng-script-intake\u002FSKILL.md",true,[78],{"path":79,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Fscript-format-contract.md","REFERENCE","参考文档",6463,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fandreamzhang\u002Fjimeng-skills\u002F.agents\u002Fskills\u002Fjimeng-script-intake\u002Freferences\u002Fscript-format-contract.md",[85,94,102,110,118,126],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":89,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":93},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":98,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":93},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":106,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":93},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":114,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":93},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":122,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":93},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":130,"sourceHtmlUrl":131,"categories":132,"keywords":133,"publishedAt":93},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]