Agent skill

Multi Expert Analyzer

by digoal in digoal/blog

分析通用复杂问题,识别所涉及的领域范畴,召唤对应领域的专家角色(可多位)分别搜证与深度解析,最后将所有专家视角无缝合成为一篇面向小白、第一人称、图文并茂的 Markdown 文章,输出到项目 markdown/ 目录。触发条件:用户提出任何需要深度分析的问题,尤其是跨学科、跨领域的复杂问题。提到"帮我分析"、"深度解析"、"多角度分析"、"专家视角"、"帮我搞清楚XX"、"为什么XX"、"XX是…

GPL-2.0Auto-check passedDocuments & Office

Install Multi Expert Analyzer

skills CLI
$ npx skills add digoal/blog --skill multi-expert-analyzer -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install digoal/blog multi-expert-analyzer --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/digoal/blog.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/skills_for_claude_web/multi-expert-analyzer .claude/skills/multi-expert-analyzer && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
multi-expert-analyzer
GitHub stars
8.6k
Token cost
~850 tokens
SKILL.md length
156 words
Files
1
Skills in repo
98
Repo updated
First seen
Licence
GPL-2.0

At a glance

分析通用复杂问题,识别所涉及的领域范畴,召唤对应领域的专家角色(可多位)分别搜证与深度解析,最后将所有专家视角无缝合成为一篇面向小白、第一人称、图文并茂的 Markdown 文章,输出到项目 markdown/ 目录。触发条件:用户提出任何需要深度分析的问题,尤其是跨学科、跨领域的复杂问题。提到"帮我分析"、"深度解析"、"多角度分析"、"专家视角"、"帮我搞清楚XX"、"为什么XX"、"XX是…

  • Works in 4 steps: :领域识别与专家分配 → :每位专家的分析框架 → :合成文章规范 → …
  • Tasks that involve Markdown
  • SKILL.md covers 工作流总览, Step 1:领域识别与专家分配, Step 2:每位专家的分析框架 and Step 3:合成文章规范, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Multi Expert Analyzer is an agent skill from digoal/blog. 分析通用复杂问题,识别所涉及的领域范畴,召唤对应领域的专家角色(可多位)分别搜证与深度解析,最后将所有专家视角无缝合成为一篇面向小白、第一人称、图文并茂的 Markdown 文章,输出到项目 markdown/ 目录。触发条件:用户提出任何需要深度分析的问题,尤其是跨学科、跨领域的复杂问题。提到"帮我分析"、"深度解析"、"多角度分析"、"专家视角"、"帮我搞清楚XX"、"为什么XX"、"XX是怎么回事"、"用第一性原理分析"、"从多个维度看"等。即使用户只是提出一个开放性问题如"为什么XX会发生"或"如何看待XX现象",也应使用本 skill,尤其当问题涉及多个专业领域时。

Its SKILL.md is about 850 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Documents & Office, covering Markdown. The repository describes itself as: AI,Opensource,Database,Business,Finance,Minds. git clone --depth 1 https://github.com/digoal/blog. The licence is GPL-2.0.

When your agent uses it

  • Tasks that involve Markdown

Example prompts

  • “帮我搞清楚XX”
  • “XX是怎么回事”
  • “用第一性原理分析”
  • “/multi-expert-analyzer”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. :领域识别与专家分配
  2. :每位专家的分析框架
  3. :合成文章规范
  4. :文件输出规范

What it can do on your machine

Read from SKILL.md and the folder at commit 69fb793. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are mermaid and markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Multi Expert Analyzer loads about 850 tokens when it runs. Until then it costs about 78 tokens; SKILL.md has 156 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~78
When it runs · the whole SKILL.md, loaded when a task matches
~850

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from digoal/blog at commit 69fb793, republished under its GPL-2.0 licence (© digoal). 156 words, ~850 tokens.

