golang-testing

Go测试模式包括表格驱动测试、子测试、基准测试、模糊测试和测试覆盖率。遵循TDD方法论，采用地道的Go实践。

Quality

68%

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 ./docs/zh-CN/skills/golang-testing/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 content is a highly actionable Go testing reference dominated by executable, copy-paste-ready code and a clear TDD workflow with validation steps. Its weaknesses are mild prose padding and a monolithic single-file structure that would benefit from splitting advanced topics into reference files.

Suggestions

Move advanced/large sections (golden files, fuzzing, HTTP handler testing, CI/CD) into reference files under references/ and link to them from SKILL.md to improve progressive disclosure.

Trim explanatory prose lead-ins and the closing "测试即文档" platitude to raise conciseness.

Add explicit validation/feedback-loop callouts where multi-step workflows appear beyond the TDD section (e.g. golden-file update flow: run -update, then re-run tests to confirm).

Dimension	Reasoning	Score
Conciseness	The body is mostly lean executable code with brief intros, but several prose lead-ins (e.g. "Go 测试的标准模式。以最少的代码实现全面的覆盖。") and the closing "测试即文档" platitude could be trimmed, keeping it at mostly-efficient rather than lean.	3 / 5
Actionability	Nearly every section provides complete, copy-paste-ready Go code plus concrete shell commands (e.g. "go test -bench=BenchmarkProcess -benchmem"), covering the common cases fully.	5 / 5
Workflow Clarity	The TDD section has an explicit red-green-refactor sequence with verification checkpoints ("verify FAIL", "verify PASS"), but the rest of the document is a pattern catalog rather than sequenced workflows, so checkpoints are not consistently present.	4 / 5
Progressive Disclosure	No bundle files exist and all ~722 lines live inline in SKILL.md with good section headers, but topics like golden files, fuzzing, HTTP handlers, and CI/CD could be split into reference files, so structure is present yet the monolithic file holds content that should be separate.	3 / 5
	Total	15 / 20 Passed

Description

66%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 names a strong set of concrete Go testing patterns and good trigger keywords, but it lacks an explicit "Use when..." clause, which is the main weakness. It is specific and largely distinct but not maximally complete.

Suggestions

Add an explicit trigger clause, e.g. "Use when writing Go tests, adding test coverage, or following a TDD workflow in Go."

Include common synonyms users might say, such as "单元测试/unit testing" and "go test", to broaden trigger coverage.

Reframe the pattern list as concrete actions (e.g. "write table-driven tests, run benchmarks, add fuzz targets") to push specificity toward 5.

Dimension	Reasoning	Score
Specificity	Lists several concrete testing patterns ("表格驱动测试、子测试、基准测试、模糊测试和测试覆盖率") rather than vague abstractions, though it enumerates categories more than discrete actions, so it stops short of a 5.	4 / 5
Completeness	It clearly states what the skill covers (the testing patterns) but provides no "Use when..." trigger guidance, which caps completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	Includes natural terms a Go user would say ("Go测试", "TDD", "基准测试", "模糊测试", "测试覆盖率"), but omits common synonyms like "单元测试/unit testing" and the literal "go test" command.	4 / 5
Distinctiveness Conflict Risk	The Go-testing-plus-TDD niche is mostly distinct with only minor overlap risk against a general Go skill, not the clear niche-with-minimal-conflict needed for a 5.	4 / 5
	Total	15 / 20 Passed

Validation

81%

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 — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (723 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 1 missing	Warning

	Total	13 / 16 Passed

Repository: affaan-m/ECC
Path: docs/zh-CN/skills/golang-testing/SKILL.md
Commit: e04ea0b

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