go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
64
74%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./internal/assets/skills/go-testing/SKILL.mdQuality
Discovery
72%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 effectively targets a specific niche (Go testing with Bubbletea/golden files) and includes strong trigger terms that developers would naturally use. However, it lacks concrete action descriptions (what the skill actually does beyond 'apply patterns') and would benefit from an explicit 'Use when...' clause rather than the informal 'Trigger:' prefix format.
Suggestions
Replace 'Apply focused Go testing patterns' with specific actions like 'Generates table-driven tests, creates golden file test fixtures, writes Bubbletea teatest scenarios, and configures test coverage'.
Add an explicit 'Use when...' clause, e.g., 'Use when the user needs to write or debug Go tests, set up test coverage, create golden file tests, or test Bubbletea TUI components'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Go testing) and mentions some specific concepts like 'Bubbletea teatest', 'golden files', and 'test coverage', but doesn't list concrete actions beyond the vague 'Apply focused Go testing patterns'. It doesn't describe what specific actions the skill performs (e.g., generate test files, create table-driven tests, set up mocks). | 2 / 3 |
Completeness | The 'what' is partially addressed ('Apply focused Go testing patterns') but vague. The 'when' is implied through the 'Trigger:' prefix listing scenarios, but there's no explicit 'Use when...' clause. Per rubric guidelines, a missing explicit trigger guidance caps completeness at 2. | 2 / 3 |
Trigger Term Quality | Includes strong natural trigger terms that users would actually say: 'Go tests', 'go test coverage', 'Bubbletea teatest', 'golden files'. These are specific, natural keywords a developer working with Go testing would use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific niche of Go testing with Bubbletea teatest and golden files. Very unlikely to conflict with other skills given the narrow technology focus. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
77%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 efficiently maps Go testing scenarios to appropriate patterns through a clear decision gate table and sequenced execution steps. Its main weakness is the absence of inline executable code examples—all concrete examples are deferred to a references file that isn't provided in the bundle. The workflow is clear with good validation checkpoints, particularly for golden file updates.
Suggestions
Add at least one minimal executable code example inline (e.g., a table-driven test skeleton or a teatest snippet) so the skill body is actionable without relying entirely on the referenced examples file.
Include the references/examples.md bundle file to support the progressive disclosure reference and ensure the skill is self-contained.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section is lean and purposeful. No unnecessary explanations of Go testing basics, no padding. The decision gate table is an efficient lookup format, and hard rules are terse directives that add genuine value beyond Claude's baseline knowledge. | 3 / 3 |
Actionability | The skill provides concrete guidance through decision gates and hard rules, but lacks any executable code examples in the body itself. The references/examples.md file is cited but not provided in the bundle, so the skill body alone relies on descriptive instructions rather than copy-paste-ready code snippets. | 2 / 3 |
Workflow Clarity | The execution steps are clearly sequenced with a logical flow from identification through pattern selection, implementation, and validation. The golden file update workflow includes an explicit feedback loop (run with -update, inspect diff, rerun without -update), and the decision gate table provides unambiguous routing for each test scenario. | 3 / 3 |
Progressive Disclosure | The skill references examples.md for detailed code examples, which is good progressive disclosure structure. However, the bundle file is not provided, so we cannot verify the reference is accurate or useful. The single reference is well-signaled but the skill could benefit from the actual bundle content to fully support the body. | 2 / 3 |
Total | 10 / 12 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- sergiodvillegas-art/gentle-ai
- Commit
3bfa934
- 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.