Kutesmart 客户与历史尺寸数据判断

需要解决的问题

在 Kutesmart 海外运营平台的客户与量体业务中，我们常需要快速判断某个客户是否存在历史量体数据。手动登录平台查询效率低，且查询结果需要作为后续业务链路的基础数据，若数据准确性不足，会导致后续量体推荐、订单处理等环节出错。需要一个轻量的接口调用方式，精准获取客户是否有历史尺寸数据的结果，无需手动操作平台界面。

核心能力与工作方式

这个技能是最小颗粒度的接口原子技能，仅负责单一接口动作 get_cus_size，核心是调用正式环境的查询接口：

• 固定调用地址：GET https://www.kutetailor.com/api/customer/customer-size/getCusSize
• 参数传递：统一使用嵌套 params 对象，避免顶层散列参数；accessToken 用于生成 Authorization: Bearer，若传入值已含 Bearer 则不重复拼接；Query 参数（如 cusId、csId）写入 params.query，JSON Body 写入 params.body，额外 Header 写入 params.headers
• 结果输出：以接口响应为唯一事实来源，仅返回客户与历史尺寸是否有数据的关键字段，不补造或篡改数据

适用边界与注意点

• 仅用于单一接口查询：本技能只完成 get_cus_size 接口调用，无法处理多接口步骤的完整业务链路，需由上层 agent 编排多个原子技能组成完整流程
• 不支持参数覆盖：固定使用 frontmatter 中的正式环境 base_url，不接受用户输入覆盖
• 需遵守权限约束：查询时需遵循当前登录态、租户和用户权限，若返回认证、权限、参数错误，需将原始错误码与信息透传给上层 agent

What Problem It Solves

In Kutesmart’s overseas operations platform for customers and measurements, we often need to quickly check whether a customer has historical measurement data. Manual login to the platform for verification is inefficient, and the result serves as foundational data for subsequent workflows—inaccurate results may cause errors in later steps like measurement recommendations or order processing. A lightweight interface call is needed to accurately retrieve this information without manual platform interaction.

Core Capabilities & How It Works

This is a minimal-granularity atomic skill that handles only the single interface action get_cus_size, focusing on calling the production query interface:

• Fixed endpoint: GET https://www.kutetailor.com/api/customer/customer-size/getCusSize
• Parameter handling: Uses a nested params object to avoid scattered top-level keys; accessToken generates Authorization: Bearer (no duplicate prefix if the input already contains Bearer); query parameters (e.g., cusId, csId) go into params.query, JSON body into params.body, and extra headers into params.headers
• Result output: Uses the interface response as the sole source of truth, returning only key fields about whether customer and historical measurement data exists, without fabricating or altering data

Applicability & Caveats

• Single-interface query only: This skill only completes the get_cus_size interface call and cannot handle multi-step workflows. Upstream agents need to orchestrate multiple atomic skills to form complete business chains
• No parameter override: Fixed to use the production base_url in frontmatter, and user inputs to override it are not accepted
• Permission compliance: Queries must follow current login state, tenant, and user permissions. Raw error codes and messages for authentication, permission, parameter, or business errors must be passed to upstream agents