CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

expert-design

平面设计专家技能包

Quality

57%

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 ./crews/content-producer/skills/expert-design/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%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 well-structured, highly actionable orchestration guide: a gated seven-step workflow with explicit validation checkpoints, a bounded visual-review loop, concrete commands, and environment-specific conventions Claude could not infer. Its only weaknesses are placeholder values in the CSS token spec and per-workflow differences that are referenced but never detailed. Strong result overall.

DimensionReasoningScore

Conciseness

The body is dense and project-specific — a workflow-selection table ("Workflow 清单(按设计任务类型选)"), tool commands, environment conventions ("资源命名约定") that Claude could not know — with no explanations of basic concepts. Minor trimmable redundancy: the "禁止事项(强制)" section restates rules already stated inline at Steps 2/3/6 ("禁止 brief 未确认就动手", "禁止跳过设计系统选取").

4 / 5

Actionability

Concrete executable commands are given (`design-full init <任务名>`, `design-full pick "<风格描述>"`), plus an exact output directory tree, specific breakpoints ("min-width: 768px / 1024px", "375px 基准移动优先"), and required brief fields. Not fully copy-paste ready: the CSS token spec uses placeholder values (`--color-primary: oklch(...)`) and no sample HTML or brief.md content is shown.

4 / 5

Workflow Clarity

The "通用骨架(七步,两闸门)" gives a clearly ordered seven-step sequence with two mandatory gates ("Step 2:Brief 确认(强制闸门)… 确认前不得进后续步骤"; "Step 6:视觉 Review(强制闸门)"), an explicit review checklist, and a bounded feedback loop ("发现偏差 → 调 CSS token 或 HTML 结构后重新输出(最多 3 轮)") — explicit validation, error recovery, and checklists, matching the top anchor.

5 / 5

Progressive Disclosure

The single file is well organized into role / modes / conventions / tools / workflow / tokens / branding sections with clear headers, and no bundle files exist, so the skill is self-contained with no nested references. Minor gap: at ~150 lines covering three workflows, the promised per-workflow differences ("差异只在 brief 必含字段与 Step 4/5") are never elaborated in the body or split into per-workflow reference files.

4 / 5

Total

17

/

20

Passed

Description

20%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 a nine-character title, not a capability description: it names the graphic-design domain but states no concrete actions, no deliverables, and no trigger conditions. Trigger-based selection would rarely fire for the skill's actual tasks (web pages, app UI prototypes, brand visual systems), and the generic domain phrase creates conflict risk with sibling creative skills. This is the weakest part of the skill and the primary improvement target.

Suggestions

Rewrite the description in third person stating concrete deliverables, e.g. 「交付网页/落地页、APP/SaaS 界面原型与品牌视觉体系的设计成品(HTML/CSS)及 DESIGN.md 设计规范。」 — this lifts specificity from 1 toward 4-5 by naming multiple specific actions.

Add an explicit trigger clause equivalent to "Use when…", e.g. 「Use when 用户需要设计网页、落地页、团队介绍页、管理后台/APP 界面原型,或建立品牌色彩/字体/间距/组件规范时。」 — a missing 'Use when' clause currently caps completeness and leaves the 'when' entirely unanswered.

Include natural trigger keywords and synonyms users would actually say (网页设计、落地页、UI 原型、设计系统、品牌规范、视觉规范) and name what is out of scope (单张配图生成、视频) to distinguish this skill from sibling creative skills like awk-img-gen and expert-video, reducing conflict risk.

DimensionReasoningScore

Specificity

The entire description is the noun phrase "平面设计专家技能包" — it names a domain but contains no action verbs, capabilities, or deliverables, matching the anchor "Entirely vague; no concrete actions; pure abstract language". It cannot score 2 because that anchor requires at least minimal or generic actions (e.g. "Processes PDF files"), and none are stated.

1 / 5

Completeness

The phrase provides only a vague 'what' ("平面设计专家技能包" implies design work but states no actions or outputs) and entirely lacks a 'when' / "Use when..." clause. It matches anchor 2 ("vague 'what' and no 'when'"); not 1 because a domain-level 'what' is present, and not 3+ because the missing explicit trigger guidance caps completeness and the 'what' itself is too vague to count as clear.

2 / 5

Trigger Term Quality

Only one generic domain keyword ("平面设计") is present; the natural phrases a user would say for this skill's actual tasks — 网页设计、落地页、APP 界面、品牌视觉 — are all absent. It is above 1 because "平面设计" is a term users naturally say, but below 3 because there are no additional relevant keywords, variations, or synonyms.

2 / 5

Distinctiveness Conflict Risk

The bare phrase "平面设计" (graphic design) is very broad within the creative domain and would plausibly trigger for poster, logo, or single-image requests that the skill body explicitly routes to awk-img-gen or expert-video — high overlap risk with sibling skills. It falls short of 3 because nothing in the description (e.g. no mention of HTML/CSS 成品 or 品牌视觉体系) narrows it below the generic domain term.

2 / 5

Total

7

/

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

description_field

'description' is very short (9 chars), consider making it more detailed

Warning

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

13

/

16

Passed

Repository

TeamWiseFlow/xiaobei

Path

crews/content-producer/skills/expert-design/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.