CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

martinfrancois/java-functional-style

Help AI coding agents write, review, and refactor Java lambdas, method references, functional interfaces, identity functions, suppliers, predicates, consumers, and callbacks with behavior-preserving readability.

1.63x
Quality

100%

Does it follow best practices?

Impact

100%

1.63x

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.

The body is a dense, high-signal rule set: it assumes Java knowledge, gives executable before/after examples for the main transforms, and ends the workflow with an explicit verification checklist plus a scan gate that must pass before finishing. The three reference files are real, well-signaled via a load-condition table, and one level deep. All four dimensions sit at the top anchor.

DimensionReasoningScore

Conciseness

The body assumes competence — it never defines lambdas, streams, or Optional — and spends its tokens only on decision rules and behavior edges ("`expr::method` evaluates `expr` once, at creation, and throws `NullPointerException` there if it is null"; "throws `ConcurrentModificationException` on `HashMap` since Java 9"). Matches the lean/every-token-earns-its-place anchor; not a 4 because I found no passage of over-explanation to trim.

5 / 5

Actionability

Guidance is executable throughout: complete before/after Java pairs for identity helpers and no-op stages, a runnable receiver-binding contrast ("Supplier<Config> a = registry.current()::config"), and exact API names ("Function.identity()", "Comparator.comparing(key).thenComparing(key2, nullsLast(naturalOrder()))", "comparingInt"). Matches the fully-executable anchor; not a 4 because the common cases all have copy-paste-ready code or exact helper names.

5 / 5

Workflow Clarity

The 12-step workflow is coherently ordered from "Check the Java baseline first" to a final gate with an explicit verification checklist: "Verify each changed callback for present and absent values, empty input, nulls, ordering, laziness, exception type and timing, side effects... Then run the `rg` scan... and reconcile every hit before finishing". Matches the anchor with explicit validation steps and an error-reconciliation loop; not a 4 because checkpoints are explicit, not implicit.

5 / 5

Progressive Disclosure

A Reference Bundle table signals each of the three bundle files with a "Load it when" condition, and all referenced paths (references/hard-stops.md, references/functional-style-examples.md, references/java-functional-api.md) exist on disk with no nested references inside them. Matches the clear-overview, well-signaled, one-level-deep anchor; not a 4 because navigation and content split are handled without organization gaps.

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.

The description is exemplary: it states concrete capabilities with the exact functional-interface types in scope, gives multiple explicit trigger conditions including the no-keyword case, and closes with clear negative boundaries that separate it from stream/Optional-semantics skills. Every judged quality matches the top anchor without relying on inference.

DimensionReasoningScore

Specificity

Names three concrete actions ("Write, review, and refactor") applied to exactly the objects in scope ("Java lambdas, method references, and functional-interface callbacks (Function, Predicate, Supplier, Consumer, Comparator, BiFunction)"). This matches the comprehensive-coverage anchor; it is not a 4 because the action list and target types leave no minor gaps.

5 / 5

Completeness

Both halves are explicit: the what ("Write, review, and refactor Java lambdas... so they stay readable and behavior-preserving") and a concrete when ("Use whenever Java code creates or changes a callback... when a cleanup or review touches identity lambdas... or when the user asks to make Java code cleaner"), plus explicit exclusions. Matches the anchor that answers both what and when with concrete trigger phrases; not a 4 because the when-clause is fully explicit rather than improvable.

5 / 5

Trigger Term Quality

Covers the natural terms users would say — "lambda", "method references", "suppliers", "stream, Optional, Map, CompletableFuture, or listener API" — and explicitly handles the synonym case: "make Java code cleaner or more functional, even if they never say 'lambda'". Matches the comprehensive-synonyms anchor; not a 4 because no common natural phrasing is missing.

5 / 5

Distinctiveness Conflict Risk

The niche is distinct (functional-style callback writing in Java) and the description actively disambiguates from adjacent skills: "Do not use for stream or Optional semantics themselves, and do not use it to force functional style where a plain loop or branch is clearer". Minimal conflict risk; not a 4 because overlap with related Java skills is explicitly carved out rather than merely minor.

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