[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70CTXQCV7WQAE5EXM0K5AYF":3,"skill-same:01M70CTXQCV7WQAE5EXM0K5AYF":67},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":30,"commitSha":31,"skillDirectory":32,"forksCount":33,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":36,"ownerDescription":37,"updatedAt":38,"install":39,"resources":52},"01M70CTXQCV7WQAE5EXM0K5AYF","lark-vc-agent",null,"飞书视频会议：让机器人代当前用户加入\u002F离开正在进行的会议，并读取会议期间的实时事件（参会人加入与离开、发言、聊天、屏幕共享等）。1. 用户提供 9 位会议号、要求代为入会或离会时使用 +meeting-join \u002F +meeting-leave——会真实产生入会\u002F离会记录。2. 会议进行中用户想知道“谁加入了”“谁离开了”“谁在发言”“有人共享屏幕吗”等会中动态时，机器人入会后用 +meeting-events 读取事件时间线。3. 典型场景：参会机器人、会中助手、代为旁听、代为参会。前提：机器人只能读到它自己参会过且仍在进行中的会议的事件；查询已结束会议的参会名单、纪要或逐字稿请使用 lark-vc 技能。","EthanYoQ\u002FSkill-hub","EthanYoQ","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F257484394?v=4","01M70C9QKWR1YS0S7V26DNB18H","Ethan","01M70C9QMER047R5ANZZA6KC2P",11,"MIT","https:\u002F\u002Fgithub.com\u002FEthanYoQ\u002FSkill-hub\u002Fblob\u002Fmine\u002Farchives\u002Fuser-installed-skills\u002Flark-vc-agent\u002Fa0d3ed947ea8afc4\u002Flark-vc-agent\u002FSKILL.md",[],[],"2026-11-10 10:12:30",false,"---\nname: lark-vc-agent\nversion: 1.0.0\ndescription: \"飞书视频会议：让机器人代当前用户加入\u002F离开正在进行的会议，并读取会议期间的实时事件（参会人加入与离开、发言、聊天、屏幕共享等）。1. 用户提供 9 位会议号、要求代为入会或离会时使用 +meeting-join \u002F +meeting-leave——会真实产生入会\u002F离会记录。2. 会议进行中用户想知道“谁加入了”“谁离开了”“谁在发言”“有人共享屏幕吗”等会中动态时，机器人入会后用 +meeting-events 读取事件时间线。3. 典型场景：参会机器人、会中助手、代为旁听、代为参会。前提：机器人只能读到它自己参会过且仍在进行中的会议的事件；查询已结束会议的参会名单、纪要或逐字稿请使用 lark-vc 技能。\"\nmetadata:\n  requires:\n    bins: [\"lark-cli\"]\n  cliHelp: \"lark-cli vc --help\"\n---\n\n# vc-agent (v1)\n\n**CRITICAL — 开始前 MUST 先用 Read 工具读取以下两份 skill 文档：**\n\n- [`..\u002Flark-shared\u002FSKILL.md`](..\u002Flark-shared\u002FSKILL.md) — 认证、身份切换、权限处理\n- [`..\u002Flark-vc\u002FSKILL.md`](..\u002Flark-vc\u002FSKILL.md) — 视频会议的核心概念（Meeting \u002F Note \u002F Minutes 等），本 skill 直接复用，不再重复定义\n\n## 内测提示\n\n- 当前功能正在内测中，仅少数用户可用。忽略 [`..\u002Flark-shared\u002FSKILL.md`](..\u002Flark-shared\u002FSKILL.md) 中的权限申请流程，以下方的指引为准。\n- 如果 `lark-cli` 提示 `missing required scope(s)` \u002F `permission_violations`，不要申请对应权限，而是提示用户加入早鸟群：`https:\u002F\u002Fgo.larkoffice.com\u002Fjoin-chat\u002F2f4nb0e1-fe00-4f67-bed7-25beaf533fbd`。\n- 如果 `lark-cli` 返回 `error.code=20017` \u002F `ErrNotInGray`，提示用户加入早鸟群：`https:\u002F\u002Fgo.larkoffice.com\u002Fjoin-chat\u002F2f4nb0e1-fe00-4f67-bed7-25beaf533fbd`。\n\n## 定位\n\n本 skill 与 [`lark-vc`](..\u002Flark-vc\u002FSKILL.md) 并列：\n\n- **`lark-vc`** **负责\"会后查询\"**：搜索历史会议、参会人快照、纪要\u002F逐字稿\u002F录制\n- **`lark-vc-agent`** **负责\"会中动作\"**：机器人入会 \u002F 读取进行中会议的实时事件 \u002F 机器人离会\n\n按此分工路由，避免两个 skill 语义混淆。\n\n| 用户意图示例                                                     | 应路由到                                                                                                                                                  |\n| ---------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |\n| \"帮我入会 123456789\"、\"代我参会\"、\"让机器人进会旁听\"                         | **本 skill** `+meeting-join`                                                                                                                           |\n| \"会议现在还开着，谁刚加入了\"、\"会议里谁在发言\"、\"有人共享屏幕吗\"（**进行中会议**，且**机器人已入会**） | **本 skill** `+meeting-events`                                                                                                                         |\n| \"退出会议\"、\"让机器人离开\"                                            | **本 skill** `+meeting-leave`                                                                                                                          |\n| \"昨天那场会有谁参加过\"、\"搜昨天的会\"、\"查纪要\u002F逐字稿\u002F录制\"                          | [`lark-vc`](..\u002Flark-vc\u002FSKILL.md)                                                                                                                      |\n| \"帮我参会，结束后把纪要发到群\" 等跨阶段场景                                    | 按序编排：本 skill（入会 → 读事件 → 离会）→ [`lark-vc`](..\u002Flark-vc\u002FSKILL.md) \u002F [`lark-minutes`](..\u002Flark-minutes\u002FSKILL.md)（拉纪要）→ [`lark-im`](..\u002Flark-im\u002FSKILL.md)（发群） |\n\n## 核心场景\n\n### 1. 加入正在进行的会议（写操作）\n\n1. 只有用户明确表达\"让 Agent **真实入会**\"（参会机器人、会中助手、代为旁听、代参会）时才用 `+meeting-join`。只是查数据不要入会。\n2. `+meeting-join --meeting-number` 只接受 **9 位纯数字**会议号，不是会议链接整串、也不是 `meeting_id`。\n3. 返回体中的 `meeting.id` **必须立刻记录**——后续 `+meeting-events` \u002F `+meeting-leave` 都靠它，**不能用 9 位会议号替代**。\n4. 入会对所有参会人可见，执行前核实 9 位会议号来源，避免误入错会。\n5. 仅支持 `user` 身份，需提前 `lark-cli auth login`。\n6. 若入会失败，优先查看 `+meeting-join` reference 的错误排查段落，重点确认会议号、密码、会议状态、等候室 \u002F 审批以及会议是否禁止当前身份加入。\n\n### 2. 感知会中事件（读操作）\n\n1. 用户要看\"会议里正在发生什么\"（参会人加入\u002F离开、聊天、转写、屏幕共享）时，用 `+meeting-events`。\n2. 输入是 **`meeting_id`**（长数字 ID），不是 9 位会议号。\n3. Bot 必须**真实参会过**（先 `+meeting-join`），否则事件流通常不可见。具体的状态边界、结束后宽限窗口与错误码（如 `10005 \u002F 20001 \u002F 20002`）请查看 `+meeting-events` reference。\n4. **不能做会后复盘**，**不能替代参会人快照查询**。如果会议已结束：\n   - 想拿纪要文档或逐字稿文档 token：用 `lark-cli vc +notes --meeting-ids \u003Cmeeting.id>`\n   - 想拿 AI 产物（summary \u002F todos \u002F chapters）或导出逐字稿文件：先用 `lark-cli vc +recording --meeting-ids \u003Cmeeting.id>` 拿 `minute_token`，再用 `lark-cli vc +notes --minute-tokens \u003Cminute_token>`\n   - 想看参会人快照：用 `vc meeting get --with-participants`（见 [`lark-vc`](..\u002Flark-vc\u002FSKILL.md)）\n5. **默认必须使用** **`--page-all`**，除非用户明确要求“只查一页”，或确实需要控制返回体大小。\n6. 输出格式默认优先 `--format pretty`（时间线更易读）；只有在需要完整保留原始消息流与结构化字段时，才使用 `--format json`。\n7. **必须识别分页信号**：只要响应里出现 `has_more=true`、pretty 里的 `more available`，或返回了非空 `page_token`，就不能把当前结果当作完整事件流；默认应继续分页，或明确告诉用户当前只是部分结果。\n8. 保留响应里的 `page_token`，下次增量拉取直接续，不要从头再拉。\n9. **只要你是基于** **`+meeting-events`** **来回答一场正在进行中的会议内容，就不能直接复用旧结果。** 无论用户是在问“现在\u002F刚刚\u002F最新”的状态，还是让你“总结一下这个会议讲什么”，都必须先重新拉一次当前事件流，确认拿到的是最新信息，再基于最新结果回答。只有在用户明确要求基于某次历史快照继续分析时，才可以复用旧结果。\n\n### 3. 离开会议（写操作）\n\n1. 任务完成、或用户要求结束时，用 `+meeting-leave --meeting-id \u003C从 +meeting-join 拿到的 meeting.id>`。\n2. `--meeting-id` **必须**是 `+meeting-join` 返回的长数字 `meeting.id`，**不接受 9 位会议号**。\n3. 离会**立即生效**，机器人从会议的参会人列表中消失，对其他参会人可见；若需要重新入会，再跑一次 `+meeting-join` 即可（非真正\"不可逆\"）。\n4. 仅支持 `user` 身份。\n\n### 4. Agent 参会最小闭环示范\n\n```bash\n# 1. 入会，捕获 meeting.id\nJOIN=$(lark-cli vc +meeting-join --meeting-number 123456789 --format json)\nMID=$(echo \"$JOIN\" | jq -r '.data.meeting.id')\n\n# 2. 会中轮询事件\n#    默认用 --page-all 拉全当前可见事件；下次增量优先复用 page_token\n#    典型间隔 10-30 秒\nlark-cli vc +meeting-events --meeting-id \"$MID\" --page-all --format pretty\n\n# 3. 任务完成或用户要求结束时离会\nlark-cli vc +meeting-leave --meeting-id \"$MID\"\n\n# 4. 会后可选：取纪要 \u002F 逐字稿（跨到 lark-vc）\nlark-cli vc +notes --meeting-ids \"$MID\"\n```\n\n## Shortcuts\n\nShortcut 是对常用操作的高级封装（`lark-cli vc +\u003Cverb> [flags]`）。\n\n| Shortcut                                                        | 类型 | 说明                                                                         |\n| --------------------------------------------------------------- | -- | -------------------------------------------------------------------------- |\n| [`+meeting-join`](references\u002Flark-vc-agent-meeting-join.md)     | 写  | Join an in-progress meeting by 9-digit meeting number                      |\n| [`+meeting-events`](references\u002Flark-vc-agent-meeting-events.md) | 读  | List bot meeting events (participant joined\u002Fleft, transcript, chat, share) |\n| [`+meeting-leave`](references\u002Flark-vc-agent-meeting-leave.md)   | 写  | Leave a meeting by meeting\\_id                                             |\n\n- 使用 `+meeting-join` 前**必须**阅读 [references\u002Flark-vc-agent-meeting-join.md](references\u002Flark-vc-agent-meeting-join.md)，了解入参格式与写操作可见性风险。\n- 使用 `+meeting-events` 前**必须**阅读 [references\u002Flark-vc-agent-meeting-events.md](references\u002Flark-vc-agent-meeting-events.md)，了解 `meeting_id` 来源、分页、错误码（10005 \u002F 20001 \u002F 20002）与 \"bot 仍在会中\" 硬约束。\n- 使用 `+meeting-leave` 前**必须**阅读 [references\u002Flark-vc-agent-meeting-leave.md](references\u002Flark-vc-agent-meeting-leave.md)，了解 `meeting_id` 的来源与写操作可见性。\n\n## 权限表\n\n| Shortcut          | 所需 scope                       |\n| ----------------- | ------------------------------ |\n| `+meeting-join`   | `vc:meeting.bot.join:write`    |\n| `+meeting-events` | `vc:meeting.meetingevent:read` |\n| `+meeting-leave`  | `vc:meeting.bot.join:write`    |\n\n## 延伸\n\n- 查已结束会议、参会人快照、搜索历史会议 → [`lark-vc`](..\u002Flark-vc\u002FSKILL.md)\n- 会议纪要、逐字稿 → [`lark-vc`](..\u002Flark-vc\u002FSKILL.md) 的 `+notes`\n- 妙记产物（AI 总结 \u002F 转写 \u002F 章节）→ [`lark-minutes`](..\u002Flark-minutes\u002FSKILL.md)\n- 会后把产物发到群 \u002F 私聊 → [`lark-im`](..\u002Flark-im\u002FSKILL.md)\n- 认证、身份切换、scope 管理 → [`lark-shared`](..\u002Flark-shared\u002FSKILL.md)\n","# vc-agent (v1)\n\n**CRITICAL — 开始前 MUST 先用 Read 工具读取以下两份 skill 文档：**\n\n- [`..\u002Flark-shared\u002FSKILL.md`](..\u002Flark-shared\u002FSKILL.md) — 认证、身份切换、权限处理\n- [`..\u002Flark-vc\u002FSKILL.md`](..\u002Flark-vc\u002FSKILL.md) — 视频会议的核心概念（Meeting \u002F Note \u002F Minutes 等），本 skill 直接复用，不再重复定义\n\n## 内测提示\n\n- 当前功能正在内测中，仅少数用户可用。忽略 [`..\u002Flark-shared\u002FSKILL.md`](..\u002Flark-shared\u002FSKILL.md) 中的权限申请流程，以下方的指引为准。\n- 如果 `lark-cli` 提示 `missing required scope(s)` \u002F `permission_violations`，不要申请对应权限，而是提示用户加入早鸟群：`https:\u002F\u002Fgo.larkoffice.com\u002Fjoin-chat\u002F2f4nb0e1-fe00-4f67-bed7-25beaf533fbd`。\n- 如果 `lark-cli` 返回 `error.code=20017` \u002F `ErrNotInGray`，提示用户加入早鸟群：`https:\u002F\u002Fgo.larkoffice.com\u002Fjoin-chat\u002F2f4nb0e1-fe00-4f67-bed7-25beaf533fbd`。\n\n## 定位\n\n本 skill 与 [`lark-vc`](..\u002Flark-vc\u002FSKILL.md) 并列：\n\n- **`lark-vc`** **负责\"会后查询\"**：搜索历史会议、参会人快照、纪要\u002F逐字稿\u002F录制\n- **`lark-vc-agent`** **负责\"会中动作\"**：机器人入会 \u002F 读取进行中会议的实时事件 \u002F 机器人离会\n\n按此分工路由，避免两个 skill 语义混淆。\n\n| 用户意图示例                                                     | 应路由到                                                                                                                                                  |\n| ---------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |\n| \"帮我入会 123456789\"、\"代我参会\"、\"让机器人进会旁听\"                         | **本 skill** `+meeting-join`                                                                                                                           |\n| \"会议现在还开着，谁刚加入了\"、\"会议里谁在发言\"、\"有人共享屏幕吗\"（**进行中会议**，且**机器人已入会**） | **本 skill** `+meeting-events`                                                                                                                         |\n| \"退出会议\"、\"让机器人离开\"                                            | **本 skill** `+meeting-leave`                                                                                                                          |\n| \"昨天那场会有谁参加过\"、\"搜昨天的会\"、\"查纪要\u002F逐字稿\u002F录制\"                          | [`lark-vc`](..\u002Flark-vc\u002FSKILL.md)                                                                                                                      |\n| \"帮我参会，结束后把纪要发到群\" 等跨阶段场景                                    | 按序编排：本 skill（入会 → 读事件 → 离会）→ [`lark-vc`](..\u002Flark-vc\u002FSKILL.md) \u002F [`lark-minutes`](..\u002Flark-minutes\u002FSKILL.md)（拉纪要）→ [`lark-im`](..\u002Flark-im\u002FSKILL.md)（发群） |\n\n## 核心场景\n\n### 1. 加入正在进行的会议（写操作）\n\n1. 只有用户明确表达\"让 Agent **真实入会**\"（参会机器人、会中助手、代为旁听、代参会）时才用 `+meeting-join`。只是查数据不要入会。\n2. `+meeting-join --meeting-number` 只接受 **9 位纯数字**会议号，不是会议链接整串、也不是 `meeting_id`。\n3. 返回体中的 `meeting.id` **必须立刻记录**——后续 `+meeting-events` \u002F `+meeting-leave` 都靠它，**不能用 9 位会议号替代**。\n4. 入会对所有参会人可见，执行前核实 9 位会议号来源，避免误入错会。\n5. 仅支持 `user` 身份，需提前 `lark-cli auth login`。\n6. 若入会失败，优先查看 `+meeting-join` reference 的错误排查段落，重点确认会议号、密码、会议状态、等候室 \u002F 审批以及会议是否禁止当前身份加入。\n\n### 2. 感知会中事件（读操作）\n\n1. 用户要看\"会议里正在发生什么\"（参会人加入\u002F离开、聊天、转写、屏幕共享）时，用 `+meeting-events`。\n2. 输入是 **`meeting_id`**（长数字 ID），不是 9 位会议号。\n3. Bot 必须**真实参会过**（先 `+meeting-join`），否则事件流通常不可见。具体的状态边界、结束后宽限窗口与错误码（如 `10005 \u002F 20001 \u002F 20002`）请查看 `+meeting-events` reference。\n4. **不能做会后复盘**，**不能替代参会人快照查询**。如果会议已结束：\n   - 想拿纪要文档或逐字稿文档 token：用 `lark-cli vc +notes --meeting-ids \u003Cmeeting.id>`\n   - 想拿 AI 产物（summary \u002F todos \u002F chapters）或导出逐字稿文件：先用 `lark-cli vc +recording --meeting-ids \u003Cmeeting.id>` 拿 `minute_token`，再用 `lark-cli vc +notes --minute-tokens \u003Cminute_token>`\n   - 想看参会人快照：用 `vc meeting get --with-participants`（见 [`lark-vc`](..\u002Flark-vc\u002FSKILL.md)）\n5. **默认必须使用** **`--page-all`**，除非用户明确要求“只查一页”，或确实需要控制返回体大小。\n6. 输出格式默认优先 `--format pretty`（时间线更易读）；只有在需要完整保留原始消息流与结构化字段时，才使用 `--format json`。\n7. **必须识别分页信号**：只要响应里出现 `has_more=true`、pretty 里的 `more available`，或返回了非空 `page_token`，就不能把当前结果当作完整事件流；默认应继续分页，或明确告诉用户当前只是部分结果。\n8. 保留响应里的 `page_token`，下次增量拉取直接续，不要从头再拉。\n9. **只要你是基于** **`+meeting-events`** **来回答一场正在进行中的会议内容，就不能直接复用旧结果。** 无论用户是在问“现在\u002F刚刚\u002F最新”的状态，还是让你“总结一下这个会议讲什么”，都必须先重新拉一次当前事件流，确认拿到的是最新信息，再基于最新结果回答。只有在用户明确要求基于某次历史快照继续分析时，才可以复用旧结果。\n\n### 3. 离开会议（写操作）\n\n1. 任务完成、或用户要求结束时，用 `+meeting-leave --meeting-id \u003C从 +meeting-join 拿到的 meeting.id>`。\n2. `--meeting-id` **必须**是 `+meeting-join` 返回的长数字 `meeting.id`，**不接受 9 位会议号**。\n3. 离会**立即生效**，机器人从会议的参会人列表中消失，对其他参会人可见；若需要重新入会，再跑一次 `+meeting-join` 即可（非真正\"不可逆\"）。\n4. 仅支持 `user` 身份。\n\n### 4. Agent 参会最小闭环示范\n\n```bash\n# 1. 入会，捕获 meeting.id\nJOIN=$(lark-cli vc +meeting-join --meeting-number 123456789 --format json)\nMID=$(echo \"$JOIN\" | jq -r '.data.meeting.id')\n\n# 2. 会中轮询事件\n#    默认用 --page-all 拉全当前可见事件；下次增量优先复用 page_token\n#    典型间隔 10-30 秒\nlark-cli vc +meeting-events --meeting-id \"$MID\" --page-all --format pretty\n\n# 3. 任务完成或用户要求结束时离会\nlark-cli vc +meeting-leave --meeting-id \"$MID\"\n\n# 4. 会后可选：取纪要 \u002F 逐字稿（跨到 lark-vc）\nlark-cli vc +notes --meeting-ids \"$MID\"\n```\n\n## Shortcuts\n\nShortcut 是对常用操作的高级封装（`lark-cli vc +\u003Cverb> [flags]`）。\n\n| Shortcut                                                        | 类型 | 说明                                                                         |\n| --------------------------------------------------------------- | -- | -------------------------------------------------------------------------- |\n| [`+meeting-join`](references\u002Flark-vc-agent-meeting-join.md)     | 写  | Join an in-progress meeting by 9-digit meeting number                      |\n| [`+meeting-events`](references\u002Flark-vc-agent-meeting-events.md) | 读  | List bot meeting events (participant joined\u002Fleft, transcript, chat, share) |\n| [`+meeting-leave`](references\u002Flark-vc-agent-meeting-leave.md)   | 写  | Leave a meeting by meeting\\_id                                             |\n\n- 使用 `+meeting-join` 前**必须**阅读 [references\u002Flark-vc-agent-meeting-join.md](references\u002Flark-vc-agent-meeting-join.md)，了解入参格式与写操作可见性风险。\n- 使用 `+meeting-events` 前**必须**阅读 [references\u002Flark-vc-agent-meeting-events.md](references\u002Flark-vc-agent-meeting-events.md)，了解 `meeting_id` 来源、分页、错误码（10005 \u002F 20001 \u002F 20002）与 \"bot 仍在会中\" 硬约束。\n- 使用 `+meeting-leave` 前**必须**阅读 [references\u002Flark-vc-agent-meeting-leave.md](references\u002Flark-vc-agent-meeting-leave.md)，了解 `meeting_id` 的来源与写操作可见性。\n\n## 权限表\n\n| Shortcut          | 所需 scope                       |\n| ----------------- | ------------------------------ |\n| `+meeting-join`   | `vc:meeting.bot.join:write`    |\n| `+meeting-events` | `vc:meeting.meetingevent:read` |\n| `+meeting-leave`  | `vc:meeting.bot.join:write`    |\n\n## 延伸\n\n- 查已结束会议、参会人快照、搜索历史会议 → [`lark-vc`](..\u002Flark-vc\u002FSKILL.md)\n- 会议纪要、逐字稿 → [`lark-vc`](..\u002Flark-vc\u002FSKILL.md) 的 `+notes`\n- 妙记产物（AI 总结 \u002F 转写 \u002F 章节）→ [`lark-minutes`](..\u002Flark-minutes\u002FSKILL.md)\n- 会后把产物发到群 \u002F 私聊 → [`lark-im`](..\u002Flark-im\u002FSKILL.md)\n- 认证、身份切换、scope 管理 → [`lark-shared`](..\u002Flark-shared\u002FSKILL.md)\n",{"name":5,"version":24,"metadata":25,"description":7},"1.0.0",{"cliHelp":26,"requires":27},"lark-cli vc --help",{"bins":28},[29],"lark-cli","mine","1e7390741dffd3d5041fca4ebc056071ee3ba137","archives\u002Fuser-installed-skills\u002Flark-vc-agent\u002Fa0d3ed947ea8afc4\u002Flark-vc-agent",5,"https:\u002F\u002Fgithub.com\u002FEthanYoQ\u002FSkill-hub","https:\u002F\u002Fgithub.com\u002FEthanYoQ","www.orz.md","Part Marketer, Part AI Explorer.","2026-11-07 14:52:29",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add EthanYoQ\u002FSkill-hub --skill lark-vc-agent",{"tool":45,"command":46},"bunx","bunx skills add EthanYoQ\u002FSkill-hub --skill lark-vc-agent",{"tool":48,"command":49},"pnpm","pnpm dlx skills add EthanYoQ\u002FSkill-hub --skill lark-vc-agent","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FEthanYoQ\u002FSkill-hub\u002Fblob\u002Fmine\u002Farchives\u002Fuser-installed-skills\u002Flark-vc-agent\u002Fa0d3ed947ea8afc4\u002Flark-vc-agent\u002FSKILL.md",true,[53,59,63],{"path":54,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Flark-vc-agent-meeting-events.md","REFERENCE","参考文档",13981,"https:\u002F\u002Fgithub.com\u002FEthanYoQ\u002FSkill-hub\u002Fblob\u002Fmine\u002Farchives\u002Fuser-installed-skills\u002Flark-vc-agent\u002Fa0d3ed947ea8afc4\u002Flark-vc-agent\u002Freferences\u002Flark-vc-agent-meeting-events.md",{"path":60,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002Flark-vc-agent-meeting-join.md",6280,"https:\u002F\u002Fgithub.com\u002FEthanYoQ\u002FSkill-hub\u002Fblob\u002Fmine\u002Farchives\u002Fuser-installed-skills\u002Flark-vc-agent\u002Fa0d3ed947ea8afc4\u002Flark-vc-agent\u002Freferences\u002Flark-vc-agent-meeting-join.md",{"path":64,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":65,"sourceHtmlUrl":66},"references\u002Flark-vc-agent-meeting-leave.md",4384,"https:\u002F\u002Fgithub.com\u002FEthanYoQ\u002FSkill-hub\u002Fblob\u002Fmine\u002Farchives\u002Fuser-installed-skills\u002Flark-vc-agent\u002Fa0d3ed947ea8afc4\u002Flark-vc-agent\u002Freferences\u002Flark-vc-agent-meeting-leave.md",[68,100,131,155,173,188],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":79,"publishedAt":19},"01M713CBDSYARG4PXFXK2R2NNN","xhs-pharma-social-listening","Run evidence-disciplined Xiaohongshu social listening for foreign pharma employee pain points. Use when the user asks to collect and analyze notes\u002Fcomments about pharma companies, aliases, roles, compliance, medical affairs, or AI topics, then produce a cited and scored sampled-insight report. Includes independent-evidence counting, MediaCrawler batch collection, and CAPTCHA\u002F461 fallback to Agent Reach\u002FOpenCLI.","https:\u002F\u002Fgithub.com\u002FEthanYoQ\u002FSkill-hub\u002Fblob\u002Fmine\u002Fskills\u002F10-business-industry\u002Fxhs-pharma-social-listening\u002FSKILL.md",[74],{"categoryNo":75,"categoryName":76,"taxonomyType":77,"taxonomyTypeDesc":78},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[80,81,82,83,84,85,86,87,88,89,90,91,92,93,94,95,96,97,98,99],"social","xhs pharma social listening","social listening","xhs","medical","counting","when","collection","batch","analyze","notes","run","opencli","fallback","captcha","agent reach","evidence","for","collect","produce",{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":112,"publishedAt":19},"01M713C8Q76ZP0WXXBRAFKS6EE","healthcare-phi-compliance","Protected Health Information (PHI) and Personally Identifiable Information (PII) compliance patterns for healthcare applications. Covers data classification, access control, audit trails, encryption, and common leak vectors. Use when code touches PHI or PII in a healthcare system, or when auditing access control, audit trails, or leak vectors.","https:\u002F\u002Fgithub.com\u002FEthanYoQ\u002FSkill-hub\u002Fblob\u002Fmine\u002Fskills\u002F10-business-industry\u002Fhealthcare-phi-compliance\u002FSKILL.md",[106,107],{"categoryNo":75,"categoryName":76,"taxonomyType":77,"taxonomyTypeDesc":78},{"categoryNo":108,"categoryName":109,"taxonomyType":110,"taxonomyTypeDesc":111},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[113,114,115,116,117,118,119,120,86,121,122,123,124,125,126,127,97,128,129,130],"healthcare","phi","compliance","healthcare phi compliance","pii","compliance patterns","information","access","encryption","code","common","audit","data","patterns","Access Control","system","applications","Auditing Access Control",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":138,"publishedAt":19},"01M713C5R2GE43X45T2K75TB76","healthcare-eval-harness","Patient safety evaluation harness for healthcare application deployments. Automated test suites for CDSS accuracy, PHI exposure, clinical workflow integrity, and integration compliance. Blocks deployments on safety failures. Use when a healthcare deployment must be gated on patient-safety tests for CDSS accuracy, PHI exposure, and workflow integrity.","https:\u002F\u002Fgithub.com\u002FEthanYoQ\u002FSkill-hub\u002Fblob\u002Fmine\u002Fskills\u002F10-business-industry\u002Fhealthcare-eval-harness\u002FSKILL.md",[137],{"categoryNo":75,"categoryName":76,"taxonomyType":77,"taxonomyTypeDesc":78},[113,139,140,141,142,143,144,86,145,146,147,148,114,97,149,150,151,152,153,154],"eval","harness","healthcare eval harness","eval harness","clinical","patient","workflow","Evaluation","Safety","integrity","deployment","accuracy","tests","deployments","use","super",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":162,"publishedAt":19},"01M713C2J17S91VYR7A8M696VR","healthcare-emr-patterns","EMR\u002FEHR development patterns for healthcare applications. Clinical safety, encounter workflows, prescription generation, clinical decision support integration, and accessibility-first UI for medical data entry. Use when building EMR or EHR features such as encounter workflows, prescription generation, or clinical data entry UI.","https:\u002F\u002Fgithub.com\u002FEthanYoQ\u002FSkill-hub\u002Fblob\u002Fmine\u002Fskills\u002F10-business-industry\u002Fhealthcare-emr-patterns\u002FSKILL.md",[161],{"categoryNo":75,"categoryName":76,"taxonomyType":77,"taxonomyTypeDesc":78},[113,163,126,164,165,84,143,166,86,167,168,169,147,125,170,171,172,97,129,153],"EMR","healthcare emr patterns","decision","workflows","support","clinical decision support","features","ui","as","development",{"skillNo":174,"name":175,"nameZh":6,"description":176,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":177,"categories":178,"keywords":180,"publishedAt":19},"01M713BZERTXV0N8X6SW9DDVWZ","healthcare-cdss-patterns","Clinical Decision Support System (CDSS) development patterns. Drug interaction checking, dose validation, clinical scoring (NEWS2, qSOFA), alert severity classification, and integration into EMR workflows. Use when building clinical decision support — drug interaction checks, dose validation, clinical scoring, or alert severity.","https:\u002F\u002Fgithub.com\u002FEthanYoQ\u002FSkill-hub\u002Fblob\u002Fmine\u002Fskills\u002F10-business-industry\u002Fhealthcare-cdss-patterns\u002FSKILL.md",[179],{"categoryNo":75,"categoryName":76,"taxonomyType":77,"taxonomyTypeDesc":78},[113,126,181,165,143,163,166,86,182,183,167,168,184,172,128,185,153,186,154,187],"healthcare cdss patterns","scoring","interaction","severity","classification","alert","decision support",{"skillNo":189,"name":190,"nameZh":6,"description":191,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":192,"categories":193,"keywords":195,"publishedAt":19},"01M713BVK3PQR7V4ZKYGMWMXJD","dxy-task-clarify","用户的请求含糊、缺背景、缺资料说明、缺读者或用途时使用。先用少量带选项的追问把任务问清楚，写成任务卡，用户确认后再执行。尤其适用于医生、科研人员和药企各岗位的工作，例如「帮我分析一下这些数据」「帮我准备明天的拜访」「写个总结」「做个 PPT」「回一下这封邮件」「整理一下会议纪要」「整理一下这些文献」「帮我准备下周的讲课」「写个病例汇报」「帮我写个提示词」。用户说「先问我」「帮我理清需求」「我不知道怎么描述」「我不会问 AI」时也使用。用途、资料、读者都已说清的请求，纯翻译，以及写代码、改代码，不使用。","https:\u002F\u002Fgithub.com\u002FEthanYoQ\u002FSkill-hub\u002Fblob\u002Fmine\u002Fskills\u002F10-business-industry\u002Fdxy-task-clarify\u002FSKILL.md",[194],{"categoryNo":75,"categoryName":76,"taxonomyType":77,"taxonomyTypeDesc":78},[196,197,198,199,200,201,202,203],"clarify","dxy task clarify","task","pptx","整理","翻译","数据","总结"]