test-development

用于测试开发面试出题；覆盖测试基础、用例设计、自动化测试、性能测试与安全测试，兼顾工程化落地能力。

Quality

66%

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 ./app/src/main/resources/skills/test-development/SKILL.md

Quality

Content

71%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 concise, actionable, and well-sequenced for an instruction-only interview skill. The main weakness is progressive disclosure: the Additional Resources section references files that are not present in the bundle.

Suggestions

Add the referenced bundle files (test-development.md, java.md, python-basic.md) under references/ so the Additional Resources links resolve.

Convert the Additional Resources mapping into explicit markdown links (e.g., [test-development.md](references/test-development.md)) for clearer signaling.

Optionally include 1-2 concrete sample questions or a small question template to lift actionability toward 5.

Dimension	Reasoning	Score
Conciseness	The body is lean with no padding or explanation of concepts Claude already knows; only the Overview sentence (重点评估其能否通过技术手段提升测试效率与质量保障深度) is slightly ornate and could be trimmed, keeping it just below a 5.	4 / 5
Actionability	Instructions are concrete and directive with specific examples (登录/支付/电商直播间, 覆盖率数据, 脚本维护成本, CI 集成方式, 编写测试工具/搭建测试平台/参与 CI/CD); minor gaps in that no actual sample questions or templates are provided.	4 / 5
Workflow Clarity	A clear 5-step sequenced interview flow is present (cover dimensions → tie to resume → push for landing details → require on-site case design → assess dev capability); no validation checkpoints, but the destructive/batch cap does not apply to an interview skill.	4 / 5
Progressive Disclosure	Structure is clean (Overview / Instructions / Additional Resources) with a well-organized category-to-file reference map that is one level deep, but the referenced files (test-development.md, java.md, python-basic.md) do not exist in the bundle, so navigation would fail.	3 / 5
	Total	15 / 20 Passed

Description

61%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 defines a specific niche and lists comprehensive coverage areas, but lacks an explicit 'Use when' trigger clause, which limits completeness. Trigger-term quality is good but not exhaustive.

Suggestions

Add an explicit 'Use when...' / '当用户需要...' trigger clause stating when Claude should invoke this skill.

Replace the single generic verb (覆盖) with more concrete actions describing what the skill actually produces (e.g., 生成、设计、追问、评估).

Include a couple of natural synonyms or phrasings users might say (e.g., 测开面试、测试工程师面试题) to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (测试开发面试出题) and several concrete sub-areas (测试基础、用例设计、自动化测试、性能测试与安全测试、工程化落地能力), but the only real action verb is 出题/覆盖, so it falls at the 'names domain and concrete areas but not comprehensive discrete actions' level rather than a clear 4.	3 / 5
Completeness	The 'what' is clear (generate test-development interview questions across listed domains), but there is no 'Use when...' or equivalent explicit trigger clause, which per the guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	Natural Chinese terms a user would say (测试开发、用例设计、自动化测试、性能测试、安全测试) are present with good coverage; a few common synonyms or phrasings are missing, so just above the midpoint.	4 / 5
Distinctiveness Conflict Risk	It targets a clear niche (test-dev interview question generation) with distinct triggers, with only minor overlap risk against general interview or general testing skills; not a 5 because trigger phrasing is implicit.	4 / 5
	Total	14 / 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: Snailclimb/interview-guide
Path: app/src/main/resources/skills/test-development/SKILL.md
Commit: b2d1ca0

Reviewed: 19 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.