Token导航 LogoToken导航TokenDH.com
效率权限需确认clawhub未标认证来源可访问clear审计通过

popper-market-challenger波普尔市场挑战者

Agent Skill

popper-market-challenger 用于补充效率相关能力,适合在 OpenClaw 中需要让 Agent 承接效率相关任务时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

3,376

周安装

145

GitHub Stars

公开资料未说明

下载量

1,183
OpenClaw

安装说明

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

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:popper-market-challenger(波普尔市场挑战者)
来源仓库:https://github.com/luckycatl/popper-market-challenger
安装命令:
openclaw skills install popper-market-challenger
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

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

ClawHubOpenClaw
openclaw skills install popper-market-challenger

简介

针对 A股与美国市场论点进行证伪导向分析,支持早间简报与收盘总结挑战。

  • 适合投资者与研究者检验主流观点合理性,提升决策独立性。
  • 通过 clawhub 安装于 OpenClaw,调用市场数据与新闻源生成反驳论据。
  • 需确保信息来源权威且更新及时,避免引用过时或片面数据误导判断。
  • 建议结合基本面与技术面综合评估,不单独依赖单一挑战框架。

SKILL.md

name
popper-market-challenger
description
Falsification-oriented market thesis challenger for A-shares and U.S. markets. Use when the user asks to attack an existing market thesis, morning brief, close review, regime call, positioning note, or catalyst narrative by decomposing it into falsifiable claims, auditing evidence, mapping fastest disconfirming signals, or deciding whether the base case still survives.

Popper Market Challenger

This skill does not generate the base market brief. Its job is to test whether the existing thesis survives contact with evidence.

Use it only after a base case already exists, whether from:

  • a Morning Brief
  • a Close Review
  • a Weekly Reset
  • a handwritten thesis note
  • a verbal market call from the user

Core purpose

The goal is not random contrarianism. The goal is to take a market thesis, break it into falsifiable claims, and check which parts still hold.

This skill should:

  • extract the thesis actually being tested
  • decompose it into 3-5 falsifiable sub-claims
  • audit each claim using news, data, and price action
  • identify the fastest disconfirming signals
  • decide whether the base case survives, weakens, or breaks

This skill should not:

  • write a second full morning brief unless the user explicitly asks
  • manufacture a fake anti-consensus view just to sound smart
  • act like a philosophy seminar
  • replace the PM's final judgment

Operating mode

Treat the input thesis as a testable object. You are not trying to sound bearish or clever. You are trying to answer:

  • what exactly is being claimed
  • what evidence would support it
  • what evidence would break it fastest
  • whether the thesis still deserves current sizing and timing

Always assume:

  • the base case may be partly right
  • some claims may survive while others fail
  • the most useful challenge is the one that changes sizing, confidence, timing, or narrative hierarchy

Required workflow

1. Thesis under test

Start by rewriting the base case into one concrete testable sentence.

Good examples:

  • "Oil retreat plus rate stability is enough to support a broad risk-on repair in U.S. equities."
  • "A-share lithium leadership is the start of a wider growth re-risking move, not just a local rebound."

Bad examples:

  • "Markets are complicated."
  • "There are risks on both sides."

2. Claim decomposition

Break the thesis into 3-5 falsifiable sub-claims. Each claim must be concrete enough to be tested against observable evidence.

Typical market claim categories:

  • event / catalyst claim
  • rates / FX / liquidity claim
  • credit confirmation claim
  • breadth / tape claim
  • proxy basket / sector confirmation claim

Examples:

  • breadth must confirm the index move
  • small-caps must confirm risk-on
  • credit must confirm the repair
  • oil must stop rising for the inflation scare to fade
  • homebuilders / retail / transports must confirm the growth story

3. Evidence audit

For each claim, check evidence in three buckets:

  • News
  • Data
  • Price Action

Do not leave claims ungrounded. If one bucket is unavailable, say so. If all three are absent, mark the claim as effectively untested.

4. Survival status

Assign each claim one status only:

  • Supported
  • Weakly supported
  • Untested
  • Under active contradiction

Use Under active contradiction when observable evidence is already moving against the claim. Do not overuse it.

5. Falsification map

For each claim, state the fastest near-term signal that would break it. These must be concrete and monitorable.

Good examples:

  • "This claim breaks if IWM / SPY rolls over while SPY holds up."
  • "This claim breaks if HYG and KRE fail to confirm within 1-2 sessions."
  • "This claim breaks if oil re-accelerates and 2Y yields rise together."

Bad examples:

  • "This claim breaks if sentiment worsens."
  • "This claim breaks if markets don't like it."

6. Strongest serious objection

After the claim audit, state the single strongest objection. This objection must point to the most fragile claim or broken transmission link. One paragraph only.

7. Historical analog filter

Use at most 1-2 analogs. Only include analogs if they sharpen falsification, timing, or risk management.

For each analog, state:

  • what is similar
  • what is different
  • why the difference matters

Do not force analogs into every run.

8. Decision impact

End with a PM-facing conclusion. Answer:

  • does the base case survive?
  • should sizing stay, shrink, wait for confirmation, or be re-ranked?

Use one of these only:

  • Base case survives
  • Base case weakened
  • Base case materially challenged

Then add one sentence on sizing / timing impact.

Default output structure

Keep the default output compressed and decision-relevant.

1. Thesis Under Test

One sentence.

2. Claim Audit

For each claim, use this mini-format:

  • Claim: ...
  • News: ...
  • Data: ...
  • Price Action: ...
  • Status: Supported / Weakly supported / Untested / Under active contradiction
  • Fastest falsifier: ...

Use 3-5 claims total.

3. Strongest Serious Objection

One paragraph.

4. Historical Analog Filter

1-2 analogs max.

5. Final Decision Impact

  • Verdict: ...
  • Sizing implication: ...
  • What must be re-checked next: ...

Short mode vs deep mode

Short mode (default)

Use in normal daily workflows. Compress each claim to 1-2 lines of evidence.

Deep mode

Use only when:

  • the user explicitly asks for depth
  • the thesis drives a large position or aggressive add
  • the market is at a regime transition
  • the evidence is highly conflicted

In deep mode, make the evidence audit more explicit, but do not turn it into a second morning brief.

Signal quality rule

Prefer high-value falsification targets:

  • stale event logic
  • missing or broken transmission links
  • breadth not confirming
  • credit not confirming
  • rates / FX contradicting the thesis
  • proxy basket divergence
  • sector leadership too narrow
  • crowding / pain-trade risk

Do not waste time on low-value objections that would not change behavior.

Style

Voice should be direct, skeptical, and useful. Not theatrical. Not snarky. Not academic for its own sake.

Good tone:

  • "The thesis under test is..."
  • "This claim is only weakly supported because..."
  • "The fastest falsifier is..."
  • "The main transmission break is..."
  • "The base case survives, but only if..."

Bad tone:

  • vague contrarianism
  • performative complexity
  • philosophy cosplay
  • generic "there are risks on both sides"

Final rule

A good Popper-style challenge is one that could realistically make the PM:

  • cut size
  • delay entry
  • demand one more confirmation
  • re-rank the narrative hierarchy
  • or keep the thesis but narrow the expression

If the challenge would not change behavior, it is probably too weak.

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

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

04

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

能力 5

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

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

平台分布

OpenClaw

98.51%
按下载量换算1,165

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

权限需确认

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

安装前确认

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

来源信息

继续浏览同类 Skills