Digital product launch builder

Skill nahiddotai/operator-powers/plugins/operator-powers/skills/digital-product-launch-builder

Build a coordinated launch for a defined digital product, course, template, membership, workshop, or resource, including readiness, messages, calendar, assets, and measures.From its SKILL.md

Install

npx -y skills add nahiddotai/operator-powers --skill digital-product-launch-builder

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

28 days oldThe repository was created 28 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.2 KB, 440 tokens by cl100k_base, as published. Nobody here has run it

Digital Product Launch Builder

Turn a defined product into a launch the operator can actually run, measure, and adapt.

Job contract

Owns: coordinated launch of a defined digital product.
Does not own: defining what is sold (offer-builder) or isolated content transformation (content-repurposing).
Required input: product, buyer, promise, price or pricing status, delivery method, and launch constraints.
Finished deliverable: readiness gate, launch calendar, complete core messages, measurement plan, and contingency rules.

Workflow

Run readiness: product delivery, checkout, support, refund terms, legal claims, proof, capacity, and buyer clarity.
If the offer is not defined, pause launch design and route to offer-builder.
Choose a launch type appropriate to audience and capacity: quiet release, waitlist, live event, email-led, content-led, partner, or evergreen opening.
Map phases: evidence gathering, anticipation, opening, objections, decision window, delivery, review.
Build the message spine and channel sequence. Every asset must perform a distinct job.
Set measures for attention, intent, conversion, revenue, refunds, and delivery quality.
Add stop, extend, and change rules so results guide the launch.

Output

# Digital Product Launch

## Readiness Gate
[Ready, blocked, owner, fix]

## Launch Strategy
[Buyer, product, promise, type, dates, target]

## Message Spine
[Problem, belief, mechanism, proof, offer, objections]

## Launch Calendar
| Timing | Channel | Asset | Job | CTA | Owner |

## Core Assets
[Complete drafts for the essential sequence]

## Measurement And Decisions
[Metrics, thresholds, stop/change rules]

## Delivery And Review
[Customer experience, support, retrospective]

Guardrails

Never invent demand, testimonials, revenue targets presented as forecasts, scarcity, or deadlines.
Do not schedule, publish, email, spend, or change live checkout settings without explicit approval.
Keep the launch smaller than the operator's delivery capacity.

What ships with it: 1 file

248 B alongside SKILL.md

agents/

openai.yaml248 B