skills/grower/inventory-aging-risk-review/SKILL.md
--- name: inventory-aging-risk-review description: Identify cannabis cultivation batches at risk of aging out, losing potency, or missing sell-through windows — producing a prioritized aging risk memo with recommended actions for each at-risk batch. Use when a grower needs to know which inventory is approaching its value cliff and what to do before it's too late. Trigger phrases: "aging inventory", "which batches are at risk", "inventory expiring", "slow-moving stock", "sell-through risk", "flow
npx skillsauth add admin-baked/bakedbot-for-brands skills/grower/inventory-aging-risk-reviewInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Give a grower a clear view of which batches are approaching their value cliff — where potency loss, COA expiry, or buyer resistance will start costing real money — with enough lead time to act before the window closes.
daily-dispensary-ops-review; this skill is grower-sideorg_id — requiredbatch_inventory — list of batches with: strain, form (flower/concentrate/pre-roll), harvest date, test date, units on hand, units ordered (pending), storage locationcoa_expiry_dates — certificate of analysis expiry per batchpartner_orders — pending purchase orders that will absorb some of this inventoryreview_date — default: todayCannabis inventory ages along two independent clocks. Both must be tracked:
Clock 1: Quality / Potency Flower: peak quality window is 0–90 days post-harvest. After 90 days, terpene degradation becomes buyer-detectable. After 180 days, significant potency loss likely. Concentrates and edibles have longer windows but are not immune.
Clock 2: Regulatory / COA A Certificate of Analysis has a validity window (typically 12 months in NY). Once expired, the product cannot legally be sold until retested. Retesting costs time and money. Getting ahead of COA expiry is mandatory, not optional.
Risk tiers — apply to each batch:
| Tier | Condition | Action | |------|-----------|--------| | 🟢 Fresh | < 30 days post-harvest, COA valid 6+ months | Monitor only | | 🟡 Watch | 31–60 days, or COA valid 3–6 months | Flag; track weekly; prepare partner outreach | | 🟠 At Risk | 61–90 days, or COA valid 1–3 months | Priority outreach to partners; consider pricing flexibility | | 🔴 Urgent | 90+ days flower / 180+ days concentrate, or COA < 30 days to expiry | Immediate action: discount, donation, disposal planning, or retest |
Batch scoring:
Units at risk calculation:
(units_on_hand − units_on_pending_PO) × estimated_wholesale_price = revenue at risk
## Inventory Aging Risk Review — [Grower/Org] — [Date]
BATCHES REVIEWED: N | TOTAL UNITS AT RISK: N | REVENUE AT RISK: $X,XXX
### Risk Summary
| Tier | Batches | Units | Revenue at Risk |
|------|---------|-------|----------------|
| 🔴 Urgent | N | N | $X,XXX |
| 🟠 At Risk | N | N | $X,XXX |
| 🟡 Watch | N | N | $X,XXX |
| 🟢 Fresh | N | — | — |
### Urgent Batches (Act This Week)
| Batch | Strain | Form | Harvest Age | COA Expires | Units Uncommitted | Action |
|-------|--------|------|-------------|-------------|------------------|--------|
| B-042 | Blue Dream | Flower | 94 days | 45 days | 12 lbs | Partner outreach + price flex |
### At-Risk Batches (Act This Month)
[Same table format — 2–4 week window to act]
### Watch Batches
[List — no immediate action, track weekly]
### Recommended Actions
| # | Batch | Action | Owner | Deadline |
|---|-------|--------|-------|----------|
| 1 | B-042 | Contact top 3 velocity partners with preferential pricing | Sales | 3 days |
| 2 | B-039 | Schedule COA retest — expires in 28 days | Compliance | This week |
### Revenue Protection Summary
[Total uncommitted revenue at risk + estimated recoverable % if actions taken]
testing
--- name: executive-brief description: Produce a concise executive brief or portfolio digest for a super user or operator — use when summarizing multi-account performance, cross-org anomalies, top actions needed, or weekly business status for leadership review. Trigger phrases: "executive summary", "weekly brief", "portfolio digest", "top actions this week", "what needs my attention", "board update", "cross-account summary". version: 0.1.0 owner: platform agent_owner: pops allowed_roles: - sup
development
--- name: anomaly-to-action-memo description: Interpret a detected anomaly or signal and produce a decision-ready action memo — use when an alert, metric deviation, or operational signal needs to be turned into a prioritized recommendation with evidence, owner, and next step. Trigger phrases: "what does this anomaly mean", "something looks off", "explain this alert", "revenue is down", "traffic dropped", "flag this for review", "what should we do about this". version: 0.1.0 owner: ops-intelligen
testing
--- name: brand-voice description: Apply BakedBot brand voice standards to any customer-facing content — use when generating or reviewing copy that must match a dispensary or brand's approved tone, language patterns, and messaging constraints. Trigger phrases: "does this match our voice", "write in our brand voice", "on-brand copy", "brand guidelines", "tone check". version: 0.1.0 owner: platform agent_owner: craig allowed_roles: - super_user - dispensary_operator - brand_operator outputs:
testing
--- name: sell-through-partner-analysis description: Analyze which retail dispensary partners are selling through a grower's products effectively, identify top performers and laggards, and produce a prioritized partner action plan. Use when a grower wants to know where their products move fastest, which partners need attention, and where to focus wholesale sales effort. Trigger phrases: "which partners are selling our product", "sell-through analysis", "partner performance", "where is inventory