CtrlK
BlogDocsLog inGet started
Tessl Logo

council

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

64

Quality

78%

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

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.

The body is a well-structured, concise skill with concrete prompt and output templates and a clear sequenced workflow; the main gap is that synthesis-stage validation/feedback checkpoints are implied rather than explicit, and a little role-description redundancy could be trimmed.

Suggestions

Add an explicit verification checkpoint after step 5: confirm all three sub-agents returned before synthesizing, and re-spawn any that are missing or off-role.

Remove the redundant role-definition table in '四个角色定位' since each role is already introduced in the opening list, or merge the two to cut tokens.

DimensionReasoningScore

Conciseness

The body is largely lean, assumes Claude's competence, and uses compact tables and templates rather than padding; a few explanatory sentences (e.g., restating what each role does in the table after the intro list) could be trimmed.

4 / 5

Actionability

Provides a concrete, copy-paste-ready sub-agent prompt template and a concrete output markdown template, giving executable guidance; minor gaps are that role-specific emphasis is described rather than templated and there are no exact spawn mechanics.

4 / 5

Workflow Clarity

A clear six-step sequence with numbered stages and explicit anti-bias guardrails; the final step ('等所有subagent返回') and persistence rules add checkpoints, but explicit validation/feedback-loops for the synthesis step are implicit rather than spelled out.

4 / 5

Progressive Disclosure

A well-organized single-file skill with clear section headers (使用时机, 角色定位, 执行流程, 持久化, 反模式) and no bundle files needed; content is appropriately scoped to one level with no nested references.

5 / 5

Total

17

/

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.

The description is specific, distinguishes a clear niche, and covers both what and when, but the trigger guidance is implicit (适用于) rather than an explicit 'Use when...' clause and natural-term coverage could be slightly broader.

Suggestions

Replace the implicit '适用于...' with an explicit 'Use when...' clause listing concrete trigger situations (e.g., 'Use when facing ambiguous business judgments, multi-path tradeoffs, or go/no-go decisions').

Add a few more natural synonyms a user might say (e.g., '商业决策', '要不要做', '选哪条路') to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain (商业决策) and several concrete actions — 结构化辩论 across 商业模式、融资策略、业务方向 — giving good coverage of what it does, though the 'actions' are debate activities rather than discrete operations.

4 / 5

Completeness

Explicitly answers 'what' (召集四方视角...结构化辩论) and 'when' (适用于...), but the 'when' clause uses '适用于' rather than a clear 'Use when...' trigger and is somewhat brief.

4 / 5

Trigger Term Quality

Includes natural trigger phrases a user would say ('模糊的商业判断', '多路径权衡', 'go/no-go 决策'), with good keyword coverage, though synonyms and concrete business-context terms could be broader.

4 / 5

Distinctiveness Conflict Risk

Has a clear niche — structured multi-perspective debate on ambiguous business decisions — with distinct triggers unlikely to conflict with sibling IR/market-research skills.

5 / 5

Total

17

/

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.

Validation14 / 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
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.