BF agi-evolution-model
此技能作为数字伙伴使用用户的任何问题都可以触发;基于双环架构(两大循环:主循环符号思维 + 次循环行为感知,加超然最外圈)的AGI进化模型,通过意向性分析、人格映射、元认知检测和错误智慧库实现持续自我演进;当用户需要智能对话、人格定制、复杂问题求解或从错误中学习时使用
As a process F 35/100 · Will not run — References files that are not bundled: LICENSE, scripts/test_phase3.py, scripts/toolnode
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 · 3
✓ No critical or high findings
Medium and low: 3
-
medium Dangerous commands
cmd-eval-dynamicscripts/perception_node.py:244Dynamic code execution from decoded/untrusted inputreturn eval(compile(tree, "<safe_calc>", "eval"), {"__builtins__": {}}, ns) -
low Dangerous commands
cmd-privilegescripts/busybox_fallback.py:77Privilege escalation / world-writable permissions (string literal in code, not executed)"rm -rf ~", "rm -rf /", "sudo rm", "mkfs", "dd if=/dev/",
code literal -
low Dangerous commands
cmd-privilegescripts/verify_toolnode_step2.py:158Privilege escalation / world-writable permissions (string literal in code, not executed){"group": "exec", "op": "run", "command": "sudo rm -rf /important"})code literal
Files scanned: 80. 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: LICENSE - warning
missing-refreference to a missing file: scripts/test_phase3.py - warning
missing-refreference to a missing file: scripts/toolnode - warning
missing-refreference to a missing file: scripts/toolnode.exe - warning
missing-refreference to a missing file: scripts/cli_file_operations.py - warning
missing-refreference to a missing file: scripts/cli_system_info.py - warning
missing-refreference to a missing file: scripts/cli_process_manager.py - warning
missing-refreference to a missing file: scripts/cli_executor.py - note
frontmatter-keyunknown frontmatter key "dependency"
Process rating: all ten parameters 35/100
- 0Tools and files. 8 referenced file(s) missing: LICENSE, scripts/test_phase3.py, scripts/toolnode
- 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. 201 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3962 tokens
- 100Running it twice. No mutating operations
- low 14 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
- -38 of 42 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 134: enough signal without eating the budget
- +4Structure: 54 headings
- +3Step-by-step instructions: 201 items
- +4Has examples (17 code blocks)
- +4Reference files are cited in the instructions (18 of 18)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 60.