CtrlK
BlogDocsLog inGet started
Tessl Logo

council

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

63

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 ./crews/main/skills/council/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%

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

The skill is highly actionable with concrete templates and a clear, well-guarded workflow, and avoids explaining concepts Claude already knows. Its main weaknesses are mild redundancy in role definitions and the absence of any progressive-disclosure structure despite the file's length.

Suggestions

Remove the duplicate role definitions: keep either the intro bullet list or the '四个角色定位' table, not both, to tighten conciseness.

Consider extracting the prompt template and output-format template into a referenced file (e.g. references/templates.md) and signaling it from the body, which would both reduce length and add one-level-deep progressive disclosure.

DimensionReasoningScore

Conciseness

The body is mostly operational and free of generic concept explanations, but the four roles are defined twice — as a bullet list in the intro (lines 13–16) and again in the '四个角色定位' table (lines 55–60) — so not every token earns its place.

2 / 3

Actionability

Provides a copy-paste-ready sub-agent prompt template, a concrete output-format template, and specific per-role guidance, giving fully executable, specific direction.

3 / 3

Workflow Clarity

The six-step execution flow is clearly sequenced with explicit checkpoints and guardrails (clarify-before-convene, write-stance-first, 前提核查, anti-bias rules that treat dual opposition as a real signal), functioning as feedback loops.

3 / 3

Progressive Disclosure

Sections are well-organized, but the skill is a single monolithic ~190-line file with no external references; since it exceeds 50 lines it does not qualify for the simple-skill auto-3 and has no file-based disclosure to reward.

2 / 3

Total

10

/

12

Passed

Description

75%

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 clearly communicates a distinct niche and an explicit use-when trigger, but is somewhat general in the actions it names and uses fairly formal trigger language. Strong on completeness and distinctiveness, weaker on trigger-term naturalness.

Suggestions

Add a few more concrete, user-natural trigger phrasings (e.g. '该不该做', '选哪条路', '要不要融资') alongside 'go/no-go' to broaden trigger coverage.

List one or two additional concrete actions beyond 'structured debate' (e.g. '权衡多路径', '诊断商业模式矛盾') to raise specificity.

DimensionReasoningScore

Specificity

Names the domain (商业模式、融资策略、业务方向) and a primary action (结构化辩论), but does not list multiple distinct concrete actions, matching the 'names domain and some actions' anchor rather than the multi-action level.

2 / 3

Completeness

Explicitly states what it does ('召集四方视角…进行结构化辩论') and when to use it via the 适用于 clause ('适用于模糊的商业判断、多路径权衡、go/no-go 决策'), clearly answering both what and when.

3 / 3

Trigger Term Quality

Includes natural terms like 'go/no-go 决策', '融资策略', and '商业模式', but the phrasing leans formal/abstract and omits common variations a user might actually say, so it sits at 'some relevant keywords but missing common variations'.

2 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (structured multi-perspective business-decision debate) and the body explicitly routes sibling tasks to other skills, making wrong-skill triggering unlikely.

3 / 3

Total

10

/

12

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.