CtrlK
BlogDocsLog inGet started
Tessl Logo

artifactory-module-architecture

处理 BK-CI 制品上传下载、制品元数据、BkRepo 或磁盘后端存储、文件任务和清理链路时使用。当用户提到构建产物、制品归档、下载令牌、报告文件、BkRepo 集成或制品清理时优先使用。

68

Quality

85%

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.

The body is an efficient, well-structured router for a two-branch architecture skill with sharp heuristics and pitfall lists. Its main weakness is actionability: all executable specifics are pushed to reference files, and those files are absent from the evaluated bundle.

Suggestions

Add minimal concrete anchors to the body — e.g. the actual BkRepo/Disk implementation class names or the metadata/task table names — so the differential checklist in 快速指导 can be executed without first opening the reference files.

Ship the referenced files: reference/1-artifact-storage.md and reference/2-bkrepo-task-extension.md are cited twice each but do not exist in the bundle, breaking the skill's navigation path.

In 快速指导 step 4, state how to confirm which backend implementation is hit (e.g. a config key, log line, or class to grep for) to close the workflow's validation gap.

DimensionReasoningScore

Conciseness

The ~50-line body is lean and heuristic-driven — sections like 高信号规则 and 关键陷阱 are one-line bullets with no concept padding or explanations Claude already knows. Every token earns its place.

5 / 5

Actionability

Concrete routing exists ("看 reference/1-artifact-storage.md"、"看 reference/2-bkrepo-task-extension.md") and step 3 gives a four-way differential ("元数据没落库 / 后端没存成功 / 路径规则错了 / 下载令牌或权限错了"), but no implementation class names, tables, endpoints, or commands appear — key executable details are entirely deferred. Not 2 because the routing and diagnostic checklist are genuinely concrete.

3 / 5

Workflow Clarity

快速指导 gives a numbered diagnostic sequence with a check-first step ("先区分是…" and "优先确认实际走的是 BkRepo 还是本地磁盘实现"), but it never says how to verify which implementation is hit, leaving a minor validation gap versus the 5 anchor.

4 / 5

Progressive Disclosure

Well-organized overview with clearly signaled one-level-deep references ("存储基础:reference/1-artifact-storage.md"、"BkRepo 与任务:reference/2-bkrepo-task-extension.md") plus cross-links to sibling skills. Held at 4 rather than 5 because the referenced reference/ files are not present in the bundle, so the navigation cannot be fully credited.

4 / 5

Total

16

/

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 states a clear capability scope for the BK-CI artifactory domain and pairs it with an explicit, concrete trigger list. It only falls short of top marks on verb specificity and synonym coverage in trigger terms.

DimensionReasoningScore

Specificity

Names the BK-CI artifact domain plus five concrete areas ("制品上传下载、制品元数据、BkRepo 或磁盘后端存储、文件任务和清理链路") with minor gaps, but the single generic verb "处理" keeps it short of the fully concrete multi-action anchor at 5.

4 / 5

Completeness

Explicitly answers both what ("处理 BK-CI 制品上传下载…清理链路") and when ("当用户提到…时优先使用") with concrete trigger phrases, matching the top anchor; no missing 'Use when' cap applies.

5 / 5

Trigger Term Quality

"当用户提到构建产物、制品归档、下载令牌、报告文件、BkRepo 集成或制品清理时优先使用" gives good natural trigger coverage, but misses common synonyms and variations (e.g. English "artifact", failure-phrases like upload not found), so not 5.

4 / 5

Distinctiveness Conflict Risk

The BK-CI/BkRepo/制品 storage niche is unmistakable and would not plausibly trigger a wrong skill; clear niche with distinct triggers.

5 / 5

Total

18

/

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.