CtrlK
BlogDocsLog inGet started
Tessl Logo

chat-x-contribute

帮助开发者上手 @blueking/chat-x 组件库开发。当用户需要了解 chat-x、开发新组件时使用。

55

Quality

61%

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-contribute/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 concise, mostly actionable overview that points outward to reference files, but it is undermined by missing referenced files, a duplicated resource block, and no validation checkpoint in the new-component workflow.

Suggestions

Create the referenced bundle files (component-api.md, development-workflow.md, QA.md, style-guide.md, type-definitions.md) so the signaled references resolve.

Remove the duplicated '📦 可用资源' section so the reference list appears exactly once.

Add a validation step to the new-component workflow (e.g. '运行 pnpm --filter @blueking/chat-x build 或 typecheck 验证通过后再写文档').

DimensionReasoningScore

Conciseness

The body is lean — terse command blocks, a compact project-structure tree, and short best-practice bullets with no padding or explanation of concepts Claude already knows — matching the 'efficient; minor instances that could be trimmed' anchor; the duplicated resource list is the main blemish keeping it from 5.

4 / 5

Actionability

Provides concrete executable commands (pnpm install/dev/build), exact file paths, and a numbered new-component procedure, matching the 'mostly executable guidance with minor gaps' anchor; the component-creation steps are skeletal (e.g. '添加类型' without specifics) so it does not reach 5.

4 / 5

Workflow Clarity

The '开发新组件' section gives a numbered sequence (create file, export, add types, write docs) but has no validation checkpoint (e.g. typecheck/build before documenting), matching the 'steps listed but checkpoints missing or implicit' anchor.

3 / 5

Progressive Disclosure

The body signals one-level-deep references via skill:// URIs and an IF-THEN load rule, but the referenced files (references/*.md) do not exist in the bundle and the entire resource list is duplicated verbatim, matching the 'minimal structure; references buried/broken' anchor rather than a clean 3-4.

2 / 5

Total

13

/

20

Passed

Description

62%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 clearly identifies the domain and provides explicit trigger conditions, scoring solidly across most dimensions. It could be strengthened with more concrete capability actions and broader trigger-term variations.

Suggestions

Enumerate more concrete actions the skill covers (e.g. '新增组件、编写类型、编写文档、调试流式渲染') to raise specificity.

Add natural trigger-term variations and synonyms a user might say, such as '组件', 'UI 组件', '流式渲染', 'bkui-vue'.

Tighten the 'when' clause with multiple explicit trigger phrases (e.g. '当用户提到 chat-x、需要新增/修改组件、或排查组件库问题时使用').

DimensionReasoningScore

Specificity

Names the domain (@blueking/chat-x component library) and 1-2 concrete actions ('了解 chat-x', '开发新组件'), matching the 'domain plus 1-2 concrete actions' anchor; it does not enumerate a comprehensive list of actions so it stays at 3 rather than 4.

3 / 5

Completeness

Both 'what' (上手 @blueking/chat-x 组件库开发) and 'when' (当用户需要了解 chat-x、开发新组件时使用) are present and explicit, but the trigger could be more specific/comprehensive, matching the 'has both what and when; when could be more explicit' anchor rather than 5.

4 / 5

Trigger Term Quality

Includes natural phrases a user would say ('需要了解 chat-x', '开发新组件') but lacks synonyms, common variations, or related terms (e.g. '组件', 'UI', file extensions), matching the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

Naming the specific package @blueking/chat-x gives it a clear niche with minimal conflict risk against unrelated skills, though it could still slightly overlap with general Vue/component-dev skills, matching the 'mostly distinct; minor overlap risk' anchor.

4 / 5

Total

14

/

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.