chat-x-unit-test

帮助开发者为 Vue 3 组件编写单元测试。当用户需要添加单元测试时使用。

Quality

77%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./bcs-services/bcs-project-manager/.cursor/skills/chat-x-unit-test/SKILL.md

Quality

Content

87%

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

This is a well-structured, concise skill that provides actionable guidance for Vue 3 unit testing. The executable code template and clear command examples are strengths. The main weakness is the lack of explicit validation workflows for ensuring test quality and handling test failures.

Suggestions

Add a validation workflow section showing how to verify test coverage and handle failing tests (e.g., 'Run tests -> Check coverage -> Fix failures -> Re-run')

Remove the duplicate '可用资源' section at the end of the file

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient, providing only essential information without explaining basic concepts Claude already knows. Every section serves a clear purpose with no padding.	3 / 3
Actionability	Provides fully executable code templates with proper imports, concrete bash commands for running tests, and copy-paste ready examples. The basic template is complete and immediately usable.	3 / 3
Workflow Clarity	The test categories are listed but lack explicit validation steps or feedback loops. The '同步更新原则' mentions updating tests but doesn't provide a clear workflow for how to verify test coverage or handle failures.	2 / 3
Progressive Disclosure	Clear overview with well-organized sections and one-level-deep references to external resources (mock-patterns.md, test-qa.md, test-strategies.md). Content is appropriately split between quick-start and detailed references.	3 / 3
	Total	11 / 12 Passed

Description

67%

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 has a solid structure with both 'what' and 'when' clauses, making it functionally complete. However, it lacks specific concrete actions beyond 'writing unit tests' and could benefit from more trigger term variations. The Vue 3 focus provides some distinctiveness but the description remains somewhat generic within the testing domain.

Suggestions

Add specific concrete actions like 'mock child components, test props and emits, verify lifecycle hooks, create snapshot tests'

Expand trigger terms to include variations like 'vitest', 'jest', '.spec.ts', 'component testing', 'test coverage'

Dimension	Reasoning	Score
Specificity	Names the domain (Vue 3 components) and one action (writing unit tests), but lacks specific concrete actions like 'mock components', 'test props', 'verify emitted events', or 'snapshot testing'.	2 / 3
Completeness	Clearly answers both what ('帮助开发者为 Vue 3 组件编写单元测试' - helps write unit tests for Vue 3 components) and when ('当用户需要添加单元测试时使用' - use when user needs to add unit tests) with explicit trigger guidance.	3 / 3
Trigger Term Quality	Includes 'Vue 3', '单元测试' (unit tests), but missing common variations users might say like 'test', 'testing', 'spec', 'vitest', 'jest', '.spec.ts', or 'component testing'.	2 / 3
Distinctiveness Conflict Risk	Specifies Vue 3 which helps distinguish from general testing skills, but '单元测试' (unit tests) is broad enough to potentially conflict with other testing-related skills for different frameworks.	2 / 3
	Total	9 / 12 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: TencentBlueKing/bk-bcs
Commit: b08ac38

Reviewed: 5 months 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.