Token导航 LogoToken导航

Agent Skill · 研究检索

support-with-evidence(有证据支持)

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

support-with-evidence 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描有提醒项,按安装量在研究检索类的 73,675 个 Skill 里排第 56,419。

总安装 451周安装 19GitHub Stars 12下载 158核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/jbrukh/skills --skill support-with-evidence

这个 Skill 是做什么的

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

support-with-evidence 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中快速定位候选结果。适用于需要根据关键词或任务场景进行信息检索的场景,如技术支持或问题排查。通过关键词输入和来源仓库筛选,Agent 可返回结构化候选结果供进一步处理。

安装前需确认权限范围和维护状态,注意是否触发联网或文件读写操作。建议结合原始 README 核验具体用法,避免直接使用未经验证的输出结论。

来源仓库内路径:skills/support-with-evidence

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/jbrukh/skills --skill support-with-evidence;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

support-with-evidence 怎么安装?

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

support-with-evidence 支持哪些 AI 工具?

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

support-with-evidence 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

support-with-evidence 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

support-with-evidence 用的人多吗?

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

support-with-evidence 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

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

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 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调用外部服务未明确有提醒
support-with-evidence

有证据支持 · 本页

45112只读未明确有提醒

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

SKILL.md 原文

Support With Evidence

Take a body of text — an argument, a set of claims, a thesis, bullet points — and extract the falsifiable ideas from it. Then go out and find real evidence for or against each one. The goal is not confirmation bias — it's an honest evidence audit. If the evidence supports the idea, you'll see it. If the evidence contradicts the idea, you'll see that too.

When to Use

  • User has claims, predictions, or assertions and wants to know what evidence exists
  • User asks "is this true?" or "can you find evidence for this?" or "support this with evidence"
  • User wants to fact-check or ground-truth a set of ideas before publishing or acting
  • User has a thesis and wants to know which parts are empirically supported and which are speculation

Do NOT use for: stress-testing a thesis for logical weaknesses (use stress-test), evaluating prompts (use think-critically), or surfacing insights from data (use surface-insight).

The Honesty Rule

This skill's job is to find evidence — not to confirm what the user hopes is true. The single most important rule:

  • Report what you find, not what the user wants to hear
  • If evidence contradicts the idea, say so clearly and present the counter-evidence
  • If you cannot find meaningful evidence either way, say so — "no evidence found" is a legitimate and valuable output
  • Never fabricate, hallucinate, or overstate evidence — cite real sources or state that the search was inconclusive
  • ENFORCEMENT: Every evidence bullet must include a source — a named study, dataset, organization, publication, or URL. If you cannot name a source, the bullet is not evidence. Discard it.

Process

Phase 1: Claim Extraction (Output)

Read the user's input. Extract all falsifiable ideas — claims that could in principle be shown true or false with evidence.

FALSIFIABILITY GATE: For each candidate claim, apply this test: "What observable evidence would confirm or deny this?" If you cannot answer that question, the claim is not falsifiable — it's an opinion, value judgment, or unfalsifiable abstraction. Do not research it. Instead, list it separately as "Non-falsifiable (skipped)" with a one-sentence explanation of why.

SHARPENING: If a claim is close to falsifiable but too vague as stated, sharpen it into a testable version. Show both the original wording and your sharpened version. Ask the user to confirm only if the sharpening substantially changes the meaning. Otherwise, proceed with the sharpened version and note what you did.

HARD RULE: Extract 1-10 claims. If the input contains more than 10 falsifiable claims, keep the 10 most substantive. If it contains zero, state: "No falsifiable claims found in the input — nothing to research."

Output:

## Extracted Claims

| # | Claim | Falsifiable? |
|---|---|---|
| 1 | [claim as stated or sharpened] | Yes |
| 2 | [claim] | Yes |
| ... | ... | ... |
| N | [non-falsifiable claim] | No — [reason] |

Phase 2: Deep Research (Silent)

For each falsifiable claim, conduct deep research using web search tools. This is not a surface-level check — dig into it.

Research procedure per claim:

  1. Search broadly. Use multiple search queries — rephrase the claim, search for supporting evidence, then search for contradicting evidence. Do not stop at the first result.
  2. Seek primary sources. Prefer peer-reviewed studies, government data, established datasets, named expert opinions, and reputable journalism over blog posts, opinion pieces, or anonymous forums.
  3. Check both sides. For every claim, actively search for evidence AGAINST it, not just for it. If the first few results all confirm, search harder for disconfirming evidence — and vice versa.
  4. Assess source quality. A single blog post is not equivalent to a meta-analysis. Weight evidence by source credibility.
  5. Note recency. Evidence from 2024-2026 is stronger than evidence from 2015 for claims about current states of affairs. Flag when evidence is dated.

RESEARCH DEPTH: Spend meaningful effort on each claim. Use at least 2-3 distinct search queries per claim. Read actual results, not just titles. If initial searches are inconclusive, try different angles — related statistics, adjacent research, expert commentary.

Do not output Phase 2 reasoning.

Phase 3: Evidence Assembly & Rating (Output)

For each falsifiable claim, present the evidence found and rate it.

