7 agent skill packs for the founder and PM side of a startup (idea review, user research, specs, decks), each one run on a real task
The most expensive mistake in a startup isn't a bug. It's building the wrong thing. These skill packs make your agent do the work around the code: question the idea, hear what users say, write the spec, and present it.
We ranked the most popular product packs by GitHub stars (October 2026). Then we ran six of the seven on one made-up startup: ReplyPilot , an AI tool that drafts customer support replies for Shopify stores.
gstack is Garry Tan's own setup. Garry is the CEO of Y Combinator, and he turned his way of building products into commands. For the product side, two matter most:
/office-hours: a YC partner session. Six hard questions about demand, the current alternative, the exact user and the narrowest first version.
/plan-ceo-review: a CEO pass on a feature plan. Is this too small, too big, or the wrong thing?
It also has engineering and design plan reviews, browser QA, a security audit and /ship.
We ran /office-hours on ReplyPilot, which has a landing page and 40 waitlist signups. It didn't brainstorm features. It said 40 signups is interest, not demand , and asked for the one merchant who'd be upset if the product disappeared.
We answered: 11 people replied, 3 took calls, one store forwarded 200 real tickets, and nobody has paid. Round two picked out the 200 tickets as the only real behavior and narrowed the pitch to replies that get this store's policy right on the specific order. It also suggested the merchant's complaint about their current tool might be a settings problem, not a market.
Then /plan-ceo-review on a one-page plan for "auto-send high-confidence replies". Its verdict: build it, but don't trust the AI's own confidence score. Use the drafts that support agents already send without edits. It added three rules we hadn't thought of:
never auto-send a reply that promises an action
hold every auto-reply for a 10-minute undo window
switch off a store's autopilot after two "this was wrong" flags in 100 sends
Garry demos the same flow on YC's channel:
Use it before you build anything. Two rounds of office hours told us more than a page of feature ideas. The CEO review is long: about 18 minutes, and our 17-line plan grew to 906 lines. Run it on decisions that matter.
2. last30days
last30days reads what people said about a topic in the last 30 days on Reddit, Hacker News, X, YouTube, GitHub and the web. It ranks posts by real engagement and writes a brief with quotes and links. It's market research you'd otherwise spend an afternoon on.
0:00 / 0:00
We asked what founders and support teams complain about in AI support tools. In about 5 minutes it read 16 Reddit threads, 13 Hacker News stories and more. Two findings shaped the ReplyPilot plan:
The billing unit is the complaint, not the price. A "resolved" ticket can mean a customer who gave up.
Bots that answer are fine. Bots that act aren't. Refunds, cancellations and order changes cause the angry escalations, which is exactly where auto-send should stop.
It was honest about thin coverage, too: only about 5 on-topic Reddit threads, and pricing figures mostly from competitors' blogs.
Use it before a new feature, a pivot or a pricing change. For a niche market, ask for 90 days instead of 30.
3. Google Workspace CLI
The Google Workspace CLI lets your agent work where your team already does: Gmail, Drive, Docs, Sheets, Calendar and Forms. The pack includes ready recipes:
turn a sheet into a report doc
create a feedback form and email it
prepare me for my next meeting
0:00 / 0:00
We gave it five customer interview notes and asked for a summary sheet, a report doc and an email to a cofounder. We used a dry run with no Google account connected, and it planned every step in 74 seconds. It also caught two places where its own instructions didn't match the current version of the tool.
Use it if your team lives in Google Docs. It acts as you, so try a dry run first. Google's README notes it isn't an officially supported product.
4. guizang-ppt-skill
guizang-ppt-skill turns notes into a slide deck that opens in the browser. It comes in two strict visual styles: an editorial magazine look, and a Swiss style with big type and a hard grid. Decks have a presenter view with notes and a timer.
We asked for a 5-slide investor update for ReplyPilot, with our numbers in the prompt. In about 3 minutes it built the deck, screenshotted every slide and fixed the overlaps itself. It used only our figures, and flagged the one number it worked out on its own.
Use it for investor updates, all-hands and talks. When someone needs to edit the file, use Anthropic's PowerPoint skill instead. The license is AGPL, so read it before building it into a product.
5. PM Skills
PM Skills, by Pawel Huryn, packs 69 skills built on frameworks PMs already trust: opportunity trees, product risks, jobs to be done, Lean Canvas, pre-mortems. The commands a founder will use:
Command
What you get
/discover
Ideas, riskiest assumptions, and experiments to test them
/write-prd
A full spec
/pre-mortem
What could kill the feature
/strategy
A one-page product strategy
/plan-launch
A go-to-market plan
We asked /write-prd for usage-based billing on a made-up webhook SaaS. In 75 seconds it wrote a 1,300-word PRD with:
goals you can measure
assumptions and open questions
a release plan
the math on where each plan becomes cheaper than the one below it
Use it when you write specs every week. The output is only as good as the context you give it: with just a README, the prices were placeholders, and it said so.
6. visual-explainer
Nobody reads a 1,300-word PRD. visual-explainer turns a plan, a spec or a code change into a clear web page with diagrams, tables and live examples.
0:00 / 0:00
We gave it the PRD from PM Skills. The page opens on a live price meter: pick a plan, drag usage up, and watch the invoice change.
The best part was what it caught. Drawing the price curve, it found two problems the PRD missed:
The PRD contradicts itself. The default spending limit stops events at 2.96M, so the PRD's own "3M events for about $99" example can't happen.
Overage costs more than the plan. On the Growth plan, extra usage costs slightly more than usage inside the plan, which sales should know.
We checked both. Neither was in the PRD.
Use it on any spec your team has to agree on. It took 13 minutes, because it tests its own page on desktop and phone.
7. user-research-skill
Cookiy's skill plans user research and makes sense of it afterwards: a research plan, a screener and an interview guide before, and themes, personas and a report after. Both are free. A third, paid option runs AI-moderated interviews on Cookiy's platform.
We asked why support agents rewrite AI drafts instead of sending them. In under 2.5 minutes it wrote a plan, a 4-question screener and a 30-minute interview guide. Two touches made it better than a template:
Real evidence first: pull each participant's own draft and sent reply before the call.
No leading questions: keep the word "auto-send" out of the conversation until the end, so agents don't hear it as a threat to their jobs.
Use it before you talk to users, so the calls answer a real question. It will keep suggesting Cookiy's paid studies, but you don't need them. Skip the synthetic participants: a model interviewing a model isn't evidence.
Which to install first
Before you build: gstack /office-hours. For something lighter, Matt Pocock's grill-me from top development skills .
Before a feature or a pivot: last30days, to hear the market.
Writing specs: PM Skills, then visual-explainer on any spec people need to agree on.
Updates and decks: guizang-ppt-skill.
Talking to users: the Cookiy planning flow.
Ship faster than your competition
Focus on customers and sales while we handle product delivery. Hire a dedicated AI maker
or a whole product team.