CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

moai-ref-testing-pyramid

Test pyramid strategy, coverage targets, test patterns, and quality metrics reference. Agent-extending skill that amplifies manager-develop test-creation and quality-validation work with production-grade testing patterns. NOT for: production code implementation, architecture design, DevOps, security audits.

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 ./.claude/skills/moai-ref-testing-pyramid/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 dense, highly actionable reference whose tables of concrete ratios, coverage targets, and tool names are its strongest asset. Its main weaknesses are sections restating common knowledge (test file conventions, TDD basics) that inflate token cost, and a frontmatter progressive-disclosure declaration that is not backed by any bundle files.

Suggestions

Cut or compress sections Claude already knows well — the Test File Conventions table and the TDD RED-GREEN-REFACTOR quick reference — keeping only the project-specific rules ('one assertion per test (when practical)', '-race flag in Go') that are actual conventions.

Either add level-2 reference files matching the declared progressive_disclosure levels (e.g., move the pattern tables and Rationalizations into references/) or remove the unbacked progressive_disclosure frontmatter block.

Flesh out hint-style table entries like 'Interface injection, mock frameworks' and 'quickcheck, hypothesis' with one concrete example each so the patterns are directly usable rather than requiring lookup.

DimensionReasoningScore

Conciseness

The tables are dense and token-efficient, but several sections restate knowledge Claude already has: the Test File Conventions table ('*_test.go', 'test_*.py', 'src/test/'), the AAA pattern explanation, and the TDD RED-GREEN-REFACTOR basics. Not 2 because most content (coverage targets with specific numbers, the Rationalizations table, Red Flags) earns its place and cannot be trimmed much further.

3 / 5

Actionability

Concrete and specific throughout: exact ratios (70/20/10), numeric coverage targets (95%+, 85%+, 75%+), named tools ('go test -cover', 'istanbul', 'Stryker', 'testcontainers', 'httptest.NewServer'), and an executable Go AAA snippet. Not 5 because some table entries are high-level hints ('Interface injection, mock frameworks', 'quickcheck, hypothesis') rather than complete executable examples.

4 / 5

Workflow Clarity

As a reference skill it needs no multi-step workflow, and where sequences exist they are clear (RED-GREEN-REFACTOR with explicit rules); the Verification section supplies concrete checkpoints ('run 3x to verify stability', 'show test counts per category'). Not 5 because there is no guidance on how to sequence or apply the different tables during actual test-creation work.

4 / 5

Progressive Disclosure

A single well-organized file (~1,800 tokens) within the declared level2_tokens budget, with clear section headers and no buried references. Not 5 because the frontmatter declares progressive_disclosure enabled with two token levels but no level-2 bundle files exist to back that structure; not 3 since the in-file organization itself is clean.

4 / 5

Total

15

/

20

Passed

Description

70%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 specific, well-bounded description with a clear niche and helpful exclusions, weakened primarily by the absence of an explicit 'Use when...' trigger clause within the description field itself. Trigger term coverage is good but misses common natural phrasings like unit/integration/e2e tests and TDD.

Suggestions

Add an explicit 'Use when...' clause to the description itself (e.g., 'Use when planning test strategy, setting coverage targets, writing unit/integration/e2e tests, or running RED-GREEN-REFACTOR cycles'), since the when_to_use frontmatter field does not count toward the description's completeness.

Include the natural trigger terms already present in when_to_use — 'unit/integration/e2e test patterns' — and add 'TDD' and 'test coverage' so users' phrasings match.

Replace the buzzword-adjacent 'production-grade testing patterns' with a concrete noun phrase such as 'table-driven, mock/stub, snapshot, and property-based test patterns'.

DimensionReasoningScore

Specificity

The first sentence lists several concrete content areas ('Test pyramid strategy, coverage targets, test patterns, and quality metrics reference') and names the target consumer ('amplifies manager-develop test-creation and quality-validation work'). Not 5 because no specific patterns or metrics are named, and 'production-grade testing patterns' is mildly buzzwordy; not 3 because coverage goes beyond 1-2 items.

4 / 5

Completeness

The 'what' is clear (test pyramid strategy, coverage targets, patterns, and metrics reference), but there is no explicit 'Use when...' clause in the description field; the 'when' is only weakly implied by 'amplifies manager-develop test-creation and quality-validation work'. Per the rubric guideline, a missing explicit trigger clause caps completeness at 3, even though a separate when_to_use field exists in the frontmatter.

3 / 5

Trigger Term Quality

Includes natural phrases users would say such as 'test pyramid', 'coverage targets', 'test patterns', 'quality metrics', and 'test-creation'. Not 5 because common variations like 'unit tests', 'integration tests', 'e2e tests', 'TDD', and 'test coverage' are absent from the description itself.

4 / 5

Distinctiveness Conflict Risk

A clear niche (test strategy/quality reference for a manager-develop agent) with explicit negative boundaries ('NOT for: production code implementation, architecture design, DevOps, security audits') that sharply reduce overlap with adjacent skills. Minimal conflict risk.

5 / 5

Total

16

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

modu-ai/moai-adk

Path

.claude/skills/moai-ref-testing-pyramid/SKILL.md

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.