agentleFS
intelligems-iointelligems-io/intelligems-mcp-skills/skills/price-sensitivity-analysis/SKILL.md

price-sensitivity-analysis

Skill0 starsChanged 5 months agoMITView on GitHub

Use when a user asks what Intelligems test data says about price tolerance, discount response, AOV tradeoffs, or segment-specific price behavior.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    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:

    Use this skill to interpret price, discount, shipping, and offer tests.

    line 9
  2. Distinctive:

    Search relevant experiences by name, category, or explicit IDs.

    line 14
  3. Distinctive:

    Do not recommend a permanent pricing change without profit evidence and business-context caveats.

    line 37
  4. Distinctive:

    Use only the user's authenticated MCP or API context.

    line 41

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Price Sensitivity Analysis

Use this skill to interpret price, discount, shipping, and offer tests.

Steps

  1. Resolve organization, period, and product or offer scope.
  2. Search relevant experiences by name, category, or explicit IDs.
  3. Analyze overview metrics first: conversion rate, RPV, GPV, AOV, net revenue, confidence.
  4. Segment the results by device, visitor type, country, traffic source, and landing page when relevant.
  5. Compare results across tests to identify repeatable price tolerance patterns.

Questions To Answer

  • Did price or discount changes increase profit, not just conversion?
  • Which segments are most price-sensitive?
  • Did higher AOV offset lower conversion, or did lower price dilute value?
  • Are discounts training behavior or unlocking incremental demand?
  • What guardrails should future price tests use?

Output

Return:

  1. Price sensitivity summary.
  2. Evidence table by test and segment.
  3. Profit and risk interpretation.
  4. Recommendations for pricing, discounting, and follow-up tests.
  5. Caveats around sample size, seasonality, and missing margin data.

Do not recommend a permanent pricing change without profit evidence and business-context caveats.

Data Safety

Use only the user's authenticated MCP or API context. Do not save raw responses, exports, graph URLs, order data, customer data, or private store identifiers to the repository. Summarize findings and include experience IDs only when needed for the user's workflow.

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.