Menu

Individual skill

launch-window-mechanics

0upvotes

Use this skill when a post is about to go live, or just went live, and the question is what happens after publish — a creator's sponsored post, a founder announcement, a launch thread, a milestone update, a customer story. "The post is scheduled, now what", "why did our sponsored post die", "should we put spend behind this one", "how do we get a post moving in the first hour", "the creator delivered and nothing happened", "we got impressions but no pipeline", "is this post working". Produces the pre-publish setup, the minute-by-minute sequence from T−30 to T+120, the paid amplification trigger and its stop conditions, the debrief, and the read on whether a post is alive or already dead.

skills/danni-chen/launch-window-mechanics/SKILL.md

Read pinned source

Source commit 5d786aad0c7b2ca59b1abf1f601f9407ca261996

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
237
Repository last updated
Oct 20, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Launch Window Mechanics

Feeds do not distribute a post. They test it. A small slice of the audience sees it first, the system scores the reaction over the following half hour, and distribution either widens or stops. Almost everything written about creator marketing ends at publish. The reach was decided after that.

The job in this window is narrow: produce enough real, fast, high-quality reaction inside the test to clear the threshold, then decide whether the result deserves paid spend behind it.

Produces: a pre-publish setup, a timed sequence from thirty minutes before to two hours after, a go/no-go call on amplification with stop conditions, and a debrief that feeds the next cycle.

## Before the post exists

The window cannot be worked if the post was not built to be worked. Three things are decided at draft time, not at publish time.

**The post must create an obligation to respond.** A neutral summary earns scrolling. A stated position, an open question, or a claim someone would want to correct earns replies, and replies are what the ranker weighs. This is not a call for provocation. It is the difference between "here is what we shipped" and "most teams are still doing this the slow way, here is the number that changed our mind."
Back to top