---

name: amazon-competitive-pricing-monitor description: "Retrieve and compare Amazon competitive pricing for a reviewed set of ASINs or SKUs."

Amazon Competitive Pricing Monitor

Retrieve and compare Amazon competitive pricing for a reviewed set of ASINs or SKUs.

Required Aident Actions

• <action-tag>direct:amazon_sp_tools:amazon_sp_get_competitive_pricing</action-tag> (required inputs: marketplaceId, itemType): Get competitive pricing information for a list of products by ASIN or SKU.

Use Aident Loadout to read the current Action schema before constructing inputs. Check the required integration connection in Aident Vault. If an Action is billable or mutating, run Aident preflight, show the affected target and quoted cost or risk, and wait for explicit user confirmation before execution.

Workflow

1. Confirm the requested outcome, source material, destination, audience, constraints, and acceptance criteria.
2. Apply the source-derived guidance below to create a concrete plan. Resolve amAction · Get Competitive Pricingnted effect directly advances the requested outcome. Do not invoke every listed Action by default.
3. Inspect the current schema and prepare the minimum valid input for each selected Action.
4. Preflight each selected Action. Execute it only after any required confirmation, in dependency order, and carry returned IDs or asset URLs into later steps.
5. Verify the returned IDs, URLs, statuses, or artifacts against the acceptance criteria. Report partial completion precisely and do not repeat paid or mutating calls blindly.

Source-Derived Guidance

• Collect the marketplace, identifier type, exact ASINs or SKUs, and comparison objective.
• Validate identifiers and keep each request within the current Action limit.
• Use direct:amazon_sp_tools:amazon_sp_get_competitive_pricing with the reviewed marketplace and product list.
• Report returned offers, landed prices, condition, Buy Box indicators, and missing products without inventing inventory or order data.
• Return pricing observations and recommendations without changing listings, prices, ads, or inventory.

Execution Boundaries

• Treat upstream provider-specific commands as background knowledge only. Execute the workflow through the exact Aident Actions above.
• Never request raw credentials in chat. Use Aident Vault connection flows for required accounts.
• Preserve user-provided wording, brand constraints, rights restrictions, and target identifiers. Do not invent authorization.
• Stop when a required integration is disconnected, preflight rejects the input, the target is ambiguous, or the user declines a required confirmation.

Output

Return the execution plan, selected Action names, confirmed targets, Aident result identifiers or asset URLs, verification evidence, and any remaining blocked step.

Attribution

This Skill adapts the reviewed upstream workflow. See UPSTREAM.md for the pinned source and LICENSE.txt for the preserved license.