CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/scalatest

Configures and runs ScalaTest - Scala-native test framework with multiple specification styles (FlatSpec, FunSuite, WordSpec, FreeSpec, AsyncFlatSpec for async); Matchers DSL (`should equal`, `should contain`, `shouldBe a [Class]`); integrates with ScalaCheck for property-based testing; sbt + Maven + Gradle support; tagged-test selective execution. Use when working with Scala codebases.

75

Quality

94%

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

Overview
Quality
Evals
Security
Files

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, code-rich skill body with clear sequencing and a properly externalized Matchers reference. The main weakness is conciseness: pinned version numbers are time-sensitive and sit inline rather than in a deprecated section.

Suggestions

Move or generalize pinned version numbers ('3.2.19', '3.2.18.0') into a version-pin note or a deprecation/old-patterns section so they don't age the skill and don't penalize conciseness.

Tighten the Overview's definitional lines ('ScalaTest is the de facto Scala testing framework') since Claude already knows what ScalaTest is — keep only the cross-skill positioning.

Consider collapsing the 'How to use' 8-step preview and the per-step sections where content overlaps (e.g., Step 3 summary vs. the Matchers DSL section) to reduce repetition.

DimensionReasoningScore

Conciseness

Mostly lean with code-forward steps and no padding about what Scala/libraries are, but pinned time-sensitive version numbers ('3.2.19', '3.2.18.0') appear inline rather than in a deprecated/old-patterns section, which the rubric penalizes; not level 1 because prose is tight and assumes Claude's competence.

2 / 3

Actionability

Fully executable, copy-paste-ready code throughout — build.sbt deps, FlatSpec/FunSuite/WordSpec/AsyncFlatSpec/ScalaCheck/lifecycle/tag examples, and CI yaml — with specific commands like 'sbt clean coverage test coverageReport'.

3 / 3

Workflow Clarity

Clear 8-step sequence in 'How to use' with '(Step N)' cross-references to detailed sections, plus a worked example and inherent validation via running tests; not capped at 2 because test-writing is not a destructive/batch operation requiring explicit validate-fix-retry checkpoints.

3 / 3

Progressive Disclosure

Well-organized sections (Overview, When to use, How to use, Steps 1-8, Worked example, Anti-patterns, Limitations, References) with a single one-level-deep, clearly-signaled reference to references/matchers-dsl.md (verified present) for the Matchers detail.

3 / 3

Total

11

/

12

Passed

Description

100%

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 strong, third-person description that names concrete capabilities, includes natural trigger terms, and provides an explicit 'Use when' clause with a clear Scala-testing niche. Minor weakness is that the 'Use when working with Scala codebases' trigger is broad rather than enumerating ScalaTest/Scala-testing-specific triggers.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Configures and runs ScalaTest', 'multiple specification styles (FlatSpec, FunSuite, WordSpec, FreeSpec, AsyncFlatSpec)', 'Matchers DSL', 'integrates with ScalaCheck', 'tagged-test selective execution' — matching the level-3 anchor of several specific concrete actions.

3 / 3

Completeness

Explicitly answers both what (detailed capability list) and when via the explicit trigger 'Use when working with Scala codebases'; the presence of an explicit 'Use when' clause keeps it above the level-2 cap.

3 / 3

Trigger Term Quality

Natural terms a user would say are well covered — 'ScalaTest', 'Scala', 'ScalaCheck', 'property-based testing', 'Matchers DSL', 'sbt/Maven/Gradle' — rather than abstract jargon; not level 2 because common variations are present, not just one keyword.

3 / 3

Distinctiveness Conflict Risk

Clear Scala-testing niche naming a specific framework, with junit5/kotest positioned as alternatives elsewhere; unlikely to fire for non-Scala or non-testing work.

3 / 3

Total

12

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents