What problem does it solve? When a client asks to integrate Kingdee K/3 Cloud with external systems (e-commerce, OA, BI, third-party platforms), consultants often guess endpoints, pick the wrong authentication method, or confuse WebAPI tasks with plugin tasks. This Skill provides a decision index for K/3 Cloud WebAPI integration so the agent gives correct guidance instead of hallucinated endpoints. ## Core Features & Use Cases - Boundary triage: Distinguishes whether a requirement should go through WebAPI, a server-side Python/DLL plugin, or a customer-built integration layer (ESB/iPaaS). - On-demand references: Four lazy-loaded reference files covering authentication (ValidateUser / LoginByAppSecret / signature), 12 common endpoints (ExecuteBillQuery, Save, BatchSave, Submit, Audit, Push, attachments), error handling (three-layer error model, throttling, retry strategy), and integration pattern selection (Pull / Push / Batch / Event). - Use Case: A client says "sync our Tmall orders into K/3 Cloud." The agent first classifies this as a Push pattern, then provides the Save/Submit/Audit endpoint templates, idempotency advice, and field-ordering pitfalls from the references. ## Quick Start Ask the agent how to connect an external system such as an e-commerce platform or OA to K/3 Cloud, and it will classify the integration pattern and load the relevant WebAPI reference.
