CtrlK
BlogDocsLog inGet started
Tessl Logo

design-full

平面设计全案——完整网页/落地页、APP/产品界面、品牌视觉体系。从需求 brief 到设计系统选取、素材获取、HTML/CSS 编写、视觉 review、交付归档的完整工作流。接到"做网页/落地页/APP 界面/品牌视觉"类平面设计需求时走本技能。

68

Quality

85%

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

77%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-sequenced, actionable workflow with strong validation gates and feedback loops. Its main weaknesses are mild Step 4/5 repetition across sub-workflows and a progressive-disclosure gap where the referenced design-system library files are missing from the bundle.

Suggestions

Add the actual design-systems/ directory with index.json and the per-system .md files the body references, or move the 14-row library table into a single referenced file so references resolve to real bundle files.

De-duplicate Step 4/5 guidance: state it once in the main workflow and have sub-workflow A reference it instead of repeating the CSS-token / semantic-tag / responsive / hover bullet list verbatim.

Replace the placeholder oklch(...) values in the CSS token example with concrete sample tokens (or label the block explicitly as a template) so the example is copy-paste executable.

DimensionReasoningScore

Conciseness

Largely efficient and assumes Claude's knowledge of HTML/CSS/responsive design, but Step 4/5 guidance is repeated almost verbatim in sub-workflow A, which is trimmable padding that keeps it just below the lean 5 anchor.

4 / 5

Actionability

Provides concrete executable commands (design-full init/pick), real scripts, a directory tree, a brief template, and a CSS custom-properties block, but the CSS example uses placeholder oklch(...) values rather than copy-paste-ready tokens, leaving a minor gap below the fully-executable 5 anchor.

4 / 5

Workflow Clarity

A clear 7-step sequence with two explicit强制 gates (brief confirmation, visual review), a feedback loop (偏差 → 调整 → 重输出,最多 3 轮), and a final 禁止事项 checklist matches the anchor requiring explicit validation steps, error-recovery loops, and checklists.

5 / 5

Progressive Disclosure

Sections are well-organized and the script references resolve to real files, but the 14-system library table is bulk content inlined in the body and the referenced separation target (design-systems/<name>.md and design-systems/index.json) does not exist in the bundle, which is more than the minor gap allowed by the 4 anchor.

3 / 5

Total

16

/

20

Passed

Description

92%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 strong: it states concrete capabilities, gives an explicit use-when trigger in natural user language, and carves out a distinct niche. Its only weakness is trigger-term breadth — one compound phrase rather than a comprehensive set of synonyms and file extensions.

DimensionReasoningScore

Specificity

Names the domain and lists multiple concrete capabilities (完整网页/落地页、APP/产品界面、品牌视觉体系) plus a comprehensive workflow (brief → 设计系统选取 → 素材获取 → HTML/CSS 编写 → 视觉 review → 交付归档), matching the comprehensive-coverage anchor rather than the 4 anchor which allows minor gaps.

5 / 5

Completeness

Explicitly answers both 'what' (the three design scopes and full workflow) and 'when' with a concrete trigger clause, matching the anchor that requires clearly explicit answers to both with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural user phrasing ('接到"做网页/落地页/APP 界面/品牌视觉"类平面设计需求时走本技能') giving good keyword coverage, but is a single compound trigger without synonyms or file extensions, so it falls short of the comprehensive 5 anchor.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (full-stack flat/visual design for web, UI, and brand) with distinct triggers and explicit non-applicability (video work excluded), giving minimal conflict risk per the clear-niche anchor.

5 / 5

Total

19

/

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.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository
TeamWiseFlow/xiaobei
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.