CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

console-dev

Console 前端交付范式:4 道门禁驱动的前端开发流程。Use when: 新增前端能力、settings section 迁移、新增页面、重构布局、或 F190/Console 级前端流程需要 Product/Design/Implementation/Verification gate。 Not for: 小样式点改、纯后端 API、纯计算逻辑、独立 Design System token 定义。 Output: 通过 Product / Design-System / Implementation / Verification gate 的前端代码与证据。

Quality

86%

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

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 dense, well-sequenced instruction skill: the four-gate workflow has explicit validation checkpoints and a concrete mistakes ledger, and the writing is highly token-efficient. The main defect is that all four external references point to files absent from the bundle, so the disclosure structure cannot actually be navigated.

Suggestions

Ship the referenced files (interaction-narrative.md, design-in-context-checklist.md, f190-frontend-lessons.md) inside the skill's references/ directory, or correct the paths so `../.cat-cafe-shared-refs/` and `docs/architecture/feature-placement.md` resolve from the skill root.

Give Gate 4's screenshot/browser proof one concrete example (e.g. which command or preview flow produces the evidence), since that step currently relies on the sibling browser-preview skill without saying how to invoke it.

Inline a one-line decision summary for docs/architecture/feature-placement.md (or remove the reference) so the L1–L4 entry decision remains actionable when the external file is unavailable.

DimensionReasoningScore

Conciseness

The body is lean and telegraphic with no padding or explanations of concepts Claude already knows — e.g. the Implementation Gate is a bare table ('200 行 | 触发拆分审查', '350 行 | 默认必须拆,除非结构理由写清楚') and Gate 4 is a terse evidence checklist. Every line carries a rule or threshold; it assumes competence throughout.

5 / 5

Actionability

Concrete, executable guidance for an instruction-only skill: specific thresholds ('200 行', '350 行'), named state coverage ('loading / empty / partial / full / error'), explicit migration fields ('Source Behavior / Must Preserve Home Behavior / Decision / Proof'), and a mistakes table with fixes. Falls short of 5 because some guidance stays abstract ('在真实宿主和可信内容态里验证主对象、主动作与状态反馈') and it delegates to referenced files that are not present in the bundle.

4 / 5

Workflow Clarity

The four gates form a clear numbered sequence ('先定入口和状态,再写组件') with an explicit validation section ('必须给证据' checklist covering golden path, non-happy-path state, sibling-page sampling, modal checks, dark/mobile sampling) and a feedback loop in the Common Mistakes table (错误 → 后果 → 修复). This matches the checklist-plus-recovery anchor.

5 / 5

Progressive Disclosure

References are clearly signaled and annotated ('`../.cat-cafe-shared-refs/f190-frontend-lessons.md` — F190 Console intake 的具体案例', '`docs/architecture/feature-placement.md` — Console 入口层级决策树'), but none of the referenced paths resolve — the bundle has no references/ directory and `../.cat-cafe-shared-refs/` and `docs/architecture/` do not exist relative to the skill. Navigation breaks at every external pointer, which is more than a minor organization gap.

3 / 5

Total

17

/

20

Passed

Description

83%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 description: explicit what/when structure with concrete trigger phrases, a clear output statement, and an exclusion list that sharply bounds the skill. The residual gaps are modest — a few missing natural trigger synonyms and no in-description disambiguation from sibling frontend-process skills.

DimensionReasoningScore

Specificity

It lists several specific elements: the four named gates ('Product / Design-System / Implementation / Verification gate'), the deliverable ('通过…gate 的前端代码与证据'), and concrete trigger situations. Not 5 because the 'what' stays at the level of gate names and a paradigm label rather than enumerating the concrete actions each gate performs.

4 / 5

Completeness

It explicitly answers both questions: what ('Console 前端交付范式:4 道门禁驱动的前端开发流程…Output: 通过 Product / Design-System / Implementation / Verification gate 的前端代码与证据') and when ('Use when: 新增前端能力、settings section 迁移、新增页面、重构布局…'), plus an explicit 'Not for' exclusion list. This matches the concrete-trigger-phrase anchor exactly.

5 / 5

Trigger Term Quality

Good natural trigger coverage: '新增前端能力、settings section 迁移、新增页面、重构布局、或 F190/Console 级前端流程'. Not 5 because a few natural phrasings users would say are missing (e.g. component work, UI 改动, 截图/走查 terms); not 3 because the listed terms map directly to how the work is requested.

4 / 5

Distinctiveness Conflict Risk

The niche is clear ('Console 前端交付范式', F190/Console-level flows) and the 'Not for' clause excludes 小样式点改、纯后端 API、纯计算逻辑, lowering conflict risk. Not 5 because the description does not disambiguate against closely related sibling skills the ecosystem clearly contains (tdd, quality-gate, browser-preview, pencil-design), so a generic frontend request could still route to the wrong skill.

4 / 5

Total

17

/

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/console-dev/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.