CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

council

召集四方视角对商业模式、融资策略、业务方向等关键决策进行结构化辩论。适用于模糊的商业判断、多路径权衡、go/no-go 决策。

Quality

80%

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 ./crews/main/skills/council/SKILL.md
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 highly actionable, well-structured process skill: the prompt and output templates are copy-paste ready and the workflow is clearly sequenced with anti-anchoring checkpoints. The main weakness is conciseness — role definitions are repeated three times across sections and the anti-pattern list overlaps the not-for-use table.

Suggestions

Consolidate the three presentations of the role definitions (intro bullets, the 角色定位 table, and the 角色侧重 list in step 4) into a single authoritative table, keeping per-role emphasis only where it changes the sub-agent prompt.

Trim overlap between 不适合使用的场景 and 反模式 by keeping the redirect table for scoping and reducing the anti-pattern list to genuinely new failure modes.

Add a brief checkpoint after step 4 to verify each sub-agent response follows the four-part format before synthesis, closing the workflow_clarity gap.

DimensionReasoningScore

Conciseness

The role definitions are presented three times (intro bullets, the "四个角色定位" table, and the "角色侧重" list in step 4), and "反模式" partially repeats "不适合使用的场景" — the content could be noticeably tightened, matching anchor 3. It is not anchor 2: most sections are functional and free of padding, and not anchor 4 because the triple repetition exceeds minor over-explanation.

3 / 5

Actionability

Fully executable guidance: a copy-paste sub-agent prompt template ("你是商业决策议会中的 [角色名]…不超过 300 字" with an exact four-part response format), an exact output template for the verdict, and concrete synthesis guardrails ("驳回外部观点时,必须说明理由", "最强的异见必须保留在报告中"). This matches the copy-paste-ready top anchor for an instruction-only skill; there are no meaningful gaps for the common case.

5 / 5

Workflow Clarity

A clear six-step sequence with explicit checkpoints: clarify first ("如果问题模糊,先问一个澄清性问题"), strategist commits before reading others, wait for all sub-agents (anti-pattern: "不等所有subagent返回结论后,就匆忙下出结论"), and guardrailed synthesis. It falls short of anchor 5 only because there is no explicit verification that sub-agent outputs conform to the requested format before synthesis; it is clearly above anchor 3 since checkpoints are present and explicit.

4 / 5

Progressive Disclosure

No bundle files exist, so the score reflects the single-file structure: well-organized sections (使用时机, 不适合使用的场景, 角色定位, 执行流程, 持久化规则, 多轮跟进, 反模式) with clear headers make navigation easy — matching anchor 4. It is not anchor 5 because the ~180-line body contains redundantly repeated role content that a tighter split or consolidation would address.

4 / 5

Total

16

/

20

Passed

Description

78%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 explicitly states what the skill does and when to use it, with a clear niche and mostly natural trigger terms. Its main weakness is specificity: it conveys one core action (convening a structured four-perspective debate) rather than enumerating several concrete capabilities.

Suggestions

Enumerate the concrete actions the skill performs (e.g., distill the decision question, spawn independent role-specific agents, synthesize a verdict with dissent preserved) instead of naming only the single action of structured debate.

Add natural trigger synonyms users would say, such as '复盘后的方向调整', '值不值得投入', or '先验证还是先融资', to strengthen trigger coverage.

DimensionReasoningScore

Specificity

Names the domain ("商业模式、融资策略、业务方向等关键决策") and one concrete action ("召集四方视角…进行结构化辩论"), which matches the anchor for naming a domain with 1-2 concrete actions. It does not list several distinct concrete actions, so it falls short of anchor 4.

3 / 5

Completeness

Explicitly answers both parts: the 'what' is "召集四方视角…进行结构化辩论" and the 'when' is a concrete applicability clause — "适用于模糊的商业判断、多路径权衡、go/no-go 决策". The when-clause names specific trigger scenarios rather than a generic statement, matching the top anchor; it is clearly above anchor 4's 'when could be more explicit'.

5 / 5

Trigger Term Quality

Good natural keyword coverage: "商业模式", "融资策略", "业务方向", "多路径权衡", and "go/no-go 决策" are phrases users would plausibly say. Missing common synonyms like "复盘", "方向调整", or "该不该/要不要" phrasing, so it does not reach comprehensive coverage (anchor 5).

4 / 5

Distinctiveness Conflict Risk

A clear niche (structured multi-perspective debate on ambiguous business decisions) with mostly distinct triggers, but there is minor overlap risk with generic decision-making or business-analysis skills. It does not fully lock out adjacent skills the way anchor 5 requires.

4 / 5

Total

16

/

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.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository

TeamWiseFlow/xiaobei

Path

crews/main/skills/council/SKILL.md

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.