CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

project-module-architecture

处理 BK-CI 项目创建、项目属性、成员权限、项目标签、项目分片和项目资源边界时使用。当用户提到项目管理、projectId 含义、项目配置、成员管理或项目迁移时优先使用。

Quality

79%

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/project-module-architecture/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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-organized overview that concentrates genuine BK-CI domain insight (projectId semantics, cross-module coupling, common misdiagnoses) without padding. Its weaknesses are incomplete actionability (no executable verification steps) and broken external references, since the referenced reference/*.md files and sibling-skill pointers do not resolve within the provided bundle.

Suggestions

Add concrete executable guidance for the triage workflow, e.g., a sample SQL query or API/service name showing how to look up T_PROJECT.english_name, project attributes, or sharding state, so the 快速指导 steps can actually be executed.

Fix the reference paths: the body points to `reference/1-project-foundation.md` and `reference/2-project-operations.md`, but no such directory or files exist in the bundle — either ship them under the correct directory name or correct the paths so the pointers resolve.

Add an explicit validation checkpoint in the workflow, such as instructing to confirm the diagnosis (project state, attributes, permissions) against the database/service before making project field or routing changes, and check downstream modules afterward.

DimensionReasoningScore

Conciseness

The ~45-line body is lean and every token is BK-CI-specific knowledge Claude would not already know (projectId ≈ T_PROJECT.english_name, sharding/routing as infrastructure, named pitfalls); there is no padding and nothing re-explains general concepts, matching 'lean and efficient'.

5 / 5

Actionability

There are some concrete anchors (specific field mapping to T_PROJECT.english_name, named pitfalls, file pointers), but no executable steps — no queries, commands, endpoints, or concrete examples — and directives like "就要同时考虑对其他模块的影响" remain directional, matching 'some concrete guidance but incomplete'.

3 / 5

Workflow Clarity

A rough triage sequence is present (确认主线 → 看 reference 文件 → 应用规则 → 检查下游影响), but there is no validation checkpoint confirming a diagnosis before changes are made, matching 'sequence present but checkpoints missing or implicit' rather than 'most checkpoints present'.

3 / 5

Progressive Disclosure

The body is well-sectioned with one-level-deep, clearly signaled pointers ("看 reference/1-project-foundation.md"), but the bundle contains no reference/ or references/ directory, so both referenced files are dangling, and sibling skills ("00-bkci-global-architecture", "auth-module-architecture") are named without paths — structure is good but references do not resolve against the actual bundle.

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.

A strong description: it states a concrete capability scope for the BK-CI project module and pairs it with an explicit, trigger-phrase-rich 'use when' clause. The main residual weaknesses are a single generic verb ('处理') covering all capabilities and some overlap-prone member-management/configuration terms.

DimensionReasoningScore

Specificity

Names the BK-CI project domain and six concrete scope areas ("项目创建、项目属性、成员权限、项目标签、项目分片和项目资源边界"), but all hang off the single generic verb "处理" rather than varied concrete actions, so it matches 'several specific actions with minor gaps' rather than comprehensive action coverage.

4 / 5

Completeness

Explicitly answers both 'what' (handles project creation, attributes, member permissions, tags, sharding, resource boundaries) and 'when' with concrete trigger phrases ("当用户提到项目管理、projectId 含义、项目配置、成员管理或项目迁移时优先使用"), matching the top anchor; score 4 would require the 'when' to be merely adequate rather than explicit.

5 / 5

Trigger Term Quality

Includes natural phrases users would actually say ("项目管理", "projectId 含义", "项目配置", "成员管理", "项目迁移"), giving good keyword coverage, but misses common variations and synonyms such as "创建项目", "项目列表", or englishName, so it falls short of comprehensive synonym-level coverage.

4 / 5

Distinctiveness Conflict Risk

The description is clearly niched to the BK-CI Project module with distinct triggers like "projectId 含义", but terms such as "成员管理" and "项目配置" carry minor overlap risk with closely related skills (e.g., an auth-module skill), so it is mostly distinct rather than minimal-conflict.

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

TencentBlueKing/bk-ci

Path

ai/skills/project-module-architecture/SKILL.md

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.