Research competitor pricing strategies by extracting pricing pages, comparing product listings on Google Shopping and Amazon, and analyzing market positioning. Produces pricing benchmarks, tier comparisons, and feature-per-price analysis.
Scanned 9/5/2026
Install to Claude Code
npx -y skills add sandbaseai/sandbase-skills --skill competitive-pricing --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Competitive Pricing?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/sandbaseai-competitive-pricing)More formats (shields.io, HTML) on the badges page.
---
name: competitive-pricing
description: "Research competitor pricing strategies by extracting pricing pages, comparing product listings on Google Shopping and Amazon, and analyzing market positioning. Produces pricing benchmarks, tier comparisons, and feature-per-price analysis."
---
# Competitive Pricing
Research competitor pricing strategies by extracting pricing pages, comparing product listings on Google Shopping and Amazon, and analyzing market positioning. Produces pricing benchmarks, tier comparisons, and feature-per-price analysis. Read [the API map](references/sandbase-api-map.md) before selecting a capability.
## Call SandBase capabilities
For every selected tool, call `sandbase_describe_tool` first and use only arguments in its current input schema. Then call `sandbase_call_tool` with the exact `tool_name`.
## Available Tools
- `strale_pricing_page_extract`
- `google_shopping_bulk_products`
- `amazon_bulk_product_details`
- `context_dev_extract_structured_data`
- `firecrawl_scrape`
## Workflow
1. Understand the user's research question, target, and context.
2. Call `sandbase_describe_tool` for each selected tool to confirm parameter schema.
3. Call `sandbase_call_tool` with the exact tool_name and schema-defined arguments.
4. Synthesize findings into a clear, evidence-backed answer.
5. Cite sources, note evidence gaps, and separate observations from interpretations.
## Guidelines
- Always call `sandbase_describe_tool` before using any capability.
- Cite sources and preserve attribution (URLs, usernames, dates, metrics).
- Separate factual observations from analysis and recommendations.
- If data is unavailable, note the gap and continue with available evidence.
- Read-only research only. Never take actions on platforms.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!