markdown-optimizer
Skill21 starsChanged 5 months agoMITView on GitHub
Recommend a discount percentage and new price for each slow-moving product by running the bundled markdown_optimizer.py script, respecting pricing guardrails that come from the Store Policy Agent (never hardcode them). Use after sales-analysis-chart has identified the slow movers and after fetching the markdown guardrails via the Store Policy Agent's get_markdown_policy. The script applies the max-discount cap and margin floor, computes each new price and margin, flags items that cannot be meaningfully promoted within the floor for clearance instead, and renders a recommended-discount chart.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- microsoft/new-copilot-studio-tech-guide-krword for word, first seen Oct 25, 2026
Other versions1 project uses a version of this.
Word for word · 1
- microsoft/new-copilot-studio-tech-guide-kr★ 0100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository14 other files it gives its agents.
- distance-calculatorSkill
- bundle-settlement-calculatorSkill
- membership-card-pdfSkill
- membership-card-pngSkill
- merch-report-htmlSkill
- points-reconciliationSkill
- prorated-refund-calculatorSkill
- sales-analysisSkill
- slip-pdf-generatorSkill
- membership-card-pngSkill
- prorated-refund-calculatorSkill
- points-reconciliationSkill
- slip-pdf-generatorSkill
- membership-card-pngSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 16
After sales-analysis-chart has produced the structured slow_movers list, and after you have fetched the guardrails from the Store Policy …
- Very specific: line 24
Guardrails: - call the Store Policy Agent - get_markdown_policy("promo").
- Very specific: line 66
Call out any item flagged for clearance, noting clearance is a separate manager decision (get_markdown_policy("clearance")).
- Distinctive: line 77
All data is mock; recommendations are for demo purposes only.
≈ “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.
Files
Markdown Optimizer (BlastBox Omega)
This skill decides how much to mark down each slow-moving product by running the
bundled markdown_optimizer.py script. You do not write any Python and you do
not hardcode the pricing rules: the guardrails come from the Store Policy Agent
via get_markdown_policy(markdown_type) and are passed to the script as CLI flags. This
keeps all policy in one place (the Policy Agent owns it).
When to use
After sales-analysis-chart has produced the structured slow_movers list, and after
you have fetched the guardrails from the Store Policy Agent. Use it whenever a
manager asks what to mark down and by how much within policy.
Inputs (gather these first, then pass them as flags)
- Slow movers - the
slow_moversJSON fromsales-analysis-chart: a list of{sku, name, price, cost}(extra keys are ignored). - Guardrails - call the Store Policy Agent -
get_markdown_policy("promo"). It returnsmax_discount_pct,margin_floor_pct, andmin_useful_promo_discount_pct(e.g.30,15,10). Pass all three. Do not invent or hardcode them. For a clearance pass, callget_markdown_policy("clearance")and use--markdown-type clearance.
Run the bundled script
For a promo markdown, pass the slow movers and the three guardrails:
python3 markdown_optimizer.py \
--markdown-type promo \
--max-discount 30 --margin-floor 15 --min-useful 10 \
--slow-movers '[{"sku":"SKU-VR-NEBULA","name":"Nebula VR Headset","price":199.99,"cost":70.00},
{"sku":"SKU-GALAXY-PAD","name":"Galaxy Pad Controller","price":49.99,"cost":18.00}]'For a clearance pass (no promo math, every item flagged for a manager decision):
python3 markdown_optimizer.py --markdown-type clearance \
--slow-movers '[{"sku":"SKU-OMEGA-CORE","name":"Omega Core Console","price":399.99,"cost":320.00}]'The script prints one line per item, then RECOMMENDATIONS_JSON=<json>, and writes
markdowns.png (a bar chart of the recommended promo discounts).
What the script does (for your report, not for you to reimplement)
- floor price =
cost / (1 - margin_floor_pct/100)- the lowest price that still keeps the required gross margin. - recommended discount % =
min(max_discount_pct, floor-allowed %). When the cap binds you get the headline discount; when the floor binds the new margin equals the floor (bindingsays which). - Items whose floor-allowed discount is below
min_useful_promo_discount_pctcome back withflag_clearance: true- they can't be meaningfully promoted, so they should be cleared out via a clearance pass (a separate decision requiring a manager flag).
Report
- Present a table: product, current price, recommended discount %, new price, new margin, and whether the margin floor or max-discount cap was binding.
- Call out any item flagged for clearance, noting clearance is a separate manager
decision (
get_markdown_policy("clearance")). - Hand the finalized promo set (
RECOMMENDATIONS_JSON) to merch-report-pdf for the shareable report.
Notes
- The bundled script is
markdown_optimizer.py; it depends only onmatplotlib(available in the runtime) and prints recommendations even if the chart is skipped. - The guardrail numbers MUST come from the Store Policy Agent. If they are missing, fetch them before running - do not guess.
- All data is mock; recommendations are for demo purposes only.
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.

