CtrlK
BlogDocsLog inGet started
Tessl Logo

dispatch-module-architecture

处理 BK-CI 构建调度时使用,例如构建机选择、队列推进、配额控制、第三方构建机调度、Docker/Kubernetes 调度。当用户要改任务分配策略而不是 Agent/Worker 执行细节时优先使用。

64

Quality

81%

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

75%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 well-organized, concise routing skill that clearly scopes when to use the dispatch module, maps problem types to reference documents, and hands off to sibling skills appropriately. Weaknesses are mild redundancy between sections and reliance on reference files whose presence in the bundle could not be verified.

Suggestions

Deduplicate the reference-document listing: keep it in one place (延伸阅读 or 快速指导) instead of repeating the same three files in both sections.

Verify the referenced files actually ship with the skill at the stated paths (reference/1-dispatch-foundation.md etc.) — no references/ directory was present in the bundle, so the navigation links may be broken.

Add one or two concrete anchors inside SKILL.md (e.g., the key service or table names for queue/quota handling) so the body is actionable even before opening the reference docs.

DimensionReasoningScore

Conciseness

The ~50-line body is lean with no explanation of concepts Claude already knows, but the three reference documents are listed twice (快速指导 step 3 and 延伸阅读) and 高信号规则 partially restates the 适用/不适用场景 content. This matches anchor 4 (efficient with minor instances that could be trimmed), not 5 (redundant listings prevent every token earning its place).

4 / 5

Actionability

As an instruction-only routing skill it gives concrete mappings — problem type to specific file ('模块结构与核心对象:reference/1-dispatch-foundation.md' etc.) and explicit switch conditions to sibling skills. Not anchor 5 because the body contains no domain specifics (key classes, services, or diagnostic commands) a user could act on without opening the referenced files; not 3 because the routing rules themselves are concrete and complete for a router skill.

4 / 5

Workflow Clarity

快速指导 is a numbered triage sequence with an explicit decision rule ('调度问题要先区分资源不足、策略不匹配还是执行侧异常') and clear handoff conditions. No validation checkpoints are present, but the skill involves no destructive or batch operations, so no cap applies — anchor 4, not 5 (no explicit validation steps or feedback loops).

4 / 5

Progressive Disclosure

The body is a clear overview with three topic-labeled, one-level-deep references, which matches anchor 4's good structure. Not anchor 5: the reference list is duplicated across 快速指导 and 延伸阅读, and the referenced files (reference/1-dispatch-foundation.md etc.) are not present in the provided bundle (no references/ directory exists), so the navigation cannot be verified as real.

4 / 5

Total

16

/

20

Passed

Description

78%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, well-scoped description with explicit trigger guidance and active disambiguation against sibling Agent/Worker skills. Its main weakness is that the 'what' is conveyed only through an example enumeration of topic areas rather than an explicit capability statement, and it lacks synonym-level keyword coverage.

Suggestions

Open with an explicit capability statement (e.g., '提供 BK-CI Dispatch 模块的架构与改动指导') so the 'what' is stated directly rather than implied by the example list.

Add common user-facing variations of the trigger terms, such as 排队/排队超时、资源池、构建机不足, to broaden natural keyword coverage.

DimensionReasoningScore

Specificity

Names the domain (BK-CI 构建调度) and enumerates five concrete areas — '构建机选择、队列推进、配额控制、第三方构建机调度、Docker/Kubernetes 调度' — which is several specific items with comprehensive domain coverage. Falls short of anchor 5 because the items are enumerated as topics rather than concrete actions the skill performs.

4 / 5

Completeness

The 'when' is explicit and strong ('当用户要改任务分配策略而不是 Agent/Worker 执行细节时优先使用'), and the 'what' is conveyed through the enumerated example areas. Not anchor 5 because the description never states what the skill actually does (e.g., provides architecture guidance) — the 'what' is only implied by the example list.

4 / 5

Trigger Term Quality

Includes natural terms a BK-CI user would say — '构建机选择', '队列推进', '配额控制', 'Docker/Kubernetes 调度', '任务分配策略' — giving good keyword coverage. Not anchor 5 because common variations and synonyms (e.g., 排队、资源池、构建机不够/排队超时) are missing.

4 / 5

Distinctiveness Conflict Risk

It carves out a clear niche (BK-CI build dispatch) and actively disambiguates against the nearest competing skills via '而不是 Agent/Worker 执行细节时优先使用', minimizing wrong-skill triggers. This matches the anchor-5 example of a clear niche with distinct triggers.

5 / 5

Total

17

/

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