CtrlK
BlogDocsLog inGet started
Tessl Logo

supporting-modules-architecture

处理 BK-CI 支撑服务模块时使用,例如 Ticket、Environment、Notify、Log、Quality、OpenAPI 等能力的定位、边界和入口选择。当用户要判断该去哪个支撑模块而不是修改核心流水线链路时优先使用。

60

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 ./ai/skills/supporting-modules-architecture/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 routing skill with clear decision logic and concrete per-module routing paths. Its main weaknesses are a duplicated reference list and — more seriously — references to module docs that are not present in the bundle.

Suggestions

Add the missing reference/1-ticket-module.md through reference/6-openapi-module.md files (or correct the paths) so the signaled references resolve.

Remove the duplicated reference list in 延伸阅读 and link to it once, keeping 延伸阅读 only for cross-skill pointers (process-module-architecture, 00-bkci-global-architecture).

Add an explicit decision checkpoint for ambiguous cases (e.g. 'if the capability could belong to two modules, check X first') to strengthen workflow clarity.

DimensionReasoningScore

Conciseness

Mostly lean with short bullets and lists, but the six-file reference list is duplicated verbatim in both 快速指导 and 延伸阅读, which is unnecessary padding; not a 4 because the duplication is a clear tightening target.

3 / 5

Actionability

Concrete routing directives — per-capability file paths ("Ticket:reference/1-ticket-module.md") and explicit switch instructions ("切到 process-module-architecture") — give mostly executable guidance; not a 5 because the routing criteria for ambiguous cases are advisory rather than copy-paste ready.

4 / 5

Workflow Clarity

The 快速指导 numbered list lays out a clear decision sequence (identify capability → route to reference → or switch skill), supported by 高信号规则 and 关键陷阱 for edge cases; not a 5 because there is no explicit checkpoint for the ambiguous 'which module' decision itself.

4 / 5

Progressive Disclosure

Structure is well organized with clearly signaled one-level-deep references, but the referenced files (reference/1-ticket-module.md … reference/6-openapi-module.md) do not exist in any references/ directory — the references are dangling, which is worse than the 'minor organization gaps' of a 4.

3 / 5

Total

14

/

20

Passed

Description

73%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 well-targeted description that names the supporting-module niche, gives an explicit 'use when' trigger, and disambiguates from the core pipeline. It is held back from the top band by somewhat abstract 'what' wording and limited synonym coverage.

Suggestions

Tighten the 'what' with more concrete verbs (e.g. '定位能力归属、划清模块边界、选择正确的模块入口') to lift specificity.

Add a few natural trigger synonyms users might say (e.g. '凭证/环境/通知/日志/质量/开放接口') alongside the English module names.

DimensionReasoningScore

Specificity

Names the domain (BK-CI supporting modules) and a few concrete actions — "定位、边界和入口选择" (positioning, boundaries, entry-point selection) — but these are abstract routing actions rather than comprehensive concrete operations, matching the 'names domain and 1-2 concrete actions' anchor; not a 4 because coverage is thin and conceptual.

3 / 5

Completeness

Both 'what' (supporting-module positioning, boundaries, entry selection) and 'when' ("当用户要判断该去哪个支撑模块而不是修改核心流水线链路时优先使用") are present and explicit; not a 5 because the 'what' is somewhat abstract rather than fully concrete trigger phrases.

4 / 5

Trigger Term Quality

Concrete module keywords (Ticket, Environment, Notify, Log, Quality, OpenAPI) and the natural phrase "判断该去哪个支撑模块" give good keyword coverage a user would say; not a 5 because common synonyms/variations beyond the module names are absent.

4 / 5

Distinctiveness Conflict Risk

Clear niche (BK-CI supporting modules) with an explicit disambiguator against the core pipeline chain, minimizing conflict with sibling skills like process-module-architecture.

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