Blind Spot Detective

Before you ship that blog post or technical article, run it through this systematic gap finder. It separates blind spots (inherent limits of your approach) from blank spots (things you could add), and walks you through four frameworks including cognitive bias checks, Socratic questioning, and missing perspectives analysis. The anti-patterns section is especially useful, calling out "perfection paralysis" and "scope creep trap" as real hazards. What I like is it acknowledges you can't fix everything, you just need to know what you're leaving out. Best used on complete drafts, not works in progress.

skills.sh installs: 330
GitHub stars: 182
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add jwynia/agent-skills --skill blind-spot-detective --agent claude-code

Installs into .claude/skills of the current project.

Files

Blind Spot Detective

Purpose

Systematically identify what's missing in non-fiction writing—both blind spots (inherent limitations of your approach) and blank spots (gaps that could be addressed). Provides frameworks for finding omissions, testing assumptions, and ensuring comprehensive coverage.

Core Principle

What you can't see matters more than what you can. Identifying what's missing is harder than recognizing what's included. Systematic interrogation reveals gaps that casual review misses.

Blind Spots vs. Blank Spots

Type	Definition	Solution
Blind Spots	Limitations inherent to your methodology, theory, or perspective	Adjust your approach or acknowledge limitations
Blank Spots	Gaps that could be addressed within your current approach	Expand coverage within existing framework

Key insight: Understanding which type of gap you're dealing with determines whether to change your approach or simply expand it.