[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CKQFDBEWPYVR7X5X3B80VH":3,"skill-same:01M7CKQFDBEWPYVR7X5X3B80VH":45},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":13,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7CKQFDBEWPYVR7X5X3B80VH","sales-organization-analysis",null,"销售组织与区域订单履约分析：按销售组、销售组织、省区、大区、渠道、客户类型或客户汇总订单数、状态、超时\u002F预警、满足率区间及缺货影响。当用户询问哪个销售区域、渠道或客户群履约风险高时使用。不做销售绩效\u002F责任归因，不修改组织映射或客户主数据。","CleverC2200\u002Fdsh-agent-manage","CleverC2200","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F59353299?v=4","01M7CKHTPKJB2904KS2N99NZ21","01M7CKHTQK7JT811BVWEK2EHHP",0,"MIT","https:\u002F\u002Fgithub.com\u002FCleverC2200\u002Fdsh-agent-manage\u002Fblob\u002Fmain\u002Fbusiness-resources\u002Finventory-orderfulfillment\u002Fskills\u002Fsales-organization-analysis\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: sales-organization-analysis\nversion: 0.1.0\ndescription: '销售组织与区域订单履约分析：按销售组、销售组织、省区、大区、渠道、客户类型或客户汇总订单数、状态、超时\u002F预警、满足率区间及缺货影响。当用户询问哪个销售区域、渠道或客户群履约风险高时使用。不做销售绩效\u002F责任归因，不修改组织映射或客户主数据。'\n---\n\n# 销售组织与区域分析 Skill\n\n## 具体内容\n\n### 1、适用边界\n\n- **做**：按销售组、销售组织、省区、大区、渠道、客户类型和客户聚合订单履约表现，识别区域风险和受影响客户，并支持下钻。\n- **不做**：把风险直接归因于销售人员绩效；自行补全未接入的组织\u002F客户映射；修改销售组织或客户主数据。\n- 区域、销售组、渠道和客户属性均依权威主数据映射；无法映射的订单单独列示。\n\n### 2、输入（触发范围）\n\n- “哪个大区\u002F省区超时订单多？”、“某渠道的订单满足率区间分布如何？”\n- 按销售组织、销售人员、客户类型查看未开订单、缺货订单或订单状态。\n- 比较区域\u002F渠道在某时段的订单量、超时\u002F预警和缺货影响。\n\n不用于：销售人员绩效评价、无数据支撑的责任认定或主数据变更。\n\n### 3、工作步骤\n\n1. 明确分组层级（销售组织\u002F省区\u002F大区\u002F渠道\u002F客户）和筛选期间、基地、订单状态及指标。\n2. 获取订单主键、区域\u002F组织\u002F客户映射和履约指标；校验组织映射的有效时间和覆盖率。\n3. 对订单按唯一订单键去重后聚合订单数；对 SKU 缺货量按 SKU 明细统计，对订单缺货数按订单去重。\n4. 计算各层级订单满足率时按需求量加权；满足率区间按订单级满足率分箱后统计订单数。\n5. 对比层级间的超时\u002F预警、未开订单、满足率区间和缺货订单\u002F缺货 SKU；同一订单跨多个节点不重复增加订单数。\n6. 找出高风险区域\u002F渠道并给出订单\u002FSKU 明细；对缺货成因、库存或排产覆盖问题路由到相应 Skill。\n7. 说明未映射订单、映射数据覆盖率、快照时间和不可进行责任归因的限制。\n\n### 4、异常处理\n\n- 组织或区域关系未接入\u002F过期：不按区域推断，展示未映射数量和覆盖率。\n- 订单归属组织变更：按订单创建时、履约时或当前组织统计需遵循业务确认规则；未确认时不可混用。\n- 分组基数小：展示原始订单数和样本范围，不仅展示百分比，避免误导。\n- 缺货 SKU 重复出现在多张订单：缺货 SKU 数按唯一 SKU 编码去重；缺货订单数按唯一订单号去重。\n- 查询区域无订单：明确是 0 张还是区域映射\u002F数据缺失。\n\n### 5、输出规范及安全约束\n\n- 分组层级及归属口径必须写清；百分率旁同时提供分子、分母或订单数。\n- 不将相关性描述成责任因果，不对销售人员做绩效判断。\n- 涉及客户、人员信息遵循权限与最小必要原则；明细提供范围受限时只给汇总。\n- 使用真实数据时标注快照时间；演示数据必须明确标注。\n\n### 6、参考资料路由\n\n- 订单状态、超时\u002F预警、满足率算法 → [order-fulfillment-risk](..\u002Forder-fulfillment-risk\u002FSKILL.md)。\n- SKU 缺货、基地库存和货龄 → [sku-inventory-shortage](..\u002Fsku-inventory-shortage\u002FSKILL.md)。\n- 排产和生产覆盖 → [production-fulfillment-progress](..\u002Fproduction-fulfillment-progress\u002FSKILL.md)。\n- 运单与物流商表现 → [warehouse-logistics-fulfillment](..\u002Fwarehouse-logistics-fulfillment\u002FSKILL.md)。\n- 多维联查和答案汇总 → [fulfillment-query-orchestrator](..\u002Ffulfillment-query-orchestrator\u002FSKILL.md)。\n\n### 7、业务字段、公式、案例\n\n### 字段\n\n订单号、订单创建时间、客户编码、销售组、销售组织、省区、大区、客户类型\u002F渠道、销售人员、基地、SKU、订单需求量、实际发货量、缺货量、状态、节点时间。\n\n### 公式与口径\n\n- 区域订单数 = 按指定时间有效范围内的唯一订单号计数。\n- 区域满足率先按当前卡片确认是可满足口径还是已发货口径；可满足量按同口径需求减缺货，实际发货量须有独立事实，两者不混用。汇总先合计该口径分子与需求分母，不平均订单或区域百分比；缺失覆盖不补零。\n- 满足率区间订单数 = 按订单级满足率落入互斥区间的去重订单数。\n- 区域超时\u002F预警订单 = 命中对应规则的去重订单数；可额外展示节点命中次数，但分开标识。\n- 缺货订单数按订单去重；缺货 SKU 数按 SKU 编码去重；缺货数量按统一单位加总。\n\n### 案例\n\n某省区 A 订单需求 100 件、发货 100 件；B 订单需求 900 件、发货 720 件。区域满足率为 820\u002F1000=82%，不是 (100%+80%)\u002F2=90%。\n\n### 8、输出样式\n\n| 区域\u002F组织 | 订单数 | 超时\u002F预警订单 | 未开订单 | 加权满足率 | 满足率区间分布 | 缺货订单\u002FSKU\u002F数量 |\n| --------- | -----: | ------------: | -------: | ---------: | -------------- | ----------------: |\n\n表后列出风险最高的区域和可下钻订单，并注明区域映射覆盖率、统计周期和数据更新时间。\n\n## 当前安装能力边界\n\n本 Skill 由订单工作台与订单履约 Agent 共用，技能描述不授予查询、人员范围或业务写入权限。只能使用当前 Agent 已安装、已授权的页面证据和工具；用户角色描述不代表实际授权。\n\n订单履约只使用 order01 的当前用户受控只读能力，缺失指标和接口保持未知。订单工作台沿用其当前已发布能力；页面处于 mock 时，只分析明确标记的报告摘录、演示数据或用户提供的证据，不宣称已接入实时订单系统。\n\n销售确认、每小时提醒、飞书消息、OMS 更新、WMS\u002FTMS 下发及外部改善任务尚无本次新增的写入或调度接口。可以解释流程、分析证据和生成草案，不能因加载 Skill 就启动执行或声称已完成。实际操作仍需相应工具、有效权限和明确授权。\n","# 销售组织与区域分析 Skill\n\n## 具体内容\n\n### 1、适用边界\n\n- **做**：按销售组、销售组织、省区、大区、渠道、客户类型和客户聚合订单履约表现，识别区域风险和受影响客户，并支持下钻。\n- **不做**：把风险直接归因于销售人员绩效；自行补全未接入的组织\u002F客户映射；修改销售组织或客户主数据。\n- 区域、销售组、渠道和客户属性均依权威主数据映射；无法映射的订单单独列示。\n\n### 2、输入（触发范围）\n\n- “哪个大区\u002F省区超时订单多？”、“某渠道的订单满足率区间分布如何？”\n- 按销售组织、销售人员、客户类型查看未开订单、缺货订单或订单状态。\n- 比较区域\u002F渠道在某时段的订单量、超时\u002F预警和缺货影响。\n\n不用于：销售人员绩效评价、无数据支撑的责任认定或主数据变更。\n\n### 3、工作步骤\n\n1. 明确分组层级（销售组织\u002F省区\u002F大区\u002F渠道\u002F客户）和筛选期间、基地、订单状态及指标。\n2. 获取订单主键、区域\u002F组织\u002F客户映射和履约指标；校验组织映射的有效时间和覆盖率。\n3. 对订单按唯一订单键去重后聚合订单数；对 SKU 缺货量按 SKU 明细统计，对订单缺货数按订单去重。\n4. 计算各层级订单满足率时按需求量加权；满足率区间按订单级满足率分箱后统计订单数。\n5. 对比层级间的超时\u002F预警、未开订单、满足率区间和缺货订单\u002F缺货 SKU；同一订单跨多个节点不重复增加订单数。\n6. 找出高风险区域\u002F渠道并给出订单\u002FSKU 明细；对缺货成因、库存或排产覆盖问题路由到相应 Skill。\n7. 说明未映射订单、映射数据覆盖率、快照时间和不可进行责任归因的限制。\n\n### 4、异常处理\n\n- 组织或区域关系未接入\u002F过期：不按区域推断，展示未映射数量和覆盖率。\n- 订单归属组织变更：按订单创建时、履约时或当前组织统计需遵循业务确认规则；未确认时不可混用。\n- 分组基数小：展示原始订单数和样本范围，不仅展示百分比，避免误导。\n- 缺货 SKU 重复出现在多张订单：缺货 SKU 数按唯一 SKU 编码去重；缺货订单数按唯一订单号去重。\n- 查询区域无订单：明确是 0 张还是区域映射\u002F数据缺失。\n\n### 5、输出规范及安全约束\n\n- 分组层级及归属口径必须写清；百分率旁同时提供分子、分母或订单数。\n- 不将相关性描述成责任因果，不对销售人员做绩效判断。\n- 涉及客户、人员信息遵循权限与最小必要原则；明细提供范围受限时只给汇总。\n- 使用真实数据时标注快照时间；演示数据必须明确标注。\n\n### 6、参考资料路由\n\n- 订单状态、超时\u002F预警、满足率算法 → [order-fulfillment-risk](..\u002Forder-fulfillment-risk\u002FSKILL.md)。\n- SKU 缺货、基地库存和货龄 → [sku-inventory-shortage](..\u002Fsku-inventory-shortage\u002FSKILL.md)。\n- 排产和生产覆盖 → [production-fulfillment-progress](..\u002Fproduction-fulfillment-progress\u002FSKILL.md)。\n- 运单与物流商表现 → [warehouse-logistics-fulfillment](..\u002Fwarehouse-logistics-fulfillment\u002FSKILL.md)。\n- 多维联查和答案汇总 → [fulfillment-query-orchestrator](..\u002Ffulfillment-query-orchestrator\u002FSKILL.md)。\n\n### 7、业务字段、公式、案例\n\n### 字段\n\n订单号、订单创建时间、客户编码、销售组、销售组织、省区、大区、客户类型\u002F渠道、销售人员、基地、SKU、订单需求量、实际发货量、缺货量、状态、节点时间。\n\n### 公式与口径\n\n- 区域订单数 = 按指定时间有效范围内的唯一订单号计数。\n- 区域满足率先按当前卡片确认是可满足口径还是已发货口径；可满足量按同口径需求减缺货，实际发货量须有独立事实，两者不混用。汇总先合计该口径分子与需求分母，不平均订单或区域百分比；缺失覆盖不补零。\n- 满足率区间订单数 = 按订单级满足率落入互斥区间的去重订单数。\n- 区域超时\u002F预警订单 = 命中对应规则的去重订单数；可额外展示节点命中次数，但分开标识。\n- 缺货订单数按订单去重；缺货 SKU 数按 SKU 编码去重；缺货数量按统一单位加总。\n\n### 案例\n\n某省区 A 订单需求 100 件、发货 100 件；B 订单需求 900 件、发货 720 件。区域满足率为 820\u002F1000=82%，不是 (100%+80%)\u002F2=90%。\n\n### 8、输出样式\n\n| 区域\u002F组织 | 订单数 | 超时\u002F预警订单 | 未开订单 | 加权满足率 | 满足率区间分布 | 缺货订单\u002FSKU\u002F数量 |\n| --------- | -----: | ------------: | -------: | ---------: | -------------- | ----------------: |\n\n表后列出风险最高的区域和可下钻订单，并注明区域映射覆盖率、统计周期和数据更新时间。\n\n## 当前安装能力边界\n\n本 Skill 由订单工作台与订单履约 Agent 共用，技能描述不授予查询、人员范围或业务写入权限。只能使用当前 Agent 已安装、已授权的页面证据和工具；用户角色描述不代表实际授权。\n\n订单履约只使用 order01 的当前用户受控只读能力，缺失指标和接口保持未知。订单工作台沿用其当前已发布能力；页面处于 mock 时，只分析明确标记的报告摘录、演示数据或用户提供的证据，不宣称已接入实时订单系统。\n\n销售确认、每小时提醒、飞书消息、OMS 更新、WMS\u002FTMS 下发及外部改善任务尚无本次新增的写入或调度接口。可以解释流程、分析证据和生成草案，不能因加载 Skill 就启动执行或声称已完成。实际操作仍需相应工具、有效权限和明确授权。\n",{"name":5,"version":23,"description":7},"0.1.0","main","9294f7b43e72f2fecb585524bdb8ea2ed54aa4d1","business-resources\u002Finventory-orderfulfillment\u002Fskills\u002Fsales-organization-analysis","https:\u002F\u002Fgithub.com\u002FCleverC2200\u002Fdsh-agent-manage","https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002Fdsh-agent-plugins-market","https:\u002F\u002Fgithub.com\u002FCleverC2200","2026-11-13 17:22:10",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add CleverC2200\u002Fdsh-agent-manage --skill sales-organization-analysis",{"tool":37,"command":38},"bunx","bunx skills add CleverC2200\u002Fdsh-agent-manage --skill sales-organization-analysis",{"tool":40,"command":41},"pnpm","pnpm dlx skills add CleverC2200\u002Fdsh-agent-manage --skill sales-organization-analysis","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FCleverC2200\u002Fdsh-agent-manage\u002Fblob\u002Fmain\u002Fbusiness-resources\u002Finventory-orderfulfillment\u002Fskills\u002Fsales-organization-analysis\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":18},"01M7CKW0H0PQ6NY86HQV9SX94X","greet","Greet the user and resolve bundled resources.","https:\u002F\u002Fgithub.com\u002FCleverC2200\u002Fdsh-agent-manage\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fv1-suite\u002Fskills\u002Fgreet\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":18},"01M7CKVZFF4D5A7XVEWVHZE0JK","baz","A universal skill.","https:\u002F\u002Fgithub.com\u002FCleverC2200\u002Fdsh-agent-manage\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Funiversal-only\u002Fskills\u002Fbaz\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M7CKVY72ZM2M7ACTKEZ253V8","inner","Inner skill of the hosting repo","https:\u002F\u002Fgithub.com\u002FCleverC2200\u002Fdsh-agent-manage\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fmarketplace-github-remote\u002Fskills\u002Finner\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"01M7CKVWXJBCK8Y9A50SP81Z57","beta","Flat collection skill beta","https:\u002F\u002Fgithub.com\u002FCleverC2200\u002Fdsh-agent-manage\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fmarketplace-empty-entries\u002Fbeta\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M7CKVVTP5XCKPWMYPZ4ETFAG","alpha","Flat collection skill alpha","https:\u002F\u002Fgithub.com\u002FCleverC2200\u002Fdsh-agent-manage\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fmarketplace-empty-entries\u002Falpha\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M7CKVTQX2R5DPPS7ETMQ7RQ5","root-skill","Skill on the root suite","https:\u002F\u002Fgithub.com\u002FCleverC2200\u002Fdsh-agent-manage\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fmarketplace-all-broken\u002Fskills\u002Froot-skill\u002FSKILL.md",[],[]]