CtrlK
BlogDocsLog inGet started
Tessl Logo

multi-expert-analyzer

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

71

Quality

87%

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

78%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 instruction skill with a clear multi-step workflow and a quality checklist. The main gaps are minor redundancy in the writing-requirements section and the lack of an explicit verify-and-fix feedback loop around the output checklist.

Suggestions

Convert the 质量自检清单 into an explicit feedback loop: run the checklist, fix any failing item, and re-check before finalizing the Markdown file.

Dedupe the 3.2 "严禁" list against the earlier "绝对不要"/写作要求 items to tighten the body.

Add a brief concrete method for generating the SVG files (e.g. a tool or template note) so the chart requirement is fully actionable.

DimensionReasoningScore

Conciseness

The body is mostly lean and assumes Claude's competence, but the 3.2 "严禁" list and the example expert table partly duplicate guidance already given in earlier sections, leaving minor trim opportunities.

4 / 5

Actionability

Concrete, specific guidance throughout — a per-expert analysis framework, chart-type specs with fenced examples, file naming conventions, and a file-header template — though as an instruction-only generation skill it stops short of executable code for SVG creation.

4 / 5

Workflow Clarity

A clear four-step sequence with a pipeline diagram and a quality self-check checklist, but the checklist is a one-pass review rather than an explicit validate→fix→retry feedback loop, so checkpoints are not fully explicit.

4 / 5

Progressive Disclosure

A single-file skill with no bundle files and no nested references, organized into clearly headed sections (Steps 1–4, checklist, examples); per the simple-skill exception, well-organized sections alone merit a top score.

5 / 5

Total

17

/

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 description that clearly states capabilities and provides rich, natural trigger terms covering both direct and open-ended invocations. Its only weakness is the breadth of the trigger surface, which raises minor conflict risk with generic analysis skills.

Suggestions

Narrow the trigger scope slightly (e.g. emphasize multi-domain/cross-disciplinary problems as the primary trigger) to reduce overlap with general explanation skills.

Optionally add an explicit "不要用于…" boundary clause so simple single-domain questions are less likely to invoke it.

DimensionReasoningScore

Specificity

Multiple concrete actions are named across the full pipeline — "识别所涉及的领域范畴", "召唤对应领域的专家角色…分别搜证与深度解析", "无缝合成为一篇…Markdown 文章", "输出到项目 markdown/ 目录" — giving comprehensive coverage.

5 / 5

Completeness

It explicitly answers both what (identify domains → summon experts → synthesize first-person Markdown article → output) and when (a 触发条件 clause with concrete trigger phrases plus an explicit "即使用户只是提出一个开放性问题…也应使用本 skill").

5 / 5

Trigger Term Quality

Extensive natural phrases users would actually say are listed — "帮我分析", "深度解析", "为什么XX", "XX是怎么回事", "帮我搞清楚XX", "第一性原理分析", "从多个维度看" — including synonyms and open-question variants.

5 / 5

Distinctiveness Conflict Risk

The multi-expert synthesis niche with first-person通俗 article output is reasonably distinct, but the trigger ("any deep-analysis question") is broad and could overlap with general analysis/explanation skills, so it is not maximal.

4 / 5

Total

19

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 missing

Warning

Total

15

/

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.