CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

quality-gate

开发完成后的自检门禁:愿景对照 + spec 合规 + 验证。 Use when: 准备对交付作完成声明、需要整理风险匹配的自证。 Not for: 收到 review 反馈(用 receive-review)、merge(用 merge-gate)。 Output: Spec 合规报告(含愿景覆盖度)。

Quality

70%

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/quality-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.

A highly actionable, well-validated gate procedure whose commands, thresholds, and report template are copy-paste ready. Its weaknesses are accretion: retrospective incident narratives, dated revision notes, and redundant tables inflate token cost, and several self-contained policies would live better in the already-existing shared-refs pattern than inline.

Suggestions

Move the incident-history and retrospective blocks (F041 lesson, F209 reflection with Phase B/C stories, PR #1854 counterexample, 2026-03-11 lesson, dated revision notes) into a lessons-learned reference file and keep one-line pointers in the body, recovering the conciseness currently spent on narrative padding.

Consolidate the overlapping rows of the Quick Reference and Common Mistakes tables (e.g., stale-evidence, .pen judgment, and screenshot-vs-runtime rows appear in both) into a single table to cut redundancy.

Extract the Step 2.5 close-gate policy (keyword list, exemptions, cvo_signoff checklist) and the Step 4.5 dogfood scope/why/report spec into referenced files like the existing ../.cat-cafe-shared-refs pattern, leaving the flow steps as short pointers.

DimensionReasoningScore

Conciseness

The body is noticeably verbose: inline incident history and dated retrospectives ("F041 教训", "F209 反思 2026-05-23", "2026-03-11 教训:三只Ragdoll同时跳过了...", "反例 PR #1854", revision notes like "2026-07-15 修订") are narrative padding a reader does not need to execute the gate, and the rubric explicitly penalizes time-sensitive dates outside a dedicated section. Per the anti-drift check it is above anchor 1 (the bulk is real operational instruction, not general-concept explanation) but clearly below anchor 3, where only 'some' tightening would be needed — several whole sections are retrospective rather than instructional.

2 / 5

Actionability

The body is fully executable: copy-paste-ready commands ("curl -sf http://localhost:3004/health", "git status --short | rg '^.. [^/]+\.(png|jpe?g|webp|...)'", "node scripts/check-hotfix-pattern.mjs", "pnpm --filter @cat-cafe/api test:redis"), a complete fill-in Quality Gate Report template, concrete dogfood example paths, and explicit decision rules with exact thresholds ("≥3 层 fallback 或累计 ≥5 层"). This matches the 'fully executable; copy-paste ready commands; specific examples cover common cases' anchor.

5 / 5

Workflow Clarity

The Step 0→8 sequence has explicit validation checkpoints (Step 7 read output/exit code, BLOCK conditions in Step 2.5/7.5) and genuine feedback loops ("Gate 未通过时:P1 遗漏 → 补完再过 gate", dogfood bugs "必须当轮修"), plus a STOP red-flags list — above anchor 4's 'most checkpoints' and near anchor 5. It falls short of 5 because the accreted sub-step numbering (0, 0.5, 2.5, 2.6, 2.7, 4.5, 7.5) and Step 2.5's long conditional-scope preamble make the actual control flow genuinely hard to follow on first read, which is a sequencing clarity defect rather than a missing validation.

4 / 5

Progressive Disclosure

There is real structure (## 流程, ## Quick Reference, ## Common Mistakes, ## 和其他 skill 的区别) and several clearly signaled one-level-deep references with explicit paths ("../.cat-cafe-shared-refs/close-gate.md", "../.cat-cafe-shared-refs/evidence-output-contract.md", "../.cat-cafe-shared-refs/vision-evidence-workflow.md", "docs/ops/testing-standard.md"), but no bundle files ship with the skill and large self-contained policies (the whole dogfood scope/why/report spec, close-gate matrix, fallback-layer rules) are inlined in the ~290-line body where anchor 3's 'content that should be separate is inline' applies. It is below anchor 4 because the split-out that has happened is only partial.

3 / 5

Total

14

/

20

Passed

Description

66%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 well-structured description with an explicit what/when/not-for split and excellent sibling-skill disambiguation. Its main weakness is that the capability list is abstract shorthand whose meaning depends on the body, and the natural trigger phrases live in the frontmatter triggers list rather than the description text.

Suggestions

Expand the capability shorthand into 3-4 concrete actions in the description itself (e.g., '回读原始需求核对 AC 覆盖、走通完整使用旅程、运行风险匹配的验证命令、输出合规报告'), so specificity does not depend on body context.

Fold one or two of the most natural trigger phrases from the triggers list (e.g., "准备 review", "开发完了") into the 'Use when' clause so the description alone carries natural keywords.

DimensionReasoningScore

Specificity

The description names the domain ("开发完成后的自检门禁") and a short list of actions ("愿景对照 + spec 合规 + 验证") plus a concrete output ("Spec 合规报告(含愿景覆盖度)"), but the actions are one-word abstractions rather than fully concrete capabilities, matching the 'domain plus 1-2 concrete actions, not comprehensive' anchor. It is above anchor 2 (which would name the domain with only generic actions) because three named checks and an explicit output artifact are stated.

3 / 5

Completeness

Both parts are present: what it does ("自检门禁:愿景对照 + spec 合规 + 验证", with a stated output artifact) and when to use it ("Use when: 准备对交付作完成声明..."), plus a 'Not for' clause routing to sibling skills. It falls short of anchor 5 because the 'what' is compressed jargon (e.g., "愿景对照", "风险匹配的自证") whose concrete meaning only becomes clear in the body, and the trigger phrases in the description are fewer and less natural than the frontmatter triggers list.

4 / 5

Trigger Term Quality

The description's 'Use when' clause offers phrases like "准备对交付作完成声明" and "需要整理风险匹配的自证", and sibling disambiguation names (receive-review, merge-gate), but natural user-side variations and synonyms are sparse; richer natural triggers exist only in the separate frontmatter 'triggers' list, not in the description itself. This sits at 'some relevant keywords but missing common variations', below anchor 4 where good coverage with only a few gaps would be present.

3 / 5

Distinctiveness Conflict Risk

The description carves out a clear niche (author self-check before a completion claim) and explicitly routes adjacent situations away: "Not for: 收到 review 反馈(用 receive-review)、merge(用 merge-gate)". This is exactly the 'clear niche with distinct triggers; minimal conflict risk' anchor — sibling-skill confusion is preemptively resolved inside the description itself.

5 / 5

Total

15

/

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

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 1 suspicious

Warning

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

13

/

16

Passed

Repository

zts212653/clowder-ai

Path

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