GTM Co-Founder skill
Twenty go-to-market skills for technical founders: positioning, first users, launch and pricing
- 329 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Market research goes online and reads your project's README, commits and issues
- The skills write brief and roadmap files into the project's docs/gtm-cofounder folder
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/gtm-co-founderDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Market research goes online and reads your project's README, commits and issues
- The skills write brief and roadmap files into the project's docs/gtm-cofounder folder
This is third-party code. Review the repository files before installing.
What it does
GTM Co-Founder helps a founder of a developer tool or an AI product who has neither a commercial co-founder nor a team. A set of twenty skills works inside the agent and walks through the strategy half of go-to-market: who the product is for, why they would pay and how to land first users. Marketing tactics and SEO are not part of it. Work runs as a chain. The 00-start-here skill asks five questions one at a time and writes docs/gtm-cofounder/founder-brief.md, which every other skill reads. Inside a project it first reads the README, recent commits and open issues to fill the brief with what you have already shipped. Then research-the-market searches the web for communities, newsletters and GitHub threads where your problem is discussed and saves findings with links to market-research.md. The 01-strategy-and-roadmap skill names the problem worth working on now and one next move. Separate skills follow for the steps of the path, from positioning and the homepage to pricing, founder-led sales and growth loops. The brief separates what is validated from what is assumed, and the talk-to-users skill turns assumptions into validated facts.
Who it is for. For technical founders, first go-to-market hires and founding sales leads of developer and AI products who have no team or budget.
Good fit when
- A project has 800 GitHub stars but almost nobody pays, and you need a diagnosis of what is unknown about activation, return and willingness to pay
- The product is ready and nobody came to the launch: launch-it and first-50-users build an order of moves for the first users
- You need to rewrite the homepage and the value proposition: the-homepage and value-prop-that-converts handle that
- You are choosing price and plans for a developer tool: pricing comes in
- The founder runs sales personally: founder-led-sales and founder-led-content give frames for conversations and posts
Not a fit when
- You need tactics such as ad campaigns, SEO and newsletters: the set covers strategy and has no tactics
- You need a ready market study without questions to you: the skill first takes five answers from you
- Your agent cannot search the web: market research relies on web search and gets thinner without it
Example request
Install the skills from the AIDevGTM/gtm-cofounder repository and run 00-start-here with me. My product is a CLI for checking database schemas.Limitations
- The skills give frames and questions and no finished decisions: the quality of the diagnosis depends on honest answers in the brief.
- Market research uses web search, so without network access for the agent it is limited.
- The frames are built for developer tool and AI product markets. For other products part of the advice will not fit.
- Skill texts and templates are written in English, and intermediate results are saved to the project docs/gtm-cofounder folder: founder-brief.md, market-research.md and the roadmap.
How to disable. Delete the skill folders from ~/.claude/skills or your agent's skills directory. The Claude Code plugin is removed with `/plugin uninstall gtm-cofounder@gtm-cofounder`. The brief files in docs/gtm-cofounder/ stay in the project, so delete them separately.
FAQ
How do I install GTM Co-Founder in Claude Code?
Through the plugin: `/plugin marketplace add AIDevGTM/gtm-cofounder`, then `/plugin install gtm-cofounder@gtm-cofounder`. Other routes: `npx skills add AIDevGTM/gtm-cofounder` or copying the folders from skills/ into ~/.claude/skills. If your agent cannot fetch a repository by link, run `git clone` first.
Where do I start?
Tell the agent to install the skills from the repository and run 00-start-here. It asks five questions and writes the brief, then you ask it to run research-the-market and 01-strategy-and-roadmap. The whole sequence takes about 15 minutes.
Can I use it without a coding agent?
Yes. Open the skill you need, copy the text into ChatGPT or Claude and add a line to apply it to your product with a description. For a no-terminal path, skill archives are in the repository releases, and in the Claude apps you upload them through Customize, Skills, Create skill.
How does the set differ from a chatbot's generic marketing advice?
It first learns your product and market and does not hand out ten tactics. For example, to the complaint "800 stars but nobody pays" it answers that you do not yet know whether users activate, return and would pay, and names the evidence to go and get.
Which agents are supported?
Any agent that supports the Agent Skills spec: Claude Code, Cursor, Codex, Windsurf and Antigravity. Every skill is self-contained: one folder, one SKILL.md, no dependencies.
Discussion
No questions or reviews yet.
Related
SkillsClaude Code skills for founders: pricing and launch plans, PRDs, landing page reviews, social posts and cold outreach
A library of 64 skills for founders: GTM, growth, SEO, email, graphics and video, installed with one npx command for Claude Code, Codex and more
A large growth and GTM skill library: ads, social, content, SEO, lead generation and competitor research
Skill with SaaS product-design principles: conversion, onboarding, retention, pricing and behavioral tactics
A set of skills for solopreneurs: SEO and GEO, demand research, domains, logo and banner generation, social scraping
Creative Director
Creative Director Skill
A creative director skill: insights, ideas via SIT and TRIZ, Cannes-calibrated scoring and checks against a library of landmark campaigns
Comparison with similar tools
Entries that share the main search query, and how they differ.
| Entry | Official | Repository stars | Main difference |
|---|---|---|---|
| GTM Co-Founder (this entry) | no | 329 | |
| GTM Engineer Skills | no | 1,340 | wins visibility in ChatGPT, Claude and Perplexity answers: AEO and GEO |
| Positioning | no | 109 | a 15-minute forced-choice session that produces a startup positioning statement |
| Founder Skills (Emotix) | no | 749 | idea validation, a competitor matrix, pricing and a pitch deck for founders |
README in short
The author shows the three-step path on a diagnosis example and lays out the skill catalog by stage from strategy to growth. Brief and roadmap templates sit in the repository.
README badge
Original SKILL.md
--- name: start-here description: Interview the user once and write a docs/gtm-cofounder/founder-brief.md that every other skill reads first, so the advice is about their real business, not a textbook. Use this before anything else, or whenever the agent lacks context on the user's product, ICP, market, or stage, or is giving generic GTM advice. --- # Start here (your founder brief) > Every other skill is only as sharp as what the agent knows about *your* business. This is that context. Do it once, and every skill after it gets personal. **Use this when:** it's your first time here, or the advice you're getting feels generic and textbook because the agent doesn't actually know your product, your users, or your stage. ## The core idea Answer **five core questions** and the agent writes a **`docs/gtm-cofounder/founder-brief.md`** in your project, enough to give you a real diagnosis and a roadmap in minutes. Everything else is optional and answered as you go: each skill pulls the deeper questions it actually needs, when it needs them, and tells you what answering unlocks. So you start seeing value fast, and the brief gets richer the more you use it, instead of facing a wall of questions on day one. And the part that matters most: separate what you have **validated** (a real user who is not your friend told you) from what you are **assuming** (your best guess for now). Assumptions are completely fine to start with. They just get sent to `talk-to-users` to become real, so you never build a beautiful go-to-market on a guess. ## How to run this (for the agent) - **Ask the five core questions one at a time, and nothing else.** One question, wait for the answer, let it shape the next. It should feel like a conversation with a co-founder, not a form to fill in. Never paste multiple questions at once. (If the founder would rather see all five and answer in one go, give them the list, but default to one at a time.)