AB 通用工程师-开发规范与代码质量
Shared engineering skill for Weline development standards, safe change boundaries, code quality, documentation duties, and validation evidence.
As a process B 65/100 · Nearly there — weak spots: result and completion, consistency, progress reporting
ReferenceSoftware developmentInfrastructureWriting and documentstype and topics are labelled automatically from the skill text
How to improve
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
name-formatname should be kebab-case (lowercase letters, digits, hyphens)
Process rating: all ten parameters 65/100
- 0Progress reporting. Says nothing while it works
- 40Result and completion. Does not say what the result is
- 40Consistency. Frontmatter name (通用工程师-开发规范与代码质量) differs from the folder (common-development-standards)
- 50When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Failures and branches. 5 branches
- 100Steps. 91 steps
- 100Execution cost. Instruction body is 2988 tokens
- 100Running it twice. Mutating operations check current state
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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 143: enough signal without eating the budget
- +4Structure: 16 headings
- +3Step-by-step instructions: 91 items
- +4Has examples (2 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.
External checks
ClawHub: clean
This is a Weline engineering-standards skill with explicit workflow rules and no executable payload or hidden install behavior.
LLM: benign (high) · VirusTotal: · 29 May 2026