Promotion Calendar Planner

Design monthly, quarterly, or annual ecommerce promotion calendars using business goals, platform mega-sale windows, inventory posture, and team capacity, th...

Security Scan

The skill's code, instructions, and resource needs are consistent with a standalone promotion-calendar planner and do not request unrelated credentials, installs, or system access.

Purpose & Capability

Name/description, SKILL.md workflow, and the included handler.py align: the skill transforms user planning notes into a structured promotion calendar. It declares no external dependencies, credentials, or config paths, which matches its stated offline, heuristic MVP purpose.

Instruction Scope

SKILL.md explicitly states it does not connect to live calendars or ad platforms and defines a bounded input/output contract (user planning notes -> markdown plan). The provided instructions do not ask the agent to read unrelated files or environment secrets.

Install Mechanism

No install spec is provided (instruction-only), so nothing is fetched or written during install. The presence of handler.py means the skill contains code, but there is no installer or external download mechanism declared.

Credentials

The skill declares no required environment variables or credentials and the visible code only reads the local SKILL.md and the provided user input. There is no indication it accesses unrelated credentials or external services.

Persistence & Privilege

always is false and there are no signs the skill modifies other skills or system-wide agent settings. The skill appears to run on demand and does not request permanent presence or elevated privileges.

Assessment

This skill appears coherent and low-risk: it uses local heuristics to generate markdown promotion plans and does not request secrets or install external software. Before installing, you may want to: (1) quickly scan the remainder of handler.py (not shown in the truncated snippet) for any network calls or os.environ access; (2) run the included tests locally to confirm behavior; and (3) avoid granting credentials or enabling always:true unless you need autonomous background execution. If the skill later requests API keys or tries to call external endpoints, treat that as a red flag.

Overview

Use this skill to turn annual goals, platform nodes, inventory posture, and team resource notes into a structured promotion calendar. It is designed for operators who need a promotion cadence they can explain to management and hand off to cross-functional teams.

This MVP is heuristic. It does not connect to live calendars, ad platforms, merchandising systems, or project-management tools. It relies on the user's planning notes, seasonal context, and team constraints.

Trigger

Use this skill when the user wants to:

• map a monthly, quarterly, or annual promotion cadence
• decide which sale nodes deserve a full push versus a lighter supporting role
• balance revenue, margin, inventory digestion, and team workload in one schedule
• prepare a promotion roadmap for ops, design, supply chain, and customer service
• turn rough campaign ideas into a sequenced business calendar with risk notes

Example prompts

• "Build our Q4 promotion calendar around 11.11 and Black Friday"
• "Create a quarterly promo plan that also helps us digest aged inventory"
• "We need a yearly promotion roadmap for our ecommerce team"
• "Plan a lighter monthly cadence without overloading design and customer service"

Workflow

1. Capture the planning window, business goal, seasonal anchors, and major capacity constraints.
2. Separate mandatory nodes, optional support nodes, and nodes that should probably be skipped.
3. Translate each node into a role such as acquisition, conversion, clearance, or retention.
4. Attach category focus, price posture, team preparation needs, and avoidable conflicts.
5. Return a markdown promotion plan with a calendar table, cadence principles, and a team checklist.

Inputs

The user can provide any mix of:

• annual, quarterly, or monthly business goals
• platform nodes such as 618, Prime Day, 11.11, Black Friday, or brand days
• inventory posture such as healthy core stock, aged stock, or constrained hero SKUs
• category seasonality and hero categories
• resource limits across ops, design, supply chain, CRM, media, or customer service
• margin rules, discount rules, or customer-experience constraints

Outputs

Return a markdown plan with:

• a promotion calendar table
• cadence principles before, during, and after major nodes
• a team preparation checklist
• conflict watchouts and risk notes
• assumptions and limits

Safety

• Do not claim access to live calendars, platform policy feeds, or ad platforms.
• Verify official sale dates and platform rules before locking any execution plan.
• Keep pricing, discount depth, and activation decisions human-approved.
• Treat the plan as a baseline operating rhythm, not a substitute for daily campaign management.

Best-fit Scenarios

• quarterly and annual ecommerce promotion planning
• cross-functional promotion alignment across ops, design, supply chain, and service
• businesses that need more structure than a spreadsheet of holiday names
• teams trying to reduce promotion chaos and discount overlap

Not Ideal For

• live campaign pacing and day-to-day media management
• fully automated marketing orchestration
• businesses with no meaningful seasonality or promotion planning rhythm
• regulated categories where promotional language requires extensive review first

Acceptance Criteria

• Return markdown text.
• Include calendar table, cadence principles, team checklist, and risk notes.
• Explain why key nodes matter instead of listing dates only.
• Surface at least two avoidable planning conflicts.