Token导航 LogoToken导航TokenDH.com
研究检索需要联网github未标认证来源可访问clear审计通过

dialectical-mapping-steelmanningdialectical mapping steelmanning 搜索

Agent Skill

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

总安装

1,378

周安装

58

GitHub Stars

85

下载量

483
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

3

许可证

MIT

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/lyndonkl/claude --skill dialectical-mapping-steelmanning

简介

dialectical-mapping-steelmanning 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词快速定位候选结果时使用。

  • 适用于学术研究与逻辑推演场景,支持结构化辩论与立场强化分析。
  • 通过 npx skills add 命令从指定 GitHub 仓库安装,需确认权限与网络访问能力。
  • 使用前建议核实维护状态及是否涉及联网、命令执行等敏感操作。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

SKILL.md

Dialectical Mapping & Steelmanning

Table of Contents

Workflow

Copy this checklist and track your progress:

Dialectical Mapping Progress:
- [ ] Step 1: Frame the debate
- [ ] Step 2: Steelman Position A (Thesis)
- [ ] Step 3: Steelman Position B (Antithesis)
- [ ] Step 4: Map principles and tradeoffs
- [ ] Step 5: Synthesize third way
- [ ] Step 6: Validate synthesis quality

Step 1: Frame the debate

Identify the topic, the two polarized positions (Thesis vs Antithesis), and the apparent tension. Clarify why this feels like a binary choice. See Common Patterns for typical debate structures.

Step 2: Steelman Position A (Thesis)

Present Position A in its strongest form: underlying principle (what it values), best arguments (strongest case for this position), supporting evidence, and legitimate tradeoffs it accepts. Use resources/template.md for structure. Avoid strawmanning—present version that adherents would recognize as fair.

Step 3: Steelman Position B (Antithesis)

Present Position B in its strongest form with same rigor as Position A. Ensure symmetry—both positions get charitable treatment. See resources/template.md.

Step 4: Map principles and tradeoffs

Create tradeoff matrix showing what each position optimizes for (values) and what it sacrifices (costs). Identify underlying principles (speed, quality, freedom, safety, etc.) and how each position weighs them. For complex cases with multiple principles, see resources/methodology.md for multi-dimensional tradeoff analysis.

Step 5: Synthesize third way

Find higher-order principle or hybrid approach that transcends the binary. The synthesis should honor core values of both positions, create new value (not just compromise), and make new tradeoffs explicit. Use resources/template.md for structure. For advanced synthesis techniques (temporal synthesis, conditional synthesis, dimensional separation), see resources/methodology.md.

Step 6: Validate synthesis quality

Self-assess using resources/evaluators/rubric_dialectical_mapping_steelmanning.json. Check: steelmans are charitable and accurate, principles identified, tradeoffs explicit, synthesis transcends binary (not just compromise), new tradeoffs acknowledged. Minimum standard: Average score ≥ 3.5.

Common Patterns

Pattern 1: Temporal Synthesis (Both, Sequenced)

  • Structure: Do A first, then B. Or B in some phases, A in others.
  • Example: "Speed vs Quality" → Synthesis: Iterate fast early (speed), stabilize before launch (quality). Time-box exploration, then shift to refinement.
  • When to use: Positions optimize for different lifecycle stages or contexts.

Pattern 2: Conditional Synthesis (Both, Contextual)

  • Structure: A in these situations, B in those situations. Define decision criteria.
  • Example: "Centralized vs Decentralized" → Synthesis: Centralize strategy/standards/shared resources, decentralize execution/tactics/experiments. Clear escalation criteria for edge cases.
  • When to use: Positions are optimal in different scenarios or scopes.

Pattern 3: Dimensional Separation (Both, Different Axes)

  • Structure: Optimize A on one dimension, B on another orthogonal dimension.
  • Example: "Simple vs Powerful" → Synthesis: Simple by default (80% use cases), powerful for power users (progressive disclosure, advanced mode). Complexity optional, not mandatory.
  • When to use: Tradeoff is false—can achieve both on different dimensions simultaneously.

