CtrlK
BlogDocsLog inGet started
Tessl Logo

plankton-code-quality

使用 Plankton 实现编写时代码质量强制执行 —— 通过钩子在每次文件编辑时进行自动格式化、代码检查,并由 Claude 驱动自动修复。

59

Quality

68%

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 ./skills/plankton-code-quality/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%

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

The body is a concrete, well-sequenced reference with executable setup, a complete config reference, and an explicit validation loop in its three-phase workflow. Its main weakness is monolithic length with no progressive disclosure into local bundle files, plus minor verbosity from repeated attributions.

Suggestions

Split the detailed config reference and ECC comparison into separate reference files linked one level deep from SKILL.md to improve progressive disclosure.

Remove the repeated "感谢 @alxfazio" attributions (keep a single credit) to trim unnecessary tokens.

Tighten the ECC comparison table to only the differentiating rows that affect setup decisions.

DimensionReasoningScore

Conciseness

Mostly efficient reference material without over-explaining basics, but ~190 lines with repeated "感谢 @alxfazio" attributions (4x) and a lengthy ECC comparison section could be tightened.

2 / 3

Actionability

Provides copy-paste-ready setup commands (git clone, brew install, uv sync, claude), a complete config JSON block, concrete env-var and dependency tables — fully executable guidance.

3 / 3

Workflow Clarity

The three-phase architecture is clearly sequenced with an explicit validation loop ("重新运行阶段 1+2 以验证修复结果") and feedback via exit codes / "N violation(s) remain".

3 / 3

Progressive Disclosure

Well-organized into clear sections, but it is a ~190-line monolithic document with no local bundle files; content like the full config reference and ECC comparison could be split out, and the referenced REFERENCE.md/SETUP.md are external attributions rather than local one-level-deep references.

2 / 3

Total

10

/

12

Passed

Description

60%

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 concrete and names a distinctive mechanism, but it lacks an explicit Use-when trigger clause and uses somewhat jargon-heavy phrasing that limits natural trigger-term coverage. It answers "what" well but only implies "when."

Suggestions

Add an explicit "Use when..." clause stating when a user should invoke this skill (e.g., "Use when you want automatic formatting and linting on every file edit with Claude-driven fixes").

Soften jargon like "编写时代码质量强制执行" toward natural user phrasing and add common trigger variations (lint, format, 代码规范, 代码检查).

Clarify the distinctive niche up front to reduce overlap with generic linting/formatting skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "自动格式化" (auto-formatting), "代码检查" (linting), and "由 Claude 驱动自动修复" (Claude-driven auto-fix) — rather than vague language.

3 / 3

Completeness

Clearly states what it does, but the only "when" is the technical hook trigger "每次文件编辑时" rather than an explicit "Use when..." use-case clause, so per the guideline completeness is capped at 2.

2 / 3

Trigger Term Quality

Contains relevant keywords (格式化, 代码检查, 修复) but leans technical ("编写时代码质量强制执行", "钩子") and misses common natural variations like lint/format/代码规范, so coverage is partial.

2 / 3

Distinctiveness Conflict Risk

The Plankton hook-and-subprocess mechanism is a fairly distinct niche, but broad terms like 格式化/代码检查/代码质量 could overlap with other linting or code-quality skills.

2 / 3

Total

9

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
xu-xiang/everything-claude-code-zh
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.