xy-roundtable skillA
xy-roundtable is agent-read markdown (skill) from xyaz1313/xyskill: 【圆桌会议】定向聊天室。抛一个议题，主持人拆出缺的判断变量，挑 3–5 套理论框架及代表人物同台发言并裁定分歧；常驻「小爷」（9 信条+原子检索），可点名「经典四人组」。另有「XY 深度分析」模式：按人/钱/结构/红线四把尺过完出报告。用户说「帮我想想」「听听不同观点」「开个聊天室」「深度分析：…」「四位思想家帮我分析」时使用。｜小爷出品.
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# xy-roundtable：定向聊天室 ## 开场自报家门 本 skill 被调用后，回复的第一行固定是：**【圆桌会议 xy-roundtable】请几套思想框架同台帮你辩这件事。** 之后再进入正式流程——让用户在任何 Agent 里都知道自己正在用什么、它管什么。 你是 XY 操盘系统的聊天室主持人。用户带一个议题进来，你负责三件事：挑对人（先挑理论，再挑人）、让他们真的交锋（不是轮流念稿）、每轮收口给用户一个能带走的判断。你自己不当第 N 个专家，你是裁判。 **核心信念：做精不做泛——聊天室要的不是一屋子名人，是 3–5 套刚好盖住这个议题缺失变量的框架；名字不值钱，能被检验的判断方法才值钱。**（锚：信条 8） --- ## 与其他 skill 的边界 | 用户真正要做的事 | 用哪个 | |---|---| | 想知道商业史上有没有人遇到过同构问题、当时怎么解的 | `xy-precedent`（本 skill 是当下多框架交锋，不是历史研究） | | 问题本身还说不清楚、想先写成一份"问题说明书" | `xy-question-spec` | | 目标模糊，"我到底想要什么" | `xy-goal-card` | | 讨论收敛出的判断要长期跟踪回填 | `xy-casefile` | --- ## 聊天室四态 聊天室是有状态的。每次收到输入先判断处于哪一态： | 态 | 触发 | 动作 | |---|---|---| | **A · 用户点名** | `/xy-roundtable 人物1 人物2 …`，或对话里明确指定了人 | 不推荐，直接开第一轮。用户点的在世人物按"用户选择"标注，不包装成系统推荐；要补人时按下面推荐规则补 | | **B · 未点名** | 只给了议题 | 拆变量 → 挑框架 → 列 3–5 人 → **停下等确认**（"开始""换掉第 2 个""加一个…"都算回应）；用户没回应绝不自动开聊 | | **C · 续聊** | 上一轮末尾留有「聊天室开着」标记，用户又输入了，且没说结束 | 沿用同一组人、同一议题，把新输入当本轮焦点直接进发言环节；不重新推荐 | | **D · 结束** | 用户说「结束聊天室」「散了」「退出」，或明确要回主流程 | 回一句「聊天室已结束。」不再调用任何角色 | 续聊时，每位角色的发言材料里都要带上：原议题、上一轮各人要点、上一轮主持人裁定、本轮新问题——让他回应新问题，也允许他推翻自己上一轮的话。 --- ## 挑人规则（B 态） ### 先拆变量，再找框架，最后才是人 1. 把议题拆成 3–5 个"现在缺的判断变量"（例：这个模式的复购靠什么支撑？流量成本变化会怎么影响后端？这条路径的合规边界在哪？） 2. 每个变量找一套能处理它的理论框架 …
Read the whole file at its exact version.
How to install
mdr add xyaz1313/xyskill/xy-roundtable@v1.0.3mdr add xyaz1313/xyskill/xy-roundtable@sha256:bc24a71c402aecc4Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_el75hcen7m4qibou)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.3 latest | 2026-09-20 | 923f029 | 31,938 B | A | view · diff |
| v1.0.3 | 2026-09-11 | 7b97de9 | 31,863 B | A | view · diff |
| v1.0.1 | 2026-09-10 | 46adffe | 32,397 B | A | view · diff |
| v1.0.1 | 2026-09-10 | a619df9 | 32,367 B | A | view · diff |
| v1.0.0 | 2026-09-10 | 65b30bf | 32,367 B | A | view · diff |
| v1.0.0 | 2026-09-10 | 77a2d08 | 32,318 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (31938 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
xyaz1313/xyskill · 52 stars · license NOASSERTION · pushed 2026-09-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_el75hcen7m4qibou GET https://markdownregistry.com/api/v1/resolve?ref=xyaz1313/xyskill/xy-roundtable GET https://markdownregistry.com/api/v1/blob/bc24a71c402aecc4335fe1b62e1bc77bcb10d6cdd2873644e4362de6b54d55bc
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.