CtrlK
BlogDocsLog inGet started
Tessl Logo

multi-expert-analyzer

对任何领域的棘手问题进行深度思考分析,先识别问题所属领域并按需调度多位领域专家并行作答, 之后由事实核查员和红队做克制的事实审计与对抗性反驳,最后整合为面向小白的第一人称终稿。 适用:用户抛出一个跨领域/有深度的真实问题,希望听到多位专家的视角、看到观点的边界与证伪条件, 并得到一气呵成、通俗有据的最终文章。不适用:简单事实查询、纯情绪吐槽、不要求证据的随口一问。

64

Quality

76%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/skills_archive/multi-expert-analyzer_20260708/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

70%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-sequenced, validation-rich workflow with strong actionability, but it is padded with repeated coaching maxims and its progressive-disclosure intent is undercut by referenced agents/ files that are absent from the bundle.

Suggestions

Provide the missing agents/expert.md, agents/fact-checker.md, and agents/red-team.md files referenced in the workflow so the Read-then-Agent instructions actually resolve.

Remove the duplicate 关键原则 summary section and consolidate repeated maxims ("生命线", "AI 味", "重写不是缝合") to their first occurrence to tighten the body.

Move the lengthy Step 4.2 writing-style 硬规矩 into a reference file (e.g. references/writing-style.md) referenced from SKILL.md to reduce inline bulk.

DimensionReasoningScore

Conciseness

Mostly procedural and useful, but noticeably padded with repeated maxims ("生命线", "AI 味", "重写不是缝合" appear multiple times) and a terminal 关键原则 section that restates guidance already covered in the steps; could be tightened.

3 / 5

Actionability

Gives concrete, executable orchestration guidance — specific file-naming conventions (markdown/<slug>-expert-<n>.md), tool calls (Read agents/expert.md then Agent), and parallel-in-one-turn instructions — with the minor gap that the referenced agent prompt templates are not present in the bundle.

4 / 5

Workflow Clarity

A clearly sequenced Step 0→5 pipeline with explicit validation gates (experts must finish before fact-checker/red-team) and a Step 5 self-check checklist with a retry-until-passing feedback loop — a strong match for the 5-anchor.

5 / 5

Progressive Disclosure

Structure and signaling are decent (explicit agents/*.md paths listed), but those referenced files do not exist in the bundle and the ~280-line body inlines the detailed writing-style guidance that could live in a reference file.

3 / 5

Total

15

/

20

Passed

Description

83%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, third-person description that covers what, when, and when-not with concrete trigger guidance and a clearly distinct multi-expert pipeline niche. It could be nudged toward the top anchor with slightly more granular action phrasing and a few more colloquial trigger synonyms.

DimensionReasoningScore

Specificity

Lists several concrete pipeline actions — "识别问题所属领域", "调度多位领域专家并行作答", "事实核查员和红队做事实审计与对抗性反驳", "整合为面向小白的第一人称终稿" — but they sit at process-step granularity rather than the fine-grained action list of the 5-anchor.

4 / 5

Completeness

Explicitly answers what (the full analysis pipeline) and when (the 适用 trigger clause) with concrete trigger phrases, and adds a 不适用 clause for when not to use it — a clear match for the 5-anchor.

5 / 5

Trigger Term Quality

Good keyword coverage via the 适用 clause ("跨领域/有深度的真实问题", "多位专家的视角", "观点的边界与证伪条件") that users would naturally echo, though a few more colloquial synonyms are missing and no file-extension-style triggers apply.

4 / 5

Distinctiveness Conflict Risk

The multi-expert + fact-check + red-team + first-person synthesis combination is a distinct niche with carved-out 不适用 exclusions, but retains minor overlap risk with general deep-analysis/research skills.

4 / 5

Total

17

/

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: 2 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.