Systematically identify what's missing in non-fiction writing—both blind spots (inherent limitations) and blank spots (gaps that could be addressed). Use before finalizing non-fiction or when feedback feels incomplete.
npx skills add https://github.com/jwynia/agent-skills --skill blind-spot-detective
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.
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.
| 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.
Processing information that confirms existing beliefs while ignoring contradictions.
Self-check:
Assuming readers share your specialized knowledge.
Self-check:
Recognizing biases in others but not yourself.
Self-check:
| Question Type | Purpose | Examples |
|---------------|---------|----------|
| Clarification | Explore complex ideas | What exactly do I mean? How does this relate to my main argument? |
| Assumption-Probing | Uncover hidden assumptions | What am I taking for granted? What unstated beliefs underlie this? |
| Evidence & Reasoning | Evaluate support quality | What evidence supports this? Is it sufficient? Does my conclusion follow? |
| Alternative Viewpoints | Challenge default framework | How would a different discipline view this? What would critics say? |
Read as if you:
| Gap Type | Action |
|----------|--------|
| Missing evidence | Add sources, examples, or data |
| Missing perspective | Seek input from that group or acknowledge gap |
| Missing logic | Add explicit reasoning or transitions |
| Missing context | Add background or definitions |
| Inherent limitation | Acknowledge in scope statement |
Pattern: Using blind spot detection to delay finishing. Every gap found leads to more analysis. Nothing is ever complete enough.
Why it fails: Writing is never perfect. Blind spot detection is for identifying significant omissions, not achieving impossible completeness.
Fix: Set a threshold. "I will address gaps that fundamentally undermine my argument, not every possible expansion." Time-box the detection process.
Pattern: Running blind spot analysis before having a draft. Looking for gaps in something that doesn't exist yet.
Why it fails: Blind spot detection works on existing writing. You need something to analyze. Pre-draft gap anxiety prevents ever starting.
Fix: Write first, detect second. Get a complete draft, then identify what's missing. Gaps are easier to see in concrete text than abstract plans.
Pattern: Treating every identified gap as something to address. Expanding scope until the piece becomes unmanageable.
Why it fails: Not every gap needs filling. Some gaps are appropriate for scope. Trying to address everything produces bloated, unfocused writing.
Fix: Distinguish blind spots (acknowledge limitation) from blank spots (expand coverage). For each gap, ask: "Is filling this essential to my thesis?"
Pattern: Believing you need outside experts to identify blind spots. Waiting for external validation instead of systematic self-review.
Why it fails: While outside perspectives help, you can identify many blind spots yourself with systematic frameworks. Dependency creates bottlenecks.
Fix: Use the frameworks first. Get external review for validation, not discovery. Most obvious gaps can be found with structured self-interrogation.
Pattern: Producing exhaustive lists of missing elements without prioritizing which matter most.
Why it fails: A 50-item gap list is paralyzing. Not all gaps are equal. Without priority, writers either give up or address gaps randomly.
Fix: Categorize by severity: critical (undermines thesis), significant (weakens argument), minor (would enhance). Address critical first.
Inbound:
Outbound:
Complementary:
non-fiction-revision: For implementing fixessummarization: For testing thesis clarityresearch: For filling evidence gapsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
Use when implementing any feature or bugfix, before writing implementation code
Use when you have a spec or requirements for a multi-step task, before touching code
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.
| Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases.
Official Opentrons Protocol API for OT-2 and Flex robots. Use when writing protocols specifically for Opentrons hardware with full access to Protocol API v2 features. Best for production Opentrons protocols, official API compatibility. For multi-vendor automation or broader equipment control use pylabrobot.
Take jwynia/blind-spot-detective from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.