Evidence Strength Scale:

  • Very Strong: Multiple independent, high-quality sources directly confirm. Peer-reviewed research, replication, broad expert consensus, or authoritative data.
  • Strong: Credible sources with direct evidence. Established facts, solid data, or well-sourced reporting from reputable outlets.
  • Moderate: Some evidence exists but with caveats — limited sources, indirect evidence, small sample sizes, or some conflicting data.
  • Weak: Thin evidence — anecdotal, from low-quality sources, speculative, or a single unreplicated finding.

Direction:

  • Supported: Evidence found predominantly in favor of the claim.
  • Contested: Mixed evidence — meaningful evidence exists on both sides.
  • Unsupported: Little or no evidence found either way.
  • Contradicted: Evidence found predominantly against the claim.

Output format per claim:

### Claim [#]: [claim text]

**Direction: [Supported | Contested | Unsupported | Contradicted]**
**Evidence Strength: [Very Strong | Strong | Moderate | Weak]**

**Evidence for:**
- [Evidence point with source name/URL] — [1 sentence explaining relevance]
- [Evidence point with source] — [1 sentence]
...

**Evidence against:**
- [Evidence point with source name/URL] — [1 sentence explaining relevance]
- [Evidence point with source] — [1 sentence]
...

**Assessment:** [2-3 sentences: your honest reading of what the evidence says. Does it support, contradict, or leave the claim uncertain? What's the strongest evidence on each side? What evidence is missing that would be decisive?]

HARD RULES:

  • Include at least 1 evidence bullet per claim (for or against). If you truly found nothing, state "No meaningful evidence found in search" and rate as Unsupported/Weak.
  • Every evidence bullet must name its source. No unnamed evidence.
  • If all evidence points in one direction, actively state what counter-evidence you searched for and didn't find — this is more honest than pretending the search was balanced.
  • Order evidence bullets by strength (strongest first).

Phase 4: Summary Scorecard

After all claims, output a summary table:

## Evidence Scorecard

| # | Claim | Direction | Strength | Sources |
|---|---|---|---|---|
| 1 | [short form] | Supported | Strong | 4 |
| 2 | [short form] | Contradicted | Very Strong | 6 |
| ... | ... | ... | ... | ... |

**Overall: [X] of [Y] claims supported, [Z] contested, [W] contradicted, [V] unsupported.**

If any claims were non-falsifiable, add a note:

[N] claims were non-falsifiable and excluded from research.

Phase 5: Bottom Line

End with a short synthesis — 2-4 sentences max. What's the overall evidence picture? Which claims are on solid ground and which are shaky? If the user's input was a coherent argument, does the evidence support the argument as a whole, or only parts of it?

## Bottom Line

[2-4 sentences: honest synthesis of the evidence picture]

Quality Standards

The quality bar is the evidence test: could someone follow your citations and verify what you reported?

  • Fail — No source. An evidence bullet without a named source. REJECT.
  • Fail — Fabricated. Evidence that doesn't correspond to a real source. REJECT.
  • Pass — Named source, relevant. A real source that speaks to the claim. MINIMUM.
  • Good — Primary source. A study, dataset, or authoritative report directly on point.
  • Strong — Multiple corroborating sources. Independent sources converging on the same finding.
  • Exceptional — Decisive evidence. A single source so authoritative it settles the question (e.g., a large meta-analysis, official government statistics, or a landmark ruling).

Aim for "Good" or above on at least half of evidence bullets.


Anti-Patterns

  • Confirmation bias. Only searching for evidence that supports the claim. The #1 failure mode. Always search both directions.
  • Source inflation. Treating a blog post citing a study as equivalent to the study itself. Trace to primary sources.
  • False balance. Presenting one weak blog post against a claim as equal to five peer-reviewed studies for it. Weight evidence honestly.
  • Fabricated citations. Inventing studies or statistics that don't exist. If you're unsure a source exists, say "based on search results" and describe what you found without inventing specifics.
  • Vague sourcing. "Studies show" or "experts say" without naming them. Name the study. Name the expert.
  • Recency neglect. Citing a 2012 study for a claim about 2025 market conditions without noting the gap.
  • Strength inflation. Rating weak evidence as strong because it supports the claim. Calibrate honestly.
  • Exhaustive but shallow. Listing 15 low-quality sources instead of 3 high-quality ones. Quality over quantity.

Key Principles

  1. Honesty over comfort. Report what the evidence says, not what the user wants to hear. A well-sourced "your claim is contradicted" is more valuable than a vague "seems plausible."
  2. Sources or silence. Every evidence bullet names its source. Unsourced claims are not evidence — they're opinion.
  3. Both directions. For every claim, search for AND against. Asymmetric research is dishonest research.
  4. Strength calibration. A blog post is not a meta-analysis. Rate evidence by what it actually is, not what you wish it were.
  5. Less is more. Three well-sourced evidence points beat ten weakly sourced ones.
  6. Transparent gaps. When evidence is missing or inconclusive, say so. "We don't know" is a finding.

Input

[User provides text containing claims, ideas, or assertions below]

平台分布

Codex

37.05%
按下载量换算59

Claude

31%
按下载量换算49

Cursor

19.07%
按下载量换算30

Gemini CLI

9.64%
按下载量换算15

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills