CtrlK
BlogDocsLog inGet started
Tessl Logo

brand-design-guide

海岚旅行品牌与内容设计规范(HL-MKT-GUIDE-07 V2.1):标志、色彩、字体、版面,方案 PPT 的内容规法、合格方案的设计语言(要这样、不要这样)和设计元素库(品牌母题、审定图标、组件、单页版式),附品牌手册 brand-kit.pptx。

63

Quality

74%

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

Fix and improve this skill with Tessl

tessl review fix ./experimental/simulation/scenarios/travel_agency/materials/brand-design-guide/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 disciplined, example-rich specification that gives exact values and named assets for every rule and closes with a three-question self-check — strong on actionability and token efficiency. Its weaknesses are the inlined version-history changelog and a dangling reference to brand-kit.pptx, which the description and body both promise but which is absent from the bundle.

Suggestions

Ship the referenced brand-kit.pptx (or move its five pages into a references/ file) so the promised 品牌手册 and template pages actually resolve, or remove the reference.

Move the V2.0/V2.1 change history and effective date out of the opening paragraph into a short "版本记录" section so version-sensitive text doesn't sit in the main guidance.

Add a brief explicit procedure (e.g., 1) pick template page → 2) write conclusion-style titles → 3) fill components from the element library → 4) run 自检三问) so the production workflow reads as one ordered process with the existing validation checkpoint at the end.

DimensionReasoningScore

Conciseness

The body is lean and information-dense — exact hex values, point sizes, named fonts with fallbacks, and a do/don't table with no filler and no explanations of concepts Claude already knows, which sits above anchor 3. It falls short of 5 because time-sensitive version information is inlined in the opening paragraph ("V2.1,2026年9月25日起执行…V2.0:品牌视觉更新…V2.1:新增设计元素库") rather than being confined to a changelog/deprecated section, which the guidelines penalize.

4 / 5

Actionability

For an instruction-only skill the guidance is fully concrete and executable: exact colors with proportions ("柿红 #D9531E…不超过一成"), exact type scale ("页面标题 28 至 32 磅…行距 1.3 至 1.4"), fallback fonts, named Tabler icons per category ("train 高铁;plane 航班…"), component specs, and worked do/don't title examples ("写'几天几晚加这趟行程的节奏'…不写'行程概览'"). It matches anchor 5: specific examples cover the common cases with copy-paste-ready values.

5 / 5

Workflow Clarity

The production path is implicitly sequenced (start from the template pages "内容需要时从对应的模板页开始", apply the content rules and element library, compare against the 要这样/不要这样 table) and ends with an explicit validation checklist ("交付前,顾问对照三问看一遍"). It matches anchor 4 (clear sequence with most checkpoints) rather than 5 because the steps are distributed across sections rather than given as one explicit ordered procedure, and there is no error-recovery loop; it is not 3 since a concrete pre-delivery validation checkpoint is present and no destructive/batch operation applies.

4 / 5

Progressive Disclosure

Within SKILL.md the organization is clean (eight numbered sections, tables for colors, icons, and components), but the only bundle reference — "本目录下的 `brand-kit.pptx` 是品牌手册" — does not resolve: no references/, scripts/, or assets/ directories exist and no brand-kit.pptx is present in the bundle, so a quarter of the skill's promised material (the five-page manual and the templates it contains) is unavailable. This matches anchor 3 (structure present, references not properly backed) rather than 4, where references are expected to be real and clearly navigable.

3 / 5

Total

16

/

20

Passed

Description

70%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 dense, highly specific description that names the domain and its concrete sub-artifacts well and is unmistakably distinct (company-specific brand guide with a document number). Its main weakness is the complete absence of any "Use when..." trigger clause, which caps completeness, and trigger coverage lacks natural synonyms beyond the core brand terms.

Suggestions

Add an explicit trigger clause, e.g. "制作或修改海岚旅行的方案 PPT、检查方案是否符合品牌规范、选用品牌颜色字体图标时使用本规范" (Use when creating/reviewing Hailan Travel proposal PPTs or applying brand colors, fonts, or icons).

Include natural user-facing synonyms such as 品牌手册、视觉规范、风格指南、PPT 排版/美化 alongside "设计规范" so more phrasings match.

State the skill's action explicitly (e.g., "对照规范检查/制作方案 PPT") rather than only listing the topics it covers.

DimensionReasoningScore

Specificity

The description enumerates concrete, specific content areas: "标志、色彩、字体、版面", "内容规法", "合格方案的设计语言(要这样、不要这样)", and "设计元素库(品牌母题、审定图标、组件、单页版式)", plus the attached brand manual ("附品牌手册 brand-kit.pptx"). It matches anchor 4 (several specific items, minor gaps) rather than 5 because it indexes topics/artifacts rather than stating the concrete actions the skill performs (e.g., apply/review/check proposals).

4 / 5

Completeness

The "what" is clear and concrete (a brand and content design specification covering logo, colors, fonts, layout, content rules, do/don't language, an element library, plus brand-kit.pptx), but the "when" is entirely absent — there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It is not a 4 because nothing even weakly implies the activation conditions.

3 / 5

Trigger Term Quality

Natural trigger terms are present: "品牌" (brand), "设计规范" (design guidelines), "色彩" / "字体" (colors/typography), "方案 PPT" (proposal PPT), "标志" (logo) — a user asking about brand style, PPT styling, or proposal design would plausibly say these. Not a 5 because common synonyms and variations are missing (e.g., 品牌手册/视觉规范/风格指南, "deck", "排版") and the niche phrasing "内容规法" is not a term a user would naturally say.

4 / 5

Distinctiveness Conflict Risk

It is tightly scoped to one company's brand ("海岚旅行", document number "HL-MKT-GUIDE-07 V2.1") with domain-specific artifacts (柿红方印, 审定图标库, brand-kit.pptx), giving it a clear niche with minimal overlap risk against generic design or PPT skills. It clearly matches anchor 5 rather than 4, which is only reached when there is residual overlap with closely related skills.

5 / 5

Total

16

/

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
EverMind-AI/Raven
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.