How do I install the Find Gaps skill?

Run npx skillmds@latest add schub-tech/find-gaps in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Find Gaps safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Find Gaps?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Find Gaps free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Find Gaps?

schub-tech (@schub-tech) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Find Gaps by schub-tech — Agent Skill

Name: Find Gaps
Author: schub-tech

Find Gaps

Surface research gaps in the wiki and propose a plan to fill them. Reads an idea overview's "Still to validate" lines, "What we do not know" entries, and "Next moves," then proposes targeted research questions tagged by strategy (ask the user, do web research, or both). Use when the user wants to find gaps, deepen an idea, or says "what should I research next" / "what's missing" / "find gaps". For executing web research on a specific question, use `/research-deep` instead.

schub-tech 40fa6a1 2.8 KB Updated Sep 17, 2026

File contents

Convert the wiki's existing open questions into a concrete research plan. Don't invent new questions — start from what the idea overview already flags as unvalidated, then group, prioritize, and propose a strategy for each.

Read the wiki first. Start with wiki/index.md, then the idea overview, then its deep-dive notes. Pull every "Still to validate" line, every "What we do not know" entry, and every numbered move under "Next moves." Skip questions the wiki already answers — those are noise.

Cluster each gap by research strategy:

Ask the user. Things only the user knows — domain experience, network, prior conversations, direct buyer access, founder-fit detail.
Web research. Things that should be in public sources — competitor pricing, regulatory deadlines, named partners, market sizing, dated triggers.
Hybrid. Things that need a user hint to find the right web target ("is there a Texas DIR equivalent in your actual market?").

Propose the plan as a numbered list. For each item, name the question, the strategy, the wiki section it would feed, and rough effort (one search vs. deep dive). Lead with questions that would flip the verdict — fatal-flaw checks first, decoration last. If a question is decorative (would not change the verdict either way), say so and recommend dropping it.

Confirm scope with the user before executing:

Which questions to pursue this round (don't over-batch).
Time range for web research (e.g., "since 2024", "all time").
Depth (one search → one note vs. multiple search rounds → comprehensive note).
Whether to run web items in parallel via /research-deep.

Hand off. For web items, invoke /research-deep with the confirmed questions. For user-question items, surface them inline one at a time and capture the answers — short answers go directly into the relevant Still to validate line in the Notion wiki page; longer answers may warrant a new raw source page under Notion raw/<idea-slug>/.

Tie every proposed question to a specific wiki claim it would confirm or kill (e.g. "this would test the 60%-selector-drift bank-case figure"). Don't propose research the user could answer in two minutes. If a "Still to validate" line hedges, sharpen the question before researching it.

---name: find-gapsdescription: Surface research gaps in the wiki and propose a plan to fill them. Reads an idea overview's "Still to validate" lines, "What we do not know" entries, and "Next moves," then proposes targeted research questions tagged by strategy (ask the user, do web research, or both). Use when the user wants to find gaps, deepen an idea, or says "what should I research next" / "what's missing" / "find gaps". For executing web research on a specific question, use `/research-deep` instead.---Convert the wiki's existing open questions into a concrete research plan. Don't invent new questions — start from what the idea overview already flags as unvalidated, then group, prioritize, and propose a strategy for each.**Read the wiki first.** Start with `wiki/index.md`, then the idea overview, then its deep-dive notes. Pull every "Still to validate" line, every "What we do not know" entry, and every numbered move under "Next moves." Skip questions the wiki already answers — those are noise.**Cluster each gap by research strategy:**- **Ask the user.** Things only the user knows — domain experience, network, prior conversations, direct buyer access, founder-fit detail.- **Web research.** Things that should be in public sources — competitor pricing, regulatory deadlines, named partners, market sizing, dated triggers.- **Hybrid.** Things that need a user hint to find the right web target ("is there a Texas DIR equivalent in your actual market?").**Propose the plan as a numbered list.** For each item, name the question, the strategy, the wiki section it would feed, and rough effort (one search vs. deep dive). Lead with questions that would flip the verdict — fatal-flaw checks first, decoration last. If a question is decorative (would not change the verdict either way), say so and recommend dropping it.**Confirm scope with the user before executing:**- Which questions to pursue this round (don't over-batch).- Time range for web research (e.g., "since 2024", "all time").- Depth (one search → one note vs. multiple search rounds → comprehensive note).- Whether to run web items in parallel via `/research-deep`.**Hand off.** For web items, invoke `/research-deep` with the confirmed questions. For user-question items, surface them inline one at a time and capture the answers — short answers go directly into the relevant `Still to validate` line in the Notion wiki page; longer answers may warrant a new raw source page under Notion `raw/<idea-slug>/`.Tie every proposed question to a specific wiki claim it would confirm or kill (e.g. "this would test the 60%-selector-drift bank-case figure"). Don't propose research the user could answer in two minutes. If a "Still to validate" line hedges, sharpen the question before researching it.

Frequently asked questions