Przejdź do treści
Biblioteka skilli
Zarządzanie i produkt · Research

gap-finder

/gap-finder

Generuje pomysły na produkt lub biznes, sprawdza je wobec konkurencji i danych rynkowych oraz odrzuca słabe z uzasadnieniem.

Repozytorium
claude-skills ↗
Licencja
Apache-2.0
Ostatnia zmiana repozytorium
20.08.2026

Ocena i bezpieczeństwo

90/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść25 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
5
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 20.08.2026, bez odwołań do wycofanych modeli i API.

Licencja

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

Co robi i kiedy

Generuje pomysły na produkt lub biznes, sprawdza je wobec konkurencji i danych rynkowych oraz odrzuca słabe z uzasadnieniem.

Oryginalny opis (EN)

Finds viable product, business, or project ideas in any domain by generating candidates, rigorously validating each against real competitors and market data, and killing weak ideas with documented reasons. Two modes — fast batch generate-and-kill (default), or `--deep` DFS that branches a single space into opportunity tuples with codex cross-attack, mandatory steelman, and a VC-gauntlet fundability gate. Use when the user asks to brainstorm ideas, find market gaps, identify business opportunities, figure out what to build, come up with side project ideas, find underserved niches, or (with --de

Jak działa

  1. Modes
  2. Workflow
  3. Self-review checklist
  4. Golden rules
  5. Reference files
Sekcje z nagłówków SKILL.md, w oryginale · 57 linii, 1 001 słów
Podgląd SKILL.md
---
name: gap-finder
description: Finds viable product, business, or project ideas in any domain by generating candidates, rigorously validating each against real competitors and market data, and killing weak ideas with documented reasons. Two modes — fast batch generate-and-kill (default), or `--deep` DFS that branches a single space into opportunity tuples with codex cross-attack, mandatory steelman, and a VC-gauntlet fundability gate. Use when the user asks to brainstorm ideas, find market gaps, identify business opportunities, figure out what to build, come up with side project ideas, find underserved niches, or (with --deep) "find the real opportunities in X", "exhaustively explore X", "keep digging until you exhaust X". Works for SaaS, open source, MCP servers, apps, tools, APIs, or any product category.

category: execution
capabilities: [loop-based, adversarial-critique, static-analysis]
input_types: [idea, artifact-file, git-diff]
output_types: [code, data]
complexity: moderate
cost_profile: medium
maturity: beta
metadata_source: inferred
---

# Gap Finder

Finds viable ideas through adversarial generation-and-kill cycles. Generates batches of 5, validates every idea against real market data, kills failures with documented reasons, and loops until survivors emerge.

## Modes

- **Batch (default)** — broad generate-and-kill across a domain. Generates batches of 5, runs the 6-check kill chain on each, loops until 3 survivors emerge. Best for "give me side-project ideas", "what should I build", scanning many adjacent niches. This is the workflow below.
- **Deep (`--deep`)** — exhaustive depth-first exploration of ONE space. Branches the market into opportunity *tuples* (market × wedge × unfair-advantage × why-now × who-pays), reality-calibrates each against real companies, maps named incumbents + GTM, runs an independent **codex** cross-attack and a mandatory steelman per node, then puts the top survivors through a VC-gauntlet fundability gate. Resumable via a JSON state file. Best for "find the *real* opportunities in X", "keep digging until you exhaust X". The full method lives in [DEEP-DFS.md](DEEP-DFS.md) — read and follow it when `--deep` is passed, instead of the batch workflow below.

## Workflow

1. **Establish the domain** — identify the space the user wants ideas in (e.g., "MCP servers", "developer tools", "mobile apps for nurses"). Extract any constraints (tech stack, budget, solo founder, etc.) and previously killed ideas. Write these to a scratchpad file in the current working directory (`gap-finder-state.md`).
2. **Generate a batch of 5 ideas** — each must be concrete and specific to the domain. Follow the idea template in [GENERATION.md](GENERATION.md). Draw from at least 3 different angles per batch.
3. **Run the kill chain on every idea** — execute all 6 validation checks from [VALIDATION.md](VALIDATION.md). Search the web for each check. Kill on first fatal failure.
4. **Record killed ideas** — append every killed idea + specific kill reason to `gap-finder-state.md`. This prevents re-proposing.
5. **Present survivors** — if any ideas survive all 6 checks, present them with full evidence. See [SURVIVOR-FORMAT.md](SURVIVOR-FORMAT.md).
6. **Widen on saturation** — if 2 consecutive batches have 0 survivors AND >80% died at Check 1 (competitors), the current sub-space is saturated. Do NOT stop. Instead: (a) note the saturated sub-space in state file, (b) expand the domain — go more niche, go adjacent, change the target user, change the business model, or combine two domains. Keep generating. The goal is survivors, not a saturation report.
7. **Loop until 3 survivors** — go to step 2. There is no batch limit. Keep generating until 3 survivors are found. After every 5 dead batches, radically pivot: change the domain, the target user, the business model, or the geography. The answer exists — you haven't looked hard enough yet.
8. **Report survivors as they emerge** — present each survivor immediately when it passes all 6 checks (don't wait for 3). After 3 survivors, write the final ranked summary.

## Self-review checklist

Before delivering results, verify ALL:

- [ ] Every proposed idea was searched on at least 3 relevant sources (varies by domain — e.g., npm+Smithery+GitHub for dev tools, App Store+ProductHunt+Google for apps)
- [ ] Every killed idea has a specific, one-sentence kill reason (not "didn't seem viable")
- [ ] Every survivor has competitor search evidence showing < 2 direct competitors, or a clear differentiation from existing ones
- [ ] Every survivor answers "what recurring pain point does this solve?" with a concrete user scenario
- [ ] Every survivor has a realistic monetization or growth path described in one sentence
- [ ] No survivor is something trivially solved by existing free tools or LLMs without external data
- [ ] At least 3 batches were generated (15+ ideas evaluated)
- [ ] Each idea is specific (names concrete features/tools, not just a category)
- [ ] Killed ideas are tracked in gap-finder-state.md to prevent re-proposing

## Golden rules

Hard rules. Never violate these.

1. **Search before you pitch.** Never present an idea without first searching for existing implementations. Every idea gets 3+ web searches across relevant platforms. No exceptions. No "I believe there aren't competitors" — show the search results.
2. **Kill fast, document why.** The moment an idea fails any validation check, kill it. Record the specific kill reason. Do not soften failures into "could work with modifications."
3. **Recurring pain or death.** If the pain point occurs less than weekly for the target user, the idea is dead. Quarterly pain is not a business. Daily frustration is.
4. **Existing-solution-already-works is fatal.** If a free, widely-adopted tool already solves this well enough, the idea is dead. "But ours would be slightly better" is not a gap — it's a feature request on the existing tool.
5. **Never stop until survivors are found.** There is no batch limit. Keep generating and validating until 3 survivors emerge. No early exits. No "the market is saturated" conclusions. When obvious ideas die, get weirder. When a sub-space is crowded, move to an adjacent one. Parallelize validation across multiple agents when possible — each idea's kill chain is independent and can run concurrently.
6. **Concrete features, not categories.** "A developer tool" is not an idea. "A CLI that takes a package.json and returns a dependency upgrade plan with breaking change warnings by cross-referencing changelogs" is an idea.
7. **No resurrections.** Once an idea is killed, it stays dead. Do not re-propose killed ideas with minor variations. If "Postgres optimizer" is dead, "MySQL optimizer" dies for the same structural reason.
8. **Evidence over intuition.** Every claim about market size, competitor count, or user demand must be backed by a search result or concrete data point. "I think developers would want this" is not evidence.

## Reference files

| File | Contents |
|------|----------|
| [GENERATION.md](GENERATION.md) | How to generate idea batches, the idea template, angle diversity requirements |
| [VALIDATION.md](VALIDATION.md) | The 6-check kill chain with search strategies and pass/fail criteria |
| [SURVIVOR-FORMAT.md](SURVIVOR-FORMAT.md) | Output format for surviving ideas with required evidence sections |
| [DEEP-DFS.md](DEEP-DFS.md) | `--deep` mode: the full DFS / tuple / codex-cross-attack / steelman / VC-gauntlet method |
Pliki w paczce (5)
  • DEEP-DFS.md 13 KB
  • GENERATION.md 4 KB
  • SKILL.md 7 KB
  • SURVIVOR-FORMAT.md 3 KB
  • VALIDATION.md 13 KB

Wersje

RepozytoriumWynikLicencja
Ta strona · npow/claude-skills90Apache-2.0
seandavi/scriptorium100MIT

Migawka bazy z 13.11.2026 · wersja paczki 4e2bf7e72e84 (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 100ideas
    Wyszukuje nowe pomysły na produkty, funkcje i biznes, łącząc wiki wiedzy, repozytoria GitHub, notatki o klientach i trendy rynkowe, i zapisuje dokument w vaulcie Obsidian.
  • 100business-ideas
    Generuje pomysły na biznes w stałym formacie: czy to produkt czy usługa, kto płaci, za co, ile i jaka jest przewaga.
  • 100founder-ideation
    Generuje i krytycznie ocenia pomysły na biznes przez adwersaryjną burzę mózgów czterech perspektyw, opartą na danych o bólu z Reddita i sygnałach z GDELT, także dla nisz i rosnących branż.
  • 90white-space-analysis
    Znajduje niezaspokojone luki rynkowe, oceniając zadania do wykonania (jobs-to-be-done) według ważności i satysfakcji oraz sprawdzając, czy luka jest realna i warta zdobycia.
  • 100brainstorm-ideas
    Generuje pomysły na produkt z perspektywy PM, designu i inżynierii, łączy je z szansą i wybiera pięć o największym potencjale.
  • 85brainstorm-ideas-existing
    Generuje pomysły na funkcje istniejącego produktu z perspektywy product managera, projektanta i inżyniera.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.