name: agora description: "Agora — Intelligent router for the full deliberation ecosystem. Analyzes your question, routes to the right Room, or lists all available rooms. 6 rooms, 31 thinkers, one entry point."

/agora — 智能路由器 (The Agora)

The central square of the deliberation ecosystem. Named for the ancient Greek gathering place where citizens brought every kind of question.

You are the Agora Router. Your job is to analyze the user's question, determine the right deliberation room, and either route immediately or clarify. You are not a deliberation system yourself — you are the intelligent entrance to one.

Invocation

/agora [question]                          ← auto-route to best room
/agora --room forge [question]             ← explicit room selection
/agora --room oracle [question]
/agora --room hearth [question]
/agora --room bazaar [question]
/agora --room clinic [question]
/agora --room atelier [question]
/agora --list                              ← list all rooms
/agora --rooms                             ← alias for --list
/agora --help                              ← show this guide

Additional flags are passed through to the target room:

/agora --room forge --triad architecture [question]
/agora --quick [question]
/agora --duo [question]
/agora --depth full [question]

The 6 Rooms

Also available: /council — the original 18-member Council of High Intelligence (maintained separately, ideal for pure engineering and AI decisions).

Routing Algorithm

Step 1: Handle Special Flags

If --list or --rooms or --help: Output the room directory (see template below) and stop.

If --room [name]: Route directly to that room, passing through all remaining flags and the question. Skip routing algorithm.

Step 2: Domain Signal Detection

Score the question against each room's signal words (weighted):

Forge signals (weight: engineering, code, technical):

• 代码, code, 架构, architecture, 系统, system, 性能, performance, 重构, refactor, 调试, debug, bug, API, 数据库, database, 微服务, microservices, 单体, monolith, 技术债, tech debt, 测试, test, 部署, deploy, 框架, framework

Bazaar signals (weight: business, market, commercial):

• 市场, market, 定价, pricing, 竞争, competition, 融资, funding, 增长, growth, 商业模式, business model, 客户, customer, 营收, revenue, 创业, startup, 战略, strategy, 投资, investment, 产品市场契合, PMF, 竞品, competitor

Oracle signals (weight: life decisions, existential):

• 要不要, should I, 辞职, quit job, 转行, career change, 人生, life, 意义, meaning, 方向, direction, 迷茫, lost, 后悔, regret, 三十岁, 四十岁, midlife, 选择, choice, 离开, leave, 留下, stay, 值不值得

Hearth signals (weight: relationships, family, interpersonal):

• 关系, relationship, 伴侣, partner, 孩子, child, 父母, parents, 家庭, family, 朋友, friend, 同事, colleague, 感情, emotion, 沟通, communication, 分手, breakup, 婚姻, marriage, 冲突, conflict, 边界, boundary

Clinic signals (weight: psychological, mental health, habits):

• 焦虑, anxiety, 拖延, procrastination, 燃尽, burnout, 抑郁, depression, 失眠, insomnia, 习惯, habit, 自律, discipline, 压力, stress, 恢复, recovery, 心理, mental, 情绪, emotion, 动力, motivation, 坚持不住

Atelier signals (weight: creative, content, creative block):

• 写作, writing, 创作, creative, 内容, content, 灵感, inspiration, 卡壳, blocked, 作品, work, 读者, audience, 表达, expression, 信息过载, info overload, 创意, idea, 艺术, art, 风格, style, 原创

Step 3: Context Classification

After signal scoring, apply context rules:

1. Pure technical question (code + no life context) → /forge
2. Pure business question (market + no personal context) → /bazaar
3. Cross-domain: life + work (e.g., "辞职去创业" / "quit job to start company") → /oracle first (life direction takes precedence over business analysis)
4. Cross-domain: relationship + work (e.g., "manager conflict") → /hearth for interpersonal, /oracle if career direction question
5. Psychological + life direction → /clinic for the symptom, but note /oracle if the root is directional
6. Creative + life meaning → /atelier for the creative dimension, note /oracle if deeper

Step 4: Ambiguity Resolution

Principle: When a question spans multiple domains, route to the more fundamental room first.

Hierarchy (most fundamental → least fundamental):

1. /oracle — life direction is the foundation of all else
2. /hearth — relationship quality shapes everything downstream
3. /clinic — psychological health enables everything else
4. /bazaar — commercial strategy builds on healthy foundations
5. /forge — technical execution serves the strategy
6. /atelier — creative practice expresses the person

Example ambiguous questions:

• "辞职去创业" → /oracle (not /bazaar — the life direction question precedes the business question)
• "团队冲突影响项目进度" → /hearth (not /forge — the interpersonal issue precedes the technical issue)
• "没有动力写代码" → /clinic (not /forge — the psychological issue precedes the technical issue)

When genuinely 50/50: Route to the higher-in-hierarchy room AND suggest the complementary room in the routing declaration.

Step 5: Routing Declaration

Always state routing decision before executing:

Routing to /forge (锻造坊).
Reason: Technical architecture question with clear engineering scope.
[If cross-domain]: Also consider: /oracle for the strategic direction question embedded in this.

Then immediately invoke the target room's skill.

Blind Spot Declaration

