Launch Planning Frameworks
slgoodrich/agents
Launch planning frameworks including tiered launches, timelines, checklists, and go/no-go decisions.
A skill your agent uses when the user asks to "audit our launch plan", "are we ready to launch", or evaluate launch execution/outcomes; runs one typed RAMP preflight, execution, or outcome profile…
Install Launch Readiness Auditor
$ npx skills add aaron-he-zhu/aaron-marketing-skills --skill launch-readiness-auditor -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install aaron-he-zhu/aaron-marketing-skills launch-readiness-auditor --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/aaron-he-zhu/aaron-marketing-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/launch/mobilize/launch-readiness-auditor .claude/skills/launch-readiness-auditor && 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-readiness-auditor" agent skill from https://github.com/aaron-he-zhu/aaron-marketing-skills/tree/main/launch/mobilize/launch-readiness-auditor into .claude/skills/launch-readiness-auditor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "launch-readiness-auditor", 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/aaron-he-zhu/aaron-marketing-skills/tree/main/launch/mobilize/launch-readiness-auditorType 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 aaron-he-zhu/aaron-marketing-skills --skill launch-readiness-auditor -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install aaron-he-zhu/aaron-marketing-skills launch-readiness-auditor --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aaron-he-zhu/aaron-marketing-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/launch/mobilize/launch-readiness-auditor .agents/skills/launch-readiness-auditor && 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-readiness-auditor" agent skill from https://github.com/aaron-he-zhu/aaron-marketing-skills/tree/main/launch/mobilize/launch-readiness-auditor into .agents/skills/launch-readiness-auditor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "launch-readiness-auditor", 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 aaron-he-zhu/aaron-marketing-skills --skill launch-readiness-auditor -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install aaron-he-zhu/aaron-marketing-skills launch-readiness-auditor --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aaron-he-zhu/aaron-marketing-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/launch/mobilize/launch-readiness-auditor .cursor/skills/launch-readiness-auditor && 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-readiness-auditor" agent skill from https://github.com/aaron-he-zhu/aaron-marketing-skills/tree/main/launch/mobilize/launch-readiness-auditor into .cursor/skills/launch-readiness-auditor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "launch-readiness-auditor", 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/aaron-he-zhu/aaron-marketing-skills.git --path launch/mobilize/launch-readiness-auditor--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 aaron-he-zhu/aaron-marketing-skills --skill launch-readiness-auditor -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install aaron-he-zhu/aaron-marketing-skills launch-readiness-auditor --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aaron-he-zhu/aaron-marketing-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/launch/mobilize/launch-readiness-auditor .gemini/skills/launch-readiness-auditor && 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-readiness-auditor" agent skill from https://github.com/aaron-he-zhu/aaron-marketing-skills/tree/main/launch/mobilize/launch-readiness-auditor into .gemini/skills/launch-readiness-auditor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "launch-readiness-auditor", 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 aaron-he-zhu/aaron-marketing-skills launch-readiness-auditorInstalls 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 aaron-he-zhu/aaron-marketing-skills --skill launch-readiness-auditor -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/aaron-he-zhu/aaron-marketing-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/launch/mobilize/launch-readiness-auditor .github/skills/launch-readiness-auditor && 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-readiness-auditor" agent skill from https://github.com/aaron-he-zhu/aaron-marketing-skills/tree/main/launch/mobilize/launch-readiness-auditor into .github/skills/launch-readiness-auditor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "launch-readiness-auditor", 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 aaron-he-zhu/aaron-marketing-skills --skill launch-readiness-auditor -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install aaron-he-zhu/aaron-marketing-skills launch-readiness-auditor --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aaron-he-zhu/aaron-marketing-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/launch/mobilize/launch-readiness-auditor .opencode/skills/launch-readiness-auditor && 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-readiness-auditor" agent skill from https://github.com/aaron-he-zhu/aaron-marketing-skills/tree/main/launch/mobilize/launch-readiness-auditor into .opencode/skills/launch-readiness-auditor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "launch-readiness-auditor", 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-readiness-auditor- GitHub stars
- 2.9k
- Token cost
- ~2k tokens
- SKILL.md length
- 705 words
- Files
- 2 (incl. references)
- Skills in repo
- 119
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
A skill your agent uses when the user asks to "audit our launch plan", "are we ready to launch", or evaluate launch execution/outcomes; runs one typed RAMP preflight, execution, or outcome profile…
- The user asks to audit our launch plan
- SKILL.md covers When This Must Trigger, Quick Start, Skill Contract and Data Sources, plus 9 more sections
- Calls git and python3
- Are we ready to launch
What it does
Launch Readiness Auditor is an agent skill from aaron-he-zhu/aaron-marketing-skills. Use when the user asks to "audit our launch plan", "are we ready to launch", or evaluate launch execution/outcomes; runs one typed RAMP preflight, execution, or outcome profile without mixing time horizons. Not for recording launch state — use launch-registry; not for running launch day — use launch-day-conductor. 发布就绪审计/RAMP分阶段评估/发布前放行
Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/auditor-runtime.md`). Compatibility notes: Claude Code and compatible agent-skill hosts
It sits in Marketing & SEO, covering Product launch strategy and Feature launches and release readiness. The repository describes itself as: 120 marketing skills as an AI marketing staff — plugin, portable skills, or an 8-bot team across 7 disciplines (narrative, SEO/GEO, social, email, paid, influencer, launch) on… The licence is Apache-2.0.
When your agent uses it
- The user asks to audit our launch plan
- Are we ready to launch
- Evaluate launch execution/outcomes
- Runs one typed RAMP preflight
Example prompts
- “audit our launch plan”
- “are we ready to launch”
- “/launch-readiness-auditor”
Requirements
- Python 3
- Compatibility (from SKILL.md): Claude Code and compatible agent-skill hosts
- Pre-approved tools (allowed-tools): WebFetch
What it can do on your machine
Read from SKILL.md and the folder at commit d5529cb. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
WebFetch
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
gitpython3
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
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.
Compatibility
Claude Code and compatible agent-skill hosts
From compatibility in the SKILL.md frontmatter.
Context cost
Launch Readiness Auditor loads about 2k tokens when it runs, and up to ~6.1k if it reads all its reference files. Until then it costs about 91 tokens; SKILL.md has 705 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 aaron-he-zhu/aaron-marketing-skills at commit d5529cb, republished under its Apache-2.0 licence (© aaron-he-zhu). 705 words, ~2,033 tokens.
Download SKILL.mdSave it as
.claude/skills/launch-readiness-auditor/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- launch-readiness-auditor
- description
- Use when the user asks to "audit our launch plan", "are we ready to launch", or evaluate launch execution/outcomes; runs one typed RAMP preflight, execution, or outcome profile without mixing time horizons. Not for recording launch state — use launch-registry; not for running launch day — use launch-day-conductor. 发布就绪审计/RAMP分阶段评估/发布前放行
- allowed-tools
- WebFetch
- compatibility
- Claude Code and compatible agent-skill hosts
- slug
- aaron-launch-readiness-auditor
- displayName
- Launch Readiness Auditor · 发布就绪审计
- summary
- 发布就绪审计/RAMP分阶段评估/发布前放行
- version
- 20.1.0
- license
- Apache-2.0
- homepage
- https://github.com/aaron-he-zhu/aaron-marketing-skills
- when_to_use
- Use for launch-eve readiness, an observed launch-window execution audit, or a post-lag outcome review. Each run uses one lifecycle profile and never averages…
- argument-hint
- <launch slug/plan/evidence> [preflight|execution|outcome]
- class
- auditor
- metadata.author
- aaron-he-zhu
Launch Readiness Auditor
Audit one launch at one lifecycle read. Preflight evaluates readiness/assets plus planned policy and instrumentation red lines; execution evaluates observed launch-window operation; outcome evaluates post-lag proof. There is no cross-time composite.
When This Must Trigger
- Before a committed launch/announcement when go/no-go evidence is needed.
- During/after the launch window when execution quality must be assessed.
- After the declared lag when actual outcomes and learnings are reviewed.
Quick Start
Run RAMP preflight for launch alpha against the registry stage, canon, claims, rules, and event QA.
Run the outcome profile at day 30; keep it separate from the preflight result.Skill Contract
Reads: one launch, one lifecycle read, registry/canon/claims state, and profile-specific evidence. Writes: only a permissioned v3 artifact. Done when: the selected profile is complete or its exact Unknowns are reported, with no launch execution or registry mutation.
launch-registry owns stage/date/embargo facts. launch-day-conductor executes the runbook. This auditor only judges the frozen evidence.
Data Sources
| Need | Preferred evidence |
|---|---|
| Stage/access | Projected launch record plus direct access/eligibility check |
| Narrative/claims | Canon version, claims projection, rendered assets |
| Operations/rules | Launch plan, commitments, dated official platform rules |
| Instrumentation | Verified events/UTMs and destination truth checks |
| Execution | Timestamped action/incident/response evidence |
| Outcomes | Own analytics/CRM/store truth after declared lag |
Instructions
Runtime Reads
../../../references/auditor-runbook.md../../../references/scoring-semantics.md../../../references/ramp-benchmark.md../../../references/runtime-invocation.mdreferences/auditor-runtime.md
Runtime and Setup
Read ../../../references/auditor-runbook.md, scoring-semantics.md, ramp-benchmark.md, and the RAMP catalog entry. Standalone installs use bundled immutable references/auditor-runtime.md; never fetch mutable main. Before deterministic calls, follow runtime-invocation.md, resolve AARON_SKILLS_ROOT="${CLAUDE_PLUGIN_ROOT:-$(git rev-parse --show-toplevel 2>/dev/null || true)}", and require the scorer, validator, and typed catalogs. If unavailable, return score_state: NOT_SCORED / score_confidence: not_scored with no gate verdict or persistent artifact.
Declare profile/lifecycle read (preflight|execution|outcome), target launch, launch type, market, access model, observation date, and evidence window.
Profile Procedure
- Preflight: score R1–R10, A1–A10, planned M1, and P1. A public pricing page is required only when the declared access model promises public paid availability.
- Execution: score observed M1–M10; do not substitute planned runbook quality for actual execution.
- Outcome: score P2–P10 after the declared lag; do not backfill forecast targets as actuals.
Every observed state needs source/date/type/confidence. Missing applicable evidence is Unknown; catalog-authorized conditional items may be N/A with reason. Run python3 "$AARON_SKILLS_ROOT/scripts/rubric-score.py" score <run.json> on the selected typed profile.
Verify profile-relevant vetoes: RAMP-R1 stage/access contradiction, RAMP-A1 material claim/disclosure failure, RAMP-M1 planned or observed manipulation/embargo/platform violation, and RAMP-P1 demonstrably broken instrumentation on participating surfaces.
§2 RAMP Worked Examples
- Complete preflight, raw 80, no veto/fail:
DONE/SHIP, final 80. - Complete preflight, raw 76, one verified A1 failure:
DONE_WITH_CONCERNS/FIX, final 59. - Complete preflight, verified R1 and M1 failures:
DONE/BLOCK, no final score. - Outcome read before conversion lag or without own-data actuals:
NEEDS_INPUT/UNDECIDED, no score.
Show full SKILL.md (304 more words)Show less
§3 RAMP Guardrails
- Stage truth follows promised access/eligibility; a pricing page is not universal evidence of GA.
- A genuine feedback request is not vote solicitation.
- Privacy-limited modeled measurement may be Partial; broken required instrumentation is P1 Fail.
- Launch stacking/capacity is an M10 finding, not an automatic veto.
- Never average preflight, execution, and outcome profiles or compare their scores as the same construct.
§5 RAMP Translation
State lifecycle read with every result. On trace request, qualify RAMP-R1/A1/M1/P1, especially against colliding ROAS IDs.
Report and Verdict
Begin with the auditor-runbook's exact typed conversation header. Never replace status, verdict, or score_state with prose; list each explicitly missing qualified item as ``ID: unknown``` before findings. Use the stable catalog ID verbatim (for example, RAMP-R1); never substitute an evidence-subcheck label or synthesize a suffixed ID such as RAMP-R1d`.
Lead with lifecycle-specific verdict, target/context/date, score or coverage/interval, confidence, profile detail, linked prior reads, critical evidence, Unknowns, and fix/rerun owner. A preflight SHIP authorizes no external launch action by itself; explicit execution approval remains required.
Validation Checkpoints
- One launch and one lifecycle profile are declared.
- Plan, execution, and outcome evidence were not mixed.
- Expected items only are scored; Unknown/N/A semantics are correct.
- Stage/access, policy, claims, and instrumentation vetoes are positively verified.
- No launch, submission, registry, or campaign side effect occurred.
Persistence
Persist only after explicit authorization to memory/audits/launch/YYYY-MM-DD-<topic>.md. Preserve the scorer's orthogonal status and verdict; validate the complete v3 draft with validate-audit-artifact.py against the intended relative path, persist only through one full-content Write, and revalidate the target per the auditor runbook. Edit/shell/MCP mutations of the reserved sink are unsupported. Create separate files for separate lifecycle reads and link them by launch ID rather than overwriting.
Reference Materials
Next Best Skill
- Stage/commitment facts: launch-registry
- Asset/technical fixes: launch-asset-packager
- Execute approved plan: launch-day-conductor
- Outcome monitoring: launch-monitor
© aaron-he-zhu, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (references) in launch/mobilize/launch-readiness-auditor of aaron-he-zhu/aaron-marketing-skills.
- SKILL.md
- references/auditor-runtime.md
Open the folder on GitHubat commit d5529cb
Compare with similar skills
Launch Readiness Auditor 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 Readiness Auditor this skillaaron-he-zhu/aaron-marketing-skills | 2.9k | — | ~2k | Automated safety check: Pass | Apache-2.0 | |
| Launch Planning Frameworksslgoodrich/agents | 139 | — | ~3.2k | Automated safety check: Pass | Custom licence | |
| Deliver Launch Checklistproduct-on-purpose/pm-skills | 716 | — | ~970 | Automated safety check: Pass | Apache-2.0 | |
| Mvp Launchooiyeefei/ccc | 495 | — | ~1.1k | Automated safety check: Pass | MIT | |
| 60 Launch Playbook Globalminhnv0807/ai-business-skills | 609 | — | ~3k | Automated safety check: Pass | MIT | |
| Feature Launch Playbookrampstackco/claude-skills | 945 | — | ~6.6k | Automated safety check: Pass | MIT |
Similar skills
Deliver Launch Checklist
product-on-purpose/pm-skills
Creates a cross-functional pre-launch checklist covering engineering, design, marketing, support, legal, and operations readiness, with owners, dates, and go/no-go criteria so nothing is missed…
Mvp Launch
ooiyeefei/ccc
Web app MVP launch checklist knowledge. An agent skill from ooiyeefei/ccc.
60 Launch Playbook Global
minhnv0807/ai-business-skills
A skill your agent uses when a launch needs a repeatable EXECUTION playbook — a T-30 to D+7 timeline, per-function checklists for content, design, ads, sales, and engineering, a launch-day war room…
Feature Launch Playbook
rampstackco/claude-skills
The operational playbook for launching a feature well. An agent skill from rampstackco/claude-skills.
Sealeap Amazon New Product Launch Plan
xjli360/sealeap-amazon-skills
Create a quantified Amazon new-product launch plan by translating a sales target into comparable-product benchmarks, keyword economics, budget scenarios, milestones, and stop-loss rules.
More from aaron-he-zhu/aaron-marketing-skills
All 119 skills in this repoAd Account Auditor
aaron-he-zhu/aaron-marketing-skills
A skill your agent uses when auditing a paid ad account for incremental contribution, wasted spend, or measurement integrity before scaling; runs a typed 20-item ROAS profile with verified vetoes…
Ad Creative Builder
aaron-he-zhu/aaron-marketing-skills
A skill your agent uses when the user asks to "write ad copy", "generate RSA headlines", or "build ad creative at volume"; produces ad units — RSA headlines/descriptions, hooks, and an angle matrix…
Ad Test Designer
aaron-he-zhu/aaron-marketing-skills
A skill your agent uses when the user asks to "design an A/B test", "set up a creative/landing test", "run an incrementality test", or "is this result statistically and practically material?"…
Bid Strategy Planner
aaron-he-zhu/aaron-marketing-skills
A skill your agent uses when the user asks to "pick a bid strategy", "set a tCPA/tROAS target", or "plan the learning-phase entry"; produces a bid-strategy choice (tCPA / tROAS / max-conversions /…
Conversion Signal QA
aaron-he-zhu/aaron-marketing-skills
A skill your agent uses when the user asks to "QA my conversion tracking before launch", "check my UTMs / pixel / event firing", "set up a tracking pre-flight", or "set the dedup rule so Meta and…
Creator Registry
aaron-he-zhu/aaron-marketing-skills
A skill your agent uses when the user asks "what did we pay this creator last time" or to "update the creator roster"; curates creator identity, rate, rights, exclusivity, compliance-event, and…
Related
Categories
Questions about Launch Readiness Auditor
What does Launch Readiness Auditor do?
A skill your agent uses when the user asks to "audit our launch plan", "are we ready to launch", or evaluate launch execution/outcomes; runs one typed RAMP preflight, execution, or outcome profile…. Launch Readiness Auditor is an agent skill from aaron-he-zhu/aaron-marketing-skills. Use when the user asks to "audit our launch plan", "are we ready to launch", or evaluate launch execution/outcomes; runs one typed RAMP preflight, execution, or outcome profile without mixing time horizons.
When should I use Launch Readiness Auditor?
Launch Readiness Auditor fits situations like: the user asks to audit our launch plan; are we ready to launch; evaluate launch execution/outcomes; runs one typed RAMP preflight.
How do I install Launch Readiness Auditor in Claude Code?
Run `npx skills add aaron-he-zhu/aaron-marketing-skills --skill launch-readiness-auditor -a claude-code`. Or copy the skill folder (launch/mobilize/launch-readiness-auditor in aaron-he-zhu/aaron-marketing-skills) into .claude/skills/launch-readiness-auditor in your project. Claude Code loads it when a task matches its description.
How do I install Launch Readiness Auditor in Codex?
Run `npx skills add aaron-he-zhu/aaron-marketing-skills --skill launch-readiness-auditor -a codex`. Or copy the skill folder (launch/mobilize/launch-readiness-auditor in aaron-he-zhu/aaron-marketing-skills) into .agents/skills/launch-readiness-auditor in your project. Codex loads it when a task matches its description.
Can I use Launch Readiness Auditor 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 aaron-he-zhu/aaron-marketing-skills --skill launch-readiness-auditor -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-readiness-auditor, .gemini/skills/launch-readiness-auditor, .github/skills/launch-readiness-auditor and .opencode/skills/launch-readiness-auditor in your project.
What does Launch Readiness Auditor need to run?
Going by SKILL.md and its folder, Launch Readiness Auditor needs the command-line tools its instructions call (git and python3). Our summary lists: Python 3. Its frontmatter pre-approves these tools: WebFetch. Compatibility (from SKILL.md): Claude Code and compatible agent-skill hosts.
Does Launch Readiness Auditor access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Launch Readiness Auditor 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 Readiness Auditor use?
Launch Readiness Auditor is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Launch Readiness Auditor use?
About 2k tokens (SKILL.md is roughly 8.1k 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 4k tokens, read only when the agent opens those files.
What are the alternatives to Launch Readiness Auditor?
Skills that share tags, products or a category with Launch Readiness Auditor: Launch Planning Frameworks (slgoodrich/agents, 139 stars), Deliver Launch Checklist (product-on-purpose/pm-skills, 716 stars), Mvp Launch (ooiyeefei/ccc, 495 stars) and 60 Launch Playbook Global (minhnv0807/ai-business-skills, 609 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Launch Readiness Auditor?
aaron-he-zhu (a GitHub user) maintains it in aaron-he-zhu/aaron-marketing-skills, which has 2,898 GitHub stars. The repository holds 119 skills in this directory. The repository was last updated on October 11, 2026.
Source: aaron-he-zhu/aaron-marketing-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.