基于 SOC 职业分类
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt;运行前请先检查来源。
npx skills add https://github.com/lev-os/agents --skill absurdity-heuristic命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地?可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
| id | absurdity-heuristic |
| name | Absurdity Heuristic |
| description | Classify highly unusual situations as impossible - but beware of rejecting valid predictions |
| tagline | Classify highly unusual situations as impossible - but beware of rejecting valid predictions |
| type | mental-model |
| scope | decision-making |
| category | cognitive-bias-awareness |
| domains | ["rationality","forecasting","epistemic-hygiene"] |
The absurdity heuristic classifies highly atypical situations as "absurd" or impossible based on how much they violate our intuitions about what is typical or normal. It is the mirror image of the representativeness heuristic - the less X resembles Y, or the more X violates typicality assumptions of Y, the less probable that X is the product, explanation, or outcome of Y.
While normally useful as epistemic hygiene for detecting nonsense, it becomes an "absurdity bias" when we reject valid predictions or explanations simply because they seem too unusual.
Notice when you think: "That's absurd," "That can't be right," or "That's impossible" based purely on how unusual something seems.
Ask: Is this truly impossible, or just highly unusual? Does my sense of "absurdity" come from:
The absurdity heuristic becomes a bias in three situations:
A. Deep theory should override intuition When you have information about underlying laws that should override surface reasoning. Example: Quantum mechanics predictions that seem "absurd" but are mathematically sound.
B. Abstract information conflicts with surface absurdity Attending to surface absurdity despite abstract information that should override it. Example: Rejecting studies showing marginal healthcare spending has zero net effect because "that seems absurd."
C. Unstable processes The process is not stable in its surface properties over the range of extrapolation. Example: The future is usually "absurd" compared to 50 years prior - projecting stable surface rules forward fails.
When the heuristic triggers, consciously evaluate:
In epistemic context (seeking truth): Override absurdity intuitions with evidence and deep models. In instrumental context (making decisions): Weight absurdity appropriately - unusual claims may still require unusual evidence even if theoretically possible.
Technology Forecasting
Medicine
Physics
Risk Assessment
The absurdity heuristic is a double-edged sword: invaluable for detecting nonsense in stable domains, but systematically wrong when applied to unstable processes, deep theoretical predictions, or long-term forecasts. The skill is knowing when to trust it and when to override it.
Primary Sources: LessWrong (Eliezer Yudkowsky), Robin Hanson Related Concepts: Representativeness Heuristic, Outside View, Reference Class Forecasting Complexity: Medium Estimated Learning: 30 minutes to understand, ongoing practice to apply skillfully
Routes adaptive multi-agent deliberation with fractal context cycles. Use when using /cdo, think/deep/debug/parliament work, or long runs paired with autoresearch scheduling.
Use when you need an evidence-first provenance report from `cass`, repo docs, `.lev`, `~/.agents/diagrams`, `qmd`, or Grep/Glob tools.
Use the codebase knowledge graph for structural code queries. Triggers on: explore the codebase, understand the architecture, what functions exist, show me the structure, who calls this function, what does X call, trace the call chain, find callers of, show dependencies, impact analysis, dead code, unused functions, high fan-out, refactor candidates, code quality audit, graph query syntax, Cypher query examples, edge types, how to use search_graph.