CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

review-work

Post-implementation gate review: run manual QA on the real surface yourself, then launch ONE gate reviewer (never a panel) to audit goal, constraints, code quality, security, missed context, and QA evidence. Use before a PR handoff or when the user explicitly asks to review completed work.

Quality

80%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/omo/skills/review-work/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

62%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 review orchestration itself is excellently specified — a clear phase sequence with strong validation checkpoints, feedback loops, and concrete templates. The weaknesses are structural: substantial duplicated reliability/compatibility guidance inflating the token budget, and no progressive disclosure, with large harness-specific reference material inlined in the main file.

Suggestions

Deduplicate the subagent reliability guidance: state the wait/back-off, WORKING/BLOCKED signaling, alive-not-silent, and fallback rules once — the compatibility section and the reliability section currently repeat nearly identical paragraphs, and "If a code block below conflicts with this section, this section wins" appears three times.

Move the Codex/OpenCode tool-compatibility table, the multi_agent_v1/v2 routing rules, and the full gate-reviewer spawn prompt template into a referenced bundle file (e.g. references/harness-compat.md and references/gate-reviewer-prompt.md), keeping SKILL.md to the phase workflow and verdict logic.

Trim restatements of the same rule across sections — e.g. the worktree lock/remove teardown and BLOCKED/INCONCLUSIVE handling each appear in both the orchestrator overview and Phase 3 — consolidating them into the phase where the action occurs.

DimensionReasoningScore

Conciseness

The core phases are dense, but the document is noticeably verbose: the Codex compatibility and subagent-reliability sections repeat the same rules multiple times ("If a code block below conflicts with this section, this section wins" appears three times; the back-off/timeout and "fallback only when the child is completed without the deliverable, ack-only after followup, explicitly BLOCKED:, or no longer running" guidance appears nearly verbatim in both the compatibility and reliability sections), padding out roughly a third of the body with duplication.

2 / 5

Actionability

Mostly executable guidance — copy-paste bash auto-collection commands, a complete gate-reviewer prompt template with placeholders, QA matrix and report formats, and concrete worktree commands — but the pivotal reviewer-launch example uses OpenCode `task(...)` syntax that must be translated per the compatibility table, and the web QA path references an external `browser` skill's internals without inline commands.

4 / 5

Workflow Clarity

The five phases are clearly sequenced with explicit validation checkpoints and feedback loops: "Any FAIL ends the review here", artifact-required QA rows, INCONCLUSIVE lane handling with one bounded respawn, teardown ordering ("run `git worktree unlock` followed by `git worktree remove`"), and re-review as a fresh delta-scoped pass — plus an 8-item reviewer checklist.

5 / 5

Progressive Disclosure

The body has reasonable section structure (headers, tables, phase organization) but is a 325-line monolith with no bundle files at all; content that clearly belongs in separate references — the ~58-line harness tool-compatibility table, the subagent reliability rules, and the full spawn-prompt template — is inlined in SKILL.md.

3 / 5

Total

14

/

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 that explicitly states concrete capabilities and clear usage triggers in third person, with an enumerated audit scope. Minor improvements possible by adding natural synonyms (verify, audit, sign off) and sharpening the boundary against plain code-review requests.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "run manual QA on the real surface yourself, then launch ONE gate reviewer (never a panel) to audit goal, constraints, code quality, security, missed context, and QA evidence" — enumerating the full audit scope, which comprehensively covers what the skill does.

5 / 5

Completeness

Both what and when are explicit with concrete trigger phrases: the what is the two-lane QA-plus-gate-review process, and the when is "Use before a PR handoff or when the user explicitly asks to review completed work."

5 / 5

Trigger Term Quality

Good natural keyword coverage ("manual QA", "gate review", "PR handoff", "review completed work"), but common synonyms a user might naturally say — "verify", "audit", "double-check", "sign off" — are missing.

4 / 5

Distinctiveness Conflict Risk

The post-implementation gate-review niche with QA evidence is mostly distinct, but "when the user explicitly asks to review completed work" carries minor overlap risk with generic code-review or PR-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

code-yeongyu/lazycodex

Path

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