CtrlK
BlogDocsLog inGet started
Tessl Logo

microservice-infrastructure

处理 BK-CI 微服务底层基础设施时使用,例如条件配置、事件驱动、服务间通信、国际化与日志规范。当用户要搭多环境配置、异步事件、Feign 调用或统一 i18n/日志时优先使用。

62

Quality

73%

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/microservice-infrastructure/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.

The body is a clean, well-sectioned routing overview that assumes competence and avoids padding, but its actionability and progressive disclosure are undermined because the four reference files it points to are absent from the bundle, leaving no executable detail behind the routing.

Suggestions

Add the four referenced files (reference/1-conditional-config.md through 4-i18n-logging.md) to the bundle, or remove the dangling references and inline the essential technical guidance.

De-duplicate the reference list: it appears in both 快速指导 (step 3) and 延伸阅读 — keep it in one place and cross-link from the other.

Add at least one concrete, executable anchor per topic (e.g. a minimal Feign client + timeout/fallback snippet, or a sample conditional-config YAML) so the skill is actionable even before reaching the reference docs.

DimensionReasoningScore

Conciseness

Lean, assumes Claude's competence, and avoids explaining concepts Claude already knows; the only waste is that the four reference paths are listed twice (快速指导 step 3 and 延伸阅读), so not quite every token earns its place.

4 / 5

Actionability

Routing guidance is concrete (specific reference doc paths per topic, named sibling skills to switch to), but the body stops at routing and provides no executable technical guidance on the actual tasks, and the referenced files do not exist in the bundle.

3 / 5

Workflow Clarity

The 快速指导 steps (1-4) give a clear decision/routing sequence: identify infra vs cross-cutting, route by topic to a reference doc, switch to a sibling skill if needed; no validation checkpoints are present, but none are required for a routing-decision skill.

4 / 5

Progressive Disclosure

The in-document structure is well-organized (clear sections, overview pointing to one-level-deep references signaled by topic), but the referenced files (reference/1-conditional-config.md, 2-event-driven.md, 3-service-communication.md, 4-i18n-logging.md) do not exist in the bundle, so the disclosure path is broken.

3 / 5

Total

14

/

20

Passed

Description

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

The description is well-formed: third-person voice, explicit what-and-when, concrete trigger terms, and a clearly scoped niche. Its main weakness is mild overlap risk with sibling skills that the description itself does not boundary against.

DimensionReasoningScore

Specificity

Names several concrete capability areas ("条件配置、事件驱动、服务间通信、国际化与日志规范") plus concrete trigger scenarios ("多环境配置、异步事件、Feign 调用或统一 i18n/日志"), giving comprehensive coverage with only a minor gap: capabilities are stated as domains rather than verb-actions like 'extract/fill/merge'.

4 / 5

Completeness

Explicitly answers both 'what' (处理 BK-CI 微服务底层基础设施...条件配置/事件驱动/服务间通信/国际化与日志规范) and 'when' ("当用户要搭多环境配置、异步事件、Feign 调用或统一 i18n/日志时优先使用") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural phrases a user would actually say ("多环境配置", "异步事件", "Feign 调用", "统一 i18n/日志"), but a few natural synonyms such as MQ/消息队列 or 超时/降级 are absent from the description.

4 / 5

Distinctiveness Conflict Risk

Scoped to a clear niche ("BK-CI 微服务底层基础设施"), but it does not disambiguate from the sibling skills named in the body (common-technical-practices, utility-components), leaving minor overlap risk with closely related skills.

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

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.