Token导航 LogoToken导航

Agent Skill · 研究检索

blind-spot-detective(盲点侦探)

blind-spot-detective 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

blind-spot-detective 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为权限未标注;许可证为 MIT,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 19,758。

总安装 5,472周安装 228GitHub Stars 69下载 1,824核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:blind-spot-detective(盲点侦探)
来源仓库:https://github.com/jwynia/agent-skills
仓库路径:skills/blind-spot-detective
安装命令:
npx skills add https://github.com/jwynia/agent-skills --skill blind-spot-detective
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。不同来源提供的安装方式可能略有差异;本站展示可直接复制的安装命令,安装前请核对来源页面。

skills.shnpx skills
npx skills add https://github.com/jwynia/agent-skills --skill blind-spot-detective

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

用于查找、检索和筛选相关信息。适合根据关键词、任务场景或来源线索快速定位候选结果。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。blind-spot-detective 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

来源仓库内路径:skills/blind-spot-detective

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/jwynia/agent-skills --skill blind-spot-detecti…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    权限没有明确标注,第一次使用时只给一个无关紧要的任务,观察它到底读了哪些文件和网络。

常见问题

6 条

blind-spot-detective 怎么安装?

在终端执行 npx skills add https://github.com/jwynia/agent-skills --skill blind-spot-detective。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

blind-spot-detective 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

blind-spot-detective 需要什么权限?

权限级别没有明确标注。第一次使用时建议只给无关紧要的任务,观察它实际读写了哪些内容。

blind-spot-detective 是免费的吗?

来源标注的许可证是 MIT。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

blind-spot-detective 用的人多吗?

公开数据是累计安装 5,472 次,近一周安装 228 次,下载 1,824 次,GitHub 69 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

blind-spot-detective 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 3 个目录同时收录,说明这个 Skill 流传比较广。
  • 许可证明确为 MIT,商用和分发边界好判断。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 需要许可证清楚、并且有第三方扫描结果的团队项目。

不太适合

  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
blind-spot-detective

盲点侦探 · 本页

5,47269权限未标注MIT通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

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

TypeDefinitionSolution
Blind SpotsLimitations inherent to your methodology, theory, or perspectiveAdjust your approach or acknowledge limitations
Blank SpotsGaps that could be addressed within your current approachExpand 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.


Framework 1: Cognitive Bias Check

Confirmation Bias

Processing information that confirms existing beliefs while ignoring contradictions.

Self-check:

  • Have I primarily sought sources supporting my views?
  • Have I given fair consideration to counter-evidence?
  • Am I dismissing perspectives without adequate examination?

Curse of Knowledge

Assuming readers share your specialized knowledge.

Self-check:

  • Have I defined specialized terminology?
  • Am I assuming background knowledge readers might lack?
  • Would someone new to this topic understand?

Bias Blind Spot

Recognizing biases in others but not yourself.

Self-check:

  • Have I critically examined my own assumptions?
  • Am I applying the same standards to opposing views?
  • Have I invited critique from different perspectives?

Framework 2: Socratic Questioning

Question TypePurposeExamples
ClarificationExplore complex ideasWhat exactly do I mean? How does this relate to my main argument?
Assumption-ProbingUncover hidden assumptionsWhat am I taking for granted? What unstated beliefs underlie this?
Evidence & ReasoningEvaluate support qualityWhat evidence supports this? Is it sufficient? Does my conclusion follow?
Alternative ViewpointsChallenge default frameworkHow would a different discipline view this? What would critics say?

Framework 3: Content Checklist

Thesis Clarity

  • Is the main idea clearly stated early?
  • Does each section contribute to the main thesis?
  • Have I articulated why this topic matters?
  • Would a reader easily identify my central argument?

Structure & Flow

  • Does section order make logical sense?
  • Are transitions smooth and coherent?
  • Is there clear progression of ideas?
  • Have I provided signposts for the reader?

Credibility & Evidence

  • Are all claims supported by credible evidence?
  • Have I addressed significant counter-arguments?
  • Are sources diverse and representative?
  • Have I been transparent about methodological limitations?

Audience Perspective

  • Have I considered audience knowledge vs. my knowledge?
  • Are technical terms adequately explained?
  • Would someone outside my field understand?
  • Have I considered diverse reader backgrounds?

Framework 4: Missing Elements Analysis

Missing Perspectives

  • Stakeholder gaps: Whose voice is absent?
  • Cultural gaps: What cultural perspectives are missing?
  • Historical gaps: What historical context is omitted?
  • Disciplinary gaps: What other fields would add insight?

Missing Content Types

  • Examples: Are abstract concepts grounded in concrete cases?
  • Counter-examples: Have I addressed what doesn't fit my thesis?
  • Transitions: Do ideas flow or jump?
  • Implications: Have I addressed "so what?"

Missing Logic

  • Unstated premises: What assumptions bridge my arguments?
  • Alternative explanations: What else could explain my evidence?
  • Edge cases: What situations challenge my generalizations?
  • Causal gaps: Am I conflating correlation with causation?

Detection Techniques

Outsider Test

Read as if you:

  • Disagree with your thesis
  • Know nothing about the topic
  • Come from a different culture
  • Work in a different field

Gap-Finding Questions

  • What would a hostile reviewer point out?
  • What questions would a curious reader ask?
  • What would someone from [different field] notice missing?
  • What did I almost include but cut?

Structural Audit

  1. List each section's main claim
  2. List evidence supporting each claim
  3. List possible objections to each claim
  4. Identify which objections you addressed
  5. Note unaddressed objections

Common Blind Spots by Genre

Academic Writing

  • Over-reliance on literature from one tradition
  • Ignoring practical implications
  • Assuming disciplinary jargon is universal
  • Missing interdisciplinary connections

Business Writing

  • Assuming reader shares organizational context
  • Overlooking implementation challenges
  • Missing stakeholder perspectives
  • Ignoring historical precedents

Self-Help/Advice

  • Survivorship bias (only successful examples)
  • Ignoring structural barriers
  • Assuming universal applicability
  • Missing edge cases and exceptions

Technical Writing

  • Curse of knowledge (expert blindness)
  • Missing conceptual foundation
  • Skipping "obvious" steps
  • Ignoring non-technical context

Remediation Actions

Gap TypeAction
Missing evidenceAdd sources, examples, or data
Missing perspectiveSeek input from that group or acknowledge gap
Missing logicAdd explicit reasoning or transitions
Missing contextAdd background or definitions
Inherent limitationAcknowledge in scope statement

Anti-Patterns

1. The Perfection Paralysis

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.

2. The Detective Without a Case

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.

3. The Scope Creep Trap

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?"

4. The Outside Expertise Dependency

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.

5. The Gap List Without Priorities

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.

Integration Points

Inbound:

  • Before finalizing non-fiction writing
  • During revision process
  • When feedback feels incomplete

Outbound:

  • To revision and editing
  • To additional research
  • To scope clarification

Complementary:

  • non-fiction-revision: For implementing fixes
  • summarization: For testing thesis clarity
  • research: For filling evidence gaps

平台分布

Claude Code

31.12%
按下载量换算568

OpenCode

23.83%
按下载量换算435

Antigravity

18.2%
按下载量换算332

Codex

13.57%
按下载量换算248

Gemini CLI

7.27%
按下载量换算133

windsurf

3.67%
按下载量换算67

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

权限未标注

当前来源未能明确判断权限范围,默认进入异常复核队列。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。

继续浏览同类 Skills