Founder Launch
Turn your work into a dated launch: a cheap real test first, then the countdown, the run sheet and the first 30 days.
- What
- Turn your work into a dated launch: a cheap real test first, then the countdown, the run sheet and the first 30 days.
- Cost
- Free
- Needs
- Before you start: read this whole install prompt, tell me in a few lines what this skill does and what installing it involves, and wait for my go-ahead before you do anything else.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Your launch lead. The skill starts with the cheapest real-world test that fits the business, run before the big costs are signed: a pop-up, market stall or pre-order list for a physical shop, a landing page with a real price and a pre-order or waitlist button for an online product, three paid pilot clients for a service, or a paid founding-member offer for a subscription. The success line is written before the test runs, and the result is compared with the simulated panel: if real buyers fall well short, the skill says to trust the real buyers. It then builds the countdown from today to launch day with real dates, weekly blocks, an owner and a deadline per task and the critical path marked, an hour-by-hour launch-day run sheet, and the first 30 days: the weekly numbers to track, the level that triggers a change, and reviews on days 7, 14 and 30. Output: founder/launch.md, reading founder/numbers.json, founder/ops.md, founder/brand.md and founder/marketing.md when they exist.
Version:
Install
Copy the install package below, then paste it into Muse📌 Pinned version: commit fd9385bThe install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Before you start: read this whole install prompt, tell me in a few lines what this skill does and what installing it involves, and wait for my go-ahead before you do anything else. Prerequisites: None. No API key, no account, no paid service, no Python. Install "Founder Launch" for me. It is a launch lead: it picks the cheapest real-world test for the business and runs it before the big spend, then builds a dated countdown with owners and deadlines, a launch-day run sheet and a first-30-days review plan into founder/launch.md. Repository: https://github.com/Jakeschincariol/founder-skill (the skill is the whole skills/founder-launch/ folder at the pinned commit: SKILL.md) Pinned version: install the code at commit fd9385b0cfe1b96bebce3898fbd506d73eff5a9d exactly. Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Clone https://github.com/Jakeschincariol/founder-skill into a temporary folder, check out commit fd9385b0cfe1b96bebce3898fbd506d73eff5a9d, and copy the skills/founder-launch/ folder from that checkout. Then compare every file in the folder with the fingerprints recorded for this listing on 2026-10-18: [FINGERPRINTS] - SKILL.md: SHA-256 fa44e8ff5eb16a74f22cc58febb19ab0e5c962beab7bb138024eaa48a262b2b6 If a file does not match, it changed since the listing was prepared: do not install it yet, tell me what you found and let me decide. 2. Read SKILL.md in full (and every other file in the folder) and tell me in plain words: what the skill does when used, which services it connects to, whether it reads or sends any personal information or keys, and anything that seems unusual. Stop on any red flag and tell me before going further. Confirm these points from the files: - The skill folder holds one file only: SKILL.md. There is no code, no script and no bundled tool. - The skill instructs no web browsing, no external API call and no upload. It reads local files the other founder skills wrote (numbers, operations, brand, marketing) and writes one local file, founder/launch.md. The real-world test it plans (for example a landing page or a pop-up) is something you run yourself in the real world; the skill does not create accounts, publish pages or contact anyone. - Nothing is sent anywhere during installation itself; the only download is the skill file from GitHub at the pinned commit. 3. When I say "yes, install", install it as a skill: copy the whole folder into the agent's skills directory, in a folder named "founder-launch", keeping every file (SKILL.md). 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (for example: sign in or create an account (none is needed), provide any API key (none is needed); using the skill is a separate step that only starts when I ask for it). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.