CtrlK
BlogDocsLog inGet started
Tessl Logo

unit-testing

为 BK-CI 代码编写单元测试时使用,例如 JUnit5、MockK、测试组织、依赖 Mock、异常校验和 TDD 场景。当用户要补测试或用测试驱动实现时优先使用。

63

Quality

74%

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 ./ai/skills/unit-testing/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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 tidy, well-structured instruction skill that avoids over-explanation and is appropriately scoped, but it stays at the level of principles: it lacks concrete code examples, a run/verify command, and explicit validation checkpoints that would make the guidance fully executable.

Suggestions

Add a minimal JUnit5 + MockK test skeleton (or a BK-CI-specific example) under 快速指导 so the guidance is copy-paste ready rather than principle-only.

Include an explicit verification step — e.g. run the tests and confirm a meaningful test fails when the code under test is broken, or check a coverage threshold — to turn the loose guidance list into a workflow with checkpoints.

State the project-specific way to run the tests (e.g. the Gradle/Maven command used in BK-CI) so actionability reaches concrete executable guidance.

DimensionReasoningScore

Conciseness

Lean, list-based body that does not explain concepts Claude already knows (no definition of unit tests/JUnit5/MockK), matching 'efficient; minor instances of over-explanation'; not a 5 because meta lines like "这个 skill 关注的是 BK-CI 项目里的单元测试写法,不是测试理论总览" could be trimmed.

4 / 5

Actionability

Gives concrete specific guidance ("AAA、Mock 外部依赖、显式断言", naming tests by behavior, avoid over-mocking/weak assertions) but provides no code template, no run command, and no BK-CI-specific test structure, so it is incomplete for execution; above a 2 because the directives are specific and actionable, not vague hints.

3 / 5

Workflow Clarity

The numbered "快速指导" gives a rough sequence, but validation checkpoints (run the tests, confirm a test fails without the code, check coverage) are entirely missing/implicit, matching the 'steps listed but validation gaps' anchor; not a 4 because the checkpoint gaps are not minor.

3 / 5

Progressive Disclosure

A sub-50-line skill with well-organized sections and a clearly signaled one-level cross-skill reference ("再看 backend-microservice-development"), no nested references and no bundle files needed, matching the top anchor per the simple-skills note.

5 / 5

Total

15

/

20

Passed

Description

83%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 strong, concise description that clearly states what the skill does and when to use it, with concrete technologies and natural trigger phrases. Main gap is missing a few common synonyms and the what/when distinction from sibling testing skills is only implied in the body.

DimensionReasoningScore

Specificity

Names the domain (BK-CI unit testing) and several concrete items — "JUnit5、MockK、测试组织、依赖 Mock、异常校验和 TDD 场景" — matching the 'lists several specific actions; minor gaps' anchor; not a 5 because the items are named technologies/concerns rather than a comprehensive set of discrete actions.

4 / 5

Completeness

Explicitly answers both what ("为 BK-CI 代码编写单元测试...例如 JUnit5、MockK...") and when ("当用户要补测试或用测试驱动实现时优先使用") with concrete trigger phrases, matching the top anchor; confirmed not a 4 because the 'when' clause is explicit and concrete, not merely present.

5 / 5

Trigger Term Quality

Includes natural phrases a user would say ("补测试", "测试驱动实现", "TDD") matching 'good keyword coverage; a few natural terms missing'; not a 5 because synonyms like 测试用例/覆盖率 and file/extension terms are absent.

4 / 5

Distinctiveness Conflict Risk

Scoped to the BK-CI project with a named stack (JUnit5/MockK/TDD), giving a mostly-distinct niche with minor overlap risk against related testing skills; not a 5 because the description alone does not sharply separate from a hypothetical integration-testing skill.

4 / 5

Total

17

/

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-ci
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.