BC wenwei-context-build
从指定入口文件出发，递归追踪代码调用链，梳理模块的技术实现细节（代码结构、依赖关系、接口定义、核心逻辑），生成结构化的代码知识库文档供 AI 阅读。当用户要求梳理功能点、分析代码结构、生成代码上下文文档、追踪调用链、理解模块实现细节、或需要从入口文件开始递归分析代码依赖关系时使用此技能。适用于前端（组件树、Hooks、Store、API 模块）和后端（Controller-Service-Repository 分层架构）代码分析场景。
As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
IntegrationSoftware developmentInfrastructuretype and topics are labelled automatically from the skill text
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 53/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 100Tools and files. No external tools needed
- 100Steps. 7 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 404 tokens
- 100Running it twice. No mutating operations
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 219: enough signal without eating the budget
- +4Structure: 4 headings
- +3Step-by-step instructions: 7 items
- +4Has examples (2 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.
External checks
ClawHub: clean
This is an instruction-only code documentation skill that reads user-selected source code and produces structured implementation notes, with no hidden execution or credential use.
LLM: benign (high) · VirusTotal: · 29 May 2026