CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

design-brand-identities

为组织、产品、服务、场所、文化项目或个人创建、编辑、扩展、迁移或诊断品牌识别,交付一组以假乱真的品牌示例(官网首屏、门店、包装、名片、社媒等最终效果)和一个示例级品牌工具包文件夹(标志方向、色表、字体建议、图像调子、信息要素、参考设计、指南),让用户直接看到品牌做出来是什么样。用于名称与字标、图形标、核心识别、应用系统、品牌架构、焕新迁移与动态身份;强调最小系统、一致性与真实感。不用于单个功能图标、完整字体工程、一次性营销画面或把精致网页当作品牌本身。

70

Quality

88%

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

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.

A tightly engineered process manual: every phase has a gate, a template, and a failure path, and all referenced bundle files exist one level deep with clear read-on-demand signals. The two drag factors are deliberate-feeling repetition of the same prohibitions across four sections and a ~360-line body where some tables could live in references.

Suggestions

Consolidate the code-drawn-logo / route-violation prohibitions (currently stated in §2 结构候选, §2 图像来源纪律, the §3 routing table, and §6) into a single normative list referenced from each decision point, cutting repeated tokens without losing enforcement.

Move the font-selection table (§2) and possibly the 档位 tier table into a reference file (e.g., references/kit-skeleton.md or a type-spec reference), keeping only the routing rule in the body, to shorten the always-loaded SKILL.md.

Inline the minimal command syntax for image_generate / render_file (currently delegated to ../build-polished-visual-frontends/references/assets-and-imagegen.md) so the skill's primary production loop is executable without a cross-skill read.

DimensionReasoningScore

Conciseness

The body is dense and operational — no padding explaining concepts Claude already knows, and nearly every sentence is a rule, template, or gate. However, the same route-violation prohibitions ("不许用代码画标志 / 圆弧公式重建") are repeated across §2, the §3 routing table, §6, and §8, and the 生成层 rules likewise recur, so it is more than minor tightening away from lean.

4 / 5

Actionability

Concrete, executable guidance throughout: copy-ready YAML templates (decision card, REFERENCE-CONTRACT, 最小系统合同), a deliverable→technique→anti-pattern routing table with exact tools and parameters ("image_generate(images=[...]) 最多 6 张", "render_file(output_dir=proof/probe, motion_mode=static)", "potrace / vtracer"), a font table with npm packages, and a KIT-MANIFEST line format. Minor gaps: exact image_generate prompt syntax and validation commands are deferred to external shared-skill references not included here.

4 / 5

Workflow Clarity

Exemplary sequencing with explicit validation checkpoints: 第零步 tier translation and reference-route gate before any generation, a font probe gate ("探针失败就停下修字体…不允许'先用系统字体做完再说'"), an asset-layer gate before example frames, an ordered pixel-check cascade for the defining frame with a failure loop ("B7 与 B1 不成立时重生成或回到最小系统合同"), stop-and-refactor signals (§6), five named rework tests (§7), and a full completion checklist (§8) with planned→built→verified states.

5 / 5

Progressive Disclosure

All seven in-body reference paths (references/patterns.md, kit-skeleton.md, implementation-routing.md, tool-profiles.md, brand-examples/INDEX.md + page-1.jpg, brand-kits/page-1.jpg) resolve to real files, are one level deep, and are clearly signaled with on-demand conditions ("按需读取", "本节只给路由结论"). The main body runs ~360 lines with the font-selection and tier tables inlined, which is defensible core decision content but keeps it short of a truly minimal overview-plus-references split.

4 / 5

Total

17

/

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.

A strong description: concrete verbs, fully enumerated deliverables, an explicit 'used for' trigger clause, and explicit exclusions that sharply bound the skill's territory. The only gap is a few high-frequency synonyms (logo, VI, 视觉识别) that users commonly say when they need this skill.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions ("创建、编辑、扩展、迁移或诊断品牌识别") and enumerates the exact deliverables both for the example set ("官网首屏、门店、包装、名片、社媒等最终效果") and the toolkit folder ("标志方向、色表、字体建议、图像调子、信息要素、参考设计、指南"), giving comprehensive coverage of what the skill produces.

5 / 5

Completeness

It explicitly answers both questions: what it does ("创建、编辑、扩展、迁移或诊断品牌识别,交付…品牌示例…和一个示例级品牌工具包文件夹") and when to use it ("用于名称与字标、图形标、核心识别、应用系统、品牌架构、焕新迁移与动态身份"), plus explicit negative triggers ("不用于单个功能图标、完整字体工程、一次性营销画面").

5 / 5

Trigger Term Quality

Good coverage of natural terms users would say: "品牌识别", "字标", "图形标", "品牌架构", "焕新迁移", "包装", "名片", "社媒". A few common synonyms are missing — users often say "logo", "VI", "视觉识别", "品牌设计", or "branding", none of which appear.

4 / 5

Distinctiveness Conflict Risk

Clear niche (brand identity systems) with explicit disambiguation from adjacent skills: "不用于单个功能图标、完整字体工程、一次性营销画面或把精致网页当作品牌本身" separates it from icon, font-engineering, marketing, and web-frontend skills, minimizing wrong-skill triggering.

5 / 5

Total

19

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 4 missing, 3 deeper-than-1-level

Warning

Total

15

/

16

Passed

Repository

EverMind-AI/Raven

Path

plugins-dist/design-engine/raven_design/skills/design-brand-identities/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.