BC key-vault-manager-free
(no description)
本工具通过本地MCP工具架构守护API密钥安全,确保密钥值不会以明文形式发送到LLM服务器,所有密钥操作在用户设备本地完成。…
As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
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 · 3
✓ No critical or high findings
Medium and low: 3
-
low Exfiltration
read-dotenvSKILL.md:115Reads a .env filecp .env.example .env
-
low Exfiltration
read-dotenvSKILL.md:174Reads a .env file (quoted — discussed, not commanded)避免直接使用`cat .env`或文件读取工具查看包含密钥的文件。养成使用`read_file_masked`的习惯,确保密钥明文不会被发送到LLM服务器。这一实践应贯穿所有涉及密钥文件的操作。
quoted -
low Exfiltration
read-dotenvSKILL.md:220Reads a .env file (security demo / example; quoted — discussed, not commanded)1. **禁止直接读取密钥文件**:不要使用`cat .env`或文件读取工具查看包含密钥的文件,始终使用`read_file_masked`
demoquoted
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: Map keys must be unique at line 26, column 1: suggested_price: "19.9 CNY/per_use" tools: ["read", "write", "exec"] ^ ); 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") - 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 "homepage" - note
frontmatter-keyunknown frontmatter key "pricing_tier" - note
frontmatter-keyunknown frontmatter key "pricing_model" - note
frontmatter-keyunknown frontmatter key "suggested_price"
Process rating: all ten parameters 51/100
- 0Result and completion. Does not say what the result is
- 0When it triggers. No condition that starts the skill
- 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. Tools declared in frontmatter
- 100Steps. 28 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1579 tokens
- 100Running it twice. No mutating operations
- 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)
- +3Description length 0: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +4Structure: 42 headings
- +3Step-by-step instructions: 28 items
- +4Has examples (6 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 57.
External checks
ClawHub: suspicious
This skill is a key-management helper with expected secret-handling features, but its instructions are too broad and under-scoped for safe installation without review.
LLM: suspicious (high) · 23 Jul 2026