CtrlK
BlogDocsLog inGet started
Tessl Logo

business-knowledge-workflow

获取陌生业务知识并沉淀为 BK-CI skill 或架构文档时使用,例如阅读 iWiki、结合代码交叉验证、提炼模块边界和重写知识文档。当用户要先理解业务再写文档时优先使用。

58

Quality

66%

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/business-knowledge-workflow/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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 overview that frames a sensible three-stage methodology, but it functions as a router to detail files that do not exist, and its workflow lacks explicit validation checkpoints. Actionability and progressive disclosure are the main weak spots.

Suggestions

Create the referenced bundle files (reference/1-document-discovery.md, reference/2-code-cross-check.md, reference/3-skill-distillation.md) — the body currently routes to files that are not present, so the actual executable guidance is missing.

Add explicit validation checkpoints with a fix-retry loop in the 快速指导 workflow (e.g., after code cross-check: 'if docs and code diverge, document the divergence and re-derive the module boundary') instead of only stating that documents must be verified.

Make the distillation step actionable by specifying a concrete output template (e.g., sections for 模块边界 / 关键对象 / 主链路 / 常见坑) rather than only naming what to prioritize.

DimensionReasoningScore

Conciseness

Lean, bullet-driven body that assumes Claude's competence (no padding explaining iWiki/BK-CI); minor redundancy such as 延伸阅读 re-listing references already given in 快速指导 keeps it just short of a 5.

4 / 5

Actionability

Gives some concrete directives (validate via code or runtime, prioritize module boundary / key objects / main path / common pitfalls) but no executable steps, and the detailed guidance lives in referenced files (reference/1-2-3) that do not exist, leaving key details missing.

3 / 5

Workflow Clarity

A clear three-stage sequence (文档发现与初筛 → 代码交叉验证 → 沉淀) is present, but validation checkpoints are only implicit (point 3 says documents 'must' be verified) with no explicit fix-retry feedback loop or per-stage gating.

3 / 5

Progressive Disclosure

The SKILL.md is well-sectioned as an overview with clearly signaled one-level-deep references, but the referenced bundle files (reference/1-document-discovery.md, 2-code-cross-check.md, 3-skill-distillation.md) are absent, so navigation leads to dead ends.

3 / 5

Total

13

/

20

Passed

Description

75%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 solid, third-person description that concretely names several actions and provides an explicit 'when' trigger with natural user phrasing. It is held back from a 5 by the example-list framing and a slightly abstract 'what' clause.

DimensionReasoningScore

Specificity

Lists several concrete actions (阅读 iWiki, 结合代码交叉验证, 提炼模块边界, 重写知识文档, 沉淀为 skill/架构文档), but the '例如' framing marks them as examples rather than a comprehensive enumeration, leaving minor coverage gaps.

4 / 5

Completeness

Explicitly answers both 'what' (获取陌生业务知识并沉淀为 skill/架构文档) and 'when' (当用户要先理解业务再写文档时优先使用); the 'what' is slightly abstract and could be sharper to reach a 5.

4 / 5

Trigger Term Quality

Good coverage of natural domain terms (iWiki, 业务知识, 代码交叉验证, 模块边界, 知识文档, skill, 架构文档) plus the natural user phrase '要先理解业务再写文档', though a few synonymous phrasings users might say are absent.

4 / 5

Distinctiveness Conflict Risk

Occupies a distinct niche (business-knowledge acquisition + distillation for BK-CI/iWiki) with specific triggers; minor overlap risk with the related skill-writer skill it explicitly defers to.

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