CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

merge-gate

合入 main,消费风险匹配的验证与适用的 review 证据。Use when: 准备合入 PR。 Not for: 未完成作者自检、处理 review findings 或 Feature 终态验收。 Output: 产品快车道的作者自验或风险要求的独立 review,加受影响检查支撑的合入证据与结果。

Quality

72%

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

Quality

Content

63%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 exceptionally actionable, with real commands, explicit fail-closed validation gates, and well-worked error-recovery paths — top marks on execution guidance. It is severely let down by token efficiency and file structure: the same governance rules are duplicated across many sections, dated incident narratives are embedded in normative text, and large self-contained topics that belong in reference files are all inlined in a ~770-line monolith with no bundle files at all.

Suggestions

Move self-contained topics — 浏览器验证政策, 判例 #4152/#4163, remote review QA (Q1-Q4), and the reviewer downgrade table — into reference files under references/ and keep only a one-line pointer plus the operative rule in SKILL.md.

Consolidate the continuity rules currently restated in Review Provenance Matrix, Evidence Manifest, Evidence Validation Checker, Quick Reference, and Common Mistakes into one canonical section, leaving the others as short pointers; extract the multi-hundred-word 'stale' table cell into its own subsection.

Relocate dated incident history (PR #1300, #160, #2214, F168 opus5 gate 实录, specific main SHAs) into a dedicated '历史判例 / old patterns' section so time-sensitive details stop inflating the normative text.

DimensionReasoningScore

Conciseness

At ~770 lines, the body restates the same continuity/provenance rules across five or more sections (Provenance Matrix, Evidence Manifest, Evidence Validation Checker, Quick Reference, Common Mistakes) and weaves dated incident history ('2026-04-20 PR #1300 确认', '2026-09-20 opus5 六次 gate 实录', main SHA 'a3aa1ceded') into normative text, plus multi-hundred-word prose inside single table cells (the 'stale' row). This matches 'noticeably verbose; several unnecessary explanations or padded sections'; not 1 because almost none of it explains concepts Claude already knows — it is genuinely project-specific policy, just far over token budget and heavily duplicated.

2 / 5

Actionability

The guidance is fully executable: real shell commands for PR creation (HEREDOC body), body-handle guards with rg patterns, hotfix detection with jq parsing and fail-closed exits, classify-merge-outcome.mjs with explicit tri-state exit-code case handling, worktree finish/inventory invocations, and worked pass/fail output examples for evidence validation. This matches the 'fully executable; copy-paste ready commands covering common cases' anchor.

5 / 5

Workflow Clarity

The merge pipeline has explicit validation checkpoints (E1-E5 hard conditions with BLOCKED failure actions) and genuine error-recovery feedback loops (re-validate after doc fix, pending-vs-failure merge exit triage, re-run check-feature-truth after post-merge sync), plus checklists. Not 5 because the step sequence is incoherent in places: Step 7.5a executes before Step 7 in the command block, and Steps 0, 5.1, and 6.1 are referenced but never defined anywhere in the document.

4 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent), so everything — browser verification policy, remote-review QA, precedent case studies #4152/#4163, reviewer downgrade matrices — is inlined in one monolithic SKILL.md. External references (../.cat-cafe-shared-refs/pr-template.md, pr-signals.md, sop-definitions/development.yaml) are clearly signaled, which keeps this at 'some structure but content that should be separate is inline' rather than the 'minimal structure' anchor 2.

3 / 5

Total

14

/

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 explicitly answers what, when, and what-not-for, and its 'Not for' clause gives it strong distinctiveness against sibling skills. Its main weaknesses are thin natural-language trigger coverage (a single 'Use when' phrase) and heavy internal jargon that makes the listed capabilities less concrete to an unfamiliar reader.

Suggestions

Expand the 'Use when' clause with 2-3 concrete trigger phrases users would naturally say (e.g. 'merge', '开 PR / 合 PR', 'squash merge', 'gh pr merge') instead of the single '准备合入 PR'.

Replace internal shorthand in the what/Output statements (e.g. '消费风险匹配的验证', '产品快车道') with plainer capability verbs so the concrete actions (select validation, obtain independent review, assemble merge evidence) read clearly to a first-time user.

DimensionReasoningScore

Specificity

The Output clause lists several distinct concrete actions (作者自验, 独立 review, 受影响检查, 合入证据), matching the 'several specific actions; minor gaps' anchor. Not 5 because the actions are wrapped in dense internal jargon ('消费风险匹配的验证与适用的 review 证据') that blurs what is concretely done.

4 / 5

Completeness

Both what ('合入 main,消费风险匹配的验证与适用的 review 证据' plus an Output line) and when ('Use when: 准备合入 PR') are explicitly present, with bonus 'Not for' exclusions. Not 5 because the when-clause is a single terse trigger phrase rather than a set of concrete trigger phrases; not 3 because the Use when guidance is explicit, so no cap applies.

4 / 5

Trigger Term Quality

The description contains some natural keywords ('合入 main', '准备合入 PR') but misses common variations and synonyms a user would say ('merge', '开 PR', 'squash merge', '合 PR'). Fits the 'some relevant keywords but missing common variations' anchor; not 4 because synonym coverage is thin within the description text itself.

3 / 5

Distinctiveness Conflict Risk

'Not for: 未完成作者自检、处理 review findings 或 Feature 终态验收' explicitly demarcates the neighboring quality-gate / receive-review / feat-lifecycle skills, and '合入 main' is a distinct niche trigger with minimal conflict risk. This matches the 'clear niche with distinct triggers' anchor; the explicit exclusion clause is what lifts it above the 'minor overlap risk' anchor 4.

5 / 5

Total

16

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (787 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

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

Warning

referenced_paths_exist

Referenced path issues: 14 missing, 2 deeper-than-1-level

Warning

Total

13

/

16

Passed

Repository

zts212653/clowder-ai

Path

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