CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

code-steward

Maintains Kotlin codebase health, idiomatic style, and modern API usage. Use this skill to fix code smells, update deprecated APIs, resolve outdated TODOs, apply Kotlin scope functions, flatten deeply nested logic, and resolve lint or detekt warnings.

Quality

86%

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

SKILL.md
Quality
Evals
Security

Quality

Content

78%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 well-structured, action-oriented skill body with concrete gradle commands, clear always/ask/never constraints, and a sequenced workflow including verification. The main gaps are the absence of before/after code examples and an explicit verification-failure feedback loop.

Suggestions

Convert the prose Examples into short before/after Kotlin code snippets (e.g., a null-check block vs. its `?.let` form) so the refactor patterns are copy-paste ready.

Add an explicit feedback loop to the VERIFY step: if compilation or lint fails, fix the issue and re-run the checks before presenting.

Tighten the Philosophy bullets and journaling paragraph, which read as guidance Claude could infer, freeing tokens for the concrete examples.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence (no explanation of Kotlin concepts), but the Philosophy bullets and the long journaling paragraph are trimming candidates that don't each earn their tokens.

4 / 5

Actionability

Concrete executable commands ('./gradlew ktfmtFormat', './gradlew detekt', './gradlew lintDebug'), specific type swaps ('java.util.Date' to 'java.time.Instant'), and a PR title example are given, but the Examples section describes refactors in prose rather than showing before/after code.

4 / 5

Workflow Clarity

A clear five-step sequence (SCAN, SELECT & PROPOSE, REFINE, VERIFY, PRESENT) with an explicit approval gate and a VERIFY step that formats, compiles, and checks lint; however, no explicit error-recovery loop (what to do when verification fails) is described.

4 / 5

Progressive Disclosure

At 49 lines with no bundle files needed, the body is well organized into Goal, Constraints, Instructions, and Examples sections, and the only external path (.agents/skills/steward/journal.md) is a clearly signaled state file, not a nested reference.

5 / 5

Total

17

/

20

Passed

Description

88%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 strong description: third-person, concise, with a clear what/when structure and concrete Kotlin-specific capabilities. Its only weaknesses are a few missing natural synonyms and slight overlap with general code-quality skills on generic trigger terms.

DimensionReasoningScore

Specificity

The description lists six concrete actions ('fix code smells, update deprecated APIs, resolve outdated TODOs, apply Kotlin scope functions, flatten deeply nested logic, and resolve lint or detekt warnings') that comprehensively cover the skill's stated scope.

5 / 5

Completeness

It clearly answers 'what' ('Maintains Kotlin codebase health, idiomatic style, and modern API usage') and 'when' with an explicit, concrete trigger clause ('Use this skill to fix code smells, update deprecated APIs, ...').

5 / 5

Trigger Term Quality

Natural user phrases like 'code smells', 'deprecated APIs', 'TODOs', 'lint', and 'detekt' are present, but common synonyms such as 'refactor', 'code cleanup', and 'ktlint' are missing.

4 / 5

Distinctiveness Conflict Risk

Kotlin-specific triggers (scope functions, detekt, deprecated Kotlin/Android APIs) define a clear niche, but generic terms like 'code smells' and 'lint warnings' carry minor overlap risk with general refactoring or code-review skills.

4 / 5

Total

18

/

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

nekomangaorg/Neko

Path

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