pricing-pocket-waterfall
Analyze Discount Leakage With Pocket-Price Waterfalls
Discounts, rebates, and credits can obscure the difference between list price and realized revenue. This workflow structures customer-level analysis and turns major deductions into policy recommendations.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "pricing-pocket-waterfall" from https://skillstore.io/skills/cmj-hub-pricing-pocket-waterfall.md and its manifest at https://skillstore.io/api/skills/cmj-hub-pricing-pocket-waterfall/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "pricing-pocket-waterfall". Annual list price is $1,000. Ramp discount is $100, volume discount is $50, and credits total $20. No other deductions apply.
Expected outcome:
- Illustrative pocket price: $830 per customer per year.
- Total deduction from list price: $170, or 17%.
- Largest deduction: ramp discount at $100.
- Policy review priority: verify the ramp discount duration and required commercial concession.
Using "pricing-pocket-waterfall". Strategic discounts average 12% of a $500,000 annual list-price revenue base. A proposed policy targets 8% without changing customer volume.
Expected outcome:
- Illustrative annual recovery: $20,000, calculated as a four-percentage-point reduction multiplied by $500,000.
- Required assumptions: unchanged revenue base, customer retention, and other deductions.
- Policy draft: require manager approval above 8% and record the commercial concession for each exception.
- This is a scenario estimate, not a guaranteed result or verified calculator output.
Security Audit
SafeAll 15 static findings are false positives: Markdown backticks and fixed documentation links do not establish command execution or unsafe traversal. No evidence found of prompt injection, credential access, or data exfiltration in the reviewed file. The referenced calculator and supporting documents were not included, so their behavior could not be verified.
Risk Factors
⚙️ External commands (12)
📁 Filesystem access (3)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/cmj-hub-pricing-pocket-waterfall/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/cmj-hub-pricing-pocket-waterfall?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/cmj-hub-pricing-pocket-waterfall?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/cmj-hub-pricing-pocket-waterfall/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/cmj-hub-pricing-pocket-waterfall.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
cmj-hub. (2026). pricing-pocket-waterfall security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/cmj-hub-pricing-pocket-waterfall/audits/1BibTeX citation
@techreport{cmj-hub-cmj-hub-pricing-pocket-waterfall-2026,
author = {cmj-hub},
title = {pricing-pocket-waterfall security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/cmj-hub-pricing-pocket-waterfall/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "pricing-pocket-waterfall security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "cmj-hub"
date-released: "2026-10-03"
url: "https://skillstore.io/skills/cmj-hub-pricing-pocket-waterfall/audits/1"
identifiers:
- type: other
value: "skillstore:cmj-hub-pricing-pocket-waterfall:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Assess Revenue Deductions
Review customer discount and credit data to distinguish list prices from realized prices and identify major deductions.
Draft Discount Approval Policies
Translate discretionary concessions into approval thresholds, required commercial exchanges, and standardized reason codes.
Prepare Cohort Pricing Reviews
Compare discount patterns across customer segments and prepare conservative recovery scenarios for a quarterly pricing review.
Try These Prompts
Review these available pricing fields: [fields]. List missing inputs needed for a pocket-price waterfall. Do not invent customer values.
Using [customer data], show deductions from annual list price to pocket price. State assumptions and missing values. Do not claim the absent calculator ran.
Review [discount findings] and [approval constraints]. Draft policies for deductions exceeding 5% of revenue. Include approval thresholds, required concessions, documentation, and reason codes.
Using [cohort data], rank the three largest deductions and compare segments. Estimate conservative recovery from [proposed discount changes]. State revenue bases, assumptions, and missing dependencies.
Best Practices
- Normalize billing cadence and distinguish percentage discounts from dollar deductions before comparing customers.
- Record missing data and inspect any separately obtained calculator before executing it with customer information.
- Use conservative recovery assumptions and connect approval thresholds to documented commercial concessions.
Avoid
- Treating list price as realized revenue while ignoring rebates, credits, or payment-term costs.
- Reporting successful script execution when the calculator is missing or its output is unavailable.
- Presenting a projected discount reduction as guaranteed recovery without retention and revenue-base assumptions.