CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

martinfrancois/java-streams

Help AI coding agents use Java Streams and Collectors well in new code, review, and cleanup without replacing one antipattern with another.

2.77x
Quality

100%

Does it follow best practices?

Impact

100%

2.77x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Overview
Quality
Evals
Security
Files

Quality

Content

100%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.

This is a tightly engineered skill body: dense, policy-only prose with no filler, executable examples covering the common cases, a numbered workflow with an explicit checkpoint and a fix-and-re-scan validation loop, and a clean three-file bundle split. The compressed prose style (e.g., stacked negative clauses) occasionally demands a re-read, but it trades zero tokens for that density.

DimensionReasoningScore

Conciseness

The body never explains concepts Claude already knows (no stream-API tutorials); every line is project-specific policy — baseline checks, goal-to-API mapping, output rules. Version-sensitive detail is correctly deferred to java-stream-api.md rather than inlined, so time-sensitive content doesn't bloat the body.

5 / 5

Actionability

Guidance is fully executable: a goal→API decision table, plus seven complete Java snippets including the copy-paste-ready limit(2)/switch duplicate-fail lookup, the SeatIndex collector class, and the mapConcurrent gather chain. Concrete verification criteria (empty inputs, one element, duplicates, nulls, ordering) are named.

5 / 5

Workflow Clarity

Steps 0–7 are clearly sequenced, step 1 contains an explicit pre-write checkpoint ("confirm the chosen terminal returns the requested type and that order, duplicates, and nulls cannot change the winner"), and step 7 closes with a feedback loop: run the marker scan, fix hits, and re-scan.

5 / 5

Progressive Disclosure

The body is an overview-plus-core-workflow that points to three real, verified bundle files via a purpose table ("Replacement antipatterns and the marker scan to run", "Worked before/after examples", "Java-version compatibility"), with contextual inline links where each file matters. References are one level deep — the only cross-reference is a sibling link, not a nested chain.

5 / 5

Total

20

/

20

Passed

Description

100%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.

An exceptionally strong description: concrete actions, explicit use-when triggers with quoted user phrasings, third-person voice, and a well-bounded Java Stream niche. Its only watch-item is sheer density — the findFirst/findAny trigger theme recurs three times — but every clause carries distinct trigger information rather than padding.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "Review Java stream performance advice", "clean up mutation and write or refactor Java Stream and Collector code" — plus an enumerated antipattern list ("materializing just to inspect, sorting before min/max, counting for existence, nested stream collections, unsafe null sorting"), giving comprehensive coverage of the skill's capabilities with no vague filler.

5 / 5

Completeness

Both "what" and "when" are explicit: the what is reviewing/cleaning/writing/refactoring Stream and Collector code, and the when is a concrete "Use whenever a Java task writes, reviews, or refactors Stream API code (map, filter, flatMap, reduce, collect) or a collector" clause followed by specific trigger scenarios. Voice is third person throughout.

5 / 5

Trigger Term Quality

It covers the natural terms a user would actually say in this domain — "parallelStream", "map, filter, flatMap, reduce, collect", "grouping collectors", "joining strings", "findFirst or findAny", "parallel streams" — including synonyms ("parallelStream" and "parallel streams") and even a near-verbatim user prompt shape ("review prompts asking whether a lookup should use findFirst or findAny").

5 / 5

Distinctiveness Conflict Risk

The skill occupies a clear niche (Java Stream API and collectors) and every trigger is stream-specific — terminal operations, collectors, sorted/limit/distinct stages, Optional in streams — so the risk of it firing for an unrelated skill is minimal.

5 / 5

Total

20

/

20

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

Validation for skill structure

No warnings or errors.

Reviewed

On this page