agentleFS
Nomanriaz786Nomanriaz786/claude-consulting-team/skills/discount-governance/SKILL.md

discount-governance

Skill1 starsChanged 25 days agoMITView on GitHub

Designs discount controls when pricing exceptions need clearer economics, authority and monitoring.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use when exceptions are frequent, approval is unclear or similar customers receive materially different terms.

    line 9
  2. Distinctive:

    Test whether deeper discounts correlate with volume, retention or deal speed.

    line 21
  3. Distinctive:

    Create an approval matrix with authority, evidence and expiry requirements.

    line 23

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

Discount Governance

When to use it

Use when exceptions are frequent, approval is unclear or similar customers receive materially different terms.

What Claude needs

  • Background from client-context.md
  • Transaction-level list and realised prices
  • Discount reasons, approvers and contract terms
  • Customer, product, channel and seller attributes
  • Contribution floors and strategic exception criteria

Method

  1. Build a discount waterfall from list price to realised net price.
  2. Segment discount depth and frequency using Pareto analysis.
  3. Test whether deeper discounts correlate with volume, retention or deal speed.
  4. Define floors and exception bands using contribution and value evidence.
  5. Create an approval matrix with authority, evidence and expiry requirements.
  6. Specify monitoring for leakage, exceptions and unintended deal behaviour.

Output format

Provide a leakage summary, discount bands and approval matrix. Include required evidence, approver, expiry, audit field and escalation trigger.

Quality checks

  • Credits and non-price concessions are included.
  • Governance preserves justified strategic exceptions.
  • Authority levels align with economic exposure.

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.