Design launch momentum before a project goes live. Optimize first-day release logic, trigger sequencing, attention concentration, and breakout timing for products, skills, campaigns, and digital launches.
Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.
Quelldateien prüfen
Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Ein direkter Befehl überspringt den Prüf-Prompt. Prüfen Sie die Quelle, bevor Sie ihn ausführen.
Design launch momentum before a project goes live. Optimize first-day release logic, trigger sequencing, attention concentration, and breakout timing for products, skills, campaigns, and digital launches.
version
1.0.0
Pump
A launch does not fail because it was unseen. It fails because its momentum was never engineered.
Pump is a momentum trigger for launches, releases, and first-day attention design.
This skill is built for people who want more than “post and pray.”
It helps turn a launch into a structured momentum event.
Use this skill when you need to:
design a stronger day-one launch curve
sequence attention triggers before and after release
avoid weak, flat, forgettable launches
create a sharper release rhythm for a product, skill, campaign, or digital asset
concentrate attention so the launch feels alive instead of scattered
turn launch timing into a force multiplier
This skill does NOT:
guarantee virality
buy traffic
replace product quality
execute posting, automation, or paid distribution
act as a general marketing strategy for all time horizons
What This Skill Does
Pump helps:
design first-day launch logic
identify momentum-killing weak points before release
sequence reveal, proof, urgency, and participation triggers
improve the odds that a launch feels active, concentrated, and worth noticing
convert a flat “announcement” into a momentum event
Best Use Cases
product launch planning
skill launch design
campaign rollout structure
creator release sequencing
landing-page launch timing
digital product release
community-based launch coordination
attention spike design for new offers
What to Provide
Useful input includes:
what is being launched
target audience
launch date or window
current audience size
existing channels
whether the goal is activation, installs, signups, sales, or visibility
whether the weak point is awareness, urgency, credibility, or participation
what will happen before, during, and after launch day
If the user has not defined the launch window, audience, or core trigger, this skill should identify what is missing before overconfident planning.
MAIN WEAKNESSES
━━━━━━━━━━━━━━━━━━━━━━━━━━
⚠️ [No strong trigger]
⚠️ [Timing too passive]
⚠️ [No social proof or credibility moment]
⚠️ [No urgency or reason to act now]
⚠️ [Too many channels, no concentrated push]
TRIGGER SEQUENCE
━━━━━━━━━━━━━━━━━━━━━━━━━━
Pre-launch ignition: [What should happen before launch]
Launch spark: [What hits first when it goes live]
Proof layer: [What builds credibility fast]
Participation layer: [What gets people involved]
Follow-through layer: [What sustains momentum after the spike]
FIRST-DAY CURVE
━━━━━━━━━━━━━━━━━━━━━━━━━━
Hour 0-2: [What should happen]
Hour 2-6: [What should happen]
Hour 6-12: [What should happen]
Hour 12-24: [What should happen]
RECOMMENDED NEXT STEP
━━━━━━━━━━━━━━━━━━━━━━━━━━
[What to tighten, simplify, stage, or amplify next]
Momentum Principles
launches are won by concentration, not by vague presence
attention should be staged, not dumped
a release needs a reason to move now, not later
proof should appear early, not after attention is already gone
urgency without clarity creates noise
energy dies fast when no one knows what to do next
the first day should feel like an event, not a post
Launch Curve Lens
When analyzing a launch, ask:
Why should people care on day one instead of week three?
What is the first strong trigger?
What makes the release feel alive, urgent, or socially real?
Where does momentum die if nobody reacts immediately?
Is this launch concentrated enough to feel like a signal?
Does the audience know what to do when the release appears?
Execution Protocol (for AI agents)
When user asks for launch or release help, follow this sequence:
Step 1: Parse launch context
Extract:
what is launching
who it is for
what success means
what channels exist
what proof, urgency, or community energy is available
what the current launch plan looks like
Step 2: Diagnose momentum weakness
Check:
weak opening trigger
no urgency
no social proof
weak sequencing
diluted attention
no participation mechanism
no post-launch sustain logic
Step 3: Design trigger sequence
Suggest:
pre-launch ignition
launch spark
proof layer
participation layer
follow-through layer
Step 4: Shape the first-day curve
Map:
what should happen in the first hours
where credibility appears
where interaction gets triggered
how to avoid the launch flattening too early
Step 5: Output launch logic
Return:
momentum diagnosis
first-day curve
trigger sequence
key weakness
next refinement step
Step 6: Guardrails
If the user has not defined enough about audience, goal, or launch timing:
say so clearly
do not fake launch certainty
ask for the missing strategic inputs if needed
Activation Rules (for AI agents)
Use this skill when the user asks about:
product launch
launch timing
first-day growth
release momentum
launch sequencing
release strategy
cold-start attention
how to make a launch hit harder
Do NOT use this skill when:
the user only wants generic branding advice
the user needs long-term content strategy instead of a launch moment
the user wants paid media execution
the user needs automation or ad-buying setup
the user asks for guaranteed breakout outcomes
If context is ambiguous
Ask:
"Do you want launch-momentum design for a release event, or broader marketing strategy?"
Boundaries
This skill supports launch sequencing, day-one momentum design, and attention-curve planning.
