BC frontend-perf-audit
前端性能审计清单。当需要诊断网页/SPA性能问题时使用。涵盖Core Web Vitals(LCP/FID/CLS)、资源加载优化、渲染阻塞消除、代码分割策略、图片懒加载、缓存策略、Bundle分析。提供Chrome DevTools和Lighthouse的具体操作步骤。
As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
AnalyzerSoftware 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: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Implicit map keys need to be followed by map values at line 4, column 1: **使用时机**： ^^^^^^^^^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - 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. 12 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 916 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 136: enough signal without eating the budget
- +4Structure: 14 headings
- +3Step-by-step instructions: 12 items
- +4Has examples (7 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 62.
External checks
ClawHub: suspicious
The skill bundle is mostly coherent, but its autoreview helper defaults to running a nested reviewer with full sandbox and approval bypass.
LLM: suspicious (high) · VirusTotal: · 29 May 2026