AC content-credential-manager
内容创业凭证管理器。追踪和管理已安装技能的 API 凭证配置状态，引导用户逐步完成每个平台的凭证配置，让内容创作技能从"装好了"到"真正可用"。触发场景：(1) 用户问"哪些技能可以用了"、"凭证配置好了吗"；(2) 开始内容创作前检查环境；(3) 新技能安装后登记凭证状态；(4) 排查"为什么XX技能不能用"。
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 · 0
✓ No critical or high findings
Files scanned: 6. 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")
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. 2 mutating operations with no state check
- 100Tools and files. No external tools needed
- 100Steps. 22 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 844 tokens
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
- +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
- +5Description quotes 3 example trigger phrases
- +3Description length 157: enough signal without eating the budget
- +4Structure: 16 headings
- +3Step-by-step instructions: 22 items
- +4Has examples (7 code blocks)
- +3All 2 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 80.
External checks
ClawHub: suspicious
This is a coherent credential manager, but it asks users to put powerful API keys and a full session cookie into chat or command arguments without enough safeguards.
LLM: suspicious (high) · VirusTotal: · 29 May 2026