agentleFS
OneWave-AIOneWave-AI/claude-skills/competitor-price-tracker/SKILL.md

competitor-price-tracker

Skill378 starsChanged 52 days agoMITView on GitHub

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

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Stay Current: Use latest best practices for sales

    line 40

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

# 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!

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.