worker-module-architecture

处理 BK-CI Worker 执行器时使用，例如任务领取与执行、插件运行、日志上报、环境变量传递和制品归档。当用户要改 Worker 执行链路而不是插件定义或调度策略时优先使用。

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 ./ai/skills/worker-module-architecture/SKILL.md

Quality

Content

38%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 well-sectioned and reads as a clean routing overview, but it is a facade over missing material: all three reference files it depends on are absent, there is no concrete guidance for actually executing changes, and the reference/skill pointers are duplicated across two sections. It needs its reference bundle created (or paths fixed) and de-duplicated before it can function.

Suggestions

Create the referenced bundle files (reference/1-runtime-flow.md, reference/2-task-plugin-log-artifact.md, reference/3-env-api-debug.md) or fix the paths — every navigational pointer in the body currently resolves to nothing.

Remove the duplication between 快速指导 (items 3–5) and 延伸阅读, which repeat the same three reference docs and three sibling skills; keep one routing section.

Add concrete executable guidance — key Worker classes/modules or entry points (e.g., task claim loop, task factory, executor interfaces) and how to verify a change (幂等/失败恢复 checks) — so the skill instructs rather than only routes.

Dimension	Reasoning	Score
Conciseness	The body is short and free of concept re-explanation, but the three reference documents and three sibling skills are each listed twice (快速指导 items 3–5 repeat verbatim in 延伸阅读). This duplication is more than the 'minor instances' of the 4 anchor, fitting the 3 anchor's 'could be tightened'.	3 / 5
Actionability	Guidance is limited to routing: "先按问题类型进入对应参考文档" and "切到 pipeline-plugin-development". There are no concrete entry points (class names, module paths, commands), and the central instruction — enter the reference docs — points at files that do not exist in the bundle, so the key executable step is broken. This matches the 2 anchor (high-level hints, missing specific steps) rather than 3.	2 / 5
Workflow Clarity	快速指导 gives an ordered triage sequence (classify problem → enter matching reference doc → switch skill if misdiagnosed), but validation checkpoints are implicit: the diagnostic test "先判断契约层还是执行层" lives in 高信号规则 rather than embedded in the workflow. Steps present, checkpoints missing — the 3 anchor.	3 / 5
Progressive Disclosure	The intended structure is good (short overview with clearly signaled one-level-deep references), but none of the three referenced paths (reference/1-runtime-flow.md, reference/2-task-plugin-log-artifact.md, reference/3-env-api-debug.md) exist in the bundle — no reference/ directory is present. Navigation fails entirely, which is below the 3 anchor's 'references present but not clearly signaled'.	2 / 5
	Total	10 / 20 Passed

Description

87%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 description: it names the domain, enumerates concrete actions, gives an explicit use-when clause, and actively disambiguates against neighboring skills. Only minor gains available from adding lifecycle/stability terms and synonyms like 构建机.

Dimension	Reasoning	Score
Specificity	The description lists five concrete actions ("任务领取与执行、插件运行、日志上报、环境变量传递和制品归档") in a named domain (BK-CI Worker executor). It falls short of the 5 anchor because lifecycle/stability optimization — a use case the body claims — is not covered, leaving minor gaps.	4 / 5
Completeness	It explicitly answers both: what ("处理 BK-CI Worker 执行器…任务领取与执行、插件运行、日志上报、环境变量传递和制品归档") and when ("当用户要改 Worker 执行链路而不是插件定义或调度策略时优先使用") with concrete trigger phrases. The when-clause is explicit and specific, matching the 5 anchor rather than the 4 anchor's 'could be more explicit'.	5 / 5
Trigger Term Quality	Terms like "Worker 执行链路", "任务领取", "日志上报", and the contrast terms "插件定义" and "调度策略" match what a BK-CI developer would naturally say. Not a 5 because common variations such as "构建机" (used in the body) are missing.	4 / 5
Distinctiveness Conflict Risk	It carves a clear niche (Worker execution) and explicitly names the adjacent territories it is NOT (插件定义, 调度策略), minimizing mis-trigger risk against sibling skills. This matches the 5 anchor's clear niche with distinct triggers.	5 / 5
	Total	18 / 20 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: TencentBlueKing/bk-ci
Path: ai/skills/worker-module-architecture/SKILL.md
Commit: d5420f2

Reviewed: 9 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.