CtrlK
BlogDocsLog inGet started
Tessl Logo

skill-writer

编写、压缩或重构 BK-CI skill 时使用,例如收紧 `description`、统一主文件骨架、下沉重内容到 `reference/`,并固化渐进式披露规则。当用户要新增或规范化 skill 时优先使用。

67

Quality

80%

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 ./ai/skills/skill-writer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is a concise, well-structured meta-skill that models its own principles: high-signal sections, clear do/don't boundaries, and a copy-paste skeleton. It scores high on conciseness and actionability, with only minor organization and checkpoint-explicitness gaps.

Suggestions

Frame the 验收清单 explicitly as a validation gate (e.g. '重构后逐条核对,未通过则回到对应快速指导步骤') to make feedback loops explicit.

Consider moving the 重内容类别 enumeration (line 36-43) into a reference file so the main file stays purely routing+action guidance.

DimensionReasoningScore

Conciseness

The ~90-line body is lean, assumes Claude's competence (no explanation of what a skill or reference is), and every section (适用场景/不适用场景/快速指导/规则/验收/延伸阅读) earns its place with high-signal guidance.

5 / 5

Actionability

Provides concrete, executable guidance — a numbered 10-step 快速指导, a copy-paste 推荐骨架, and an explicit 验收清单 — but most actions are structural directives rather than runnable code, leaving minor gaps for an instruction-only skill.

4 / 5

Workflow Clarity

The 快速指导 gives a clear ordered sequence (确定单一职责 → 写 description → 保留高信号 → 下沉重内容 → 清理遗留字段) and the 验收清单 acts as a checkpoint; no destructive/batch operation requires explicit validate→fix→retry loops, so the cap does not apply, but checkpoints are implicit rather than framed as feedback loops.

4 / 5

Progressive Disclosure

Well-organized sections with one-level-deep references (00-bkci-global-architecture, ../../HARNESS.md) and a skeleton that pushes heavy content to reference/; no bundle files exist, and the body stays overview-shaped, but a couple of inline lists (重内容类别, 高信号规则) could arguably live in references.

4 / 5

Total

17

/

20

Passed

Description

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

The description is specific, third-person, and includes an explicit 'when to use' trigger, covering concrete skill-writing actions. It is strong but could expand trigger-term synonyms and enumerate more scenarios to reach the top anchor.

Suggestions

Add 1-2 natural trigger synonyms users might say (e.g. 'skill 太长需要精简', 'skill 路由不准') to broaden trigger coverage.

List a couple more concrete actions or scenarios (e.g. 'reviewing skill boundaries', 'cleaning legacy frontmatter') to push specificity toward comprehensive.

DimensionReasoningScore

Specificity

Names the domain (编写、压缩或重构 BK-CI skill) and several concrete actions (收紧 description、统一主文件骨架、下沉重内容到 reference/、固化渐进式披露规则); coverage is good but not exhaustive of all skill-writing actions.

4 / 5

Completeness

It explicitly states both what the skill does and when to use it ('当用户要新增或规范化 skill 时优先使用'); the 'when' clause is present and reasonably explicit but is a single scenario rather than a comprehensive trigger list.

4 / 5

Trigger Term Quality

Includes natural user-facing phrases like '新增或规范化 skill' and '当用户要...优先使用', giving good keyword coverage, though it lacks synonyms or extensions a user might say beyond the stated scenarios.

4 / 5

Distinctiveness Conflict Risk

The BK-CI skill-writing niche is fairly distinct with specific triggers (description 收紧, 骨架统一, 重内容下沉); minor overlap risk with general documentation skills, but the scoped terminology keeps it mostly distinguishable.

4 / 5

Total

16

/

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
TencentBlueKing/bk-ci
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.