[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JVGWSNTHZTPSTPYG9FXKFW":3,"skill-same:01M6JVGWSNTHZTPSTPYG9FXKFW":64},{"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":33,"linkOnly":34,"markdownContent":35,"markdownBody":36,"frontMatter":37,"refName":40,"commitSha":41,"skillDirectory":42,"forksCount":43,"repositoryHtmlUrl":44,"repositoryHomepageUrl":45,"ownerHtmlUrl":46,"ownerBlogUrl":47,"ownerDescription":48,"updatedAt":49,"install":50,"resources":63},"01M6JVGWSNTHZTPSTPYG9FXKFW","workflow-forensics",null,"对失败或卡住的团队工作流进行事后调查：时间线重建、角色交接审计、 产出缺失定位、重复循环检测和根因归类。 与 systematic-debugging（代码级调试）互补，本 skill 面向工作流级诊断。","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\u002FColin4k1024\u002Ftsp\u002Fskills\u002Fworkflow-forensics\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32],"workflow","forensics","workflow forensics","debugging","harness","engineering","systematic","gsd","systematic-debugging","2026-11-10 10:12:30",false,"---\nname: workflow-forensics\ndescription: >\n  对失败或卡住的团队工作流进行事后调查：时间线重建、角色交接审计、\n  产出缺失定位、重复循环检测和根因归类。\n  与 systematic-debugging（代码级调试）互补，本 skill 面向工作流级诊断。\norigin: gsd-forensics + harness-engineering\n---\n\n# Workflow Forensics\n\n## 用途\n\n- 当一个团队工作流（`\u002Fteam-*` 链路）失败、卡住、超时或产出不符合预期时，进行 **结构化事后调查**。\n- 重建工作流时间线，定位失败点，区分 **流程问题**（角色交接缺失、产出缺失、门禁跳过）和 **技术问题**（代码错误、环境故障）。\n- 为 `tech-lead` 提供可操作的诊断报告，而不是模糊的\"某步出了问题\"。\n\n## 触发信号\n\n- `\u002Fteam-execute` 或 `\u002Fteam-review` 连续 2 次以上未能推进。\n- 角色之间 handoff 被拒绝或回退。\n- 同一任务在 `\u002Fteam-plan` 和 `\u002Fteam-execute` 之间来回超过 2 次。\n- 发布后发现关键产出缺失（如无 test-plan、无 deployment-context）。\n- 线上事故调查需要追溯\"哪一步遗漏了什么\"。\n- agent 在自主循环中陷入重复（同一工具调用 > 3 次无进展）。\n\n## 调查流程\n\n### Phase 1: 证据收集\n\n```\n收集来源：\n├── docs\u002Fartifacts\u002F{slug}\u002F     → 正式产出文件\n├── docs\u002Fmemory\u002Fsessions\u002F      → 会话日志\n├── docs\u002Fmemory\u002Fdecisions.md   → 决策记录\n├── STATE.md                   → 运行时状态\n├── HANDOFF.json               → 暂停\u002F恢复快照\n├── git log --oneline -20      → 最近提交历史\n└── .claude\u002Fmemory\u002F            → agent 记忆文件\n```\n\n**收集约束：**\n- 不读不相关任务的文件——按 `{slug}` 限定范围。\n- 对每个证据源标注 **时间戳** 和 **产出角色**。\n\n### Phase 2: 时间线重建\n\n按时间顺序列出所有工作流事件：\n\n```markdown\n## 工作流时间线\n\n| # | 时间 | 事件 | 角色 | 产出 | 状态 |\n|---|------|------|------|------|------|\n| 1 | T1 | \u002Fteam-intake 完成 | tech-lead | PRD draft | ✅ |\n| 2 | T2 | handoff → architect | tech-lead | handoff record | ✅ |\n| 3 | T3 | arch-design 开始 | architect | — | ⏳ |\n| 4 | T4 | arch-design 阻塞 | architect | — | ❌ 缺依赖 |\n| 5 | T5 | 回退到 tech-lead | architect | escalation | ? |\n```\n\n### Phase 3: 失败模式识别\n\n对照以下常见失败模式检查时间线：\n\n| 失败模式 | 症状 | 根因类别 |\n|----------|------|----------|\n| **Handoff 断裂** | 角色交接记录缺失或不完整 | 流程 |\n| **产出缺失** | 应有 artifact 不存在或为空 | 流程 |\n| **门禁跳过** | 未通过 quality gate 就推进到下一阶段 | 流程 |\n| **循环陷阱** | 同一步骤反复执行 > 2 次无进展 | 流程 \u002F 技术 |\n| **范围蠕变** | 执行阶段的产出超出计划范围 | 需求 |\n| **依赖阻塞** | 等待外部输入或其他角色产出 | 协调 |\n| **上下文丢失** | 关键决策在会话中丢失未落盘 | 上下文 |\n| **工具失败** | 构建\u002F测试\u002F部署工具连续失败 | 技术 |\n| **权限\u002F环境** | 环境配置、权限、依赖不可用 | 基础设施 |\n\n### Phase 4: 根因定位\n\n```\n对每个识别到的失败模式：\n1. 标注第一次出现的时间线位置\n2. 追溯：该位置之前最后一个正常状态是什么\n3. 差异：正常 → 异常之间发生了什么变化\n4. 归类：流程 \u002F 需求 \u002F 协调 \u002F 上下文 \u002F 技术 \u002F 基础设施\n5. 影响：该失败导致了后续哪些连锁问题\n```\n\n### Phase 5: 诊断报告\n\n输出格式：\n\n```markdown\n# Workflow Forensics Report — {slug}\n\n## 概览\n- 调查对象: {task\u002Fslug}\n- 调查时间: {ISO timestamp}\n- 调查触发: {触发原因}\n- 严重程度: Critical \u002F High \u002F Medium \u002F Low\n\n## 时间线\n（Phase 2 的表格）\n\n## 失败模式\n| 模式 | 位置 | 根因类别 | 严重程度 |\n|------|------|----------|----------|\n\n## 根因分析\n### 根因 1: {名称}\n- 第一次出现: 时间线 #{N}\n- 最后正常状态: ...\n- 变化点: ...\n- 类别: ...\n- 连锁影响: ...\n\n## 建议措施\n| # | 措施 | 目标 | Owner | 优先级 |\n|---|------|------|-------|--------|\n\n## 预防建议\n- 流程改进: ...\n- 工具改进: ...\n- 文档改进: ...\n```\n\n## 与既有能力的关系\n\n| 能力 | 关注层 | 关系 |\n|------|--------|------|\n| `systematic-debugging` | 代码级根因 | 互补：forensics 定位到技术根因后交给 debugging |\n| `error-experience-library` | 错误模式复用 | 互补：forensics 发现的模式可录入经验库 |\n| `escalation-policy` | 升级决策 | 互补：forensics 为升级提供证据 |\n| `incident-brief` | 事故模板 | 互补：forensics 报告可填充 incident brief |\n\n## 自动化检查（快速模式）\n\n当不需要完整调查时，可运行快速检查：\n\n```\n快速检查清单（\u003C 5 分钟）：\n□ docs\u002Fartifacts\u002F{slug}\u002F 下是否有 PRD、arch-design、execute-log\n□ 每个 handoff 记录是否包含完整字段（handoff-contract.md）\n□ STATE.md 最后更新时间是否 > 24h 前\n□ git log 是否有与 {slug} 相关的提交\n□ 是否有未解决的阻塞项\n```\n\n## 配套约束\n\n1. 诊断报告存放到 `docs\u002Fartifacts\u002F{slug}\u002Fforensics-report.md`。\n2. 诊断结论中的预防建议如果涉及流程变更，必须通过 `tech-lead` 确认后才能修改规则或模板。\n3. 涉及代码级问题时，转交 `systematic-debugging` 或相应角色，不在 forensics 中直接修代码。\n4. 调查过程中发现的可复用失败模式，录入 `error-experience-library`。\n5. 不做\"谁的错\"的归责——聚焦于\"哪一步断了\" + \"怎么防止再断\"。\n\n## 验证标准\n\n- [ ] 时间线覆盖从 intake 到当前的所有工作流事件\n- [ ] 每个失败模式都有明确的根因类别和时间线定位\n- [ ] 建议措施有明确 Owner 和优先级\n- [ ] 报告已存档到 `docs\u002Fartifacts\u002F{slug}\u002F`\n- [ ] 可复用模式已录入 error-experience-library（如适用）\n","# Workflow Forensics\n\n## 用途\n\n- 当一个团队工作流（`\u002Fteam-*` 链路）失败、卡住、超时或产出不符合预期时，进行 **结构化事后调查**。\n- 重建工作流时间线，定位失败点，区分 **流程问题**（角色交接缺失、产出缺失、门禁跳过）和 **技术问题**（代码错误、环境故障）。\n- 为 `tech-lead` 提供可操作的诊断报告，而不是模糊的\"某步出了问题\"。\n\n## 触发信号\n\n- `\u002Fteam-execute` 或 `\u002Fteam-review` 连续 2 次以上未能推进。\n- 角色之间 handoff 被拒绝或回退。\n- 同一任务在 `\u002Fteam-plan` 和 `\u002Fteam-execute` 之间来回超过 2 次。\n- 发布后发现关键产出缺失（如无 test-plan、无 deployment-context）。\n- 线上事故调查需要追溯\"哪一步遗漏了什么\"。\n- agent 在自主循环中陷入重复（同一工具调用 > 3 次无进展）。\n\n## 调查流程\n\n### Phase 1: 证据收集\n\n```\n收集来源：\n├── docs\u002Fartifacts\u002F{slug}\u002F     → 正式产出文件\n├── docs\u002Fmemory\u002Fsessions\u002F      → 会话日志\n├── docs\u002Fmemory\u002Fdecisions.md   → 决策记录\n├── STATE.md                   → 运行时状态\n├── HANDOFF.json               → 暂停\u002F恢复快照\n├── git log --oneline -20      → 最近提交历史\n└── .claude\u002Fmemory\u002F            → agent 记忆文件\n```\n\n**收集约束：**\n- 不读不相关任务的文件——按 `{slug}` 限定范围。\n- 对每个证据源标注 **时间戳** 和 **产出角色**。\n\n### Phase 2: 时间线重建\n\n按时间顺序列出所有工作流事件：\n\n```markdown\n## 工作流时间线\n\n| # | 时间 | 事件 | 角色 | 产出 | 状态 |\n|---|------|------|------|------|------|\n| 1 | T1 | \u002Fteam-intake 完成 | tech-lead | PRD draft | ✅ |\n| 2 | T2 | handoff → architect | tech-lead | handoff record | ✅ |\n| 3 | T3 | arch-design 开始 | architect | — | ⏳ |\n| 4 | T4 | arch-design 阻塞 | architect | — | ❌ 缺依赖 |\n| 5 | T5 | 回退到 tech-lead | architect | escalation | ? |\n```\n\n### Phase 3: 失败模式识别\n\n对照以下常见失败模式检查时间线：\n\n| 失败模式 | 症状 | 根因类别 |\n|----------|------|----------|\n| **Handoff 断裂** | 角色交接记录缺失或不完整 | 流程 |\n| **产出缺失** | 应有 artifact 不存在或为空 | 流程 |\n| **门禁跳过** | 未通过 quality gate 就推进到下一阶段 | 流程 |\n| **循环陷阱** | 同一步骤反复执行 > 2 次无进展 | 流程 \u002F 技术 |\n| **范围蠕变** | 执行阶段的产出超出计划范围 | 需求 |\n| **依赖阻塞** | 等待外部输入或其他角色产出 | 协调 |\n| **上下文丢失** | 关键决策在会话中丢失未落盘 | 上下文 |\n| **工具失败** | 构建\u002F测试\u002F部署工具连续失败 | 技术 |\n| **权限\u002F环境** | 环境配置、权限、依赖不可用 | 基础设施 |\n\n### Phase 4: 根因定位\n\n```\n对每个识别到的失败模式：\n1. 标注第一次出现的时间线位置\n2. 追溯：该位置之前最后一个正常状态是什么\n3. 差异：正常 → 异常之间发生了什么变化\n4. 归类：流程 \u002F 需求 \u002F 协调 \u002F 上下文 \u002F 技术 \u002F 基础设施\n5. 影响：该失败导致了后续哪些连锁问题\n```\n\n### Phase 5: 诊断报告\n\n输出格式：\n\n```markdown\n# Workflow Forensics Report — {slug}\n\n## 概览\n- 调查对象: {task\u002Fslug}\n- 调查时间: {ISO timestamp}\n- 调查触发: {触发原因}\n- 严重程度: Critical \u002F High \u002F Medium \u002F Low\n\n## 时间线\n（Phase 2 的表格）\n\n## 失败模式\n| 模式 | 位置 | 根因类别 | 严重程度 |\n|------|------|----------|----------|\n\n## 根因分析\n### 根因 1: {名称}\n- 第一次出现: 时间线 #{N}\n- 最后正常状态: ...\n- 变化点: ...\n- 类别: ...\n- 连锁影响: ...\n\n## 建议措施\n| # | 措施 | 目标 | Owner | 优先级 |\n|---|------|------|-------|--------|\n\n## 预防建议\n- 流程改进: ...\n- 工具改进: ...\n- 文档改进: ...\n```\n\n## 与既有能力的关系\n\n| 能力 | 关注层 | 关系 |\n|------|--------|------|\n| `systematic-debugging` | 代码级根因 | 互补：forensics 定位到技术根因后交给 debugging |\n| `error-experience-library` | 错误模式复用 | 互补：forensics 发现的模式可录入经验库 |\n| `escalation-policy` | 升级决策 | 互补：forensics 为升级提供证据 |\n| `incident-brief` | 事故模板 | 互补：forensics 报告可填充 incident brief |\n\n## 自动化检查（快速模式）\n\n当不需要完整调查时，可运行快速检查：\n\n```\n快速检查清单（\u003C 5 分钟）：\n□ docs\u002Fartifacts\u002F{slug}\u002F 下是否有 PRD、arch-design、execute-log\n□ 每个 handoff 记录是否包含完整字段（handoff-contract.md）\n□ STATE.md 最后更新时间是否 > 24h 前\n□ git log 是否有与 {slug} 相关的提交\n□ 是否有未解决的阻塞项\n```\n\n## 配套约束\n\n1. 诊断报告存放到 `docs\u002Fartifacts\u002F{slug}\u002Fforensics-report.md`。\n2. 诊断结论中的预防建议如果涉及流程变更，必须通过 `tech-lead` 确认后才能修改规则或模板。\n3. 涉及代码级问题时，转交 `systematic-debugging` 或相应角色，不在 forensics 中直接修代码。\n4. 调查过程中发现的可复用失败模式，录入 `error-experience-library`。\n5. 不做\"谁的错\"的归责——聚焦于\"哪一步断了\" + \"怎么防止再断\"。\n\n## 验证标准\n\n- [ ] 时间线覆盖从 intake 到当前的所有工作流事件\n- [ ] 每个失败模式都有明确的根因类别和时间线定位\n- [ ] 建议措施有明确 Owner 和优先级\n- [ ] 报告已存档到 `docs\u002Fartifacts\u002F{slug}\u002F`\n- [ ] 可复用模式已录入 error-experience-library（如适用）\n",{"name":5,"origin":38,"description":39},"gsd-forensics + harness-engineering","对失败或卡住的团队工作流进行事后调查：时间线重建、角色交接审计、 产出缺失定位、重复循环检测和根因归类。 与 systematic-debugging（代码级调试）互补，本 skill 面向工作流级诊断。\n","main","b0f0a87593c578a7898eccaf1b363f7f87c1f99b","plugins\u002FColin4k1024\u002Ftsp\u002Fskills\u002Fworkflow-forensics",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":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill workflow-forensics",{"tool":56,"command":57},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill workflow-forensics",{"tool":59,"command":60},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill workflow-forensics","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FColin4k1024\u002Ftsp\u002Fskills\u002Fworkflow-forensics\u002FSKILL.md",true,[],[65,75,83,91,99,107],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":69,"licenseFileUrl":70,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":74},"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":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":69,"licenseFileUrl":79,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":74},"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":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":69,"licenseFileUrl":87,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":74},"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":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":69,"licenseFileUrl":95,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":74},"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":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":69,"licenseFileUrl":103,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":74},"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":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":69,"licenseFileUrl":111,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":74},"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",[],[]]