CtrlK
BlogDocsLog inGet started
Tessl Logo

yaml-pipeline-transfer

处理 BK-CI YAML 流水线导入导出、YAML 与 Model 双向转换、PAC、模板引用与 YAML 校验时使用。当用户提到 YAML 流水线、PAC、模板化、注释保留、表达式解析或转换调试时优先使用。

72

Quality

87%

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

82%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 concise, well-structured navigation skill with a clear triage workflow and a pitfalls checklist. The main gap is that the signaled reference/*.md bundle files are absent, so the progressive-disclosure pointers lead nowhere.

Suggestions

Add the referenced reference/1-transfer-flow.md, reference/2-pac-template.md, and reference/3-debug-extension.md files to the bundle so the signaled navigation actually resolves.

Add an explicit verify/regression checkpoint to 快速指导 (e.g., after a change run an import+export round-trip and template/PAC/comment preservation regression) to lift workflow clarity from implicit to explicit validation.

Tighten actionability by including one concrete entry point per reference (e.g., a key class, command, or file path to start from) so the body directs Claude to executable next steps, not just topic areas.

DimensionReasoningScore

Conciseness

Lean and well-organized with no padding; assumes Claude's competence, explains no basic concepts, and every section (适用/不适用场景, 快速指导, 高信号规则, 关键陷阱, 延伸阅读) earns its place.

5 / 5

Actionability

Provides concrete diagnostic categories (YAML 文本解析/数据模型/YAML→Model/Model→YAML/模板展开) and named components (TransferMapper, ModelTransfer), but stays at navigation/strategy level without executable steps or commands.

4 / 5

Workflow Clarity

A clear numbered triage sequence in 快速指导 plus a 关键陷阱 checklist of regressions to verify; checkpoints are present but implicit rather than explicit validate→fix→retry loops.

4 / 5

Progressive Disclosure

Clean overview structure with well-signaled one-level-deep pointers to reference/1-transfer-flow.md, 2-pac-template.md, 3-debug-extension.md, but those bundle files are not present so navigation does not actually resolve.

4 / 5

Total

17

/

20

Passed

Description

92%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, specific description that states both capabilities and trigger conditions with concrete BK-CI-domain terms. It is well-targeted; the only soft spot is trigger vocabulary that leans technical without synonyms or file extensions.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 导入导出、YAML 与 Model 双向转换、PAC、模板引用、YAML 校验 — covering the domain comprehensively rather than at a generic level.

5 / 5

Completeness

Explicitly answers both what (处理...导入导出、双向转换、PAC、模板引用、校验) and when (当用户提到...时优先使用) with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural trigger terms a BK-CI user would say (YAML 流水线、PAC、模板化、注释保留、表达式解析、转换调试), but they are domain-specific jargon without synonyms or file extensions, so not fully comprehensive.

4 / 5

Distinctiveness Conflict Risk

Targets a clear BK-CI YAML pipeline niche with specific, distinctive triggers, giving minimal overlap or conflict risk with other skills.

5 / 5

Total

19

/

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.