CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

semi-design-guide

使用 Semi Design 组件的完整指南,包括 MCP 工具使用流程、常见模式、生成页面后的验证和最佳实践。当你需要查询 Semi Design 组件、生成组件页面或解决使用问题时,请使用此技能。

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 ./ecosystem/semi-ui-skills/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%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 cleanly organized router SKILL.md with a concrete MCP prerequisite config, but its two referenced files are absent from the bundle, leaving the actual workflows and best practices unreachable. The body also carries redundant routing layers (概述 plus 文件说明 plus 快速导航) that could be consolidated.

Suggestions

Ship WORKFLOWS.md and BEST_PRACTICES.md alongside SKILL.md (or inline the essential four-step MCP workflow and key practices), since the 快速导航 and 文件说明 links currently point to files that do not exist in the bundle.

Add one minimal concrete MCP call example (e.g. invoking get_semi_document for a specific component) directly in SKILL.md so the core flow is executable even without the reference files.

Remove the redundant 概述 section and merge 快速导航 into 文件说明 to eliminate the triple-layered routing to the same two files.

DimensionReasoningScore

Conciseness

Mostly efficient routing content, but redundancy is noticeable: the '概述' section restates the frontmatter description ('此 Skill 配合 Semi MCP 工具使用,提供:工作流…实践'), and the '快速导航' table duplicates the per-file '何时使用' lines and links already given in '文件说明', creating three layers of routing to the same two files. It is tighter than anchor 2's padded sections, but the redundant overview and duplicated navigation keep it below anchor 4's 'minor instances'.

3 / 5

Actionability

Some concrete guidance exists — the copy-paste MCP server config JSON and the named four-tool / four-step flow ('get_semi_document…' / '查找组件 → 查询详情 → 查看源码 → 查看函数实现') — but it is incomplete: actual call syntax and detailed steps are delegated to WORKFLOWS.md and BEST_PRACTICES.md, which are not present in the bundle, so the promised executable guidance is unreachable. This fits anchor 3 ('some concrete guidance but incomplete; missing key details') better than anchor 2, since the config block and named tools go beyond high-level hints.

3 / 5

Workflow Clarity

The four-step sequence is named ('查找组件 → 查询详情 → 查看源码 → 查看函数实现') and validation is mentioned ('优先复用项目现有测试;需要视觉语义验证时可选用 Midscene'), but only as a summary of a missing file — no checkpoints or error-recovery steps appear in the body itself. This matches anchor 3 ('steps listed but validation gaps; checkpoints missing or implicit') and falls short of anchor 4's 'most checkpoints present'.

3 / 5

Progressive Disclosure

The routing structure is well signaled (per-file '内容/包含/何时使用' descriptions plus a 快速导航 table, one level deep), but both referenced files — WORKFLOWS.md and BEST_PRACTICES.md — do not exist in the bundle (no references/, scripts/, assets/, or root-level .md files are present), so the disclosure structure does not actually function. The clear signaling keeps it above anchor 2's 'references are buried', but the dead targets prevent the 'easy navigation' of anchors 4-5.

3 / 5

Total

12

/

20

Passed

Description

87%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: it explicitly states what the skill covers and when to use it, with concrete, niche-specific trigger phrases tied to Semi Design. Its only weakness is mild genericness in the listed guide topics ('常见模式', '最佳实践').

DimensionReasoningScore

Specificity

Names the domain ('使用 Semi Design 组件') and lists several concrete items — 'MCP 工具使用流程、常见模式、生成页面后的验证和最佳实践' plus actions '查询 Semi Design 组件、生成组件页面、解决使用问题'. Two items ('常见模式', '最佳实践') are generic guide-terms rather than concrete actions, so it falls short of anchor 5's comprehensive coverage but exceeds anchor 3's '1-2 concrete actions'.

4 / 5

Completeness

Explicitly answers both what ('使用 Semi Design 组件的完整指南,包括 MCP 工具使用流程、常见模式、生成页面后的验证和最佳实践') and when ('当你需要查询 Semi Design 组件、生成组件页面或解决使用问题时,请使用此技能') with three concrete trigger phrases — matching anchor 5's 'clearly and explicitly answers both what AND when with concrete trigger phrases'.

5 / 5

Trigger Term Quality

Natural user phrases are present: '查询 Semi Design 组件', '生成组件页面', '解决使用问题', 'MCP 工具'. Coverage is good but lacks synonyms or variations a user might say (e.g. 'Semi UI', specific component names like Table/Form), matching anchor 4 ('a few natural terms missing') rather than anchor 5's comprehensive synonyms/extensions, and exceeding anchor 3's 'missing common variations'.

4 / 5

Distinctiveness Conflict Risk

'Semi Design' names a specific component library and the triggers are scoped to it ('查询 Semi Design 组件、生成组件页面'), giving a clear niche with minimal overlap risk against generic UI-library skills. '解决使用问题' alone is broad, but it is bound to the Semi Design context within the same clause, so anchor 5 fits better than anchor 4's 'minor overlap risk'.

5 / 5

Total

18

/

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

relative_links

Relative link issues: 3 missing, 1 suspicious

Warning

Total

15

/

16

Passed

Repository

DouyinFE/semi-design

Path

ecosystem/semi-ui-skills/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.