Kutesmart款式图片批量查询

要解决什么问题

在 Kutesmart 海外运营平台的款式目录场景中，业务方常需要批量获取款式图片的 URL，用于后续的商品展示、详情页渲染或素材归档。若逐个款式调用接口，会面临重复请求、参数管理混乱和响应结果难以统一处理的问题。kutesmart-海外运营平台款式目录-批量查询款式图片 这个技能将底层接口 style_images 封装为原子化操作，让开发者只需关注输入参数和输出结果，无需关心请求构造、认证拼接等细节。

技能如何工作

该技能的核心能力是调用 POST /api/style/style-info/listProductUrl 接口，接收款式 ID 列表（idList），返回包含图片地址的结构化数据。具体步骤如下：

• 参数封装：所有调用参数需放入嵌套的 params 对象中，避免在最外层使用点号分隔的 key。例如，Path 参数写入 params.path，Query 参数写入 params.query，JSON Body 写入 params.body，额外 Header 写入 params.headers。
• 认证处理：登录态通过 params.accessToken 生成 Authorization: Bearer 头。若传入值已包含 Bearer，技能会自动跳过重复拼接。
• 接口调用：执行器固定使用 base_url 中的正式环境地址（如 https://www.kutetailor.com），不接受用户输入覆盖。根据 style_images 的 action 定义，使用 POST 方法提交请求，Body 格式为 application/json，内容为 idList。
• 结果处理：返回结果以接口响应为唯一事实来源，技能不会补造库存、价格等字段。若返回认证、权限或业务错误，原始错误码和信息会直接传递给上层 Agent，确保问题可追溯。

适用边界与注意点

• 原子化设计：该技能仅完成 style_images 这一个接口动作。若业务流程涉及多个步骤（如先查询款式列表再批量获取图片），需由上层 Agent 通过聚合 Skill 或计划文档编排多个原子 Skill。
• 权限与租户约束：接口调用依赖当前登录态、租户和用户权限。开发者需确保调用上下文中的 accessToken 具备相应权限，否则可能返回认证或权限错误。
• 参数格式要求：Body 参数必须严格遵循 application/json 格式，避免因格式错误导致接口调用失败。
• 错误传递机制：当接口返回业务错误（如款式 ID 不存在）时，技能会原样传递错误信息，上层 Agent 需根据错误类型决定是否重试或终止流程。

The Problem It Solves

In the style catalog of Kutesmart's overseas operations platform, businesses often need to batch fetch style image URLs for product display, detail page rendering, or asset archiving. Calling interfaces individually leads to redundant requests, messy parameter management, and inconsistent response handling. The kutesmart-海外运营平台款式目录-批量查询款式图片 skill encapsulates the underlying style_images interface into an atomic operation, allowing developers to focus on inputs and outputs without dealing with request construction or authentication details.

How the Skill Works

The skill's core capability is calling the POST /api/style/style-info/listProductUrl interface. It accepts a list of style IDs (idList) and returns structured data containing image URLs. Key steps include:

• Parameter Encapsulation: All call parameters must be nested within a params object. For example, Path parameters go into params.path, Query parameters into params.query, JSON Body into params.body, and additional Headers into params.headers.
• Authentication Handling: The params.accessToken generates the Authorization: Bearer header. If the input already includes Bearer, the skill skips redundant concatenation.
• Interface Invocation: The executor uses the fixed production environment address from base_url (e.g., https://www.kutetailor.com) and does not accept user input overrides. For the style_images action, it uses the POST method with application/json body containing idList.
• Result Processing: The response is treated as the sole source of truth—no inventory, pricing, or other fields are fabricated. If authentication, permission, or business errors occur, the original error code and message are passed directly to the upper-layer Agent.

Boundaries and Considerations

• Atomic Design: The skill only handles the style_images interface action. Multi-step workflows (e.g., querying a style list before batch fetching images) require orchestration by an upper-layer Agent via aggregated Skills or planning documents.
• Permission and Tenant Constraints: Interface calls depend on the current login state, tenant, and user permissions. Ensure the accessToken in the call context has the required permissions to avoid authentication or permission errors.
• Parameter Format Requirements: Body parameters must strictly follow application/json format to prevent interface call failures.
• Error Propagation: When the interface returns business errors (e.g., invalid style IDs), the skill passes the error information as-is. The upper-layer Agent must decide whether to retry or terminate based on the error type.