[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M795P44P35CGJPYD4JWMY0WM":3,"skill-same:01M795P44P35CGJPYD4JWMY0WM":147},{"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":41,"commitSha":42,"skillDirectory":43,"forksCount":14,"repositoryHtmlUrl":44,"repositoryHomepageUrl":6,"ownerHtmlUrl":45,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":46,"install":47,"resources":60},"01M795P44P35CGJPYD4JWMY0WM","crossframe-org",null,"Use when CrossFrame Suite routes explicit Chinese analysis of teams, projects, organizations, responsibility chains, feedback write-back, repair, or retrospectives.","Elogic360\u002Fsoftware-factory","Elogic360","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F156535519?v=4","01M74NH3F0RB13PWB7JZDE2V80","elogic360","01M74NH3FPC65082MDZVMFHDM3",0,"MIT","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fintegrations\u002Fantigravity-skills\u002Fskills\u002Fcrossframe-org\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: crossframe-org\ndescription: \"Use when CrossFrame Suite routes explicit Chinese analysis of teams, projects, organizations, responsibility chains, feedback write-back, repair, or retrospectives.\"\ncategory: business\nrisk: safe\nsource: community\nsource_repo: xi-kari\u002Fcrossframe-skill\nsource_type: community\ndate_added: 2026-06-16\nauthor: xi-kari\nlicense: MIT\nlicense_source: https:\u002F\u002Fgithub.com\u002Fxi-kari\u002Fcrossframe-skill\u002Fblob\u002Fmain\u002FLICENSE\ntools:\n  - \"Agent Skills\"\n  - Codex\n  - Claude\ntags:\n  - crossframe\n  - chinese\n  - organization\n  - retrospective\n  - repair\n---\n# CrossFrame Org\n\n\n\n## When to Use This Skill\n\n- Use when `crossframe-suite` routes an explicit CrossFrame task about teams, projects, organizations, responsibility chains, authority chains, feedback write-back, retrospectives, or repair.\n- Use when an organizational failure needs mechanism candidates rather than personality judgment.\n- Do not use independently unless the user explicitly names this sibling skill.\n\n## Packaged Source Note\n\nThis AAS-ready copy preserves the original CrossFrame skill body below. Chinese remains the canonical semantic layer; English metadata is only for discovery, installation, and repository review.\n\n## Limitations\n\n- The skill body is intentionally Chinese-canonical; English metadata is for discovery and does not replace the original Chinese terms.\n- Use only after explicit CrossFrame invocation or `crossframe-suite` routing; do not apply it as a generic default reasoning layer.\n- It structures analysis, drafting, and review, but does not replace source verification, domain expertise, or legal, medical, or financial judgment.\n\n> **本 skill 不独立触发。** 所有 CrossFrame 任务统一从 `crossframe-suite` 入口调度。用户无需直接调用本 skill；suite 根据路由规则在需要时自动加载。\n\n如果组织修复判断之后要写文章、沉淀案例、做辩论或评审输出，先读取 `..\u002Fcrossframe-suite\u002FSKILL.md` 做总调度；本 skill 只负责团队、项目和组织修复专项。\n\nCrossFrame Org 是 `crossframe` 的平行组织修复 skill，不替代 canonical `crossframe`，也不复制 CrossFrame 全文。它把 CrossFrame 的事实闸、尺度闸、责任闸、机制候选和概念保真，转成团队、项目、组织场景里的可执行修复备忘录。\n\n中文是权威语义。英文只用于 skill id、文件名或必要的外部接口；不要把“承接、回流、责任链、授权链、修复副产品、停止错误加速”翻译后再反向理解。\n\n## 必须执行的顺序\n\n1. 判断输出类型：组织诊断备忘录、反馈写回方案、复盘改造建议、低风险试点计划，或组合输出。\n2. 读取 `..\u002Fcrossframe\u002FSKILL.md`。\n3. 读取 `..\u002Fcrossframe\u002Freferences\u002Fread-routing-map.md`，确定本次需要加载的 canonical protocol、worksheet、concept card 和模板。\n4. 如果组织判断触发高责任、公共制度、亲密关系、长期演化、框架治理、AI 现实验证、弱信号\u002F不透明、无法退出、工具化、隐喻\u002F来源透明或文章输出，必须追加读取 `..\u002Fcrossframe\u002Freferences\u002Fcontinuity-bundles.md`，并按需使用 `..\u002Fcrossframe\u002Fworksheets\u002Fsource-continuity-check.md`；未完成联读时只能降档。\n5. 复用 `..\u002Fcrossframe\u002Ftemplates\u002Fread-state-capsule.md` 规定的 `v5-read-state-capsule`，并在高责任、公共、AI\u002F过程性产物、生命周期、无法退出主体或文章输出场景执行 `..\u002Fcrossframe\u002Fworksheets\u002Fsource-anchor-integrity-check.md`。如果胶囊缺失，回到 `..\u002Fcrossframe\u002FSKILL.md` 补齐；本 skill 不重新发明源路由。\n6. 读取 `references\u002Forg-routing-map.md`，选择本 skill 的专项协议、引用材料和模板。\n7. 按请求读取本地协议：\n   - 项目失败、团队反复卡住：`protocols\u002Forg-diagnostic-protocol.md`\n   - 反馈没有进入下一轮结构改变：`protocols\u002Ffeedback-writeback-protocol.md`\n   - 复盘失真、复盘形式化：`protocols\u002Fretrospective-redesign-protocol.md`\n   - 需要行动、试点、改造计划：`protocols\u002Flow-risk-pilot-protocol.md`\n8. 按需读取本地引用：\n   - 责任链与授权链：`references\u002Fresponsibility-authorization-chain.md`\n   - 中层承接耗竭：`references\u002Fmiddle-manager-depletion.md`\n   - 项目失败与复盘失真信号：`references\u002Forg-failure-signals.md`\n   - 反管理鸡汤与反甩锅护栏：`references\u002Fanti-chicken-soup-guardrails.md`\n9. 如果判断使用高风险 CrossFrame 概念，按 `..\u002Fcrossframe\u002Freferences\u002Fread-routing-map.md` 读取对应概念卡，并用 `..\u002Fcrossframe\u002Fworksheets\u002Fconcept-fidelity-check.md` 做概念保真检查。\n10. 先形成内部组织 intake，再按模板输出；不要展示完整内部工作表，除非用户要求审计或完整工作表。\n\n## 内部组织 intake\n\n每次输出前，至少在内部写清：\n\n- 组织对象：团队、项目、流程、会议、角色、跨部门接口或治理层。\n- 事实边界：用户给出的事实、推测、证据缺口、不能判断的部分。\n- 失败现象：延期、返工、沉默、复盘失真、需求漂移、跨部门断裂、加速后更乱。\n- 责任链：谁对结果负责，谁能改变条件，谁承担失败成本，谁被要求继续解释。\n- 授权链：谁有权限改规则、资源、优先级、时间表、接口和停止条件。\n- 反馈链：信号从哪里来，经过谁转译，写回到什么规则、资源、角色或时间表。\n- 中层承接负荷：中层是否在替组织吸收冲突、解释、补锅、翻译和情绪成本。\n- 机制候选：至少两个互相竞争的解释，不能把问题直接压成“执行力差”。\n- 停止条件：哪些动作一旦出现负反馈就必须暂停、降档或撤回。\n- 低风险试点：最小、可观察、可撤回、能写回结构的小动作。\n\n## 输出规则\n\n- 默认先给短的 `组织推理提纲`，再输出用户需要的备忘录或方案。\n- 输出必须落到现实组织变量：角色、权限、资源、时间、接口、节奏、证据、停止条件。\n- 输出不是文章；不要走 `crossframe-essay`，除非用户明确要求写文章。\n- 第一段要用普通组织语言说明：发生了什么、为什么重复、下一步先改什么。\n- 术语只能做后台映射，不能用“这是典型的 X”替代诊断。\n\n## 硬规则\n\n- 不准写管理鸡汤：不输出“加强沟通、提升主人翁意识、统一思想、提高执行力”这类无结构变量建议。\n- 不准把问题压给执行层：任何涉及基层、执行、个人努力的判断，都必须同时检查授权链、资源链、时间链和反馈写回。\n- 不准只有复盘没有写回：每个建议都要说明写回到什么规则、资源、角色、接口或时间表。\n- 不准只有加速没有停止条件：冲刺、加会、升级管理、强推进都必须有暂停、降档、撤回或保护边界。\n- 不准把中层耗竭解释成能力不足或抗压不够；先检查组织是否把翻译、缓冲、补锅和冲突成本长期压给中层。\n- 不准把复盘报告、OKR 更新、合规记录、道歉声明或会议纪要当成修复本身；它们最多是修复副产品。\n- 不准用组织诊断替代劳动法、合规、心理健康、医疗、安全或正式申诉处置。\n- 不准为了显得积极而建议扩大范围；先找最小可逆试点。\n\n## 默认输出\n\n使用 `templates\u002Foutput-selector.md` 判断模板。常见默认：\n\n```text\n# 组织推理提纲\n\n# 组织诊断备忘录\n\n# 反馈写回方案\n\n# 低风险试点计划\n```\n\n如果用户只要求复盘改造，使用 `templates\u002Fretrospective-redesign-recommendation.md`。如果用户只要求一个行动实验，使用 `templates\u002Flow-risk-pilot-plan.md` 并附 `templates\u002Fstop-condition-card.md`。\n","# CrossFrame Org\n\n\n\n## When to Use This Skill\n\n- Use when `crossframe-suite` routes an explicit CrossFrame task about teams, projects, organizations, responsibility chains, authority chains, feedback write-back, retrospectives, or repair.\n- Use when an organizational failure needs mechanism candidates rather than personality judgment.\n- Do not use independently unless the user explicitly names this sibling skill.\n\n## Packaged Source Note\n\nThis AAS-ready copy preserves the original CrossFrame skill body below. Chinese remains the canonical semantic layer; English metadata is only for discovery, installation, and repository review.\n\n## Limitations\n\n- The skill body is intentionally Chinese-canonical; English metadata is for discovery and does not replace the original Chinese terms.\n- Use only after explicit CrossFrame invocation or `crossframe-suite` routing; do not apply it as a generic default reasoning layer.\n- It structures analysis, drafting, and review, but does not replace source verification, domain expertise, or legal, medical, or financial judgment.\n\n> **本 skill 不独立触发。** 所有 CrossFrame 任务统一从 `crossframe-suite` 入口调度。用户无需直接调用本 skill；suite 根据路由规则在需要时自动加载。\n\n如果组织修复判断之后要写文章、沉淀案例、做辩论或评审输出，先读取 `..\u002Fcrossframe-suite\u002FSKILL.md` 做总调度；本 skill 只负责团队、项目和组织修复专项。\n\nCrossFrame Org 是 `crossframe` 的平行组织修复 skill，不替代 canonical `crossframe`，也不复制 CrossFrame 全文。它把 CrossFrame 的事实闸、尺度闸、责任闸、机制候选和概念保真，转成团队、项目、组织场景里的可执行修复备忘录。\n\n中文是权威语义。英文只用于 skill id、文件名或必要的外部接口；不要把“承接、回流、责任链、授权链、修复副产品、停止错误加速”翻译后再反向理解。\n\n## 必须执行的顺序\n\n1. 判断输出类型：组织诊断备忘录、反馈写回方案、复盘改造建议、低风险试点计划，或组合输出。\n2. 读取 `..\u002Fcrossframe\u002FSKILL.md`。\n3. 读取 `..\u002Fcrossframe\u002Freferences\u002Fread-routing-map.md`，确定本次需要加载的 canonical protocol、worksheet、concept card 和模板。\n4. 如果组织判断触发高责任、公共制度、亲密关系、长期演化、框架治理、AI 现实验证、弱信号\u002F不透明、无法退出、工具化、隐喻\u002F来源透明或文章输出，必须追加读取 `..\u002Fcrossframe\u002Freferences\u002Fcontinuity-bundles.md`，并按需使用 `..\u002Fcrossframe\u002Fworksheets\u002Fsource-continuity-check.md`；未完成联读时只能降档。\n5. 复用 `..\u002Fcrossframe\u002Ftemplates\u002Fread-state-capsule.md` 规定的 `v5-read-state-capsule`，并在高责任、公共、AI\u002F过程性产物、生命周期、无法退出主体或文章输出场景执行 `..\u002Fcrossframe\u002Fworksheets\u002Fsource-anchor-integrity-check.md`。如果胶囊缺失，回到 `..\u002Fcrossframe\u002FSKILL.md` 补齐；本 skill 不重新发明源路由。\n6. 读取 `references\u002Forg-routing-map.md`，选择本 skill 的专项协议、引用材料和模板。\n7. 按请求读取本地协议：\n   - 项目失败、团队反复卡住：`protocols\u002Forg-diagnostic-protocol.md`\n   - 反馈没有进入下一轮结构改变：`protocols\u002Ffeedback-writeback-protocol.md`\n   - 复盘失真、复盘形式化：`protocols\u002Fretrospective-redesign-protocol.md`\n   - 需要行动、试点、改造计划：`protocols\u002Flow-risk-pilot-protocol.md`\n8. 按需读取本地引用：\n   - 责任链与授权链：`references\u002Fresponsibility-authorization-chain.md`\n   - 中层承接耗竭：`references\u002Fmiddle-manager-depletion.md`\n   - 项目失败与复盘失真信号：`references\u002Forg-failure-signals.md`\n   - 反管理鸡汤与反甩锅护栏：`references\u002Fanti-chicken-soup-guardrails.md`\n9. 如果判断使用高风险 CrossFrame 概念，按 `..\u002Fcrossframe\u002Freferences\u002Fread-routing-map.md` 读取对应概念卡，并用 `..\u002Fcrossframe\u002Fworksheets\u002Fconcept-fidelity-check.md` 做概念保真检查。\n10. 先形成内部组织 intake，再按模板输出；不要展示完整内部工作表，除非用户要求审计或完整工作表。\n\n## 内部组织 intake\n\n每次输出前，至少在内部写清：\n\n- 组织对象：团队、项目、流程、会议、角色、跨部门接口或治理层。\n- 事实边界：用户给出的事实、推测、证据缺口、不能判断的部分。\n- 失败现象：延期、返工、沉默、复盘失真、需求漂移、跨部门断裂、加速后更乱。\n- 责任链：谁对结果负责，谁能改变条件，谁承担失败成本，谁被要求继续解释。\n- 授权链：谁有权限改规则、资源、优先级、时间表、接口和停止条件。\n- 反馈链：信号从哪里来，经过谁转译，写回到什么规则、资源、角色或时间表。\n- 中层承接负荷：中层是否在替组织吸收冲突、解释、补锅、翻译和情绪成本。\n- 机制候选：至少两个互相竞争的解释，不能把问题直接压成“执行力差”。\n- 停止条件：哪些动作一旦出现负反馈就必须暂停、降档或撤回。\n- 低风险试点：最小、可观察、可撤回、能写回结构的小动作。\n\n## 输出规则\n\n- 默认先给短的 `组织推理提纲`，再输出用户需要的备忘录或方案。\n- 输出必须落到现实组织变量：角色、权限、资源、时间、接口、节奏、证据、停止条件。\n- 输出不是文章；不要走 `crossframe-essay`，除非用户明确要求写文章。\n- 第一段要用普通组织语言说明：发生了什么、为什么重复、下一步先改什么。\n- 术语只能做后台映射，不能用“这是典型的 X”替代诊断。\n\n## 硬规则\n\n- 不准写管理鸡汤：不输出“加强沟通、提升主人翁意识、统一思想、提高执行力”这类无结构变量建议。\n- 不准把问题压给执行层：任何涉及基层、执行、个人努力的判断，都必须同时检查授权链、资源链、时间链和反馈写回。\n- 不准只有复盘没有写回：每个建议都要说明写回到什么规则、资源、角色、接口或时间表。\n- 不准只有加速没有停止条件：冲刺、加会、升级管理、强推进都必须有暂停、降档、撤回或保护边界。\n- 不准把中层耗竭解释成能力不足或抗压不够；先检查组织是否把翻译、缓冲、补锅和冲突成本长期压给中层。\n- 不准把复盘报告、OKR 更新、合规记录、道歉声明或会议纪要当成修复本身；它们最多是修复副产品。\n- 不准用组织诊断替代劳动法、合规、心理健康、医疗、安全或正式申诉处置。\n- 不准为了显得积极而建议扩大范围；先找最小可逆试点。\n\n## 默认输出\n\n使用 `templates\u002Foutput-selector.md` 判断模板。常见默认：\n\n```text\n# 组织推理提纲\n\n# 组织诊断备忘录\n\n# 反馈写回方案\n\n# 低风险试点计划\n```\n\n如果用户只要求复盘改造，使用 `templates\u002Fretrospective-redesign-recommendation.md`。如果用户只要求一个行动实验，使用 `templates\u002Flow-risk-pilot-plan.md` 并附 `templates\u002Fstop-condition-card.md`。\n",{"name":5,"risk":24,"tags":25,"tools":31,"author":35,"source":36,"license":15,"category":37,"date_added":38,"description":7,"source_repo":39,"source_type":36,"license_source":40},"safe",[26,27,28,29,30],"crossframe","chinese","organization","retrospective","repair",[32,33,34],"Agent Skills","Codex","Claude","xi-kari","community","business",1781568000000,"xi-kari\u002Fcrossframe-skill","https:\u002F\u002Fgithub.com\u002Fxi-kari\u002Fcrossframe-skill\u002Fblob\u002Fmain\u002FLICENSE","main","c475fc64e94e803b50d14a791dfee8853fbb2c5c","integrations\u002Fantigravity-skills\u002Fskills\u002Fcrossframe-org","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory","https:\u002F\u002Fgithub.com\u002FElogic360","2026-11-08 22:21:22",{"source":8,"skillName":5,"commands":48,"prompt":58,"zipAvailable":59},[49,52,55],{"tool":50,"command":51},"npx","npx skills add Elogic360\u002Fsoftware-factory --skill crossframe-org",{"tool":53,"command":54},"bunx","bunx skills add Elogic360\u002Fsoftware-factory --skill crossframe-org",{"tool":56,"command":57},"pnpm","pnpm dlx skills add Elogic360\u002Fsoftware-factory --skill crossframe-org","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fintegrations\u002Fantigravity-skills\u002Fskills\u002Fcrossframe-org\u002FSKILL.md",true,[61,67,71,75,79,83,87,91,95,99,103,107,111,115,119,123,127,131,135,139,143],{"path":62,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":65,"sourceHtmlUrl":66},"agents\u002Fopenai.yaml","REFERENCE","参考文档",312,"https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fintegrations\u002Fantigravity-skills\u002Fskills\u002Fcrossframe-org\u002Fagents\u002Fopenai.yaml",{"path":68,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":69,"sourceHtmlUrl":70},"evals\u002Fcrossframe-org-smoke-tests.md",4202,"https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fintegrations\u002Fantigravity-skills\u002Fskills\u002Fcrossframe-org\u002Fevals\u002Fcrossframe-org-smoke-tests.md",{"path":72,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":73,"sourceHtmlUrl":74},"examples\u002Fbad-output-vs-good-output.md",1687,"https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fintegrations\u002Fantigravity-skills\u002Fskills\u002Fcrossframe-org\u002Fexamples\u002Fbad-output-vs-good-output.md",{"path":76,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":77,"sourceHtmlUrl":78},"examples\u002Fmiddle-manager-depletion-case.md",1284,"https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fintegrations\u002Fantigravity-skills\u002Fskills\u002Fcrossframe-org\u002Fexamples\u002Fmiddle-manager-depletion-case.md",{"path":80,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":81,"sourceHtmlUrl":82},"examples\u002Fproject-failure-case.md",1745,"https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fintegrations\u002Fantigravity-skills\u002Fskills\u002Fcrossframe-org\u002Fexamples\u002Fproject-failure-case.md",{"path":84,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":85,"sourceHtmlUrl":86},"examples\u002Fretrospective-distortion-case.md",1380,"https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fintegrations\u002Fantigravity-skills\u002Fskills\u002Fcrossframe-org\u002Fexamples\u002Fretrospective-distortion-case.md",{"path":88,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":89,"sourceHtmlUrl":90},"protocols\u002Ffeedback-writeback-protocol.md",1721,"https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fintegrations\u002Fantigravity-skills\u002Fskills\u002Fcrossframe-org\u002Fprotocols\u002Ffeedback-writeback-protocol.md",{"path":92,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":93,"sourceHtmlUrl":94},"protocols\u002Flow-risk-pilot-protocol.md",1521,"https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fintegrations\u002Fantigravity-skills\u002Fskills\u002Fcrossframe-org\u002Fprotocols\u002Flow-risk-pilot-protocol.md",{"path":96,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":97,"sourceHtmlUrl":98},"protocols\u002Forg-diagnostic-protocol.md",1474,"https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fintegrations\u002Fantigravity-skills\u002Fskills\u002Fcrossframe-org\u002Fprotocols\u002Forg-diagnostic-protocol.md",{"path":100,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":101,"sourceHtmlUrl":102},"protocols\u002Fretrospective-redesign-protocol.md",1537,"https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fintegrations\u002Fantigravity-skills\u002Fskills\u002Fcrossframe-org\u002Fprotocols\u002Fretrospective-redesign-protocol.md",{"path":104,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":105,"sourceHtmlUrl":106},"references\u002Fanti-chicken-soup-guardrails.md",1324,"https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fintegrations\u002Fantigravity-skills\u002Fskills\u002Fcrossframe-org\u002Freferences\u002Fanti-chicken-soup-guardrails.md",{"path":108,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":109,"sourceHtmlUrl":110},"references\u002Fmiddle-manager-depletion.md",1704,"https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fintegrations\u002Fantigravity-skills\u002Fskills\u002Fcrossframe-org\u002Freferences\u002Fmiddle-manager-depletion.md",{"path":112,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":113,"sourceHtmlUrl":114},"references\u002Forg-failure-signals.md",2340,"https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fintegrations\u002Fantigravity-skills\u002Fskills\u002Fcrossframe-org\u002Freferences\u002Forg-failure-signals.md",{"path":116,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":117,"sourceHtmlUrl":118},"references\u002Forg-routing-map.md",3513,"https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fintegrations\u002Fantigravity-skills\u002Fskills\u002Fcrossframe-org\u002Freferences\u002Forg-routing-map.md",{"path":120,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":121,"sourceHtmlUrl":122},"references\u002Fresponsibility-authorization-chain.md",1837,"https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fintegrations\u002Fantigravity-skills\u002Fskills\u002Fcrossframe-org\u002Freferences\u002Fresponsibility-authorization-chain.md",{"path":124,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":125,"sourceHtmlUrl":126},"templates\u002Ffeedback-writeback-plan.md",640,"https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fintegrations\u002Fantigravity-skills\u002Fskills\u002Fcrossframe-org\u002Ftemplates\u002Ffeedback-writeback-plan.md",{"path":128,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":129,"sourceHtmlUrl":130},"templates\u002Flow-risk-pilot-plan.md",657,"https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fintegrations\u002Fantigravity-skills\u002Fskills\u002Fcrossframe-org\u002Ftemplates\u002Flow-risk-pilot-plan.md",{"path":132,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":133,"sourceHtmlUrl":134},"templates\u002Forg-diagnostic-memo.md",1042,"https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fintegrations\u002Fantigravity-skills\u002Fskills\u002Fcrossframe-org\u002Ftemplates\u002Forg-diagnostic-memo.md",{"path":136,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":137,"sourceHtmlUrl":138},"templates\u002Foutput-selector.md",950,"https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fintegrations\u002Fantigravity-skills\u002Fskills\u002Fcrossframe-org\u002Ftemplates\u002Foutput-selector.md",{"path":140,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":141,"sourceHtmlUrl":142},"templates\u002Fretrospective-redesign-recommendation.md",733,"https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fintegrations\u002Fantigravity-skills\u002Fskills\u002Fcrossframe-org\u002Ftemplates\u002Fretrospective-redesign-recommendation.md",{"path":144,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":145,"sourceHtmlUrl":146},"templates\u002Fstop-condition-card.md",470,"https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fintegrations\u002Fantigravity-skills\u002Fskills\u002Fcrossframe-org\u002Ftemplates\u002Fstop-condition-card.md",[148,156,163,170,177,184],{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":152,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":155,"publishedAt":19},"01M79G206MT3J6S0GY3C45P2KV","vss-summarize-video","Use to summarize a recorded video via the LVS summarization microservice (HITL-gated) with a VLM fallback. Not for report generation or live RTSP captioning.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fvss-summarize-video\u002FSKILL.md",[],[],{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":152,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":162,"publishedAt":19},"01M79G1WN63PGRE8CKD47WEBQ5","vss-setup-video-analytics-api","Use to deploy the vss-video-analytics-api REST service standalone (config-source, data-log bind, Elasticsearch, optional Kafka). Not for full warehouse deploy.","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fvss-setup-video-analytics-api\u002FSKILL.md",[],[],{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":152,"licenseFileUrl":6,"sourceHtmlUrl":167,"categories":168,"keywords":169,"publishedAt":19},"01M79G1S9F7VY3EF6H53PRP5AN","vss-setup-behavior-analytics","Use to deploy the vss-behavior-analytics service standalone (entrypoint, config-source, optional calibration). Not for the full warehouse deploy.","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fvss-setup-behavior-analytics\u002FSKILL.md",[],[],{"skillNo":171,"name":172,"nameZh":6,"description":173,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":152,"licenseFileUrl":6,"sourceHtmlUrl":174,"categories":175,"keywords":176,"publishedAt":19},"01M79G1N1S1Y27PFZPYMNK1MTQ","vss-search-archive","Use this skill to run top-level VSS fusion search on archived video, or to ingest video files \u002F RTSP streams for search. Do NOT use for ad-hoc visual Q&A (use vss-ask-video), live captioning (use vss-deploy-dense-captioning), or video summarization and reports (use vss-summarize-video).","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fvss-search-archive\u002FSKILL.md",[],[],{"skillNo":178,"name":179,"nameZh":6,"description":180,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":152,"licenseFileUrl":6,"sourceHtmlUrl":181,"categories":182,"keywords":183,"publishedAt":19},"01M79G1H6WN0Q6C0VCAXCZX6B7","vss-query-analytics","Use this skill when reading video-analytics metrics, incidents, alerts, and sensor data via the VA-MCP server (port 9901). Not for live VLM or incident-range narrative reports.","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fvss-query-analytics\u002FSKILL.md",[],[],{"skillNo":185,"name":186,"nameZh":6,"description":187,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":152,"licenseFileUrl":6,"sourceHtmlUrl":188,"categories":189,"keywords":190,"publishedAt":19},"01M79G1DYPNXQS7QHZ0AAF5FX5","vss-manage-video-io-storage","Use to call the VIOS REST API (sensor list, timelines, clip extraction, snapshots, add\u002Fdelete sensors and streams). Not for VLM inference or search.","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fvss-manage-video-io-storage\u002FSKILL.md",[],[]]