CtrlK
BlogDocsLog inGet started
Tessl Logo

setup-code-review

Install or update Tessl Code Review in a GitHub repository by writing a thin caller workflow that invokes the Tessl Code Review Action. Inspects existing workflows and any Code Review caller already present, asks when reviews should run and whether findings should block the merge, proposes the change, and only writes after explicit approval. 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 wants to switch it between advisory and gate mode.

85

0.94x
Quality

92%

Does it follow best practices?

Impact

72%

0.94x

Average score across 5 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

The canonical home for this skill is tessl/code-review-setup

SKILL.md
Quality
Evals
Security

Quality

Content

85%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, procedure-driven skill with a clear six-phase workflow, concrete executable commands, explicit validation checkpoints, and clean progressive disclosure into real reference files. Its main weakness is mild verbosity in a few policy-rationale passages that could be tightened.

Suggestions

Tighten the 'Who may request a round' paragraph in phase 3 — it restates the allowlist rationale at length; the one-line trade-off plus the pointer to workflow-templates.md would carry the same content with fewer tokens.

Compress the approver-logins handling across phases 1, 2, and 6 into a single condensed statement plus the existing reference, since the same policy is explained in three places.

Inline one minimal caller-workflow template excerpt (or a fenced skeleton) so phase 4's 'take the template' instruction is actionable without opening the reference, narrowing the actionability gap.

DimensionReasoningScore

Conciseness

Largely efficient and assumes Claude's competence (no explanation of GitHub Actions or YAML), but a few passages run long and restate policy rationale — e.g., the 'Who may request a round' paragraph and the approver-logins handling — which could be trimmed.

4 / 5

Actionability

Provides concrete executable commands (the gh api release/SHA resolution chain, the YAML-parse one-liner, the exact permissions block) with mostly complete guidance; minor gaps exist because the actual workflow templates live in a reference file rather than inline.

4 / 5

Workflow Clarity

Six explicitly sequenced phases with a hard 'Do not write any file before phase 4' rule, a dedicated Verify phase containing a real parser command and checklist, and explicit feedback loops ('stop and ask' if no release resolves) for a destructive/write operation.

5 / 5

Progressive Disclosure

A concise overview body points to four well-signaled, one-level-deep reference files (interview, workflow-templates, operations, file-profiles), each a real file covering a distinct concern, with content appropriately split and easy navigation.

5 / 5

Total

18

/

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.

A strong, specific, third-person description that names concrete actions, supplies natural trigger phrases, and explicitly covers both what the skill does and when to invoke it. It is highly distinct and unlikely to trigger for the wrong skill.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'writing a thin caller workflow that invokes the Tessl Code Review Action', '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 both 'what' (install/update a caller workflow via inspect, ask, propose, write-after-approval) and 'when' with a concrete 'Use when...' clause listing multiple trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural trigger terms a user would actually say — 'add, set up, enable, configure, update, or remove', 'AI code review', 'automated pull-request review', 'switch it between advisory and gate mode' — including synonyms and variations.

5 / 5

Distinctiveness Conflict Risk

A clearly named product ('Tessl Code Review') scoped to a GitHub repository via a caller workflow gives it a distinct niche with minimal overlap risk against 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.

Repository
tesslio/product-plugins
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.