CtrlK
BlogDocsLog inGet started
Tessl Logo

expert-panel

多猫专家辩论团:在现有协作习惯上加一层轻量编排 + WHY 链标准 + 交付链。 Use when: 用户明确要求 expert panel、专家辩论、多猫分析或三猫讨论。 Not for: 普通“帮我分析一下”、单猫能搞定的问题、代码实现、bug fix、日常聊天。 Output: 洞察卡片(rich block) + 语音总结 + 正式报告(DOCX/PDF)。

68

Quality

83%

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

75%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 dense, well-structured orchestration skill that delivers concrete templates (WHY-chain four cells, dispatch payload rules, 9-section report) and an explicit sequenced workflow with a Contributor Check validation step plus degradation fallbacks. It respects token budget well and is highly actionable for an instruction-only skill; the main improvement space is splitting long reference material (report structure, delivery checklist) into a separate reference file.

DimensionReasoningScore

Conciseness

Mostly lean and operational — tables for roles, dispatch payloads, mistakes, and degradation are token-efficient and avoid explaining concepts Claude already knows; a few sections (e.g., repeated restatements of the three-things framing and the 'WHY 链' rationale) could be tightened, but overall it earns its tokens.

4 / 5

Actionability

Provides concrete, executable guidance: exact dispatch payload allow/deny lists, the four-cell WHY-chain output template, a 9-section report structure, and a copy-ready 5-step execution skeleton; it is instruction-only rather than code, but the guidance is specific and actionable with minor gaps (no exact commands for delivery tools).

4 / 5

Workflow Clarity

Clear 5-step sequence (Dispatch → Independent → Synthesis → Contributor Check → Delivery) with an explicit validation checkpoint (Contributor Check) and a convergence-persistence checklist; it explicitly frames itself as a natural rhythm rather than rigid phases, and includes degradation fallbacks — minor gap is that the batch/destructive-ish delivery lacks a formal validate-fix-retry loop, but the Common Mistakes and 应急降级 tables compensate.

4 / 5

Progressive Disclosure

Well-organized into clearly headed sections with tables and templates instead of a monolithic wall; no bundle files are referenced (references/scripts/assets directories absent), so all content is inline in SKILL.md, which is appropriate for this orchestration-skill size — a small amount of the report-structure and delivery detail could arguably be split out, but the one-level structure is navigable.

4 / 5

Total

16

/

20

Passed

Description

91%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, well-structured description that explicitly answers what, when, and when-not with rich bilingual trigger coverage and concrete deliverables. Third-person imperative voice is maintained; the only minor weakness is that the 'what' actions lean slightly toward orchestration framing rather than enumerated concrete operations.

DimensionReasoningScore

Specificity

Names the domain (multi-cat expert debate orchestration) and several concrete actions/deliverables: 角色分配, WHY 链标准, 交付链, and three concrete output formats (洞察卡片/语音总结/正式报告), but the orchestration actions are framed abstractly rather than as fully enumerated concrete operations.

4 / 5

Completeness

Explicitly answers both 'what' (编排层+角色分配+WHY链+交付链) and 'when' ('Use when: 用户明确要求 expert panel、专家辩论、多猫分析或三猫讨论') plus 'Not for' boundary, with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural trigger coverage including synonyms users would say ('专家辩论', 'expert panel', '多猫分析', '三猫讨论', '技术参谋', '竞品分析') with both Chinese and English variants and explicit negative triggers.

5 / 5

Distinctiveness Conflict Risk

Clear niche (explicit-call high-cost multi-cat debate orchestration) with explicit 'Not for' guardrails against triggering on ordinary analysis; minor residual overlap with collaborative-thinking/deep-research which it intentionally composes with, but the explicit-invocation boundary keeps conflict risk low.

4 / 5

Total

18

/

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

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.