CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

omc-review

Evaluate finished work for defects, risk, and simplification before it ships

Quality

67%

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

Fix and improve this skill with Tessl

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

Quality

Content

75%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 disciplined, operational instruction skill: it sequences the review workflow with verification checkpoints, gives exact commands and output contracts, and avoids padding almost entirely. Remaining improvements are structural — breaking up the dense Quality Gates paragraph and folding the two-axes pass into the main workflow — rather than substantive.

Suggestions

Split the single-paragraph Quality Gates section into a short list or steps so its conditions (no entries vs. configured, BLOCK vs. advisory) are scannable.

Integrate the two-axes sub-agent pass into the numbered Workflow (e.g. as a step conditional on diff size) so the sequencing is unambiguous.

Add one brief example of a well-formed finding (file, line, failure scenario, severity) to make the output contract concrete.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — no explanations of what diffs or reviews are, and lines like "A plausible-sounding finding that does not reproduce is noise" earn their tokens — but a few justificatory clauses and slight redundancies ("Advisory by default — review informs, it does not gate") could be trimmed, matching the efficient-with-minor-excess anchor rather than the every-token-earns-its-place anchor.

4 / 5

Actionability

Guidance is concrete and executable: the exact command `omc quality-gates list --stage omc-review --json`, verdict strings `VERDICT: PASS`/`VERDICT: BLOCK`, the record shape `{ gate, mode, verdict }`, named standards-discovery targets (CLAUDE.md/AGENTS.md, docs/standards/, CONTRIBUTING.md, CODING_STANDARDS.md), and a defined output format ("file, line, and concrete failure scenario"); the minor gap is the absence of a worked example of a finding, which keeps it below the fully copy-paste-ready anchor.

4 / 5

Workflow Clarity

The five numbered steps include an explicit validation checkpoint ("Verify each candidate finding before reporting it") and the Quality Gates section adds real feedback loops (BLOCK → REQUEST CHANGES, unresolved → gate_unavailable, reusing the gate lane on re-review), but the two-axes sub-agent pass sits outside the numbered Workflow list, leaving mild sequencing ambiguity — clear sequence with minor gaps rather than a fully integrated checklist.

4 / 5

Progressive Disclosure

The skill is self-contained with no bundle files and clean, well-labeled sections (Goal, Workflow, What to check, Two axes, Rules, Output, Quality Gates) and no nested references; however, the body runs ~53 lines and the Quality Gates section is one dense unbroken paragraph, a minor organization gap that keeps it just below the well-organized-simple-skill top anchor.

4 / 5

Total

16

/

20

Passed

Description

42%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 communicates a clear purpose but reads as an internal label rather than a trigger: it states what the skill does yet omits any invocation guidance and misses the primary natural keywords ("review", "code review") a user would say. Adding an explicit "Use when..." clause with those phrases would lift both completeness and trigger-term quality.

Suggestions

Append an explicit trigger clause, e.g. "Use when asked to review a diff, PR, or finished task before merging or shipping."

Include the natural keywords users say — "review", "code review", "check for bugs", "PR review" — instead of only meta-vocabulary like "defects" and "risk".

State the artifact produced (a severity-ranked findings report) to sharpen the "what" and further distinguish the skill from generic review tools.

DimensionReasoningScore

Specificity

"Evaluate finished work for defects, risk, and simplification" names the domain and what is checked, matching the anchor for a domain plus 1-2 concrete actions; it is a single action (evaluate) with three objects rather than the several distinct actions of the anchor above.

3 / 5

Completeness

The "what" is clear (evaluate finished work for defects, risk, and simplification) but there is no "Use when..." clause or equivalent; "before it ships" describes the artifact's stage rather than when to invoke the skill, so the score is capped at the anchor for a clear "what" with a missing or weakly implied "when".

3 / 5

Trigger Term Quality

Domain nouns like "defects", "risk", and "before it ships" are present, but the natural phrases users actually say — "review", "code review", "check for bugs" — are entirely absent, which is the defining trait of the anchor for one or two generic keywords missing the natural phrases.

2 / 5

Distinctiveness Conflict Risk

"Evaluate finished work for defects, risk, and simplification" identifies the review niche, but defects and risk overlap heavily with generic code-review and security-review skills, matching the anchor for somewhat specific with overlap risk; no trigger phrases carve out a fully distinct lane.

3 / 5

Total

11

/

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

Yeachan-Heo/oh-my-claudecode

Path

skills/review/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.