CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

huashu-design

设计哲学顾问,从20种风格中推荐3个方向并生成视觉Demo和AI提示词。当用户提到"设计风格"、"设计方向"、"配色方案"、"视觉风格"、"设计评审"、"推荐风格"时使用。

Quality

82%

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

SKILL.md
Quality
Evals
Security

Quality

Content

71%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 well-structured, highly actionable skill body with excellent progressive disclosure — real, well-signaled reference files and concrete commands, formats, and numeric constraints. Its weaknesses are token efficiency: a promotional footer, a duplicated prohibition rule, and an under-specified Phase 6.

Suggestions

Remove the promotional footer (花叔出品 / 公众号 / 粉丝数 / 代表作) — it consumes tokens with no instructional value for executing the skill.

State the 赛博霓虹/#0D1117 prohibition once (e.g., only in User Preferences) instead of duplicating it in Phase 5, and reference the single location from Phase 5.

Either expand Phase 6 (生成AI提示词后的迭代优化) with concrete steps like Phase 1-5 have, or fold it into Phase 5; also link `references/scene-templates.md` from the workflow body (e.g., in Phase 3 or Phase 5) since it is currently reachable only via the References Library table.

DimensionReasoningScore

Conciseness

The body is mostly efficient prescriptive tables and rules that assume Claude's competence, but it carries unnecessary tokens: the promotional footer (「花叔出品 | 公众号「花叔」| 30万+粉丝…」), the 赛博霓虹/#0D1117 prohibition stated twice (Phase 5 and User Preferences), and preference items unrelated to the skill's operation. More than 'minor instances of over-explanation', so below the 4 anchor.

3 / 5

Actionability

Concrete, executable guidance throughout: the Playwright screenshot command with viewport flags, demo file naming under `_temp/design-demos/`, a defined prompt structure ([设计哲学约束]+[内容描述]+[技术参数]) with #HEX values, and numeric constraints (100-200字, 3-4条). Phase 6 (「变体建议 / 平台优化 / 混合实验」) is a thin exception that keeps it from fully copy-paste-ready coverage.

4 / 5

Workflow Clarity

Phases 1-7 are clearly sequenced with explicit feedback loops — Phase 4 enumerates the 选方向/混合/微调/重来 branches and Phase 7 produces a severity-tagged fix list with a 5-minute quick-win prioritization. No destructive or batch operations are involved, so no validation cap applies; the under-specified Phase 6 is the minor gap.

4 / 5

Progressive Disclosure

A clear overview with well-signaled, one-level-deep references: all three files in the References Library table (design-styles.md, scene-templates.md, critique-guide.md) exist in the bundle and match their descriptions, each row states both content and when to read it (「读取时机」), and the 20-style detail is correctly externalized rather than inlined. The only nit is that scene-templates.md is referenced only in the table, never in the workflow body.

5 / 5

Total

16

/

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: concise, third-person, concrete about what it does, and with an explicit 'use when' clause listing six natural trigger phrases. The only shortfalls are the unlisted critique capability and a few missing natural trigger variations.

DimensionReasoningScore

Specificity

States several concrete actions —「从20种风格中推荐3个方向」「生成视觉Demo」「AI提示词」— in third person with no vague padding. Minor gap: the design-critique capability implied by the trigger「设计评审」is not listed in the 'what' clause, so coverage is not comprehensive.

4 / 5

Completeness

Explicitly answers both questions: the 'what' (recommend 3 of 20 styles, generate visual demos and AI prompts) and an explicit 'use when' clause with six concrete trigger phrases (「当用户提到…时使用」). This matches the anchor 'clearly and explicitly answers both what AND when with concrete trigger phrases'.

5 / 5

Trigger Term Quality

Six natural phrases a user would actually say (「设计风格」「设计方向」「配色方案」「视觉风格」「设计评审」「推荐风格」), including synonym pairs (设计/视觉风格). A few common variations like 排版、海报、PPT美化 are missing, which keeps it below the comprehensive-coverage anchor.

4 / 5

Distinctiveness Conflict Risk

A clear niche (design-philosophy direction selection with named triggers) that is mostly distinct; only minor overlap risk with generic visualization or general design skills sharing terms like「视觉风格」.

4 / 5

Total

17

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

alchaincyf/huashu-skills

Path

huashu-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.