BC ielts-tuyaya-upload
上传雅思阅读复盘文件到服务器,支持 token 模式(进个人主页)和匿名模式。当用户想要上传已有的复盘 JSON、查看个人复盘仪表板时使用。触发词:上传复盘、上传复盘文件、sync review、upload review、查看我的复盘记录、我的仪表板、dashboard、tuyaya 上传、批量同步。
As a process C 58/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
AnalyzerData and analyticsInfrastructuretype 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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Secrets in code
secret-password-literalscripts/upload.js:81Hard-coded password / key literal (may be an example)pwd = pwd.slice(0, -1);
-
low Dangerous commands
cmd-shell-rcSKILL.md:211Writes to a shell startup file (quoted — discussed, not commanded)1. `echo $IELTS_USER_TOKEN` 是否真的有值(可能 `.zshrc` 没 source)
quoted
Files scanned: 7. 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 58/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 100Tools and files. No external tools needed
- 100Steps. 22 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1290 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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -2localhost URLs: will not work for another user
- +1No license
- +2Single-language instructions
- +3Description length 152: enough signal without eating the budget
- +4Structure: 22 headings
- +3Step-by-step instructions: 22 items
- +4Has examples (13 code blocks)
- +3All 2 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.
External checks
ClawHub: suspicious
The skill mostly does what it says, but it handles account tokens and “anonymous” identity data in ways users should review carefully before installing.
LLM: suspicious (high) · VirusTotal: · 23 Jun 2026