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.
In this repository9 other files it gives its agents.
- api-integration-builderSkill
- client-performance-reviewSkill
- mcp-contextSkill
- profit-growth-auditSkill
- profit-trap-detectionSkill
- segment-intelligenceSkill
- testing-strategy-health-checkSkill
- test-roadmapSkill
- weekly-test-pulseSkill
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
- Distinctive: line 9
Use this skill to interpret price, discount, shipping, and offer tests.
- Distinctive: line 14
Search relevant experiences by name, category, or explicit IDs.
- Distinctive: line 37
Do not recommend a permanent pricing change without profit evidence and business-context caveats.
- Distinctive: line 41
Use only the user's authenticated MCP or API context.
≈ “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.
Files
Price Sensitivity Analysis
Use this skill to interpret price, discount, shipping, and offer tests.
Steps
- Resolve organization, period, and product or offer scope.
- Search relevant experiences by name, category, or explicit IDs.
- Analyze overview metrics first: conversion rate, RPV, GPV, AOV, net revenue, confidence.
- Segment the results by device, visitor type, country, traffic source, and landing page when relevant.
- 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:
- Price sensitivity summary.
- Evidence table by test and segment.
- Profit and risk interpretation.
- Recommendations for pricing, discounting, and follow-up tests.
- 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.
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.

