BC sensitive-data-masker
Intelligent sensitive data detection and masking. Uses Microsoft Presidio + SQLite for automatic PII redaction with local restoration support.
Intelligent sensitive data detection and masking.
As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
AnalyzerSoftware developmentData and analyticstype 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 · 5
✓ No critical or high findings
Medium and low: 5
-
low Secrets in code
secret-password-literalCHANNEL-MASKER-GUIDE.md:38Hard-coded password / key literal (may be an example) (quoted — discussed, not commanded)masked_text = "[PASS…228],帮我配置数据库"
quoted -
low Secrets in code
secret-password-literalCHANNEL-MASKER-GUIDE.md:51Hard-coded password / key literal (may be an example)[PASS…228],帮我配置数据库
-
low Secrets in code
secret-password-literalCHANNEL-MASKER-GUIDE.md:93Hard-coded password / key literal (may be an example)脱敏后:我的 [PASS…228]
-
low Secrets in code
secret-password-literalCHANNEL-MASKER-GUIDE.md:257Hard-coded password / key literal (may be an example)用 password=Depl…123 这个密码部署服务
-
low Secrets in code
secret-password-literalCHANNEL-MASKER-GUIDE.md:262Hard-coded password / key literal (may be an example)用 [PASS…228] 这个密码部署服务
Files scanned: 16. 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") - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 51/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
- 30Running it twice. 3 mutating operations with no state check
- 100Tools and files. No external tools needed
- 100Steps. 28 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1342 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 15 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
- -212 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 142: enough signal without eating the budget
- +4Structure: 23 headings
- +3Step-by-step instructions: 28 items
- +4Has examples (10 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 69.