Download SKILL.mdSave it as .claude/skills/multi-expert-analyzer/SKILL.md (or your agent's skills folder).
name
multi-expert-analyzer
description
分析通用复杂问题,识别所涉及的领域范畴,召唤对应领域的专家角色(可多位)分别搜证与深度解析,最后将所有专家视角无缝合成为一篇面向小白、第一人称、图文并茂的 Markdown 文章,输出到项目 markdown/ 目录。触发条件:用户提出任何需要深度分析的问题,尤其是跨学科、跨领域的复杂问题。提到"帮我分析"、"深度解析"、"多角度分析"、"专家视角"、"帮我搞清楚XX"、"为什么XX"、"XX是怎么回事"、"用第一性原理分析"、"从多个维度看"等。即使用户只是提出一个开放性问题如"为什么XX会发生"或"如何看待XX现象",也应使用本 skill,尤其当问题涉及多个专业领域时。

Multi-Expert Analyzer

一个将复杂问题拆解为多专家协作分析、最终合成通俗深度文章的 Skill。


工作流总览

问题输入
   ↓
Step 1: 领域识别 & 专家分配
   ↓
Step 2: 每位专家独立深度分析
   ↓
Step 3: 汇总合成 → 第一人称通俗文章
   ↓
输出 Markdown 文件到 markdown/ 目录

Step 1:领域识别与专家分配

拿到问题后,先停下来思考,不要急于作答:

  1. 识别核心领域:这道题属于哪些一级学科?(经济学、物理学、心理学、社会学、工程学、医学、法学、历史学、哲学……)
  2. 识别交叉领域:是否有边界地带需要跨学科视角?
  3. 分配专家角色:
    • 每个主要领域指定一位专家,给出具体的专家身份(如"行为经济学家"而非笼统的"经济学家")
    • 专家数量:1~4位为佳,避免冗余
    • 在文章内部用"站在 xxx 的角度"等措辞自然引入各专家视角,不要在章节名或正文中暴露"多专家合成"的元信息

示例专家分配:

问题类型可能的专家角色
为什么年轻人不愿生育行为经济学家、人口社会学家、发展心理学家
量子计算机为何难以商用量子物理学家、半导体工程师、信息论专家
某政策为何失败公共政策学者、博弈论经济学家、历史学家
如何评估一家公司财务分析师、行业分析师、战略管理学者

Step 2:每位专家的分析框架

每位专家必须按以下框架作答(内部思考过程,不直接呈现给读者):

2.1 复述并分析问题
  • 从本专业视角重新定义问题
  • 指出问题的核心变量与隐含假设
  • 识别问题的复杂性来源
2.2 第一性原理推导
  • 从该领域最基本的公理/规律出发
  • 明确前置条件与成立假设(写入正文,不要列表格,要文笔流畅)
  • 逐步推导至结论
2.3 权威数据与案例支撑
  • 引用权威研究、统计数据、历史案例
  • 必须标注来源(机构/研究者/年份)
  • 优先选择反直觉或颠覆性的证据,增加阅读价值
2.4 图表制作(必须包含)

选择最适合的图表类型:

Mermaid(适合流程、关系、时序):

mermaid
graph LR
    A[原因] --> B[机制] --> C[结果]

SVG(适合精美示意图、数据可视化):

  • 输出为独立 .svg 文件,存储到 markdown/ 目录
  • 在 Markdown 中用 ![说明](filename.svg) 引用
  • SVG 宽度建议 800px,使用清晰的字体和配色

ASCII Text(适合简单结构图、矩阵):

┌─────────┐    ┌─────────┐
│  输入    │───▶│  输出   │
└─────────┘    └─────────┘

每篇文章至少包含 2 个图表,图表须有标题和简短说明。

2.5 适用边界
  • 这个结论在什么条件下成立?
  • 什么情况下会失效或得出相反结论?
  • 不适用的典型场景举例
2.6 可证伪性设计
  • 如何证明:观测哪些指标/数据可以验证结论?
  • 如何证伪:出现什么现象说明结论错误?
  • 观测周期:多长时间/多大样本可以得出判断?

Step 3:合成文章规范

3.1 文章结构
标题(吸引人的问题式或悬念式标题)
├── 引言(钩子 + 问题背景,200字内)
├── [核心内容章节 1~N](融合各专家视角,自然过渡)
│   ├── 图表穿插其中
│   └── 数据/案例支撑
├── 边界与例外(何时结论不成立)
├── 如何验证这个结论(证明与证伪方法)
└── 结语(升华或留白)
3.2 写作要求

语气与人称:

  • 全文第一人称("我认为"、"在我看来"、"我们可以看到")
  • 专家视角用"站在 xxx 的角度看"、"从 xxx 的视角来分析"、"xxx 领域的研究告诉我们"等措辞自然引入
  • 绝对不要出现"专家A认为"、"综合以上分析"、"综合各方观点"等合成痕迹

行文风格:

  • 面向小白:假设读者零专业背景
  • 逻辑清晰:每个论点都有铺垫和落地
  • 生动有趣:类比、故事、反直觉的数据
  • 一气呵成:段落间有过渡句,不要割裂感
  • 前置条件和假设融入正文,不要列表格

严禁:

  • 章节名出现"第X专家"、"从X角度"、"综合分析"
  • 正文出现"以上是各专家的观点"类措辞
  • 把前提条件列成表格(要写进流畅的正文里)
3.3 长度参考
  • 引言:150~300字
  • 每个核心章节:500~1000字 + 至少1个图表
  • 边界与验证:300~500字
  • 结语:100~200字
  • 总长建议:2000~5000字(视问题复杂度调整)

Step 4:文件输出规范

目录结构
markdown/
├── [问题关键词]-analysis.md    ← 主文章
└── [图表名].svg               ← SVG 图表文件(如有)
文件命名
  • 主文章:用问题的核心关键词命名,英文小写加连字符,如 why-youth-dont-have-babies.md
  • SVG 文件:[topic]-[chart-type].svg,如 fertility-mechanism.svg
Markdown 文件头
markdown
# [吸引人的标题]

> [一句话摘要,概括核心结论]

*分析领域:经济学 · 社会学 · 心理学*  
*阅读时长:约 X 分钟*

---

质量自检清单

在输出前,对照以下清单检查:

  • 是否识别了所有相关领域并分配了专家?
  • 每个核心论点是否有数据/案例支撑?
  • 是否包含至少 2 个图表(Mermaid/SVG/ASCII)?
  • SVG 是否单独输出为文件并在 Markdown 中正确引用?
  • 第一性原理的前置条件是否融入正文(而非列表)?
  • 文章是否有清晰的适用边界说明?
  • 是否有具体可操作的证明/证伪方法?
  • 全文是否第一人称、无合成痕迹?
  • 语言是否通俗易懂、小白可读?
  • 文件是否已存储到 markdown/ 目录?

触发示例

以下都应触发本 Skill:

  • "为什么中国楼市会出现这种局面?"
  • "帮我深度分析一下 AI 替代人类工作这个问题"
  • "第一性原理解释为什么减肥这么难"
  • "多角度分析一下俄乌战争的走向"
  • "为什么有些公司越来越大却越来越慢?"
  • "用专家视角告诉我黑洞是什么"
  • "帮我搞清楚通货膨胀到底是怎么回事"

© digoal, GPL-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/skills_for_claude_web/multi-expert-analyzer of digoal/blog.

Open the folder on GitHubat commit 69fb793

Compare with similar skills

Multi Expert Analyzer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Multi Expert Analyzer compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Multi Expert Analyzer this skilldigoal/blog8.6k—~850Automated safety check: PassGPL-2.0
Markdown Article FormatterJimLiu/baoyu-skills26k7 repos~3.5kAutomated safety check: PassMIT
MarkitdownImCa0/just-laws78114 repos~3.2kAutomated safety check: NotesMIT
Obsidian MarkdownAtmosphere/atmosphere3.8k20 repos~1.3kAutomated safety check: PassApache-2.0
Gzh Designisjiamu/gzh-design-skill3.9k1 repos~2.2kAutomated safety check: PassAGPL-3.0
Crosspostingwasp-lang/wasp19k—~1.1kAutomated safety check: PassMIT

Similar skills

  • Markdown Article Formatter

    JimLiu/baoyu-skills

    Reformats plain text or Markdown articles with frontmatter, a title, a summary, headings, bold, lists and code blocks, and saves a separate formatted copy.

    26k GitHub starsUsed in 7 repos~3.5k tokens
    Documents & OfficeAuto-check passed
  • Markitdown

    ImCa0/just-laws

    Convert files and office documents to Markdown. An agent skill from ImCa0/just-laws.

    781 GitHub starsUsed in 14 repos~3.2k tokens
    Documents & OfficeAuto-check: notes
  • Obsidian Markdown

    Atmosphere/atmosphere

    Create and edit Obsidian Flavored Markdown with wikilinks, embeds, callouts, properties, and other Obsidian-specific syntax.

    3.8k GitHub starsUsed in 20 repos~1.3k tokens
    Documents & OfficeAuto-check passed
  • Gzh Design

    isjiamu/gzh-design-skill

    微信公众号文章排版引擎,将 Markdown 转换为可直接粘贴到公众号编辑器的 HTML。主题风格从 references/theme-index.md 注册的自定义主题库中选取,自动章节编号、关键词下划线标记、引言卡片、目录导航、代码块、图片/GIF、作者签名。支持 Markdown / Word(.docx) / PDF / 纯文本输入(非 Markdown…

    3.9k GitHub starsUsed in 1 repo~2.2k tokens
    Documents & OfficeAuto-check passed
  • Crossposting

    wasp-lang/wasp

    Crosspost Wasp blog articles (MDX) to DEV.to and Medium. An agent skill from wasp-lang/wasp.

    19k GitHub stars~1.1k tokensUpdated yesterday
    Documents & OfficeAuto-check passed
  • Review The Docs

    supabase/supabase

    Official

    Review Supabase docs changes locally in your supabase/supabase checkout — either an open PR (triage, classify, verify) or your own branch before opening a PR (local self-review).

    111k GitHub stars~4.6k tokensUpdated yesterday
    Documents & OfficeAuto-check passed

More from digoal/blog

All 98 skills in this repo
  • 三层审查模型,逐段逐句验证文章真伪、证据链与逻辑结构。Use when the user asks to fact-check, verify, audit, or evaluate the credibility of an article, essay, report, opinion piece, social-media post, or any written claim —…

    8.6k GitHub stars~939 tokensUpdated 11 days ago
    Auto-check passed
  • Find latent bugs in a local PostgreSQL source tree (RELxxSTABLE branch or HEAD) the way a core hacker does: build a heavily-poisoned debug instance (cassert + cache-discard + -O0/-ggdb3 + core…

    8.6k GitHub stars~4k tokensUpdated 11 days ago
    Auto-check passed
  • Digoal

    digoal/blog

    Portable digital employee distilled from digoal's personal blog for PostgreSQL, PolarDB, DuckDB, AI+database, vector/RAG, database operations, source-code reading, technical content creation…

    8.6k GitHub stars~2.2k tokensUpdated 11 days ago
    Auto-check passed
  • 从论文 PDF 文件或论文 PDF URL 生成通俗易懂、图文并茂、带批判性评估的中文 Markdown 解读,并保存到当前项目的 markdown 目录。Use when the user asks to interpret,精读,解读,summarize,explain,analyze, or write an article from an academic paper PDF…

    8.6k GitHub stars~1.5k tokensUpdated 11 days ago
    Auto-check passed
  • Analyze a product from documentation, websites, PDFs, articles, release notes, pricing pages, app listings, reviews, filings, or related links; save separate intermediate analyses from seven roles…

    8.6k GitHub stars~1.8k tokensUpdated 11 days ago
    Auto-check passed
  • Turn a blog post, article, notes, or any source material into a set of vertical poster images — one cover plus several coherent content slides that explain the core points.

    8.6k GitHub stars~1.4k tokensUpdated 11 days ago
    Auto-check passed

Questions about Multi Expert Analyzer

What does Multi Expert Analyzer do?

分析通用复杂问题,识别所涉及的领域范畴,召唤对应领域的专家角色(可多位)分别搜证与深度解析,最后将所有专家视角无缝合成为一篇面向小白、第一人称、图文并茂的 Markdown 文章,输出到项目 markdown/ 目录。触发条件:用户提出任何需要深度分析的问题,尤其是跨学科、跨领域的复杂问题。提到"帮我分析"、"深度解析"、"多角度分析"、"专家视角"、"帮我搞清楚XX"、"为什么XX"、"XX是…. Multi Expert Analyzer is an agent skill from digoal/blog.

When should I use Multi Expert Analyzer?

Multi Expert Analyzer fits situations like: tasks that involve Markdown.

How do I install Multi Expert Analyzer in Claude Code?

Run `npx skills add digoal/blog --skill multi-expert-analyzer -a claude-code`. Or copy the skill folder (skills/skills_for_claude_web/multi-expert-analyzer in digoal/blog) into .claude/skills/multi-expert-analyzer in your project. Claude Code loads it when a task matches its description.

How do I install Multi Expert Analyzer in Codex?

Run `npx skills add digoal/blog --skill multi-expert-analyzer -a codex`. Or copy the skill folder (skills/skills_for_claude_web/multi-expert-analyzer in digoal/blog) into .agents/skills/multi-expert-analyzer in your project. Codex loads it when a task matches its description.

Can I use Multi Expert Analyzer in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add digoal/blog --skill multi-expert-analyzer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/multi-expert-analyzer, .gemini/skills/multi-expert-analyzer, .github/skills/multi-expert-analyzer and .opencode/skills/multi-expert-analyzer in your project.

What does Multi Expert Analyzer need to run?

SKILL.md names no scripts, command-line tools or credentials: Multi Expert Analyzer is instructions for the agent only.

Does Multi Expert Analyzer access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Multi Expert Analyzer safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Multi Expert Analyzer use?

Multi Expert Analyzer is published under the GPL-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Multi Expert Analyzer use?

About 850 tokens (SKILL.md is roughly 3.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Multi Expert Analyzer?

Skills that share tags, products or a category with Multi Expert Analyzer: Markdown Article Formatter (JimLiu/baoyu-skills, 26k stars), Markitdown (ImCa0/just-laws, 781 stars), Obsidian Markdown (Atmosphere/atmosphere, 3.8k stars) and Gzh Design (isjiamu/gzh-design-skill, 3.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Multi Expert Analyzer?

digoal (a GitHub user) maintains it in digoal/blog, which has 8,587 GitHub stars. The repository holds 98 skills in this directory. The repository was last updated on September 28, 2026.

Source: digoal/blog on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.