Token导航 LogoToken导航TokenDH.com
研究检索只读clawhub未标认证来源可访问clear审计提醒

structured-falsification结构化证伪

Agent Skill

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

总安装

2,521

周安装

103

GitHub Stars

公开资料未说明

下载量

816
OpenClaw

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:structured-falsification(结构化证伪)
来源仓库:https://github.com/shenjianjun687-ops/structured-falsification
安装命令:
openclaw skills install structured-falsification
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

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

ClawHubOpenClaw
openclaw skills install structured-falsification

简介

提供复杂决策与投资分析的结构化证伪框架,支持多因素判断。

  • 适用于 OpenClaw 中评估技术选型或投资方案时。
  • 通过 clawhub 安装,建议结合来源仓库和 README 核验适用条件。
  • 使用前需确认权限、维护状态及是否引用外部数据源。
  • 注意评估是否会触发联网查询或生成报告文件。structured-falsification 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

name
structured-falsification
description
>

Structured Falsification (结构化证伪法)

A five-step reasoning framework that forces rigorous disconfirmation before arriving at conclusions. Designed for AI agents and LLMs to produce concise, high-confidence outputs on complex tasks.

Core principle: Show conclusions, not derivation. The agent runs the full five-step process internally but outputs only the final ranked conclusions with confidence levels and key risks. Verbose reasoning is a sign the framework wasn't applied rigorously enough — tighten the analysis, don't expand the output.

When to Auto-Trigger

  • Multiple competing options with no clear winner
  • User asks "should I…", "which one…", "what about…", "evaluate…", "compare…"
  • Investment target analysis, due diligence, competitive assessment
  • Technology selection, architecture decision, vendor evaluation
  • Any task where the cost of a wrong answer is high

The Five Steps (internal process)

Step 1: Decompose Value Nodes

Map the problem space. Identify where real value / risk / leverage sits.

  • What does this problem *actually* need? (Not surface requirements — underlying drivers)
  • Map key entities and their relationships (supply chain / dependency graph / stakeholder map)
  • Classify each node: critical vs. nice-to-have vs. irrelevant

Step 2: Falsify Each Candidate (core step)

For every option / target / claim, run:

  1. Surface logic: Why does the market / conventional wisdom support this?
  2. Challenge: Where is the logic fragile? Causal chain breaks? Concept substitution? Hidden assumptions?
  3. Verdict: Rate association strength — direct / indirect / tangential

Output: a falsification table (internal) with columns: Candidate | Surface Logic | Challenge | Verdict

Step 3: Identify True Beneficiaries / Best Options

Apply priority filters:

  1. Infrastructure / tooling (selling shovels during a gold rush) → highest certainty
  2. Core technology owners (commercializable IP) → highest upside
  3. Application layer (using tech to cut costs / add features) → value capture may be limited

Step 4: Stress Test Survivors

For each surviving candidate:

  • Is the causal chain A→B→C fully intact at every link?
  • Is there actual evidence? (Business data, orders, customers, benchmarks)
  • If this logic fails, how bad is the downside?
  • Any show-stopper that eliminates this candidate entirely?

Step 5: Rank and Conclude

  • Sort by certainty (High / Medium / Low)
  • Attach to each: one-line logic, key assumption, core risk
  • Explicitly flag "not recommended" items with reasons
  • One-sentence bottom line

Self-Correction Checklist

Before producing output, verify:

  • [ ] Did I falsify hard enough? If every candidate survived, the filter is too loose.
  • [ ] Did I confuse "good company" with "good thesis"? Logic > quality.
  • [ ] Am I hedging excessively? Pick a direction. Uncertainty should be flagged, not hidden behind "it depends".
  • [ ] Did I anchor on the first plausible answer? Force a search for disconfirming evidence.
  • [ ] Is my output concise? If the conclusion section exceeds 50% of the total output, re-tighten.

Output Format

Only output the following. No step-by-step narration. No "let me think about this".

## 结论

| # | 候选 | 判断 | 确定性 | 核心逻辑(一句话) | 关键假设 | 主要风险 |
|---|------|------|--------|---------------------|----------|----------|
| 1 | ...  | ✅/⚠️/❌ | 高/中/低 | ... | ... | ... |
| 2 | ...  | ...  | ...    | ...                 | ...      | ...      |

**一句话总结:** ...

Domain Configurations

Load domain-specific checklists when the context matches:

  • Investment analysis → Read references/investment.md
  • Technology selection → Read references/tech-decision.md
  • Other domains → Use the generic framework above, or read a custom config from references/

To create a custom domain config, copy references/domain-template.md and fill in the sections.

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

需要根据任务场景推荐可安装能力包时

04

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

OpenClaw

87.49%
按下载量换算714

安全审计

VirusTotal

通过

ClawScan

可疑

Static analysis

通过

权限和风险

只读

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

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills