[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MPGZ24FN9SJ7XTX2GJESNH":3,"skill-same:01M6MPGZ24FN9SJ7XTX2GJESNH":81},{"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":36,"linkOnly":37,"markdownContent":38,"markdownBody":39,"frontMatter":40,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":50,"repositoryHtmlUrl":51,"repositoryHomepageUrl":52,"ownerHtmlUrl":53,"ownerBlogUrl":54,"ownerDescription":55,"updatedAt":56,"install":57,"resources":70},"01M6MPGZ24FN9SJ7XTX2GJESNH","lark-note",null,"飞书会议纪要（Note）直查：已知 note_id 时查询纪要详情、展示类型、关联文档 token，并读取 unified 原始逐字记录。当用户已持有 note_id，或从文档显式 vc-node-id 获得 note_id 时使用。不负责会议\u002F日程\u002F妙记定位、文档标题搜索或 Docx 正文读取。","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fzlsbksdxl\u002Fcodex-lark\u002Fskills\u002Flark-note\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],"lark note","lark","note","docx","cli","help","文档","node","搜索","token","id","vc","2026-11-10 10:12:30",false,"---\nname: lark-note\nversion: 1.0.0\ndescription: \"飞书会议纪要（Note）直查：已知 note_id 时查询纪要详情、展示类型、关联文档 token，并读取 unified 原始逐字记录。当用户已持有 note_id，或从文档显式 vc-node-id 获得 note_id 时使用。不负责会议\u002F日程\u002F妙记定位、文档标题搜索或 Docx 正文读取。\"\nmetadata:\n  requires:\n    bins: [\"lark-cli\"]\n  cliHelp: \"lark-cli note --help\"\n---\n\n# note (v1)\n\n身份：仅使用 `--as user`。使用前阅读 [`..\u002Flark-shared\u002FSKILL.md`](..\u002Flark-shared\u002FSKILL.md)。\n\n**CRITICAL — 开始前 MUST 先用 Read 工具读取 [`..\u002Flark-vc\u002Freferences\u002Fvc-domain-boundaries.md`](..\u002Flark-vc\u002Freferences\u002Fvc-domain-boundaries.md)**，不读将导致命令使用、会议产物决策、领域边界职责判断错误：\n> 1. 了解日历 & VC、会议产物 & 文档的关联关系和职责划分\n> 2. 了解会议产物（妙记和纪要）之间的关联关系，例如：**妙记和纪要产生条件相互独立**\n> 3. 了解不同会议产物的组成部分，以便根据需求决策使用哪种产物的数据\n\nNote 域只接受显式 `note_id`：用户直接提供，或 `docs +fetch` 返回的 `\u003Cvc-transcribe-tab vc-node-id=\"...\">` 中的 `vc-node-id`。不要从 `doc_token`、标题、正文或 backlink 反推 `note_id`。\n\n## 命令路由\n\n| 用户表达 \u002F 上下文 | 路由 |\n|---------|------|\n| 已知 `note_id`，查纪要类型 \u002F 文档 token | `note +detail --note-id NOTE_ID` |\n| `docs +fetch` 返回 `\u003Cvc-transcribe-tab vc-node-id=\"...\">` | 取 `vc-node-id` 作为 `NOTE_ID`，先 `note +detail --note-id NOTE_ID` |\n| 只持有 `meeting_id` | 先 `vc +detail --meeting-ids \u003Cid>` 拿 `note_id`，再 `note +detail --note-id NOTE_ID` |\n| 只持有 `minute_token`（妙记 URL） | 先 `minutes +detail --minute-tokens \u003Ctoken>` 顶层取 `note_id`，再 `note +detail --note-id NOTE_ID`（不要把 `minute_token` 当 `note_id`） |\n| 只持有日程 `event_id` | 先 `calendar +meeting --event-ids \u003Cid>` 拿 `meeting_id`，再按上一行继续 |\n| 已知 `note_id`，读纪要正文 | `note +detail` → `docs +fetch --doc \u003Cnote_doc_token>` |\n| 已知 `note_id`，查 unified 原始记录 \u002F 逐字稿 | `note +transcript --note-id NOTE_ID` |\n| 只有自然语言纪要标题，用户要逐字稿 \u002F 原始记录 \u002F 谁说了什么 | 不进本 skill；先走文档搜索与 `docs +fetch`，拿到 `vc-node-id` 后再回来 |\n\n## `note_display_type` 路由\n\n| `note +detail` 结果 | 用户要逐字稿 \u002F 原始记录时 |\n|------|---------------|\n| `normal` + `verbatim_doc_token` 非空 | `docs +fetch --doc \u003Cverbatim_doc_token>` |\n| `unknown` + `verbatim_doc_token` 非空 | 先按独立文档处理；不要猜成 unified |\n| `unknown` + 无逐字稿 token | 停止重试并说明无法确定逐字稿入口 |\n| `unified` | `note +transcript --note-id \u003Cnote_id>` |\n\n判别键是 `note_display_type`，不是 `verbatim_doc_token` 是否为空：unified 纪要也可能返回非空 `verbatim_doc_token`。\n\n## 关键字段\n\n- `note_id`：Note 域唯一入口。\n- `note_display_type`：`unknown` \u002F `normal` \u002F `unified`。\n- `note_doc_token`：纪要正文文档，正文读取交给 [lark-doc](..\u002Flark-doc\u002FSKILL.md)。\n- `verbatim_doc_token`：普通纪要逐字稿文档；unified 逐字稿不按这个 token 路由。\n\n## 不在本 Skill 范围\n\n- 通过 `meeting_id` 定位纪要（`note_id`）→ [lark-vc](..\u002Flark-vc\u002FSKILL.md)（`vc +detail`）。\n- 通过 `minute_token` 定位纪要（`note_id`）→ [lark-minutes](..\u002Flark-minutes\u002FSKILL.md)（`minutes +detail` 顶层返回 `note_id`）。\n- 通过日程 `event_id` 定位会议(`meeting_id`) \u002F 用户绑定纪要(`meeting_note`) → [lark-calendar](..\u002Flark-calendar\u002FSKILL.md)（`calendar +meeting`）。\n- 自然语言纪要标题搜索 → [lark-drive](..\u002Flark-drive\u002FSKILL.md) \u002F [lark-doc](..\u002Flark-doc\u002FSKILL.md)。\n- Docx 正文读取 → [lark-doc](..\u002Flark-doc\u002FSKILL.md)。\n- 妙记基础信息与媒体文件 → [lark-minutes](..\u002Flark-minutes\u002FSKILL.md)。\n\n## Shortcuts\n\n| Shortcut | 何时读 reference |\n|----------|------|\n| [`+detail`](references\u002Flark-note-detail.md) | 需要解释输出字段或根据展示类型继续路由 |\n| [`+transcript`](references\u002Flark-note-transcript.md) | 需要拉取 unified 原始记录或处理本地输出文件 |\n\n## 核心概念\n\n- **会议纪要（Note）**：视频会议结束后生成的结构化文档，通过 `note_id` 标识。一个 Note 包含 AI 智能纪要文档、逐字稿文档和会中共享文档。\n- **note_id**：纪要的唯一标识符，可通过 `vc +detail --meeting-ids` 获取。\n- **AI 智能纪要（MainDoc）**：AI 生成的会议总结与待办，对应 `note_doc_token`。\n- **逐字稿（VerbatimDoc）**：会议的逐句发言记录，含说话人和时间戳，对应 `verbatim_doc_token`。\n- **共享文档（SharedDoc）**：会中投屏共享的文档，对应 `shared_doc_tokens`。\n\n## 核心场景\n\n### 1. 通过 note_id 获取纪要文档 Token\n\n1. 当用户已有 `note_id`，需要获取对应的 `note_doc_token`、`verbatim_doc_token` 或 `shared_doc_tokens` 时，使用 `note +detail`。\n2. `note_id` 通常来自 `vc +detail` 的返回结果。\n3. 获取到文档 Token 后，可使用 `docs +fetch` 读取文档内容，或使用 `drive metas batch_query` 获取文档元信息。\n\n```bash\n# 1. 从会议获取 note_id\nlark-cli vc +detail --meeting-ids \u003Cmeeting_id>\n\n# 2. 用 note_id 拿文档 Token\nlark-cli note +detail --note-id \u003Cnote_id>\n\n# 3. 读取纪要文档内容\nlark-cli docs +fetch --doc \u003Cnote_doc_token> --doc-format markdown\n```\n","# note (v1)\n\n身份：仅使用 `--as user`。使用前阅读 [`..\u002Flark-shared\u002FSKILL.md`](..\u002Flark-shared\u002FSKILL.md)。\n\n**CRITICAL — 开始前 MUST 先用 Read 工具读取 [`..\u002Flark-vc\u002Freferences\u002Fvc-domain-boundaries.md`](..\u002Flark-vc\u002Freferences\u002Fvc-domain-boundaries.md)**，不读将导致命令使用、会议产物决策、领域边界职责判断错误：\n> 1. 了解日历 & VC、会议产物 & 文档的关联关系和职责划分\n> 2. 了解会议产物（妙记和纪要）之间的关联关系，例如：**妙记和纪要产生条件相互独立**\n> 3. 了解不同会议产物的组成部分，以便根据需求决策使用哪种产物的数据\n\nNote 域只接受显式 `note_id`：用户直接提供，或 `docs +fetch` 返回的 `\u003Cvc-transcribe-tab vc-node-id=\"...\">` 中的 `vc-node-id`。不要从 `doc_token`、标题、正文或 backlink 反推 `note_id`。\n\n## 命令路由\n\n| 用户表达 \u002F 上下文 | 路由 |\n|---------|------|\n| 已知 `note_id`，查纪要类型 \u002F 文档 token | `note +detail --note-id NOTE_ID` |\n| `docs +fetch` 返回 `\u003Cvc-transcribe-tab vc-node-id=\"...\">` | 取 `vc-node-id` 作为 `NOTE_ID`，先 `note +detail --note-id NOTE_ID` |\n| 只持有 `meeting_id` | 先 `vc +detail --meeting-ids \u003Cid>` 拿 `note_id`，再 `note +detail --note-id NOTE_ID` |\n| 只持有 `minute_token`（妙记 URL） | 先 `minutes +detail --minute-tokens \u003Ctoken>` 顶层取 `note_id`，再 `note +detail --note-id NOTE_ID`（不要把 `minute_token` 当 `note_id`） |\n| 只持有日程 `event_id` | 先 `calendar +meeting --event-ids \u003Cid>` 拿 `meeting_id`，再按上一行继续 |\n| 已知 `note_id`，读纪要正文 | `note +detail` → `docs +fetch --doc \u003Cnote_doc_token>` |\n| 已知 `note_id`，查 unified 原始记录 \u002F 逐字稿 | `note +transcript --note-id NOTE_ID` |\n| 只有自然语言纪要标题，用户要逐字稿 \u002F 原始记录 \u002F 谁说了什么 | 不进本 skill；先走文档搜索与 `docs +fetch`，拿到 `vc-node-id` 后再回来 |\n\n## `note_display_type` 路由\n\n| `note +detail` 结果 | 用户要逐字稿 \u002F 原始记录时 |\n|------|---------------|\n| `normal` + `verbatim_doc_token` 非空 | `docs +fetch --doc \u003Cverbatim_doc_token>` |\n| `unknown` + `verbatim_doc_token` 非空 | 先按独立文档处理；不要猜成 unified |\n| `unknown` + 无逐字稿 token | 停止重试并说明无法确定逐字稿入口 |\n| `unified` | `note +transcript --note-id \u003Cnote_id>` |\n\n判别键是 `note_display_type`，不是 `verbatim_doc_token` 是否为空：unified 纪要也可能返回非空 `verbatim_doc_token`。\n\n## 关键字段\n\n- `note_id`：Note 域唯一入口。\n- `note_display_type`：`unknown` \u002F `normal` \u002F `unified`。\n- `note_doc_token`：纪要正文文档，正文读取交给 [lark-doc](..\u002Flark-doc\u002FSKILL.md)。\n- `verbatim_doc_token`：普通纪要逐字稿文档；unified 逐字稿不按这个 token 路由。\n\n## 不在本 Skill 范围\n\n- 通过 `meeting_id` 定位纪要（`note_id`）→ [lark-vc](..\u002Flark-vc\u002FSKILL.md)（`vc +detail`）。\n- 通过 `minute_token` 定位纪要（`note_id`）→ [lark-minutes](..\u002Flark-minutes\u002FSKILL.md)（`minutes +detail` 顶层返回 `note_id`）。\n- 通过日程 `event_id` 定位会议(`meeting_id`) \u002F 用户绑定纪要(`meeting_note`) → [lark-calendar](..\u002Flark-calendar\u002FSKILL.md)（`calendar +meeting`）。\n- 自然语言纪要标题搜索 → [lark-drive](..\u002Flark-drive\u002FSKILL.md) \u002F [lark-doc](..\u002Flark-doc\u002FSKILL.md)。\n- Docx 正文读取 → [lark-doc](..\u002Flark-doc\u002FSKILL.md)。\n- 妙记基础信息与媒体文件 → [lark-minutes](..\u002Flark-minutes\u002FSKILL.md)。\n\n## Shortcuts\n\n| Shortcut | 何时读 reference |\n|----------|------|\n| [`+detail`](references\u002Flark-note-detail.md) | 需要解释输出字段或根据展示类型继续路由 |\n| [`+transcript`](references\u002Flark-note-transcript.md) | 需要拉取 unified 原始记录或处理本地输出文件 |\n\n## 核心概念\n\n- **会议纪要（Note）**：视频会议结束后生成的结构化文档，通过 `note_id` 标识。一个 Note 包含 AI 智能纪要文档、逐字稿文档和会中共享文档。\n- **note_id**：纪要的唯一标识符，可通过 `vc +detail --meeting-ids` 获取。\n- **AI 智能纪要（MainDoc）**：AI 生成的会议总结与待办，对应 `note_doc_token`。\n- **逐字稿（VerbatimDoc）**：会议的逐句发言记录，含说话人和时间戳，对应 `verbatim_doc_token`。\n- **共享文档（SharedDoc）**：会中投屏共享的文档，对应 `shared_doc_tokens`。\n\n## 核心场景\n\n### 1. 通过 note_id 获取纪要文档 Token\n\n1. 当用户已有 `note_id`，需要获取对应的 `note_doc_token`、`verbatim_doc_token` 或 `shared_doc_tokens` 时，使用 `note +detail`。\n2. `note_id` 通常来自 `vc +detail` 的返回结果。\n3. 获取到文档 Token 后，可使用 `docs +fetch` 读取文档内容，或使用 `drive metas batch_query` 获取文档元信息。\n\n```bash\n# 1. 从会议获取 note_id\nlark-cli vc +detail --meeting-ids \u003Cmeeting_id>\n\n# 2. 用 note_id 拿文档 Token\nlark-cli note +detail --note-id \u003Cnote_id>\n\n# 3. 读取纪要文档内容\nlark-cli docs +fetch --doc \u003Cnote_doc_token> --doc-format markdown\n```\n",{"name":5,"version":41,"metadata":42,"description":7},"1.0.0",{"cliHelp":43,"requires":44},"lark-cli note --help",{"bins":45},[46],"lark-cli","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Fzlsbksdxl\u002Fcodex-lark\u002Fskills\u002Flark-note",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":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill lark-note",{"tool":63,"command":64},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill lark-note",{"tool":66,"command":67},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill lark-note","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fzlsbksdxl\u002Fcodex-lark\u002Fskills\u002Flark-note\u002FSKILL.md",true,[71,77],{"path":72,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002Flark-note-detail.md","REFERENCE","参考文档",1244,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fzlsbksdxl\u002Fcodex-lark\u002Fskills\u002Flark-note\u002Freferences\u002Flark-note-detail.md",{"path":78,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Flark-note-transcript.md",1132,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fzlsbksdxl\u002Fcodex-lark\u002Fskills\u002Flark-note\u002Freferences\u002Flark-note-transcript.md",[82,92,100,108,116,124],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":86,"licenseFileUrl":87,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":91},"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.","MIT","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":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":86,"licenseFileUrl":96,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":91},"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":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":86,"licenseFileUrl":104,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":91},"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":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":86,"licenseFileUrl":112,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":91},"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":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":86,"licenseFileUrl":120,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":91},"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":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":86,"licenseFileUrl":128,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":91},"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",[],[]]