BC code-security
Review application code in the current workspace for concrete security issues and provide proportionate fixes. Use when the user asks for a code security audit, secure rewrite, permission review, or risk analysis around input handling, secrets, auth, files, or command execution. Do not use for host hardening or infrastructure-wide security posture. Chinese triggers: 安全审查、查漏洞、SQL 注入、XSS、路径穿越、权限问题、敏感信息泄露.
As a process C 63/100 · Has gaps — weak spots: result and completion, inputs and preconditions, failures and branches
How to improve
- 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: 3. 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: Nested mappings are not allowed in compact mappings at line 2, column 14: description: Review application code in the current workspace for concrete secu… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
Process rating: all ten parameters 63/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
- 100Tools and files. No external tools needed
- 100Steps. 11 steps
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 74 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
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- -15SKILL.md body under 300 characters: nearly empty
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 406: enough signal without eating the budget
- +4Structure: 3 headings
- +3Step-by-step instructions: 11 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 59.