chat-x-contribute

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

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

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

Quality

Content

53%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 compact, reasonably actionable development guide with real commands and a clear component workflow. It is undermined by a verbatim-duplicated resources section, dangling references to nonexistent files, and a note pointing to IF-THEN rules that are absent.

Suggestions

Delete the duplicated '📦 可用资源' section (keep one copy) and remove or fix the note about IF-THEN rules, since no such rules exist in the body.

Create the referenced files under references/ (component-api.md, development-workflow.md, QA.md, style-guide.md, type-definitions.md) or remove the skill:// links so no reference is broken.

Add a validation checkpoint to the new-component workflow, e.g., '5. Run pnpm --filter @blueking/chat-x build to verify the component compiles and exports correctly'.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean (concise project overview, commands, structure), but the '📦 可用资源' section is duplicated verbatim (lines 50–55 and 60–66), wasting roughly a quarter of the document on identical content, plus a trailing orphan note.	3 / 5
Actionability	Provides copy-paste-ready commands ('pnpm --filter @blueking/chat-x dev/build'), concrete paths ('src/components/new-component/'), and a numbered 4-step component workflow. Minor gap: no example component snippet to anchor the steps.	4 / 5
Workflow Clarity	The '开发新组件' sequence is listed but has no validation or verification checkpoints (e.g., 'run build/dev to confirm the component renders'), and the closing note instructs following 'IF-THEN 规则' that do not exist anywhere in the file.	3 / 5
Progressive Disclosure	The body lists five 'skill://chat-x-contribute/references/*.md' paths, but no references/ directory (or any bundle files) exists, so every reference is broken; the resource list is also duplicated rather than well-signaled, leaving navigation unusable.	2 / 5
	Total	12 / 20 Passed

Description

73%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 concise, third-person description that clearly states both what it does and when to use it, scoped tightly to the @blueking/chat-x library. Its main weakness is that the capability statement remains at the 'get started' level rather than listing concrete actions.

Dimension	Reasoning	Score
Specificity	It names the domain ('@blueking/chat-x 组件库开发') and one broad action ('帮助开发者上手' — onboarding), but does not enumerate concrete capabilities (e.g., adding components, writing docs, following the release workflow). Fits anchor 3 rather than 4, which expects several specific actions; not 2 because the domain is precisely named with a real action.	3 / 5
Completeness	Both parts are explicit: what ('帮助开发者上手 @blueking/chat-x 组件库开发') and when ('当用户需要了解 chat-x、开发新组件时使用'). Not 5 because the 'what' stays at the onboarding level without concrete capability statements; comfortably above anchor 3 since the trigger clause is explicit rather than implied.	4 / 5
Trigger Term Quality	Natural user phrasings are present: '当用户需要了解 chat-x、开发新组件时使用' covers '了解 chat-x' and '开发新组件'. A few natural terms are missing (e.g., '贡献/contribute', 'bkui', '组件库调试'), so it fits anchor 4 rather than 5; clearly above anchor 3's 'missing common variations'.	4 / 5
Distinctiveness Conflict Risk	Scoped to one named library ('@blueking/chat-x'), a clear niche with distinct triggers ('chat-x', '开发新组件') and minimal overlap with generic Vue or documentation skills.	5 / 5
	Total	16 / 20 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: TencentBlueKing/bk-bcs
Path: bcs-services/bcs-project-manager/.cursor/skills/chat-x-contribute/SKILL.md
Commit: 9544047

Reviewed: 11 days ago

Table of Contents

Discovery Implementation Validation

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.