Six skill recipes that chain free skills into real founder work

1Set up once

Most of these skills install in Claude Code, which needs a paid plan: Pro is $20 a month, or $17 a month billed yearly (pricing). Claude Code isn't on Free. A few also ship a ZIP you can upload on claude.ai, and we flag those. If you haven't set up yet, start with Set up Claude.

Each repo's README gives one of these install routes:

Work in one project folder. Keep your profile.md facts file there, and save each step's output as a file. Then paste this between steps:

Run [skill name] on [input file or what I describe]. Read profile.md first.
Save the result as [folder/file.md]. Use only facts from my files or
sources you cite, and mark anything you couldn't verify as "unverified".
Then stop and give me a 5-line summary before the next step.

2Recipe: Validate an idea in an afternoon

You finish with a go, pivot or stop note and three cheap experiments. More options in the library under Validate an idea.

1. Challenge the premise. gstack /office-hours asks six forcing questions, one at a time, and pushes back on your framing. It needs Claude Code plus Git and Bun.
2. Score it. Founder skills: /founder:validate-idea scores your idea on seven dimensions. Then /founder:user-interviews writes a Mom Test interview script.
3. Map the competition. Startup skill startup-competitors builds battle cards from reviews and forums. Its releases include a ZIP for claude.ai. Its README warns it uses a lot of tokens and suggests a Max plan.
4. Find real pain (optional, paid). Social research mines comments and competitor ads. It needs a paid ScrapeCreators API key.

Then do the interviews before you build anything. The validate your idea guide shows how.

3Recipe: Competitor teardown to landing page copy

You finish with a positioning statement and a first draft of your landing page. Library goals: Validate and Marketing.

1. Tear down competitors. Use startup-competitors from Step 2, or the competitors skill in Marketing skills. Save research/competitors.md.
2. Pick your position. Positioning /positioning runs a 15-minute forced-choice session and ends with a statement under 30 words and a 90-day proof plan.
3. Write the page. Marketing skills copywriting drafts it, then cro reviews it for conversion. Its releases include ZIPs for claude.ai.
4. Make it sound human. Humanizer removes the tells of AI writing. It edits for readers, not to beat AI detectors.

Read research/competitors.md and positioning.md. Using the copywriting skill,
draft my landing page: headline, subhead, 3 benefit sections, proof, FAQ, CTA.
Every claim must trace to profile.md. Where I have no proof yet, write
[Add proof] instead of inventing it.

4Recipe: Deck and model review before an investor sees them

You finish with scored reviews, a fix list and practice answers for the hardest questions. Library goal: Raise money.

1. Review the deck and model. lool ventures founder skills, built by a VC firm: Deck Review scores 35 criteria, Financial Model Review scores 46. Install it as a plugin in Claude Code or Cowork. Its README says the npx route won't run these skills.
2. Drill the hard questions. VCupid /vcdevil gives you 10 lethal questions to defend, and /vcangel the 10 strongest signals to lead with. It reads a STARTUP_PROFILE.md you fill in first.
3. Sit the committee. lool's IC Simulation runs a mock investment committee with three partner types who disagree.
4. Fix and re-run. Change the deck, run the reviews again, and compare.

5Recipe: Outbound list to first emails

You finish with 20 researched accounts, verified contacts and drafted emails you send yourself. Library goal: Get customers.

1. Research accounts. Anthropic's sales plugin: account-research covers each company's news, priorities and fit with your ideal customer. In Claude Code: claude plugin marketplace add anthropics/knowledge-work-plugins, then claude plugin install sales@knowledge-work-plugins.
2. Find contacts. Apollo finds and verifies contacts. It runs on Apollo's free credits, then paid. Enrichment uses credits, and the plugin asks before it spends them.
3. Write the emails. Founder skills (GTM) outreach-specialist writes sequences for email and DMs. Or the sales plugin's draft-outreach saves drafts for you to review.
4. Edit and send by hand. Run each email through Humanizer, then send a few a day yourself.

If you're technical, YALC is an open-source Clay alternative for lists and enrichment. It needs Node.js 20, and you pay any data providers you connect.

6Recipe: Ship an MVP without breaking it

You finish with a plan on file, tests, and a security pass before real users arrive. Library goal: Build the product.

1. Work like a careful engineer. Superpowers: brainstorm, write the plan, test first, review before you merge. Install: /plugin install superpowers@claude-plugins-official.
2. Keep the plan in files. Planning with files saves plans as markdown, so long tasks survive a /clear or a new session.
3. Make it look designed. frontend-design from Anthropic's skills: /plugin marketplace add anthropics/skills, then /plugin install example-skills@anthropic-agent-skills.
4. Check security. Trail of Bits skills review your code before you store real user data.

The ship with Claude Code guide covers the rest.

7Recipe: Your Monday ops hour

You finish with a cash forecast, a runway check and a draft investor update. Library goal: Run the company.

1. See the cash. Anthropic's small-business plugin, from the same knowledge-work repo: cash-flow-snapshot gives a 30/60/90-day forecast from QuickBooks, Xero, Stripe or a CSV you upload. monday-brief builds a one-page Monday doc, but needs your tools connected (see connectors).
2. Check runway. Charlie CFO works through runway, burn and what to cut first. Install: npx skills add EveryInc/charlie-cfo-skill.
3. Monthly: update investors. Investor updates tracks what you promised last month and states missing data as missing.
4. Friday: wrap the week. The sales plugin's weekly-wrap sums up what closed, moved and slipped.

To run parts of this on a schedule, see automate your week.

8Make a recipe your own

After you've run a recipe three times, you know which steps you keep and which you skip. Write that down as your own skill: one SKILL.md that names each step, the skill it uses and the file it saves. The build a skill guide shows how.

To see how a set of skills shares one facts file, look at the free starter skills (raise-profile and one-liner) in the Free Stack. The paid Raise Skill Pack ($27) is a worked example of a full pack.

What's next

Build your own with Build a skill. Find more skills by goal in the Skill Library, or get everything free in one place in the Free Stack.