competitive-pricing
Skill52 starsChanged 11 days agoApache-2.0View on GitHub
Produce a competitive pricing report comparing TechHub's catalog prices against current market prices, with flagged products and recommendations. Use when asked to benchmark prices, review pricing, or recommend price changes.
In this repository7 other files it gives its agents.
- agents/deep_support/AGENTS.mdAGENTS.md
- agents/pricing_research/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- order-troubleshootingSkill
- returns-and-warrantySkill
- order-troubleshootingSkill
- returns-and-warrantySkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Write the report to /reports/<category>_pricing.md.
- Very specific: line 28
Only recommend; changes go through propose_price_change and need approval.
≈ “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.
Files
Competitive pricing report
Steps
- Get our current prices for the requested products or category from the
catalog-analyst. - For each product, ask the
market-researcherfor current prices at 3+ major US retailers (for example Amazon, Best Buy, the manufacturer's store), with URLs and whether each is a sale price. - For each product compute: market median, our price, and the gap (
(ours - median) / median). - Flag products more than 5% above or 10% below the median.
- Write the report to
/reports/<category>_pricing.md.
Report format
| Product | Our price | Market median | Gap | Flag | Sources |
Sources are citation numbers, e.g. [1][2][3].
Then:
- Recommendations: one line per flagged product (raise, lower, hold), with the reason.
- Watch list: promotions or model refreshes that could move prices soon.
- Sources:
### Sources, one line per number:[1] Retailer - product: URL.
Only recommend; changes go through propose_price_change and need approval.
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
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.

