Agent skill · Business & Finance

pricing-packaging-planner

Use when the user asks to "plan launch pricing", "design pricing tiers / packaging", or "set up a launch discount / early-bird offer"; produces a launch pricing and packaging plan — tier structure and naming, a value-to-price map aligned to the message house, a launch-offer ladder with a true deadline reason, beta / early-adopter pricing with a post-launch graduation path, and guarantee / refund terms — with every price claim and offer term submitted to memory/events/claims.ndjson. Not for the canonical offer / claim record — use offer-claims-registry; not for paid-newsletter subscription econ

aaron-he-zhugithub.com/aaron-he-zhuGitHub ↗
claude-codeApache-2.0
Install
npx skills add aaron-he-zhu/aaron-marketing-skills --skill pricing-packaging-planner --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 13 KB
Bundled scripts: none
Version: 19.1.0
Requires: Claude Code and compatible agent-skill hosts
Path: launch/assemble/pricing-packaging-planner/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 2,508
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Pricing Packaging Planner Plans what a launch charges and how it is packaged — tier structure and naming, a value-to-price map tied to the message-house pillars, a launch-offer ladder with a true deadline reason, beta / early-adopter pricing with its graduation path, and guarantee / refund design. It sits in the **Assemble** phase of the RAMP loop and feeds the RAMP `A` sub-item "pricing & packaging clear (tiers, launch-offer terms, guarantee/refund)"; the pricing state it declares per stage (a live pricing page when GA promises public paid availability) is also what the `R1` stage-truth check reads downstream. It works one lever — pricing/packaging — and hands off. Every price claim, discount term, and guarantee wording it drafts is a **candidate**, not a live offer: it submits them to `memory/events/claims.ndjson` via an authorized `operation: propose` request to `registry-events.py`, and [offer-claims-registry](../../../protocol/offer-claims-registry/SKILL.md) — whose `offers.md` is the live-offer SSOT — formalizes them. **Scope guard**: this skill designs launch pricing and packaging only. It does **not** own the canonical offer / claim record ([offer-claims-registry](../../.

What's inside
Steps it walks through
  1. Quick Start
  2. Skill Contract
  3. Handoff Summary
  4. Data Sources
  5. Instructions
  6. Save Results
  7. Reference Materials
  8. Next Best Skill
More from aaron-marketing-skills
All skills →
About this skill
What does the pricing-packaging-planner skill do?

Use when the user asks to "plan launch pricing", "design pricing tiers / packaging", or "set up a launch discount / early-bird offer"; produces a launch pricing and packaging plan — tier structure and naming, a value-to-price map aligned to the message house, a launch-offer ladder with a true deadline reason, beta / early-adopter pricing with a post-launch graduation path, and guarantee / refund terms — with every price claim and offer term submitted to memory/events/claims.ndjson. Not for the canonical offer / claim record — use offer-claims-registry; not for paid-newsletter subscription econ

How do I install it?

Run `npx skills add aaron-he-zhu/aaron-marketing-skills --skill pricing-packaging-planner --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From aaron-he-zhu/aaron-marketing-skills, a repository with 2,508 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going