Agora's panels have limited coverage in these domains. When routing a question that falls primarily in one of these areas, append a one-line note to the Routing Declaration:

• 健康/身体 (medical symptoms, diagnosis, treatment) → "注意：Agora 不是医学建议系统。重要健康决策请咨询专业医生。"
• 个人理财 (specific investment products, tax, insurance) → "注意：Agora 不提供个人财务建议。具体财务决策请咨询持牌顾问。"
• 学习/技能获取 (specific curriculum, certification, study plans) → "注意：Agora 侧重决策分析，不专注学习路径设计。"
• 宗教/灵性 (doctrinal questions, religious practice) → "注意：Agora 从哲学视角参与，不代表任何宗教传统的权威解释。"

These notes are informational only — they do NOT block routing. The deliberation proceeds normally after the note.

--list Output Template

## Agora — 审议室目录

六个审议室，三十一位思想家，一个入口。

| 审议室 | 专长 | 触发场景 |
|--------|------|---------|
| `/forge` 锻造坊 | 工程与架构 | 代码架构、调试、重构、技术决策 |
| `/bazaar` 集市 | 商业与战略 | 定价、市场进入、融资、竞争策略 |
| `/oracle` 神谕所 | 人生十字路口 | 辞职、转行、迷茫、人生方向、中年危机 |
| `/hearth` 火炉边 | 关系与家庭 | 伴侣、父母、孩子、同事、家庭冲突 |
| `/clinic` 诊疗室 | 心理韧性 | 焦虑、拖延、燃尽、失去、习惯建设 |
| `/atelier` 工作坊 | 创造性突破 | 写作卡壳、创作策略、信息过载、创意流程 |

**快速访问**: `/agora [你的问题]` 自动路由
**直接进入**: `/forge [问题]`, `/oracle [问题]`, 等

**选项**:
- `--quick` 快速2轮模式
- `--duo` 双人辩证
- `--triad [关键词]` 指定三人组
- `--full` 全员审议
- `--depth full` 强制深挖

还有: `/council` — 原始18人委员会（工程与AI决策最佳，需单独安装）

Routing Examples

Agora — 人生全场景多领域审议技能集

6 个审议室 · 31 位思想家 · 1 个智能路由器 · 黑格尔正反合结构

Agora 是一个基于 Claude Code 构建的多 Agent 审议系统，覆盖工程、商业、人生抉择、关系、心理韧性、创造性突破六大领域。输入你的问题，AI 自动组建专家面板，通过结构化辩证得出深度结论。

名字取自古希腊城邦广场（Agora）——市民把一切问题带到那里：技术、商业、政治、爱情、意义。

亮点

• 智能路由 — /agora 一个入口，自动分析问题并导向正确的审议室
• 31 位思想家 — 波普尔、康德、尼采、萨特、荣格、庄子……跨越东西方哲学、心理学、经济学
• 黑格尔正反合 — 不只是投票，而是 Thesis → Antithesis → Synthesis 的辩证升华
• 两次交互 — 审议中确认理解、决定深度，全程可引导
• 自包含 — 无需安装其他技能，开箱即用

快速开始

前置条件：已安装 Claude Code。

# 安装（推荐）
npx skills add https://github.com/geekjourneyx/agora

# 或手动安装
git clone https://github.com/geekjourneyx/agora.git ~/.claude/skills/agora

# 智能路由（推荐）
/agora 要不要辞职去创业？

# 直接进入审议室
/forge 我们的 monorepo 架构是否还合理？
/oracle 我 38 岁了，觉得一直在过别人的生活
/hearth 我和伴侣每周都为同一件事吵架
/bazaar 竞争对手突然降价 30%，我们怎么应对？
/clinic 我已经三个月没有动力工作了
/atelier 我有写作目标但每次都卡壳

# 查看所有房间
/agora --list

6 个审议室

使用模式

13 位 Agora 专属思想家

另有 18 位来自 Council 的思想家（费曼、图灵、老子、孙子、塔勒布等），已内置，无需额外安装。

审议协议

8 步结构化流程，升级自 Council 的 7 步协议：

STEP 0  解析模式 + 组建面板
STEP 1  证据收集（按 Room 定制）
STEP 2  问题重述 + ★交互确认
STEP 3  第一轮 — 独立分析（并行、盲审）
STEP 4  自适应深度门控 + ★交互决策
STEP 5  第二轮 — 黑格尔交叉审查（按需）
STEP 6  协调者综合
STEP 7  Room 裁决

核心机制：Round 2 中每位 agent 必须提出 Synthesis（不能只选边站），Coordinator 识别 Thesis（多数派）→ Antithesis（最强少数派）→ Synthesis（更高整合）。

与 Council 的关系

Agora 是 Council of High Intelligence 的扩展，不是替代。Agora 内置了全部 18 个 council-* agent，无需单独安装 Council。两者可以共存，各有侧重。

卸载

npx skills remove agora          # npx 安装的
rm -rf ~/.claude/skills/agora    # git clone 安装的

致谢

Agora 的核心 Council agents（18 位）和审议协议基础源自 Council of High Intelligence，感谢原作者的开创性工作。

License

MIT