BF statsoft-cli
跨平台统计软件 CLI 集成,面向 AI Agent;覆盖 34+ 款软件(R/Stata/SAS/SPSS/Python/贝叶斯/ML等),双语。核心价值:激活历史代码资产,用于 AI 工作流自动化。 / Cross-platform statistical software CLI integration for AI Agent; 34+ packages (R/Stata/SAS/SPSS/Python/Bayesian/ML, etc.), bilingual. Core value: activating historical code assets for AI workflow automation.
跨平台统计软件 CLI 集成,面向 AI Agent;覆盖 34+ 款软件(R/Stata/SAS/SPSS/Python/贝叶斯/ML等),双语。核心价值:激活历史代码资产,用于 AI 工作流自动化。 / Cross-platform statistical software CLI integration…
As a process F 35/100 · Will not run — References files that are not bundled: references/*.md
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.
Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The text references files that are not there: add them or drop the references.
- 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 · 4
✓ No critical or high findings
Medium and low: 4
-
medium Dangerous commands
cmd-privilegescripts/cross-platform/Matlab/setup_matlab.sh:182Privilege escalation / world-writable permissionsecho "$(LANG_ZH " 3. 运行安装程序: sudo sh install_matlab.sh" " 3. Run the installer: sudo sh install_matlab.sh")"
-
low Dangerous commands
cmd-execpolicy-bypassscripts/windows-only/GraphPad/setup_graphpad.ps1:2Runs PowerShell with execution policy bypassed (code comment)# Usage: powershell -ExecutionPolicy Bypass -File setu…ps1
comment -
low Dangerous commands
cmd-execpolicy-bypassscripts/windows-only/JMP/setup_jmp.ps1:2Runs PowerShell with execution policy bypassed (code comment)# Usage: powershell -ExecutionPolicy Bypass -File setu…ps1
comment -
low Dangerous commands
cmd-execpolicy-bypassscripts/windows-only/SPSS/setup_spss.ps1:2Runs PowerShell with execution policy bypassed (code comment)# 用法: powershell -ExecutionPolicy Bypass -File setu…ps1 [-Version "26"]
comment
Files scanned: 78. 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") - warning
missing-refreference to a missing file: references/*.md - note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "displayName" - note
frontmatter-keyunknown frontmatter key "cn_name" - note
frontmatter-keyunknown frontmatter key "summary" - note
frontmatter-keyunknown frontmatter key "triggers" - note
frontmatter-keyunknown frontmatter key "required_commands" - note
frontmatter-keyunknown frontmatter key "permissions"
Process rating: all ten parameters 35/100
- 0Tools and files. 1 referenced file(s) missing: references/*.md
- 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
- 100Steps. 40 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2242 tokens
- 100Running it twice. No mutating operations
- low 10 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
- +4No input/output examples
- +2Single-language instructions
- +3Description length 312: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 40 items
- +4Reference files are cited in the instructions (7 of 7)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 64.