Pattern 4: Higher-Order Principle (Transcend via Meta-Goal)

  • Structure: Both A and B are means to same end. Find better means.
  • Example: "Build vs Buy" → Synthesis: Neither—rent/SaaS. Or: Build core differentiator, buy commodity. Higher principle: Maximize value creation per dollar/hour.
  • When to use: Binary options are tactics, not ends. Reframe around shared ultimate goal.

Pattern 5: Compensating Controls (Accept A's Risk, Mitigate with B's Safeguard)

  • Structure: Lean toward A, add B's protections as guardrails.
  • Example: "Move Fast vs Prevent Errors" → Synthesis: Move fast with automated testing, staged rollouts, quick rollback. Accept some errors, contain blast radius.
  • When to use: One position clearly better for primary goal, other provides risk mitigation.

Guardrails

Key requirements:

  1. Steelman, not strawman: Present each position as its adherents would recognize. Ask: "Would someone who holds this view agree this is a fair representation?" If not, strengthen it further.
  2. Identify principles, not just preferences: Go deeper than "Side A wants X, Side B wants Y." Find the underlying values each side optimizes for: freedom, safety, speed, equity, efficiency, etc.
  3. Synthesis should transcend, not just compromise: Splitting the difference (50% A, 50% B) is usually weak. Good synthesis finds a new option C that honors both principles at a higher level -- "both-and" thinking rather than "either-or" averaging.
  4. Make tradeoffs explicit: Every synthesis has costs. State what you gain and what you sacrifice vs pure positions. Avoid presenting synthesis as "best of both with no downsides."
  5. Avoid false equivalence: Steelmanning does not require treating both sides as equally correct. One position may have stronger arguments or evidence. Synthesis should reflect this (lean toward the stronger position, add safeguards from the weaker).
  6. Check for false dichotomy: Some "debates" are manufactured. Both A and B may be bad options. Ask: "Is this actually a binary choice, or are we missing option C/D/E?"
  7. Test synthesis with adversarial roles: Before finalizing, inhabit each original position and critique the synthesis. Would a partisan of A or B accept it, or see it as capitulation? If the synthesis cannot survive friendly fire, strengthen it.

Common pitfalls:

  • Strawmanning: "Position A naively believes X" (uncharitable). Instead: "Position A prioritizes Y principle because..."
  • False balance: Steelmanning doesn't require treating bad-faith arguments as if made in good faith. If one position is empirically wrong or logically inconsistent, note this after steelmanning.
  • Mushy middle: "Do a little of both" is not synthesis. Synthesis finds NEW approach, not diluted mix.
  • Ignoring power dynamics: Some debates aren't idea conflicts—they're conflicts of interest. Synthesis may not resolve structural problems.
  • Analysis paralysis: Dialectical mapping is a tool for decision-making, not an end. Set time bounds, converge on synthesis, decide.

Quick Reference

Key resources:

Typical workflow time:

  • Simple binary debate (2 positions, clear principles): 20-30 minutes
  • Complex multi-stakeholder debate: 45-60 minutes
  • Strategic frameworks (long-term decisions): 60-90 minutes

When to escalate:

  • More than 2 positions (multi-party dialectics)
  • Nested tradeoffs (position A itself is a synthesis of A1 vs A2)
  • Empirical questions disguised as value debates
  • Bad faith arguments (not resolvable via steelmanning) → Use resources/methodology.md for these advanced cases

Inputs required:

  • Debate topic: The decision or question being debated
  • Position A (Thesis): One side of the binary
  • Position B (Antithesis): The opposing side
  • Context (optional): Constraints, stakeholders, decision criteria

Outputs produced:

  • dialectical-mapping-steelmanning.md: Complete analysis with steelmanned positions, tradeoff matrix, synthesis, and recommendations

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

04

需要参考平台分布和安装热度时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

能力 5

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

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

平台分布

Claude Code

26.95%
按下载量换算130

Gemini CLI

26.72%
按下载量换算129

Antigravity

19.35%
按下载量换算93

windsurf

13.29%
按下载量换算64

OpenCode

8.62%
按下载量换算42

github-copilot

3.89%
按下载量换算19

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

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

来源信息

继续浏览同类 Skills