Token导航 LogoToken导航TokenDH.com
开发需要联网github未标认证来源可访问许可证需确认审计提醒

agoraagora 搜索

Agent Skill

agora 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

1,829

周安装

74

GitHub Stars

146

下载量

574
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/geekjourneyx/agora --skill agora

简介

agora 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息。

  • 适合在 Codex、Claude、Cursor、Gemini CLI 中围绕仓库状态或协作事项进行整理。
  • 通过命令行调用,可结合来源仓库和原始 README 核验具体用法。
  • 安装前需确认权限范围、维护状态及是否触发联网或文件操作。
  • agora 属于开发类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

/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

Room中文SpecialtyKey Panel
/forge锻造坊Engineering & ArchitectureFeynman, Ada, Torvalds, Popper, Occam, Nietzsche, Wittgenstein
/bazaar集市Business & StrategySchumpeter, Munger, Sun Tzu, Machiavelli, Taleb, Kahneman
/oracle神谕所Life Crossroads & ExistentialSartre, Aurelius, Jung, Frankl, Nietzsche, Kahneman
/hearth火炉边Relationships & FamilyFromm, Adler, Zhuangzi, Kant, Aurelius, Watts
/clinic诊疗室Psychological ResilienceSkinner, Frankl, Aurelius, Kahneman, Zhuangzi, Jung
/atelier工作坊Creative BreakthroughSocrates, Lao Tzu, Watts, Nietzsche, Occam, Feynman, Wittgenstein

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

QuestionRouteReason
"代码架构太烂了"/forgeClear technical scope
"要不要辞职"/oracleLife direction question
"孩子不听话"/hearthParent-child relationship
"定价策略怎么定"/bazaarBusiness decision
"最近很焦虑"/clinicPsychological challenge
"写作卡壳了"/atelierCreative block
"辞职去创业要不要"/oracle → suggest /bazaarLife direction precedes business analysis
"团队沟通影响代码质量"/hearth → suggest /forgeInterpersonal precedes technical
"没有动力写代码"/clinic → suggest /forgePsychological precedes technical
"代码写完了但不知道要不要开源"/bazaar → suggest /oracleBusiness question with personal values dimension

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

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

平台分布

Codex

31.48%
按下载量换算181

Claude

31.43%
按下载量换算180

Cursor

19.62%
按下载量换算113

Gemini CLI

9.58%
按下载量换算55

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

需要联网

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

安装前确认

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

来源信息

继续浏览同类 Skills