CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

nullaway

Guide for resolving NullAway static analysis errors. Best practices for: - Passing ObservableSupplier/Supplier<@Nullable T> - Dereferencing potentially @Nullable values - Adding @NullMarked to Java code

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

—

The risk profile of this skill

Fix and improve this skill with Tessl

tessl review fix ./agents/skills/nullaway/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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 highly actionable with concrete executable Java recipes and avoids concept-over-explanation, but it is verbose due to cross-section repetition, lacks an explicit validation-gated workflow, and is monolithic with no progressive disclosure to reference files.

Suggestions

Consolidate the assumeNonNull-vs-assert decision and the 'investigate the call tree' rule into a single canonical section to remove repetition.

Add an explicit numbered workflow with a validate checkpoint (e.g. run PublicTransitLeakTest smoke test -> fix -> re-run -> only then proceed to CQ) for the regression-risky migration path.

Split detailed recipes and annotation-placement rules into a separate reference file (e.g. RECIPES.md) and link from SKILL.md to improve progressive disclosure.

DimensionReasoningScore

Conciseness

The guide is information-dense and avoids explaining concepts Claude already knows, but it repeats the assumeNonNull-vs-assert distinction and the 'investigate the call tree' rule across multiple sections, and emphatic CAUTION boxes add length that could be tightened.

3 / 5

Actionability

Provides fully executable, copy-paste-ready Java examples with concrete APIs (NullUtil.assumeNonNull, SupplierUtils.upcast, supplier.asNonNull()) and exact annotation imports, covering the common cases via before/after recipes.

5 / 5

Workflow Clarity

A refactor recipe gives a rough sequence and the Testing section names a smoke-test validation checkpoint, but the guide is rule-oriented with mostly implicit checkpoints and no explicit validate-then-proceed loop, which caps clarity at 3 for a regression-risky code-change context.

3 / 5

Progressive Disclosure

The ~250-line guide has clear section headers and logical organization, but it is monolithic with no bundle files and no external references; content such as detailed recipes and annotation-placement rules is inlined where separate reference files would aid navigation.

3 / 5

Total

14

/

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.

The description is specific and well-targeted to NullAway with concrete best-practice actions, but lacks an explicit 'when to use' trigger clause. Adding a 'Use when resolving NullAway errors or @Nullable/@NullMarked warnings' sentence would raise completeness.

Suggestions

Add an explicit trigger clause such as 'Use when resolving NullAway static analysis errors, @Nullable dereference warnings, or when adding @NullMarked to Java code.'

Include common synonyms users might say, e.g. 'NullAway warnings' or 'null-check errors', to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

Lists several concrete actions ('resolving NullAway static analysis errors', 'Passing ObservableSupplier/Supplier<@Nullable T>', 'Dereferencing potentially @Nullable values', 'Adding @NullMarked to Java code') with only minor coverage gaps, matching the anchor for several specific actions.

4 / 5

Completeness

Clearly states the 'what' (resolving NullAway errors with specific best practices) but provides no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Includes the natural trigger 'NullAway static analysis errors' plus domain terms like @Nullable, @NullMarked, and ObservableSupplier/Supplier that users of the tool would say, though common synonyms like 'null check' or 'NullAway warning' are missing.

4 / 5

Distinctiveness Conflict Risk

Targets the specific NullAway tool by name, giving it a clear niche with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

16

/

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.

Repository

chromium/chromium

Path

agents/skills/nullaway/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.