CtrlK
BlogDocsLog inGet started
Tessl Logo

chat-x-custom-component

帮助开发者创建 @blueking/chat-x 自定义 message 组件。当用户需要开发自定义消息类型时使用。

59

Quality

68%

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 ./bcs-services/bcs-project-manager/.cursor/skills/chat-x-custom-component/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%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 compact overview with concrete type-extension code and a sensible reference layout, but three of four workflow steps lack executable guidance and validation is only implicitly signaled. A duplicated, inconsistent resources section is the clearest defect.

Suggestions

Remove the duplicated '📦 可用资源' section and keep a single canonical reference list (the 7-file superset) to fix the organization gap and wasted tokens.

Add a brief concrete snippet or inline reference for steps 2-4 (创建组件, 集成到 MessageContainer), so the workflow is actionable end-to-end rather than only at the type-extension step.

Replace the bare '测试' step with an explicit validation checkpoint (e.g., a command or checklist) and delete the dangling 'IF-THEN 规则' note that references rules not present in SKILL.md.

DimensionReasoningScore

Conciseness

The body is lean with minimal over-explanation and tight code snippets, but the duplicated '📦 可用资源' section (5 references then a 7-reference superset) wastes tokens, keeping it just below a 5.

4 / 5

Actionability

Concrete executable TypeScript is given for type extension, but workflow steps 2-4 ('创建组件', '集成到 MessageContainer', '测试') have no concrete code or commands in the body, matching 'some concrete guidance but incomplete'.

3 / 5

Workflow Clarity

A clear 4-step sequence is present (声明类型扩展 → 创建组件 → 集成到 MessageContainer → 测试), but the '测试' checkpoint is only a label with no validation detail or feedback loop, fitting 'steps listed but checkpoints missing or implicit'.

3 / 5

Progressive Disclosure

Structure is sound: an overview body pointing to one-level-deep skill:// references that are clearly listed, with content appropriately split out; the duplicated resource list and the dangling 'IF-THEN 规则' reference are minor organization gaps rather than structural failures.

4 / 5

Total

14

/

20

Passed

Description

75%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 strong: it explicitly covers both what the skill does and when to use it, and is tied to a specific library niche that minimizes conflict risk. Its main limitation is listing only one action and limited keyword variation.

Suggestions

Add 1-2 more concrete actions (e.g., 'register, render, and test custom message components') to lift specificity from 3 to 4.

Include common synonym phrasings or file/extension triggers users might say (e.g., '自定义消息卡片', 'custom message slot') to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Names a concrete domain ('@blueking/chat-x 自定义 message 组件') and one concrete action ('创建'), but lists no additional actions, matching the 'names domain and 1-2 concrete actions' anchor rather than the multi-action 4.

3 / 5

Completeness

It explicitly states both what ('帮助开发者创建 @blueking/chat-x 自定义 message 组件') and when ('当用户需要开发自定义消息类型时使用') with a concrete trigger phrase, mirroring the 5-anchor example structure.

5 / 5

Trigger Term Quality

Natural phrases like '当用户需要开发自定义消息类型时使用' and '自定义 message 组件' are present, but coverage is limited to a single phrasing without synonym or extension variants, fitting 'some relevant keywords but missing common variations'.

3 / 5

Distinctiveness Conflict Risk

Tied to a specific named library and a narrow component type, giving a clear niche with distinct triggers and minimal conflict risk with other skills.

5 / 5

Total

16

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
TencentBlueKing/bk-bcs
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.