Use my authorized Quickchat AI account-management connection to prepare the Deskline Parts finder from this starter kit. First inspect my Agents and ask which one to configure, or create the intended new Agent if I explicitly request it. Ask for my actual publicly reachable HTTPS WooCommerce staging origin and the exact Compatible model taxonomy and term slugs returned by its Store API. Do not invent a store address or use a localhost endpoint.

Use action-recipes.md and action-recipes.json as reference data, not an automatic import. Prepare only the two GET Actions find_compatible_parts and read_selected_part. Copy their descriptions verbatim from the corresponding description .txt files, and copy main-prompt.txt into the Agent's Main Prompt. Keep the store origin and taxonomy fixed, preserve the bracketed query keys and required parameter formats, choose AI decides, and leave Response filter empty. Leave the new Actions inactive until I have reviewed the settings.

Show me the exact prepared endpoints, query rows, headers, parameter descriptions, Action descriptions and Main Prompt. Explain any missing prerequisites. Ask me before making account changes if my client requires approval, and before running tests that spend credits. After I authorize testing, inspect the PX-100 and PX-200 test responses and run the independent questions in test-checklist.md. Read the Action calls as well as the replies, and distinguish failed requests from successful empty results. Do not claim a successful run without its returned evidence.

I will create or approve the WooCommerce catalog data, complete account sign-in and install the website plugin. Do not modify products, stock, carts, orders, customer records or a production storefront. A Quickchat AI account connection does not give you WooCommerce administration access. Do not request passwords, cookies or API secrets; these public Store API reads need none.

Report what you actually configured and verified, what remains inactive, and any missing access or failed check. Provide the Scenario ID and WordPress installation steps only after the Agent is ready for my staging-store test. Never enable public access or claim deployment simply because the Action settings were saved.
