CtrlK
BlogDocsLog inGet started
Tessl Logo

create-setting-item

指导如何在 Project Graph 项目中创建新的设置项。当用户需要添加新的设置项、配置选项或需要了解设置系统的实现方式时使用此技能。

66

Quality

79%

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 ./.trae/skills/create-setting-item/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

76%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 highly actionable, well-structured guide with executable code throughout. Its main weaknesses are a missing validation checkpoint for the batch translation step and some inline reference material that could be split out.

Suggestions

Add an explicit validation step after step 3 (e.g. 'run tsc / verify every locale .yml file contains the new key') with a fix-and-retry loop, so the batch translation update cannot silently produce missing-key errors.

Move the full categories/groups listing and/or the 'complete example' into a reference file and link to it from SKILL.md to reduce duplication and inline bulk.

Trim the duplicated '完整示例' section or cross-reference the per-step examples instead of restating them, to improve token efficiency.

DimensionReasoningScore

Conciseness

The body is mostly efficient with no padding about concepts Claude already knows, but the full inline categories/groups listing and the duplicated 'complete example' could be trimmed, so it is not fully lean.

4 / 5

Actionability

It provides copy-paste-ready, executable code for every step (Zod schemas, icon imports, YAML translations, categories arrays, SettingField and Settings access) covering the common cases.

5 / 5

Workflow Clarity

The 5 steps are clearly sequenced, but step 3 is a batch operation ('为每个语言文件添加翻译') with no validation checkpoint (e.g. typecheck or verify all locale files updated), which caps workflow clarity at 3 per the batch-operation guideline.

3 / 5

Progressive Disclosure

Good section structure with a clearly signaled cross-skill reference (manage-translations blockquote) and no nested references; minor gaps are the large inline categories reference and duplicated complete example that a reference file could absorb.

4 / 5

Total

16

/

20

Passed

Description

82%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, third-person description that clearly states both what the skill does and when to use it, scoped to a specific project niche. It could be slightly more specific about the concrete actions covered and include a few more natural trigger synonyms.

Suggestions

Enumerate the concrete actions the skill guides (e.g. 'define the Zod schema, add an icon, add translations, and assign the item to a settings group') to raise specificity.

Add a couple more natural trigger phrases users might say, such as '加个设置开关' or '修改设置项', to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain ('Project Graph 项目中创建新的设置项') and 1-2 concrete actions (add setting items / config options, understand the settings system), but does not enumerate the several specific actions the skill actually covers, so it is not comprehensive.

3 / 5

Completeness

It explicitly answers 'what' ('指导如何在 Project Graph 项目中创建新的设置项') and 'when' ('当用户需要添加新的设置项、配置选项或需要了解设置系统的实现方式时使用此技能') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Trigger phrases like '当用户需要添加新的设置项、配置选项' map well to what a user would naturally say, giving good keyword coverage, though a few natural synonyms (e.g. '加个开关', '修改设置') are missing.

4 / 5

Distinctiveness Conflict Risk

The narrow niche of creating setting items within the specific Project Graph project, with distinct triggers, gives minimal conflict risk with other skills.

5 / 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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
graphif/project-graph
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.