home / skills / onewave-ai / claude-skills / competitor-price-tracker

competitor-price-tracker skill

safe

This skill helps you monitor competitor pricing pages, detect price changes, and generate actionable recommendations for faster pricing decisions.

npx playbooks add skill onewave-ai/claude-skills --skill competitor-price-tracker

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

1.5 KB

---
name: competitor-price-tracker
description: Monitor competitor pricing pages and send alerts when prices change. Track discount patterns, promotional cycles, and pricing strategy shifts.
---

# Competitor Price Tracker
Monitor competitor pricing pages and send alerts when prices change. Track discount patterns, promotional cycles, and pricing strategy shifts.

## Instructions

You are an expert at competitive intelligence and pricing analysis. Monitor competitor pricing strategies, identify patterns, and provide actionable recommendations for pricing decisions.

### Output Format

```markdown
# Competitor Price Tracker Output

**Generated**: {timestamp}

---

## Results

[Your formatted output here]

---

## Recommendations

[Actionable next steps]

```

### Best Practices

1. **Be Specific**: Focus on concrete, actionable outputs
2. **Use Templates**: Provide copy-paste ready formats
3. **Include Examples**: Show real-world usage
4. **Add Context**: Explain why recommendations matter
5. **Stay Current**: Use latest best practices for sales

### Common Use Cases

**Trigger Phrases**:
- "Help me with [use case]"
- "Generate [output type]"
- "Create [deliverable]"

**Example Request**:
> "[Sample user request here]"

**Response Approach**:
1. Understand user's context and goals
2. Generate comprehensive output
3. Provide actionable recommendations
4. Include examples and templates
5. Suggest next steps

Remember: Focus on delivering value quickly and clearly!

Overview

This skill monitors competitor pricing pages and sends timely alerts when prices change, enabling quick response to market moves. It tracks discount patterns, promotional cycles, and broader pricing strategy shifts to surface trends and actionable insights. The skill is implemented in Python and designed for production-ready monitoring and reporting.

How this skill works

The tracker crawls specified competitor product pages on a scheduled cadence, extracts price and promotion fields, and normalizes values for comparison. It stores historical price points, detects significant changes or pattern shifts, and generates alerts via email or webhook. Analytical routines summarize discount frequency, average promotional depth, and seasonality to inform pricing decisions.

When to use it

When you need real-time alerts for competitor price changes
To analyze competitors' promotional cadence and discount depths
Before launching a new promotion to avoid margin erosion
When setting automated repricing or price-matching rules
To produce periodic competitive pricing reports for leadership

Best practices

Track a focused list of direct competitors and representative SKUs rather than every product page
Normalize currencies, unit sizes, and bundle pricing before comparison
Set thresholds for alerts (e.g., absolute change, percentage change, or new promotion flag)
Respect robots.txt and rate limits; use caching and backoff to avoid being blocked
Validate parsed price fields with periodic manual checks to avoid false positives

Example use cases

Send instant alerts when a competitor drops price more than 5% on a top-selling SKU
Identify recurring weekend or holiday promotions to time your own discounts
Compare average promotional depth across competitors to set competitive margin targets
Feed price-change events into a dynamic repricer or CRM workflow via webhook
Generate weekly executive summaries showing price volatility and recommended actions

FAQ

How often should I check competitor prices?

Frequency depends on market dynamics: high-velocity categories may need hourly checks, while stable categories can use daily or weekly sampling.

How do you avoid false positives from temporary formatting changes?

Use multi-field validation (price, currency, promotion tag), schema validation, and fall back to manual review for unexpected parsing failures before alerting.