Self Improver
Affitor/affiliate-skills
Review affiliate campaign results and improve strategy. An agent skill from Affitor/affiliate-skills.
Use after a social launch, campaign, creator collaboration, or distribution test has enough evidence to decide what should be repeated, changed, or stopped.
Install Launch Retrospective
$ npx skills add Ootto-AI/claude-content-skills --skill launch-retrospective -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Ootto-AI/claude-content-skills launch-retrospective --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/Ootto-AI/claude-content-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/launch-retrospective .claude/skills/launch-retrospective && 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-retrospective" agent skill from https://github.com/Ootto-AI/claude-content-skills/tree/main/skills/launch-retrospective into .claude/skills/launch-retrospective/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "launch-retrospective", 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/Ootto-AI/claude-content-skills/tree/main/skills/launch-retrospectiveType 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 Ootto-AI/claude-content-skills --skill launch-retrospective -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Ootto-AI/claude-content-skills launch-retrospective --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Ootto-AI/claude-content-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/launch-retrospective .agents/skills/launch-retrospective && 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-retrospective" agent skill from https://github.com/Ootto-AI/claude-content-skills/tree/main/skills/launch-retrospective into .agents/skills/launch-retrospective/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "launch-retrospective", 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 Ootto-AI/claude-content-skills --skill launch-retrospective -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Ootto-AI/claude-content-skills launch-retrospective --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Ootto-AI/claude-content-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/launch-retrospective .cursor/skills/launch-retrospective && 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-retrospective" agent skill from https://github.com/Ootto-AI/claude-content-skills/tree/main/skills/launch-retrospective into .cursor/skills/launch-retrospective/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "launch-retrospective", 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/Ootto-AI/claude-content-skills.git --path skills/launch-retrospective--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 Ootto-AI/claude-content-skills --skill launch-retrospective -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Ootto-AI/claude-content-skills launch-retrospective --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Ootto-AI/claude-content-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/launch-retrospective .gemini/skills/launch-retrospective && 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-retrospective" agent skill from https://github.com/Ootto-AI/claude-content-skills/tree/main/skills/launch-retrospective into .gemini/skills/launch-retrospective/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "launch-retrospective", 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 Ootto-AI/claude-content-skills launch-retrospectiveInstalls 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 Ootto-AI/claude-content-skills --skill launch-retrospective -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Ootto-AI/claude-content-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/launch-retrospective .github/skills/launch-retrospective && 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-retrospective" agent skill from https://github.com/Ootto-AI/claude-content-skills/tree/main/skills/launch-retrospective into .github/skills/launch-retrospective/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "launch-retrospective", 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 Ootto-AI/claude-content-skills --skill launch-retrospective -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Ootto-AI/claude-content-skills launch-retrospective --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Ootto-AI/claude-content-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/launch-retrospective .opencode/skills/launch-retrospective && 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-retrospective" agent skill from https://github.com/Ootto-AI/claude-content-skills/tree/main/skills/launch-retrospective into .opencode/skills/launch-retrospective/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "launch-retrospective", 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.
Facts
- Skill name
launch-retrospective- GitHub stars
- 130
- Token cost
- ~828 tokens
- SKILL.md length
- 382 words
- Files
- 1
- Skills in repo
- 52
- Repo updated
- First seen
- Licence
- MIT
At a glance
Use after a social launch, campaign, creator collaboration, or distribution test has enough evidence to decide what should be repeated, changed, or stopped.
- Works in 4 steps: Reconstruct the intended plan → Gather the evidence with limits attached → Distinguish facts from explanations → …
- Phrases include run a launch retro
- SKILL.md covers 1. Reconstruct the intended plan, 2. Gather the evidence with…, 3. Distinguish facts from… and 4. Commit to operational changes, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Launch Retrospective is an agent skill from Ootto-AI/claude-content-skills. Use after a social launch, campaign, creator collaboration, or distribution test has enough evidence to decide what should be repeated, changed, or stopped. Trigger phrases include "run a launch retro", "what did we learn from this campaign?", "postmortem this launch", "should we repeat this?", and "turn these results into next steps". Do not use this to assign blame, invent missing data, or write a live performance dashboard; use social-analytics-report for the in-flight metric read and campaign-brief to plan…
Its SKILL.md is about 830 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Product & Project Management, covering Retrospectives, Runbooks and postmortems and Data analysis. The repository describes itself as: Free, copy-paste Claude skills that run your content growth factory — turn ideas + your NotebookLM memory into scroll-stopping Instagram reels. By Ootto. The licence is MIT.
When your agent uses it
- Phrases include run a launch retro
- What did we learn from this campaign?
- Postmortem this launch
- Should we repeat this?
Example prompts
- “run a launch retro”
- “what did we learn from this campaign?”
- “postmortem this launch”
- “/launch-retrospective”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 5263be7. It shows what the files ask for, not the result of running them.
Tool permissions
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.
Runs code
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.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Launch Retrospective loads about 828 tokens when it runs. Until then it costs about 139 tokens; SKILL.md has 382 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.
Safety
Auto-check passed
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.
SKILL.md
The full file from Ootto-AI/claude-content-skills at commit 5263be7, republished under its MIT licence (© Ootto-AI). 382 words, ~828 tokens.
Download SKILL.mdSave it as
.claude/skills/launch-retrospective/SKILL.md (or your agent's skills folder).- name
- launch-retrospective
- description
- Use after a social launch, campaign, creator collaboration, or distribution test has enough evidence to decide what should be repeated, changed, or stopped. Trigger phrases include "run a launch retro", "what did we learn from this campaign?", "postmortem this launch", "should we repeat this?", and "turn these results into next steps". Do not use this to assign blame, invent missing data, or write a live performance dashboard; use social-analytics-report for the in-flight metric read and campaign-brief to plan the next campaign.
Launch Retrospective
Turn a completed campaign into durable operational learning: what happened, why it may have happened, and the next smallest decision.
1. Reconstruct the intended plan
Bring together the original objective, audience, approved message, channel roles, budget or partner scope where supplied, timing, measurement plan, and decisions made during execution. Compare what actually shipped with what was planned. Separate a deliberate change from an accidental deviation.
2. Gather the evidence with limits attached
Use available performance data, qualitative feedback, partner notes, approvals, and execution records. State dates, metric definitions, missing data, and material confounders. Keep a timeline so the team does not attribute an outcome to a change that happened after it.
3. Distinguish facts from explanations
List observations first: what was published, what audiences did, and what tracking shows. Then list hypotheses about message, format, distribution, timing, destination, or process. Give each hypothesis a confidence level and the evidence that would strengthen or weaken it.
4. Commit to operational changes
Return a short set of keep, change, test, and stop decisions with owners and due dates. Update reusable inputs such as the campaign brief template, proof library, UTM vocabulary, or creator brief. Leave a clear record of unresolved questions so they are not rewritten as facts next time.
Show full SKILL.md (172 more words)Show less
Hard rules
- Do not use a retrospective to blame individuals, creators, or customers for an outcome.
- Never claim causation where the evidence only shows correlation.
- Include negative and inconclusive results; they are part of the learning.
- Do not compare campaigns with different objectives or measurement conditions as if they were identical.
- Separate process failure from message failure before prescribing a fix.
Failure modes
| Failure | Do this instead |
|---|---|
| The retro is a victory lap or blame document | Use a factual timeline, uncertainty, and future-oriented decisions. |
| A single metric explains the whole launch | Combine the original job, data boundary, qualitative evidence, and process record. |
| Lessons stay as vague observations | Turn each learning into a named change, test, or stop decision. |
| The same tracking issue returns next launch | Update the UTM or measurement workflow with a clear owner. |
Where it sits
Use social-analytics-report for structured performance evidence during the launch. Use campaign-brief, paid-social-brief, influencer-partnerships, and utm-campaign-plan as source records. Feed confirmed lessons into the next campaign-brief rather than treating the retro as a standalone document.
© Ootto-AI, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/launch-retrospective of Ootto-AI/claude-content-skills.
Open the folder on GitHubat commit 5263be7
Compare with similar skills
Launch Retrospective 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 Retrospective this skillOotto-AI/claude-content-skills | 130 | — | ~828 | Automated safety check: Pass | MIT | |
| Self ImproverAffitor/affiliate-skills | 701 | — | ~2.6k | Automated safety check: Pass | MIT | |
| After Action Reportrampstackco/claude-skills | 945 | — | ~2.5k | Automated safety check: Pass | MIT | |
| Launch Retro Analyzeraaron-he-zhu/aaron-marketing-skills | 2.9k | — | ~3k | Automated safety check: Pass | Apache-2.0 | |
| Release Retrospectivemurphytrueman/design-system-ops | 206 | — | ~3.2k | Automated safety check: Pass | MIT | |
| 66 Crisis Playbook Globalminhnv0807/ai-business-skills | 609 | — | ~2.8k | Automated safety check: Pass | MIT |
Similar skills
After Action Report
rampstackco/claude-skills
Run a structured after-action review (postmortem, retrospective) on a launch, incident, or completed project to capture timeline, root cause analysis, contributing factors, and actionable lessons.
Launch Retro Analyzer
aaron-he-zhu/aaron-marketing-skills
A skill your agent uses when the user asks to "run a launch retro / post-mortem", "compare launch results vs targets by channel", or "decide what to keep or kill for the next launch"; produces a…
Release Retrospective
murphytrueman/design-system-ops
Review how a shipped release, migration or deprecation went against its plan: blast radius, comms, migration, timeline, support load, each gap classed.
66 Crisis Playbook Global
minhnv0807/ai-business-skills
A skill your agent uses when a brand faces a communications CRISIS or a campaign is failing in public — L1 to L5 severity classification, a first-four-hours process, response templates by type, an…
66 Crisis Playbook
minhnv0807/ai-business-skills
Dung khi thuong hieu DANG bi tan cong hoac campaign gay phan ung xau — phan loai 5 cap L1 den L5, quy trinh 4 gio dau, template phan hoi tung tinh huong, ai duoc phat ngon, danh sach TUYET DOI khong…
More from Ootto-AI/claude-content-skills
All 52 skills in this repoAgent Reach
Ootto-AI/claude-content-skills
MUST USE when user wants to 调研/research/搜索/search/查/找/look up anything on the internet — e.g.
Ab Hook Tester
Ootto-AI/claude-content-skills
Generates two genuinely distinct hook variants for the same reel so you can post-test which opening actually wins.
AI Brain
Ootto-AI/claude-content-skills
Give Claude a permanent, searchable long-term memory using an Obsidian vault as the store.
Caption And Hashtags
Ootto-AI/claude-content-skills
Write the caption, hashtag set, and first comment for a reel or post.
Collab Outreach
Ootto-AI/claude-content-skills
Drafts personalized pitches to creators and brands for collab reels, shoutouts and partnerships.
Comment Responder
Ootto-AI/claude-content-skills
Turn every comment into a lead on autopilot. An agent skill from Ootto-AI/claude-content-skills.
Related
Categories
Questions about Launch Retrospective
What does Launch Retrospective do?
Use after a social launch, campaign, creator collaboration, or distribution test has enough evidence to decide what should be repeated, changed, or stopped. Launch Retrospective is an agent skill from Ootto-AI/claude-content-skills. Use after a social launch, campaign, creator collaboration, or distribution test has enough evidence to decide what should be repeated, changed, or stopped.
When should I use Launch Retrospective?
Launch Retrospective fits situations like: phrases include run a launch retro; what did we learn from this campaign?; postmortem this launch; should we repeat this?.
How do I install Launch Retrospective in Claude Code?
Run `npx skills add Ootto-AI/claude-content-skills --skill launch-retrospective -a claude-code`. Or copy the skill folder (skills/launch-retrospective in Ootto-AI/claude-content-skills) into .claude/skills/launch-retrospective in your project. Claude Code loads it when a task matches its description.
How do I install Launch Retrospective in Codex?
Run `npx skills add Ootto-AI/claude-content-skills --skill launch-retrospective -a codex`. Or copy the skill folder (skills/launch-retrospective in Ootto-AI/claude-content-skills) into .agents/skills/launch-retrospective in your project. Codex loads it when a task matches its description.
Can I use Launch Retrospective in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Ootto-AI/claude-content-skills --skill launch-retrospective -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-retrospective, .gemini/skills/launch-retrospective, .github/skills/launch-retrospective and .opencode/skills/launch-retrospective in your project.
What does Launch Retrospective need to run?
SKILL.md names no scripts, command-line tools or credentials: Launch Retrospective is instructions for the agent only.
Does Launch Retrospective access the network?
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.
Is Launch Retrospective safe to install?
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.
What licence does Launch Retrospective use?
Launch Retrospective is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Launch Retrospective use?
About 828 tokens (SKILL.md is roughly 3.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Launch Retrospective?
Skills that share tags, products or a category with Launch Retrospective: Self Improver (Affitor/affiliate-skills, 701 stars), After Action Report (rampstackco/claude-skills, 945 stars), Launch Retro Analyzer (aaron-he-zhu/aaron-marketing-skills, 2.9k stars) and Release Retrospective (murphytrueman/design-system-ops, 206 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Launch Retrospective?
Ootto-AI (a GitHub organization) maintains it in Ootto-AI/claude-content-skills, which has 130 GitHub stars. The repository holds 52 skills in this directory. The repository was last updated on October 8, 2026.
Source: Ootto-AI/claude-content-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.