CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ccgui-plugin-creator

为 CC GUI 桌面客户端创建、修改、迭代插件(Tier-0 声明式 CSS/JSON,或 Tier-1 单文件 ESM)。当用户要"做一个插件 / 给 CC GUI 加个功能 / 改输入框或界面样式 / 加设置页、侧边栏或状态栏入口 / 加面板页签或命令面板命令 / 把某套工作流包装成插件 / 改一下我做过的那个插件",或提到 ccgui 插件、插件目录、从本地目录安装插件时使用。

77

Quality

97%

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

92%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 written, highly actionable skill: both tiers get complete working examples, the workflow includes validation and iteration feedback loops, and detail is properly pushed into a real references/sdk-api.md bundle file. The only flaw is systematic restatement of hard constraints across §3, §6, and §7, which trims conciseness without harming correctness.

Suggestions

Consolidate the manifest constraint duplicates: §6's first two bullets restate the id/version/tier regex and permission rules already given as comments in the §3 manifest example — keep one normative statement and reference it from the other.

In §7's checklist, replace full restatements of the rules (e.g. the id regex, permission matching) with short verification prompts, since the checklist's job is to trigger a check rather than re-teach the constraint.

DimensionReasoningScore

Conciseness

The body is dense with hard constraints and executable specifics, with no padding explaining concepts Claude already knows. However, the same hard constraints are stated three to four times (id/version regex in §3 comments, §6, and the §7 checklist; permission minimality in §3/§6/§7; the no-import rule in §2, the code comment, §6, and §7), and §6 substantially restates §3 — minor duplication that could be consolidated. This is anchor 4 (efficient with trimmable redundancy) rather than 5 (every token appears exactly once by necessity).

4 / 5

Actionability

Two complete, copy-paste-ready examples (a full Tier-0 manifest.json and a full Tier-1 main.js with proper effect cleanup), exact validation regexes, a concrete directory layout, and precise install steps ("侧边栏「插件」→「从本地目录安装」"). The common cases for both tiers are fully covered, matching the anchor-5 pattern.

5 / 5

Workflow Clarity

Clear sequence (decide tier → structure files → write manifest → implement → deliver) with explicit validation in §5 ("验收:让用户确认看到效果;没看到就让用户看插件页该行的错误提示,别猜") and an error-recovery feedback loop (re-install hot-reloads the same id). The §7 pre-completion checklist caps a well-sequenced process, matching anchor 5.

5 / 5

Progressive Disclosure

The bulk API reference is correctly offloaded to references/sdk-api.md (verified to exist in the bundle), referenced explicitly at the right moments (§3, §6, §7, §8) and exactly one level deep. §8 deliberately points to the project's plugin-development guide instead of duplicating it ("本 skill 不复制它以免出现第二份过期快照"). This is the anchor-5 pattern of a lean overview with well-signaled references.

5 / 5

Total

19

/

20

Passed

Description

100%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.

An exemplary description: it states concrete capabilities with tier distinctions, provides an explicit 'use when' clause rich with verbatim natural trigger phrases, and anchors everything to a specific host application. Third-person voice is maintained and there is no padding.

DimensionReasoningScore

Specificity

"为 CC GUI 桌面客户端创建、修改、迭代插件(Tier-0 声明式 CSS/JSON,或 Tier-1 单文件 ESM)" names the domain and multiple concrete operations, and the trigger list enumerates concrete capability areas (设置页、侧边栏、状态栏、面板页签、命令面板命令、界面样式). This matches the anchor-5 example's comprehensiveness; no vague fluff pulls it toward 4.

5 / 5

Completeness

Explicitly answers both: what ("创建、修改、迭代插件", two named tiers) and when ("当用户要……时使用" with a list of concrete trigger phrases). This is the anchor-5 exemplar structure; anchor 4 would require a less explicit 'when', which is not the case here.

5 / 5

Trigger Term Quality

Quotes natural user phrasings verbatim ("做一个插件", "给 CC GUI 加个功能", "改一下我做过的那个插件") plus keyword variants (ccgui 插件, 插件目录, 从本地目录安装插件). Coverage of natural terms and synonyms is comprehensive, matching the anchor-5 pattern; it is far above anchor 4, which allows missing natural terms.

5 / 5

Distinctiveness Conflict Risk

Clear niche anchored to a named host application ("给 CC GUI 加个功能"), with trigger terms that mention ccgui explicitly. Minimal conflict risk with generic styling or plugin skills; not merely 'mostly distinct' as anchor 4 describes.

5 / 5

Total

20

/

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

zhukunpenglinyutong/desktop-cc-gui

Path

src-tauri/resources/skills/ccgui-plugin-creator/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.