CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

omit-needless-words

Use when reviewing a PR, branch, diff, doc, skill, or comment block for wordiness, history or roadmap prose, restated information, or code and tests beyond what the spec asks for.

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

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

An exemplarily tight instruction-only skill: five terse rules, a concrete process with real commands and decision conditionals, and an exact output template. The only meaningful gap is a missing explicit verification step before emitting findings, which keeps workflow clarity just below the top anchor. Structure and token efficiency are essentially ideal for a skill of this size.

DimensionReasoningScore

Conciseness

The body is lean and padding-free ("Review changed prose and code against five rules. The review obeys them too."), explains nothing Claude already knows, and the one unfamiliar term (AMANALAP) is defined in the same line — every token earns its place.

5 / 5

Actionability

Concrete commands are given ("gh pr diff", "gh api repos/OWNER/REPO/contents/PATH?ref=HEAD_SHA") alongside an exact copy-paste output template with path:line format and Fix formats, plus explicit conditionals (why-vs-what comments, untrusted input, required copies) covering the common cases. As an instruction-only skill with fully actionable guidance, the absence of code is not penalized.

5 / 5

Workflow Clarity

The sequence (Target → Spec → Check context → Apply rules → Output) is clearly ordered with a checkpoint in step 3 ("Check context before calling something new") and a strict output template, but there is no final verification pass (e.g., confirming each cited path:line against the diff), leaving a minor validation gap relative to the explicit-validation anchor.

4 / 5

Progressive Disclosure

This is a single-file, ~42-line skill with no external reference needs and no bundle files; its three well-organized sections (The Rules, Process, Output) satisfy the rubric's guideline that sub-50-line simple skills score 5 on well-organized sections alone.

5 / 5

Total

19

/

20

Passed

Description

78%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 trigger-focused description that explicitly covers both what the skill finds and when to use it, with natural, specific trigger terms. Its main weakness is specificity of actions — it lists the problem categories to look for but relies on a single generic verb ("reviewing") rather than naming the concrete actions it performs. The broad PR/diff review trigger also carries minor overlap risk with general code-review skills.

DimensionReasoningScore

Specificity

Names the domain and four concrete review targets ("wordiness, history or roadmap prose, restated information, or code and tests beyond what the spec asks for") but offers only one action verb ("reviewing"), matching the 'names domain and 1-2 concrete actions, not comprehensive' anchor rather than the several-specific-actions anchor above it.

3 / 5

Completeness

Both parts are explicit with concrete trigger phrases: what (finds "wordiness, history or roadmap prose, restated information, or code and tests beyond what the spec asks for") and when ("Use when reviewing a PR, branch, diff, doc, skill, or comment block"). The 'when' is already maximally explicit and specific, so the anchor-4 caveat ('when' could be more explicit) does not apply.

5 / 5

Trigger Term Quality

"PR, branch, diff, doc, skill, comment block" are natural terms users would say when needing this skill, but common synonyms like "verbose", "wordy", "documentation", or "README" are missing, which fits 'good keyword coverage; a few natural terms missing' rather than the comprehensive-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

The qualifiers (wordiness, restated information, excess code) carve a distinct conciseness-review niche, but the broad lead-in "reviewing a PR, branch, diff" overlaps with general code-review skills, matching 'mostly distinct; minor overlap risk with closely related skills' rather than the minimal-conflict anchor.

4 / 5

Total

16

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository

NVIDIA/OpenShell

Path

.agents/skills/omit-needless-words/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.