CtrlK
BlogDocsLog inGet started
Tessl Logo

tessl/code-review-setup

Install Tessl Code Review into a GitHub repository. Inspects the repository's existing workflows and any Code Review caller already present, asks the two setup questions (when reviews run, and whether findings block the merge), then writes or updates a thin caller workflow that invokes the Tessl Code Review Action. Use when someone wants to add, set up, enable, configure, update, or remove Tessl Code Review, AI code review, or automated pull-request review in a repository, or asks to switch it between advisory and gate mode.

87

0.94x
Quality

97%

Does it follow best practices?

Impact

72%

0.94x

Average score across 5 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

Overview
Quality
Evals
Security
Files

Quality

Content

92%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 well-structured, actionable procedure with explicit sequencing, a validation checkpoint, and clean progressive disclosure to real reference files. It is slightly verbose in a few justificatory passages but otherwise every token earns its place.

Suggestions

Tighten the 'Who may request a round' and mention-guard passages, which restate the same trade-off (privileged round spends credits) twice; collapse to one statement plus the alternatives.

The 'Customizing the review itself' section repeats the profile/lenses framing already given in phase 2; consider merging to avoid restating the routing mechanism.

DimensionReasoningScore

Conciseness

Generally efficient and assumes Claude's competence, focusing on non-obvious domain knowledge (Action-vs-repo ownership, fork traffic, gate semantics) rather than basics; a few justificatory passages (e.g. 'Who may request a round') repeat their rationale and could be tightened.

4 / 5

Actionability

Provides concrete, executable guidance: real `gh api` commands for resolving a pinned SHA, an exact YAML-parse validation command, named inputs (mode, profile, lenses, approver-logins, allowed-associations), and a target file path covering the common install/update cases.

5 / 5

Workflow Clarity

Six phases are explicitly sequenced with 'Do not write any file before phase 4', a dedicated Verify phase with a checklist, and feedback loops (stop-and-ask when a SHA won't resolve, surface conflicts rather than overwrite) for the destructive write operation.

5 / 5

Progressive Disclosure

Body is a clear overview pointing one level deep to real, well-signaled reference files (interview.md, file-profiles.md, workflow-templates.md, operations.md) via markdown links, keeping bulk template content out of the main file; all referenced paths exist in ./references/.

5 / 5

Total

19

/

20

Passed

Description

100%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 exemplary: third-person voice, concrete actions, comprehensive natural trigger terms, and an explicit 'Use when...' clause covering both what and when. It is specific to its niche with negligible conflict risk.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Install or update', 'writing a thin caller workflow', 'Inspects existing workflows', 'asks when reviews should run and whether findings should block', 'proposes the change', 'only writes after explicit approval' — with comprehensive coverage.

5 / 5

Completeness

Explicitly answers what (install/update a caller workflow with inspect/ask/propose/write steps) and when (explicit 'Use when...' clause with concrete trigger phrases), satisfying the top anchor.

5 / 5

Trigger Term Quality

Comprehensive natural trigger coverage with synonyms: 'add, set up, enable, configure, update, or remove', 'AI code review', 'automated pull-request review', 'advisory and gate mode' — terms a user would naturally say.

5 / 5

Distinctiveness Conflict Risk

Clear niche scoped to Tessl Code Review with product-specific triggers ('advisory and gate mode', 'Tessl Code Review'), minimal overlap risk with other skills.

5 / 5

Total

20

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents