agentleFS
asgard-ai-platformasgard-ai-platform/skills/algo-price-elasticity/SKILL.md

algo-price-elasticity

Skill238 starsChanged 6 months agoMITView on GitHub

Calculate price elasticity of demand to quantify how price changes affect sales volume. Use this skill when the user needs to estimate demand sensitivity, set optimal prices, or evaluate the revenue impact of price changes — even if they say 'how sensitive are customers to price', 'will a price increase hurt sales', or 'elasticity calculation'.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When you need consumer willingness-to-pay distribution (use Van Westendorp or conjoint)

    line 23
  2. Distinctive:

    When pricing multiple products together (use bundle pricing)

    line 24
  3. Distinctive:

    Check: sign should be negative (price up → quantity down).

    line 46
  4. Very specific:

    Run python scripts/arc_elasticity.py --verify to execute built-in sanity tests.

    line 90

≈ “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

Price Elasticity of Demand

Overview

Price elasticity measures the percentage change in quantity demanded for a 1% change in price. Ed = %ΔQ / %ΔP. |Ed| > 1 = elastic (price-sensitive), |Ed| < 1 = inelastic (price-insensitive). Critical for pricing decisions and revenue optimization.

When to Use

Trigger conditions:

  • Estimating how a price change will affect unit sales and revenue
  • Determining if demand is elastic or inelastic for a product
  • Optimizing price for maximum revenue or profit

When NOT to use:

  • When you need consumer willingness-to-pay distribution (use Van Westendorp or conjoint)
  • When pricing multiple products together (use bundle pricing)

Algorithm

IRON LAW: Elasticity Is NOT Constant Along a Linear Demand Curve
It varies at every price point. At high prices, demand is elastic
(small price increase → big volume drop). At low prices, demand is
inelastic. Always calculate at the SPECIFIC price point of interest.
Revenue-maximizing price is where Ed = -1 (unit elastic).

Phase 1: Input Validation

Collect: price-quantity pairs over time (or across markets). Control for: seasonality, promotions, competitor actions, other confounders. Gate: Minimum 10 price-quantity observations, confounders identified.

Phase 2: Core Algorithm

Point elasticity: Ed = (dQ/dP) × (P/Q) at a specific price point Arc elasticity: Ed = ((Q₂-Q₁)/((Q₂+Q₁)/2)) / ((P₂-P₁)/((P₂+P₁)/2)) between two points Regression method: log(Q) = α + β×log(P) + controls → β is the elasticity (constant elasticity model)

Phase 3: Verification

Check: sign should be negative (price up → quantity down). Cross-validate with holdout periods. Gate: Elasticity is negative, confidence interval is reasonable.

Phase 4: Output

Return elasticity estimate with revenue impact projection.

Output Format

{
  "elasticity": -1.5,
  "interpretation": "elastic — 1% price increase → 1.5% quantity decrease",
  "revenue_impact": {"price_change_pct": 10, "quantity_change_pct": -15, "revenue_change_pct": -6.5},
  "metadata": {"method": "log-log regression", "r_squared": 0.82, "observations": 52}
}

Examples

Sample I/O

Input: Price increased 10% from $100 to $110, quantity dropped from 1000 to 850 Expected: Arc elasticity = ((-150/925) / (10/105)) = -1.70 (elastic)

Edge Cases

InputExpectedWhy
Luxury goodMay be positive (Veblen)Higher price → higher perceived value
Necessity (insulin)Near zeroDemand barely responds to price
Perfect substitute availableVery elastic (< -3)Customers switch immediately

Gotchas

  • Omitted variable bias: Without controlling for advertising, seasonality, and competitor prices, elasticity estimates are biased.
  • Short-run vs long-run: Short-run elasticity is typically lower (customers are locked in). Long-run gives them time to find substitutes.
  • Cross-price elasticity: Demand for product A may depend on product B's price. Ignoring this in a portfolio context leads to suboptimal pricing.
  • Asymmetric elasticity: Consumers may react differently to price increases vs decreases. Don't assume symmetry.
  • Small sample noise: With few observations, elasticity estimates have wide confidence intervals. Report intervals, not just point estimates.

Scripts

ScriptDescriptionUsage
scripts/arc_elasticity.pyCompute arc elasticity and revenue impactpython scripts/arc_elasticity.py --help

Run python scripts/arc_elasticity.py --verify to execute built-in sanity tests.

References

  • For regression-based elasticity estimation, see references/regression-estimation.md
  • For cross-price elasticity analysis, see references/cross-price.md

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.