Oral Paper Skill
Adkid-Zephyr/oral-paper-skill
Help authors learn from exemplary ICLR, ICML, and NeurIPS papers through source-linked manuscript comparisons, concrete writing and experiment suggestions, and guided reflection.
A skill your agent uses 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…
$ npx skills add swan-gtm/gtm-skills --skill launch-window-mechanics -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install swan-gtm/gtm-skills launch-window-mechanics --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/swan-gtm/gtm-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/danni-chen/launch-window-mechanics .claude/skills/launch-window-mechanics && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "launch-window-mechanics" agent skill from https://github.com/swan-gtm/gtm-skills/tree/main/skills/danni-chen/launch-window-mechanics into .claude/skills/launch-window-mechanics/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "launch-window-mechanics", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/swan-gtm/gtm-skills/tree/main/skills/danni-chen/launch-window-mechanicsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add swan-gtm/gtm-skills --skill launch-window-mechanics -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install swan-gtm/gtm-skills launch-window-mechanics --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/swan-gtm/gtm-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/danni-chen/launch-window-mechanics .agents/skills/launch-window-mechanics && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "launch-window-mechanics" agent skill from https://github.com/swan-gtm/gtm-skills/tree/main/skills/danni-chen/launch-window-mechanics into .agents/skills/launch-window-mechanics/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "launch-window-mechanics", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add swan-gtm/gtm-skills --skill launch-window-mechanics -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install swan-gtm/gtm-skills launch-window-mechanics --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/swan-gtm/gtm-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/danni-chen/launch-window-mechanics .cursor/skills/launch-window-mechanics && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "launch-window-mechanics" agent skill from https://github.com/swan-gtm/gtm-skills/tree/main/skills/danni-chen/launch-window-mechanics into .cursor/skills/launch-window-mechanics/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "launch-window-mechanics", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/swan-gtm/gtm-skills.git --path skills/danni-chen/launch-window-mechanics--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add swan-gtm/gtm-skills --skill launch-window-mechanics -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install swan-gtm/gtm-skills launch-window-mechanics --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/swan-gtm/gtm-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/danni-chen/launch-window-mechanics .gemini/skills/launch-window-mechanics && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "launch-window-mechanics" agent skill from https://github.com/swan-gtm/gtm-skills/tree/main/skills/danni-chen/launch-window-mechanics into .gemini/skills/launch-window-mechanics/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "launch-window-mechanics", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install swan-gtm/gtm-skills launch-window-mechanicsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add swan-gtm/gtm-skills --skill launch-window-mechanics -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/swan-gtm/gtm-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/danni-chen/launch-window-mechanics .github/skills/launch-window-mechanics && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "launch-window-mechanics" agent skill from https://github.com/swan-gtm/gtm-skills/tree/main/skills/danni-chen/launch-window-mechanics into .github/skills/launch-window-mechanics/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "launch-window-mechanics", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add swan-gtm/gtm-skills --skill launch-window-mechanics -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install swan-gtm/gtm-skills launch-window-mechanics --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/swan-gtm/gtm-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/danni-chen/launch-window-mechanics .opencode/skills/launch-window-mechanics && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "launch-window-mechanics" agent skill from https://github.com/swan-gtm/gtm-skills/tree/main/skills/danni-chen/launch-window-mechanics into .opencode/skills/launch-window-mechanics/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "launch-window-mechanics", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
launch-window-mechanicsA skill your agent uses 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…
Launch Window Mechanics is an agent skill from swan-gtm/gtm-skills. 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…
Its SKILL.md is about 2.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including reference files (for example `references/amplification.md`, `references/consumer-ai.md` and `references/creator-scorecard.md`).
It sits in Product & Project Management, covering Storytelling and Project management. The repository describes itself as: Open, production-grade GTM skills for AI agents. The licence is MIT.
Read from SKILL.md and the folder at commit 67abd04. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Launch Window Mechanics loads about 2.8k tokens when it runs, and up to ~8.1k if it reads all its reference files. Until then it costs about 180 tokens; SKILL.md has 1,502 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from swan-gtm/gtm-skills at commit 67abd04, republished under its MIT licence (© swan-gtm). 1,502 words, ~2,774 tokens.
.claude/skills/launch-window-mechanics/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.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.
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."
Rights and attribution are contractual, not operational. The creator agreement must grant paid usage rights on the post itself, with a stated window. Without that clause, the post you spend six hours validating cannot be amplified, and renegotiating mid-window costs both time and leverage. This is the most common preventable failure in the sequence. Attribution goes in at the same time: a distinct tracking parameter or code per creator, and where links are not permitted, a read on branded-search lift instead.
The traffic needs somewhere to land. Reach is the entry, retention is the business. A spike arriving at a page with no next step is a spike that churns. Decide the destination before creating the demand: a signup path, a template, a resource, a community.
Choosing who to run this with: references/creator-scorecard.md.
Reactions are not worth the same, and the gaps between them are much larger than most teams assume. Ordered by leverage, strongest first:
| Signal | Why it scores | What it means operationally |
|---|---|---|
| Author replying to each commenter | Evidence of a live conversation rather than a broadcast | The highest-value action available, by a wide margin. Sit in the comments and answer individually |
| Substantive replies from others | Costs real effort, therefore hard to fake | Build the tension or open question into the post so that replying is the natural response |
| Reshares carrying added commentary | Redistributes into a graph the post could not otherwise reach | Line up two or three people who will add a genuine opinion, not agreement |
| Saves and bookmarks | The silent endorsement, and a strong quality proxy | Lists, data, and frameworks earn these; opinion posts rarely do |
| Profile clicks | The post made someone curious about the author | A byproduct of a clear point of view, not something to engineer |
| Likes | The weakest signal on offer | Likes with no replies is a recognised low-quality pattern |
| Hides, mutes, reports | Strongly negative, and suppressive | Exactly what purchased engagement produces |
Two structural constraints apply nearly everywhere. Outbound links in the post body suppress distribution, so the link goes in the first comment. Verified accounts receive materially wider reach than unverified ones, which makes verification a cost of entry rather than an upgrade.
Weightings, thresholds, and per-surface differences: references/platform-signals.md.
| When | Action |
|---|---|
| T−30 | Publish into the hours the target audience actually reads, not the hours convenient for the team. Draft the first comment carrying the link. Write three to five seed questions that would each pull a second person into the thread. Tell the people who genuinely care that it is about to go up |
| T+0–15 | Post the link comment immediately. The author answers every comment as it lands, individually, in substance. Target roughly ten substantive reactions inside fifteen minutes. This block clears the first threshold or it does not |
| T+15–60 | The author keeps replying and extends threads rather than closing them with thanks. Reshares with commentary land here. Post a second question to restart the conversation once the first wave settles |
| T+60–120 | Keep replying. Check the amplification trigger. Cross-post to a second surface for a second pulse rather than a duplicate |
| T+6–8h | The amplification decision resolves. Trigger met and sentiment positive, deploy. Otherwise let it run |
| T+2d | Publish the process teardown: how it was actually made, what it cost, what broke. Reliably produces a second wave, and it is planned in the original brief rather than improvised |
| T+3–7d | Publish the method or template and the getting-started path, so viewers become participants |
Never edit the original after publish. Never post and leave.
Paid spend does not rescue a weak post. It widens one that organic distribution already validated. The post itself is boosted so it stays native, rather than rebuilt as an ad, which discards the social proof that made it work in the first place.
Trigger. Engagement reaches roughly 1.5 to 2x the account's own trailing baseline, within six to eight hours of publish, with sentiment clearly positive. The baseline is that account's own recent performance, never a cross-industry benchmark, because a strong post on a small account and a weak post on a large one produce identical absolute numbers.
Stop. Cut on any one of these, not on all: cost per action running thirty percent over target for two consecutive days; frequency climbing while click-through declines; organic engagement on the original falling below its own baseline; a cluster of brand-safety-negative comments.
A trigger stated in numbers is what separates a decision from a habit. Without one, spend goes behind whatever the team happens to like.
Four-layer model, budget caps, test design, and a worked example: references/amplification.md.
The post goes live in an hour. Walk me through the setup.Six hours in: engagement is 1.4x our average, sentiment is mixed. Boost or hold?Our creator post got 900 likes and 4 comments. Is it working?Score these three creators for a launch we need to work hard in the first hour.© swan-gtm, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 5 other files (references) in skills/danni-chen/launch-window-mechanics of swan-gtm/gtm-skills.
Open the folder on GitHubat commit 67abd04
Launch Window Mechanics next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Launch Window Mechanics this skillswan-gtm/gtm-skills | 172 | — | ~2.8k | Automated safety check: Pass | MIT | |
| Oral Paper SkillAdkid-Zephyr/oral-paper-skill | 357 | — | ~1.9k | Automated safety check: Pass | None | |
| Prd V10 Case Study Buildermattgierhart/PRD-driven-context-engineering | 180 | — | ~2.9k | Automated safety check: Pass | MIT | |
| Operating System Visualizationmingchen666/Reviva | 244 | — | ~1.2k | Automated safety check: Pass | None | |
| CCPM Project Managementautomazeio/ccpm | 8.4k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Uvastral-sh/claude-code-plugins | 313 | 2 repos | ~980 | Automated safety check: Pass | Apache-2.0 |
Adkid-Zephyr/oral-paper-skill
Help authors learn from exemplary ICLR, ICML, and NeurIPS papers through source-linked manuscript comparisons, concrete writing and experiment suggestions, and guided reflection.
mattgierhart/PRD-driven-context-engineering
Build customer case studies as marketing and chasm-crossing reference assets during PRD v1.0 Market Adoption.
mingchen666/Reviva
A skill your agent uses whenever the user wants visual learning for operating systems, process states, CPU scheduling, Gantt charts, synchronization, semaphore/PV problems, deadlock, Banker's…
automazeio/ccpm
Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.
astral-sh/claude-code-plugins
Guide for using uv, the Python package and project manager. An agent skill from astral-sh/claude-code-plugins.
kunchenguid/firstmate
Agent-only procedure for Firstmate project management. An agent skill from kunchenguid/firstmate.
swan-gtm/gtm-skills
Annual and quarterly revenue plan construction, top-down vs bottoms-up reconciliation, plan versioning, stretch goal handling, and FP&A-RevOps collaboration for B2B revenue teams.
swan-gtm/gtm-skills
A skill your agent uses when setting up AI-powered personalization, building Clay or lemlist workflows, or automating prospect research — 6 AI personalization prompts (lemlist style) plus 2 email…
swan-gtm/gtm-skills
A skill your agent uses when a list of people already exists and someone needs to know who on it is worth contacting — event or webinar attendees, registrants, a prospecting export, a CRM segment, a…
swan-gtm/gtm-skills
A skill your agent uses when you need to know what people are saying about a brand across the web and social — "monitor brand mentions", "what are people saying about [brand] this week", "run a…
swan-gtm/gtm-skills
Use this skill before staging a prospect and before drafting any first touch, when a segment has gone silent, and when deciding whether an account is genuinely cold.
swan-gtm/gtm-skills
Use this skill on a monthly cadence to detect champions and heavy users of your paying customers who changed jobs, verify the move against live LinkedIn data, score the new company, and surface…
A skill your agent uses 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…. Launch Window Mechanics is an agent skill from swan-gtm/gtm-skills. 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.
Launch Window Mechanics fits situations like: A post is about to go live; the question is what happens after publish — a creators sponsored post; A founder announcement; A launch thread.
Run `npx skills add swan-gtm/gtm-skills --skill launch-window-mechanics -a claude-code`. Or copy the skill folder (skills/danni-chen/launch-window-mechanics in swan-gtm/gtm-skills) into .claude/skills/launch-window-mechanics in your project. Claude Code loads it when a task matches its description.
Run `npx skills add swan-gtm/gtm-skills --skill launch-window-mechanics -a codex`. Or copy the skill folder (skills/danni-chen/launch-window-mechanics in swan-gtm/gtm-skills) into .agents/skills/launch-window-mechanics in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add swan-gtm/gtm-skills --skill launch-window-mechanics -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/launch-window-mechanics, .gemini/skills/launch-window-mechanics, .github/skills/launch-window-mechanics and .opencode/skills/launch-window-mechanics in your project.
SKILL.md names no scripts, command-line tools or credentials: Launch Window Mechanics is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Launch Window Mechanics is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.8k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 5.4k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Launch Window Mechanics: Oral Paper Skill (Adkid-Zephyr/oral-paper-skill, 357 stars), Prd V10 Case Study Builder (mattgierhart/PRD-driven-context-engineering, 180 stars), Operating System Visualization (mingchen666/Reviva, 244 stars) and CCPM Project Management (automazeio/ccpm, 8.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
swan-gtm (a GitHub organization) maintains it in swan-gtm/gtm-skills, which has 172 GitHub stars. The repository holds 32 skills in this directory. The repository was last updated on October 8, 2026.
Source: swan-gtm/gtm-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.