CtrlK
BlogDocsLog inGet started
Tessl Logo

multi-expert-analyzer1

召唤多领域专家智能体,对任何棘手、跨学科、有争议或开放性的问题进行并行深度分析,再经过事实核查员与红队子智能体的克制审阅,最终重写为一篇面向小白、第一人称、图文并茂、有人味的深度长文。触发条件:用户提出任何值得深挖的复杂问题,尤其是跨领域、需要多方视角、需要权威数据支撑的问题;提到"帮我深度分析"、"多专家视角"、"专家怎么看"、"这个问题涉及哪些领域"、"帮我搞清楚 XX 到底是怎么回事"、"用第一性原理分析一下"、"这个观点站得住脚吗"、"帮我论证一下",或者只是抛出一个开放性问题如"为什么 XX 会发生"、"如何看待 XX 现象"、"XX 到底靠不靠谱"。即使用户没有明确要求"专家"或"深度分析"这几个字,只要问题本身跨越多个专业领域、需要审慎论证而非泛泛而谈,也应使用本 skill。本 skill 与仓库中其他类似名称的技能相互独立,请完全按照本文件的流程执行,不要套用其他技能的模板或输出结构。

68

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

73%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, actionable multi-stage workflow with strong validation and feedback loops, weakened mainly by verbosity from repeated emphasis and illustrative lists that could be tightened.

Suggestions

State the '克制' (restraint) principle once in stage 3 and reference it from later stages instead of restating it multiple times, to reduce repeated emphasis.

Trim the four-item example reflection-phrase list to one or two examples — the surrounding instruction ('自然地补一句反思') already conveys the intent.

Cut meta-commentary that restates a requirement's purpose (e.g., '这一条是为了让结论保持可检验'), since the requirement text itself communicates the intent.

DimensionReasoningScore

Conciseness

Mostly efficient with no basic-concept padding, but includes unnecessary explanation that could be tightened — repeated restatements of the '克制' principle across stages, a four-item example reflection-phrase list, and meta-commentary such as '这一条是为了让结论保持可检验'; this exceeds the 'minor instances' threshold of the 4 anchor, fitting 3.

3 / 5

Actionability

Provides concrete, specific guidance for an instruction-only skill — exact file paths ('markdown/expert-<领域简称>-draft.md', 'markdown/assets/'), an 8-point expert-draft checklist, and explicit rewrite rules; falls short of 5 only because no complete worked example of a finished output is given to cover the common cases.

4 / 5

Workflow Clarity

Four clearly sequenced phases (分诊 → 专家并行作答 → 审阅 → 重写终稿) with explicit validation steps (自我验证 in stage 2, 终稿完成后的自检 checklist in stage 4) and feedback loops ('就地修改后再检查一遍,直到自己挑不出明显毛病为止'), matching the 5 anchor; not a destructive/batch skill so the cap-3 rule does not apply.

5 / 5

Progressive Disclosure

Well-organized with a clear overview summary plus per-phase section headers and no nested references; scores 4 rather than 5 because the skill is self-contained with no one-level-deep references or content split into files, and a few sections (e.g., the example reflection-phrase list) are inline where trimming would tighten organization.

4 / 5

Total

16

/

20

Passed

Description

96%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, comprehensive description that clearly states a multi-action pipeline and provides abundant concrete trigger phrases, with only minor distinctiveness risk arising from acknowledged similarly-named sibling skills.

DimensionReasoningScore

Specificity

Lists multiple concrete pipeline actions — '召唤多领域专家智能体', '并行深度分析', '事实核查员与红队子智能体的克制审阅', '重写为一篇面向小白、第一人称、图文并茂、有人味的深度长文' — covering the workflow comprehensively, matching the 5 anchor rather than 4 (which would imply coverage gaps).

5 / 5

Completeness

Explicitly answers both 'what' (the four-stage analysis-to-rewrite pipeline) and 'when' via a dedicated '触发条件' clause with concrete trigger phrases, matching the 5 anchor; 4 would require the 'when' to be less explicit, but here it is concrete and explicit.

5 / 5

Trigger Term Quality

Includes a comprehensive set of natural user phrases — '帮我深度分析', '多专家视角', '专家怎么看', '用第一性原理分析一下', '这个观点站得住脚吗', '为什么 XX 会发生', '如何看待 XX 现象' — with synonyms and open-ended question variants, fitting the comprehensive-coverage anchor; 4 would require natural terms to be missing, which they are not.

5 / 5

Distinctiveness Conflict Risk

Has a clear niche and distinct triggers and even states '本 skill 与仓库中其他类似名称的技能相互独立', but the explicit acknowledgement of similarly-named skills (and the '1' suffix in the name) signals minor overlap risk with closely related skills, fitting the 4 anchor rather than the 5 'minimal conflict risk' anchor.

4 / 5

Total

19

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 missing

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

14

/

16

Passed

Repository
digoal/blog
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.