CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cross-cat-handoff

跨猫交接与 review 双路由。Use when: 交接、exact-HEAD external PR review task 或 PR tracking。Not for: 自己任务。Output: 足够接手的交接与适用的责任/审查回执。

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/cross-cat-handoff/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 a dense, well-structured protocol document: concrete contracts, named entry points, explicit ordering and fail-closed checkpoints make it highly actionable with clear workflow logic. Its costs are verbosity from repeated constraints across sections and a monolithic all-inline structure with off-bundle references, which cap conciseness and progressive disclosure.

Suggestions

Consolidate the local-review routing rules stated in the Review Entry Mode Classifier, Local Cat Review Return Route, and 常见错误 table into one authoritative section, leaving the error table to one-line pointers, to cut repeated constraints.

Move detailed contract material (Action Successor payload semantics, F246 Phase J, verdict delivery custody) into reference files under references/ and keep SKILL.md as an overview with clearly signaled one-level-deep links.

Break the long multi-clause paragraphs (e.g., the terminalPredicate/expectedOwnerRevision rules) into short bulleted rules so each constraint is scannable and independently enforceable.

DimensionReasoningScore

Conciseness

It earns tokens by assuming domain competence — no space is spent explaining known concepts — but long compound sentences (e.g., the paragraph covering 'terminalPredicate 在公开 schema 中可选...') and constraints restated across multiple sections (local-review routing rules appear in the classifier, the Return Route section, and the common-errors table) could be meaningfully tightened, matching anchor 3 rather than the minor-trim level 4.

3 / 5

Actionability

Concrete guidance dominates: a complete action payload block with named fields, specific entry points ('post_message', 'cross_post_message', 'multi_mention', 'github_record_external_review_verdict'), typed enum values ('approved | changes_requested | commented'), and required-field checklists. Some passages remain directional ('按实际外部条件继续行动或走合法路由') and there is no worked end-to-end example message, keeping it below the copy-paste-ready level 5.

4 / 5

Workflow Clarity

Sequencing is explicit ('必须先跑上面的 author/custody/handoff source 分类,再显式确认 review mode') and validation checkpoints are real — exact HEAD/body SHA locking, verifiable delivery proof URL, read-back to the same subject, and a 自检 section. It falls short of level 5 because the flows are organized as per-scenario contracts rather than one stepwise workflow with explicit error-recovery loops (409/superseded handling lives in a table, not as feedback steps).

4 / 5

Progressive Disclosure

Section headers and tables give the body real structure (pushing above level 2), but it is a ~230-line monolithic file with every detailed contract inlined (Action Successor payload rules, F246 Phase J, verdict delivery custody), and the references it does point to ('../.cat-cafe-shared-refs/shared-rules.md', 'review-notes/') are outside the bundle and do not resolve — matching anchor 3's 'content that should be separate is inline' despite the decent organization.

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 is well-structured with explicit Use when / Not for / Output clauses, giving it strong completeness and a clear niche. Its weaknesses are abstract capability wording ('双路由') and jargon-heavy trigger phrasing inside the description itself, where the natural synonyms live in the separate frontmatter triggers list.

Suggestions

Move one or two natural synonyms (e.g., 'handoff', '传话') from the frontmatter triggers list into the description's 'Use when' clause so the description alone carries the natural keywords.

Replace the abstract 'review 双路由' with the two concrete routing outcomes (external GitHub verdict delivery vs. local author-cat route) to sharpen the what-statement.

Simplify 'exact-HEAD external PR review task' to include a plainer phrase like 'reviewing external PRs' alongside the precise term.

DimensionReasoningScore

Specificity

Names the domain ('跨猫交接与 review 双路由') and a concrete output ('足够接手的交接与适用的责任/审查回执'), but the actions stay abstract — '双路由' names a mechanism without listing the concrete routing actions, so it matches anchor 3 rather than the several-specific-actions level 4.

3 / 5

Completeness

Explicitly answers what ('跨猫交接与 review 双路由... Output: 足够接手的交接与适用的责任/审查回执'), when ('Use when: 交接、exact-HEAD external PR review task 或 PR tracking'), and even when not ('Not for: 自己任务') with concrete trigger phrases, matching the anchor-5 example's structure.

5 / 5

Trigger Term Quality

'交接' and 'PR tracking' are natural terms, but 'exact-HEAD external PR review task' is technical jargon, and common synonyms like 'handoff' or '传话' appear only in the frontmatter triggers list, not the description itself — some relevant keywords but missing common variations, matching anchor 3.

3 / 5

Distinctiveness Conflict Risk

The cross-cat handoff/review-routing niche is clear and the explicit 'Not for: 自己任务' exclusion reduces mis-triggering, but the review and PR-tracking triggers overlap with closely related sibling skills (e.g., request-review), matching 'mostly distinct; minor overlap risk' rather than minimal conflict at 5.

4 / 5

Total

15

/

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: 1 suspicious

Warning

Total

14

/

16

Passed

Repository

zts212653/clowder-ai

Path

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