golang-testing

テスト駆動開発とGoコードの高品質を保証するための包括的なテスト戦略。

Quality

49%

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/ja-JP/skills/golang-testing/SKILL.md

Quality

Content

50%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 skill is a comprehensive, mostly-executable Go testing reference, but it is overlong and tutorial-heavy for a SKILL.md, padding concepts Claude already knows. It also lacks a sequenced workflow with validation checkpoints and inlines reference material that should live in separate files.

Suggestions

Trim explanatory prose around code blocks to only what is non-obvious, and remove definitions of concepts Claude already knows (TDD, what mocking is) to improve token efficiency.

Add a short sequenced 'testing workflow' with explicit validation checkpoints (write failing test -> run `go test` -> implement -> re-run -> check `go test -race -cover`) instead of only topic sections.

Move the large reference material (HTTP/DB mocking recipes, benchmark/fuzz examples, quick-reference table) into files under references/ and link to them from SKILL.md to apply progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is ~960 lines of largely tutorial-style content explaining concepts Claude already knows (what TDD is, how table-driven tests work, basic mocking), with verbose commentary around every code block; this matches 'noticeably verbose; several unnecessary explanations or padded sections' rather than the leaner 3-anchor.	2 / 5
Actionability	It provides many concrete, executable Go code blocks and shell commands (table-driven tests, httptest, benchmarks, fuzzing, coverage commands), with only minor gaps such as placeholder bodies and undefined helpers (setupTestDB, runMigrations), fitting 'mostly executable guidance with minor gaps'.	4 / 5
Workflow Clarity	Topics are clearly organized into sections but there is no end-to-end sequenced workflow with validation checkpoints for the batch/destructive-leaning operations shown (DB migrations, testcontainer teardown, coverage runs); the feedback-loops note caps such skills at 3 when validation steps are absent.	3 / 5
Progressive Disclosure	No bundle files exist (references/scripts/assets are absent) and all material — including large API-style reference blocks and the quick-reference table — is inlined in SKILL.md; structure exists via headers but content that should be split into separate files is inline, matching 'some structure but could be better organized'.	3 / 5
	Total	12 / 20 Passed

Description

48%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 identifies the Go testing/TDD niche but stays abstract, omitting concrete actions and any explicit 'Use when...' trigger clause. It is distinct enough yet generic in phrasing, so it lands near the rubric midpoint.

Suggestions

Add concrete actions, e.g. 'Writes table-driven and sub-tests, mocks dependencies, runs benchmarks and fuzz tests, and measures coverage'.

Append an explicit trigger clause such as 'Use when writing or reviewing Go tests, improving coverage, or debugging Go code'.

Include natural trigger keywords users say ('go test', 'unit test', 'benchmark', 'race detector', 'coverage') to improve trigger-term quality.

Dimension	Reasoning	Score
Specificity	The description 'テスト駆動開発とGoコードの高品質を保証するための包括的なテスト戦略' names the domain (Go testing/TDD) but lists no concrete actions — it only states an abstract goal of 'ensuring quality', matching the 'names domain but actions are minimal/generic' anchor rather than the 3-anchor which requires 1-2 concrete actions.	2 / 5
Completeness	It gives a clear 'what' (a testing strategy for TDD and Go quality) but has no 'Use when...' or equivalent trigger clause — the judging guideline caps completeness at 3 when explicit trigger guidance is missing.	3 / 5
Trigger Term Quality	It surfaces relevant keywords ('テスト駆動開発', 'Goコード', 'テスト') that a user might say, but misses common natural variations and concrete triggers like 'unit test', 'benchmark', 'coverage', or 'go test', fitting 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	Scoping to Go testing/TDD makes it mostly distinct from other skills with only minor overlap risk against a generic code-review skill; it does not reach 5 because the description lacks concrete triggers that fully separate it from adjacent testing skills.	4 / 5
	Total	12 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (960 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: affaan-m/ECC
Path: docs/ja-JP/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.