BC log-sanitizer-free
日志脱敏工具免费版解决日志安全的\"隐性泄露\"痛点：开发者将应用日志上传到排查平台时无意间泄露数据库密码、API令牌被写入调试日志、生产环境日志包含用户隐私字段、合规审计要求日志中不得出现明文敏感信息。这些场景下，原始日志直接归档或转发会带来严重的安全与合规风险。Use，可自发提升工作效率. 适用于需要log sanitizer相关能力的开发场景,包含结构化的工作流程和可复用的模板,帮助用户快速完成任务并保持代码质量.
日志脱敏工具免费版解决日志安全的\"隐性泄露\"痛点：开发者将应用日志上传到排查平台时无意间泄露数据库密码、API令牌被写入调试日志、生产环境日志包含用户隐私字段、合规审计要求日志中不得出现明文敏感信息。这些场景下，原始日志直接归档或转发会带来严重的安全与合规风险。Use，可自发提升工作效率.
As a process C 55/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
- 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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Secrets in code
secret-password-literalSKILL.md:241Hard-coded password / key literal (may be an example) (placeholder value)api_key: sk-a…... → api_key: ***REDACTED***
placeholder
Files scanned: 2. 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: Unexpected scalar at node end at line 6, column 77: …密钥等敏感信息，支持正则规则与自定义模式，本地运行零数据外泄.。日志脱敏工具免费版解决日志安全的"隐性泄露"痛点：开发者将应用日志上传到排查平台时无意间泄露" ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
description-long-hermesdescription is 212 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "displayName" - note
frontmatter-keyunknown frontmatter key "summary" - note
frontmatter-keyunknown frontmatter key "edition" - note
frontmatter-keyunknown frontmatter key "tools" - note
frontmatter-keyunknown frontmatter key "pricing_tier"
Process rating: all ten parameters 55/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
- 20When it triggers. No condition that starts the skill
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 38 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2156 tokens
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
- low 14 top-level sections: this looks like several domains in one skill
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
- +2Single-language instructions
- +3Description length 212: enough signal without eating the budget
- +4Structure: 36 headings
- +3Step-by-step instructions: 38 items
- +4Has examples (11 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 66.