sandbaseai/sandbase-skills / research/competitive-pricing
competitive-pricing
VerifiedResearch 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 2.2 KB |
| references/sandbase-api-map.md | markdown | 1.1 KB |
SKILL.md
View on GitHub---
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
Use the capability identifiers below as discovery hints, not MCP tool names. Find the matching endpoint with `sandbase_discover(q: "<provider and capability>")`; use its returned `name` in `sandbase_inspect(name: "<returned name>")`. Read `inputSchema`, pricing, and `execute_as`, then call `sandbase_run` using `execute_as.arguments.name` and schema-defined `arguments`. If a `run_id` is returned, poll `sandbase_run_get(run_id: "<returned run_id>")` within the task budget until `completed` or `failed`; report pending or failed runs without resubmitting them automatically.
## Capability identifiers
- `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. Resolve each selected capability with `sandbase_discover`, then inspect the returned `name` with `sandbase_inspect` to confirm the schema and pricing.
3. Follow `execute_as` with `sandbase_run`; collect async results with `sandbase_run_get` as described above.
4. Synthesize findings into a clear, evidence-backed answer.
5. Cite sources, note evidence gaps, and separate observations from interpretations.
## Guidelines
- Always call `sandbase_inspect` 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.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| add-product-e2e-evalpaperclipai/paperclipAdd or extend a Paperclip full-stack runner E2E workflow, fixture, matcher, or report evidence path for local or Daytona execution. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| add-runner-evalpaperclipai/paperclipAdd or extend a Paperclip Runner protocol evaluation definition, roster, assertion, or report fixture with provenance and narrow validation. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| diagnose-why-work-stoppedpaperclipai/paperclipCompatibility entry point for failed, stalled, looping, or over-recovered Paperclip work. Use fix-failed-paperclip-run for the full diagnosis, regression, repair, real verification, and green-PR workflow; honor an explicitly requested diagnosis-only scope. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| fix-failed-paperclip-runpaperclipai/paperclipDiagnose and fix failed, stuck, slow, or incorrectly blocked Paperclip tasks and runs. Use with a task/run URL or failure report to trace the root cause, prove a regression red then green, check second-order effects, verify the real workflow, and deliver a PR with passing checks. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |