Skills

How to Build a Skill That Checks Your Prices Against Competitors

Build a Claude skill that compares your prices with competitors' public pricing pages every week and reports the gaps in a clean table.

Supermarket shelves with yellow price tags showing product prices for competitor price comparison
Image: Pixabay / Pixabay Content License

Key Takeaways

  • A price-checking skill is a SKILL.md file plus a price-list reference file; Claude loads it only when your request matches its description.
  • Anthropic's rules: name max 64 chars (lowercase, numbers, hyphens); description max 1,024 chars and must say what the skill does and when to use it.
  • Run it in Claude Code or claude.ai — the Claude API gives skills no network access, so it cannot fetch live prices there.
  • Require a source and a check date for every price, and "could not verify" instead of a guessed price.

A price-checking agent skill is a reusable set of instructions that tells Claude how to compare your prices with your competitors’ prices and report back in a consistent format. Build it once as a SKILL.md file, install it in Claude Code or claude.ai, and a weekly “check my prices” prompt returns a clean comparison table.

Small businesses lose sales quietly when a competitor drops a price and nobody notices for a month. Checking by hand means opening five pricing pages and copying numbers into a spreadsheet — work nobody schedules. A skill turns that chore into a routine: same products, same competitors, same output, every week.

What You Will Build

The skill does one job: given your product list and 3–5 competitors, it finds each competitor’s current price for the matching product, compares it with yours, and flags anything that moved. It does not set your prices — you decide; the skill only gathers and formats.

Know one honest limit first. Anthropic’s docs say Skills on the Claude API run in a sandboxed container with no network access, so they cannot fetch live pages there. Build this skill for Claude Code, which has network access, or for claude.ai, where access varies by plan and admin settings. If a site blocks automated visits, the skill should say so — never invent a price it could not verify.

Prerequisites

  • A claude.ai account on a paid plan (Pro, Max, Team, or Enterprise) with code execution enabled, or Claude Code installed on your computer.
  • 5–10 products to track, plus 3–5 competitors with each pricing page URL.
  • Your current prices in a simple file — a spreadsheet or a Markdown table works.
  • About 45 minutes for the first build, then 10 minutes a week to run it.

Step 1: Define Exactly What Gets Compared

Write down the comparison before you write the skill. For each product, record your price, the competitor’s matching product name, and its pricing page URL. Mismatched products are the top cause of useless comparisons: your “Standard” plan and a rival’s “Starter” plan are rarely the same thing. Set a weekly cadence in the skill.

Step 2: Create the Folder and the Frontmatter

Every skill is a folder containing a SKILL.md file. Create a folder named price-check for it. The file starts with YAML frontmatter holding two required fields. Per Anthropic’s docs, the name is at most 64 characters — lowercase, numbers, and hyphens only, without the words “anthropic” or “claude” — and the description is at most 1,024 characters, non-empty, and must say what the skill does and when to use it.

---
name: price-check
description: Compares our prices with named competitors' public pricing pages and reports the gaps in a table. Use when the user asks to check or compare competitor prices.
---

# Price Check

## Workflow

1. Read `prices.md` in this folder for our current prices and the competitor list.
2. For each product, visit the competitor's pricing page and record the matching product's current price, with the date checked.
3. Build a table: product, our price, each competitor's price, difference in percent. Flag prices that changed and any competitor now cheaper than us.

## Rules

- Only use prices visible on the competitor's own public pricing page. Never guess a price.
- If a page cannot load, write "could not verify" and say why. Always show the date checked. Never change our prices.

The description is the trigger: Claude reads only the name and description at startup — about 100 tokens per skill, per Anthropic’s docs — and loads the rest only when your request matches. Use the exact phrases you will actually type. New to skill structure? Our guide to creating your first Claude skill covers the folder layout and installation paths.

Step 3: Add Your Price List as a Reference File

Keep the data out of the instructions. Save your products, prices, and competitor URLs in prices.md in the same folder, and tell SKILL.md to read it. Claude loads reference files only when needed — Anthropic calls this progressive disclosure — so a long price list costs nothing until a check runs. Update prices.md whenever your prices change.

Step 4: Install It Where You Work

Install it separately on each surface — custom skills do not sync. In Claude Code, copy the folder into ~/.claude/skills/ (personal) or the project’s .claude/skills/ folder (shared with the team); Claude Code discovers it automatically. On claude.ai, zip the folder — the folder itself must be inside the zip, not loose files at the root — and upload it in Settings under Features, with code execution enabled.

Step 5: Test It With Real Prompts

Try “run the weekly price check” and a casual phrasing like “are we still cheaper than Acme on the Standard plan?” Check three things: does it fire when it should, does every price carry a source and a date, and does it say “could not verify” instead of guessing when a page fails? If it fires on the wrong tasks, the description is too broad; if it never fires, it is too narrow. Fix the description first.

Step 6: Make It a Weekly Habit

A 10-minute weekly slot is enough once the setup exists. Save each report in the same place so you can see trends. When a big move appears, dig deeper before reacting: our Perplexity competitor research workflow shows how to investigate a rival’s pricing changes with cited sources.

Tips and Common Mistakes

  • Compare like with like. Note plan limits and included features next to each price, or a cheaper-looking rival will mislead you.
  • Date every price. A price without a check date is a rumor. Require the skill to stamp each row.
  • Do not scrape aggressively. Read public pricing pages respectfully and follow each site’s terms. If a page blocks the skill, record “could not verify” and move on.

FAQ

Do I need to code to build a price-checking skill?

No. A basic skill is a folder with a Markdown file and a price list — the same writing you would do for a standard operating procedure. Scripts are optional.

Will the skill work in claude.ai, Claude Code, and the API?

Not the same way everywhere. It works best in Claude Code, which has network access, and in claude.ai with code execution enabled. Through the Claude API, skills have no network access, so they cannot fetch live competitor pages.

What if a competitor’s pricing page cannot be read?

It should write “could not verify” for that row, explain why, and continue with the rest. Never let it fill the gap with a guessed price — a missing price is honest, an invented one is a bad decision waiting to happen.

Conclusion

A price-checking skill will not set your prices, but it will end the month-long blind spots where a competitor quietly undercuts you. Define the comparison, write a focused SKILL.md, keep your price list in a reference file, and test it until it fires reliably. Run it weekly and verify the numbers that matter against the competitor’s own page.

WebGool Tech Senior AI & Small Business Editor
Verified Contributor

Keep Reading

More in Skills

Explore all

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top