CtrlK
BlogDocsLog inGet started
Tessl Logo

expert-panel

多猫专家辩论团:在现有协作习惯上加一层轻量编排 + WHY 链标准 + 交付链。 Use when: 技术趋势判断、竞品分析、行业事件分析、需要多视角决策支持、operator说"帮我分析一下"。 Not for: 单猫能搞定的问题、代码实现、bug fix、日常聊天。 Output: 洞察卡片(rich block) + 语音总结 + 正式报告(DOCX/PDF)。

72

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

77%Weight 40%Scale 1-3

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

The body is a well-structured, highly actionable orchestration playbook with a clear sequenced workflow and explicit validation checkpoints. Its main weaknesses are redundancy between the Common Mistakes table and inline rules, and a monolithic structure with no progressive disclosure to supporting files.

Suggestions

Remove duplication between the 'Common Mistakes' table and the inline 禁止 rules in sections 2-3 (Evidence/Reasoning separation, Light-default, 不抹平分歧 are restated verbatim); keep one canonical statement and cross-reference it.

Merge '什么时候叠加其他 skill?' and '下一步' into a single skill-chaining table — both list deep-research/feat-lifecycle/collaborative-thinking paths and overlap.

Split the detailed 9-section 报告结构 and 应急降级/收敛沉淀检查 reference material into a referenced file (e.g. REPORT_STRUCTURE.md) so SKILL.md stays an overview, adding one-level-deep navigation.

DimensionReasoningScore

Conciseness

The body is dense and directive and assumes Claude's competence, but the 'Common Mistakes' table restates inline 禁止 items verbatim (Evidence/Reasoning separation, Light-default, 不抹平分歧) and '下一步' overlaps '什么时候叠加其他 skill?', so it could be tightened. Not score 3 because of this redundancy.

2 / 3

Actionability

Provides concrete executable guidance: dispatch payload allow/forbid lists, an exact WHY 链四格 field template, a role table, a 9-section report structure, and a degradation table — fully actionable for an instruction-only skill with no need for code.

3 / 3

Workflow Clarity

A clear 5-step sequence (Dispatch → Independent → Synthesis → Contributor Check → Delivery) with an explicit validation checkpoint (Contributor Check, '这步不能跳过') and feedback loops (收敛沉淀检查 有/没有, 凭证过期 handling), matching the anchor with explicit validation and error-recovery loops.

3 / 3

Progressive Disclosure

No bundle files exist and all content sits in one ~186-line monolithic file with no one-level-deep references; sections are well organized but detailed reference material (9-section 报告结构, 应急降级) is inline that could be split. Not score 3 because the 'one-level-deep references' anchor is not met.

2 / 3

Total

10

/

12

Passed

Description

100%Weight 40%Scale 1-3

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: it states concrete capabilities, provides an explicit Use when trigger (plus Not for boundaries), names concrete deliverables, and occupies a distinct niche. It uses third-person noun phrases with no first/second-person voice, so no specificity penalty applies.

DimensionReasoningScore

Specificity

Lists multiple concrete actions and outputs ('WHY 链标准', '交付链', '洞察卡片(rich block)', '语音总结', '正式报告(DOCX/PDF)'), matching the 'lists multiple specific concrete actions' anchor rather than the vague score-2 anchor.

3 / 3

Completeness

Explicitly answers both what (orchestration layer + WHY chain + delivery chain + Output artifacts) and when (explicit 'Use when:' clause), so it is not capped at 2 for missing trigger guidance.

3 / 3

Trigger Term Quality

Includes natural user phrases ('帮我分析一下', '竞品分析', '趋势判断') plus a dedicated triggers list, giving good coverage of terms a user would actually say; not merely technical jargon.

3 / 3

Distinctiveness Conflict Risk

A clearly niche multi-perspective debate orchestration concept with a 'Not for' carve-out (代码实现/bug fix/日常聊天); unlikely to fire for unrelated skills despite the somewhat generic '帮我分析一下'.

3 / 3

Total

12

/

12

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
zts212653/clowder-ai
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.