create-setting-item

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

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/create-setting-item/SKILL.md

Quality

Content

65%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with concrete, copy-paste-ready code and a clear 5-step sequence tailored to the project. Its weaknesses are mild repetition in the worked example, a lack of an explicit verification checkpoint, and a monolithic single-file structure with no progressive disclosure.

Suggestions

Add an explicit verification step after step 5 (e.g. 'Confirm the setting appears in 视觉 > 基础 and persists after reload') to close the workflow loop and lift workflow_clarity.

Trim the '完整示例' section or fold it into the per-step examples to remove the duplicate walk-through of all five steps and tighten conciseness.

Move the full category/group taxonomy listing into a references file (e.g. references/categories.md) and link to it from the body, so the main file stays an overview and improves progressive_disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and project-specific (exact file paths, Zod types, category structures Claude would not know), but the '完整示例' section re-walks all five steps already covered and the categories object is expanded twice, so it could be tightened; it does not reach the 'every token earns its place' level.	2 / 3
Actionability	It provides concrete file paths (e.g. app/src/core/service/Settings.tsx), copy-paste-ready Zod/YAML/TSX snippets, exact import statements, and specific component usage, giving fully executable guidance.	3 / 3
Workflow Clarity	The five steps are clearly sequenced, but the multi-file edit has no explicit validation/verification checkpoint (e.g. confirming the setting renders), and per the rubric missing verification for a batch-style multi-file workflow caps clarity at 2 rather than 3.	2 / 3
Progressive Disclosure	Sections are well-organized, but everything lives in a single ~310-line file with no bundle files and content that could be split (the full category taxonomy, the complete worked example) kept inline, fitting 'some structure but content that should be separate is inline'.	2 / 3
	Total	9 / 12 Passed

Description

75%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is clear, scoped to a specific project task, and includes an explicit 'Use when...' trigger clause. It is strong on completeness and distinctiveness but slightly generic on action specificity and trigger variation.

Dimension	Reasoning	Score
Specificity	It names the domain ('Project Graph 项目中创建新的设置项') and some actions ('添加新的设置项、配置选项') but does not enumerate multiple distinct concrete actions, so it stops at the 'domain and some actions' anchor rather than reaching the 'multiple specific concrete actions' level.	2 / 3
Completeness	It states what the skill does ('指导如何...创建新的设置项') and gives an explicit when clause ('当用户需要添加新的设置项...时使用此技能'), clearly answering both what and when with explicit triggers.	3 / 3
Trigger Term Quality	Terms like '创建新的设置项', '添加新的设置项', and '配置选项' are natural and relevant, but the coverage is somewhat repetitive and lacks common variations, fitting 'some relevant keywords but missing common variations' rather than the broad coverage of level 3.	2 / 3
Distinctiveness Conflict Risk	The niche is narrow and project-specific (creating settings items inside Project Graph), with triggers tied to that exact task, making it unlikely to fire for unrelated skills.	3 / 3
	Total	10 / 12 Passed

Validation

100%

Warnings & errors only

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: graphif/project-graph
Path: .agents/skills/create-setting-item/SKILL.md
Commit: cea8af2

Reviewed: 10 days ago

Table of Contents

Discovery Implementation Validation

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.