Competitive pricing skill
Research competitor pricing strategies by extracting pricing pages, comparing product listings on Google Shopping and Amazon, and analyzing market positioning.
by sandbaseai·Apache-2.0 license·★ 199 Stars on the repo·GitHub ↗
npx degit sandbaseai/sandbase-skills/research/competitive-pricing#main ~/.claude/skills/competitive-pricingChecked ·commit main
Inside this skill
SKILL.md · the author's own words# Competitive Pricing Research competitor pricing strategies by extracting pricing pages, comparing product listings on Google Shopping and Amazon, and analyzing… ## 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_t… ## Available Tools - `strale_pricing_page_extract` - `google_shopping_bulk_products` - `amazon_bulk_product_details` - `context_dev_extract_structured_data` - `firecrawl_scrape`
Word-for-word excerpt, not a result. Read the full SKILL.md ↓
Files of Competitive pricing
Show the full text37 lines
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 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_extractgoogle_shopping_bulk_productsamazon_bulk_product_detailscontext_dev_extract_structured_datafirecrawl_scrape
Workflow
- Understand the user's research question, target, and context.
- Call
sandbase_describe_toolfor each selected tool to confirm parameter schema. - Call
sandbase_call_toolwith the exact tool_name and schema-defined arguments. - Synthesize findings into a clear, evidence-backed answer.
- Cite sources, note evidence gaps, and separate observations from interpretations.
Guidelines
- Always call
sandbase_describe_toolbefore 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.
| 1 | |
| 2 | name competitive-pricing |
| 3 | 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." |
| 4 | |
| 5 | |
| 6 | # Competitive Pricing |
| 7 | |
| 8 | 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] before selecting a capability. |
| 9 | |
| 10 | ## Call SandBase capabilities |
| 11 | |
| 12 | 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`. |
| 13 | |
| 14 | ## Available Tools |
| 15 | |
| 16 | `strale_pricing_page_extract` |
| 17 | `google_shopping_bulk_products` |
| 18 | `amazon_bulk_product_details` |
| 19 | `context_dev_extract_structured_data` |
| 20 | `firecrawl_scrape` |
| 21 | |
| 22 | ## Workflow |
| 23 | |
| 24 | Understand the user's research question, target, and context. |
| 25 | Call `sandbase_describe_tool` for each selected tool to confirm parameter schema. |
| 26 | Call `sandbase_call_tool` with the exact tool_name and schema-defined arguments. |
| 27 | Synthesize findings into a clear, evidence-backed answer. |
| 28 | Cite sources, note evidence gaps, and separate observations from interpretations. |
| 29 | |
| 30 | ## Guidelines |
| 31 | |
| 32 | Always call `sandbase_describe_tool` before using any capability. |
| 33 | Cite sources and preserve attribution (URLs, usernames, dates, metrics). |
| 34 | Separate factual observations from analysis and recommendations. |
| 35 | If data is unavailable, note the gap and continue with available evidence. |
| 36 | Read-only research only. Never take actions on platforms. |
| 37 |
Discussion
Alternatives
Browse more free Claude skills or everything in Sales.