CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

request-review

Route a change to a non-author local peer when local review is the selected independent validation source. Use when: risk routing chooses a stateful local reviewer for implementation, governance, or semantic context. Not for: cloud as the selected source, vision-guardian acceptance, self-check, or review feedback handling. Output: risk-matched review packet in the current thread/PR; mailbox archive only when the change needs the full packet.

Quality

75%

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 ./cat-cafe-skills/request-review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

70%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 highly actionable, validation-heavy policy document with concrete templates, commands, fail-closed checkpoints, and worked positive/negative examples. Its weaknesses are token-heavy dense prose with incident-specific detail inlined in SKILL.md, and a monolithic structure whose few references point outside the skill bundle.

Suggestions

Move the long edge-case policy blocks (verdict return routing details, the R4 brake sidecar mechanics, the consumption-handle measurement rules) into a references/ file and keep a one-line summary plus link in SKILL.md.

Trim incident-specific asides (e.g., "F320 #5195 两路复审 6 轮") to a single short rationale or move them into a patterns/anti-patterns reference, cutting substantial tokens from the always-loaded body.

Either bring the referenced shared files (delivery-intent-judgment.md, review-request-template.md) into the skill bundle or note their external location explicitly, so the inline links resolve for a reader of the skill.

DimensionReasoningScore

Conciseness

The body assumes Claude's competence (no explanations of git or general concepts) and is dense with real rules, but long run-on paragraphs, repeated caveats, and incident-specific asides ("F320 #5195 两路复审 6 轮", the F100/F311 consumption-handle passage) could be meaningfully tightened — anchor 3, not 4.

3 / 5

Actionability

Provides a fill-in review packet template and concrete executable commands (git status/diff pipelines, `pnpm worktree:new ... --ttl-days 7`, `gh pr comment {N} --body-file`), which is mostly copy-paste ready. It falls short of anchor 5 because some operations defer detail elsewhere (e.g., `worktree:finish` + `--check` syntax lives in the receive-review skill).

4 / 5

Workflow Clarity

The process is clearly sequenced (understand delivery → choose validation source → pre-request evidence → packet depth → sandbox → verdict routing → feedback loop) with explicit validation checkpoints throughout: a BLOCKED-gate evidence table, fail-closed accepted-source re-ack procedure, and an R4-brake pause/recover loop — a direct match for anchor 5.

5 / 5

Progressive Disclosure

Sections are well organized and references are clearly signaled as markdown links, but no bundle files exist and the referenced paths (`../.cat-cafe-shared-refs/...`, `../receive-review/SKILL.md`) sit outside the bundle and do not resolve, while long policy blocks (verdict return routing, R4 brake mechanics) that could be separate reference files are fully inlined — anchor 3 rather than 4.

3 / 5

Total

15

/

20

Passed

Description

71%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 well-structured with an explicit what, when, and not-for boundary that sharply distinguishes it from adjacent review skills. Its main weaknesses are trigger language dominated by internal routing jargon rather than natural user phrasing, and capability coverage that mentions only the routing/packet surface of the skill.

Suggestions

Rewrite the Use-when clause around natural user-side phrasing (e.g., "use when a change needs an independent non-author reviewer before merge") instead of internal terms like "stateful local reviewer" and "risk routing".

Add one or two common trigger variations to the description itself (e.g., "code review", "review my change") so the natural keywords are not confined to the triggers field.

Mention the risk-matched evidence/validation dimension of the output, not just packet delivery, so the capability list is more comprehensive.

DimensionReasoningScore

Specificity

Names several concrete actions — "Route a change to a non-author local peer" and "Output: risk-matched review packet in the current thread/PR; mailbox archive only when the change needs the full packet" — but coverage centers on routing and packet output while the skill's validation/risk-matching mechanics are absent, matching anchor 4 rather than comprehensive anchor 5.

4 / 5

Completeness

Both halves are explicit: a clear what ("Route a change to a non-author local peer") plus an explicit "Use when:" clause and "Not for:" exclusions. It falls short of anchor 5 because the when-condition is phrased in system-routing vocabulary instead of concrete user-facing trigger phrases, but it is well above anchor 3's merely-implicit when.

4 / 5

Trigger Term Quality

The frontmatter triggers field lists natural phrases ("request review", "请 review", "帮我看看"), but the description's own Use-when clause relies on internal jargon ("risk routing chooses a stateful local reviewer") rather than keywords a user would naturally say, missing common variations and synonyms — anchor 3, not 4.

3 / 5

Distinctiveness Conflict Risk

"Not for: cloud as the selected source, vision-guardian acceptance, self-check, or review feedback handling" carves out a clear niche with explicit exclusions of every adjacent capability, giving minimal conflict risk — a direct match for anchor 5.

5 / 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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 3 suspicious

Warning

Total

14

/

16

Passed

Repository

zts212653/clowder-ai

Path

cat-cafe-skills/request-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.