CF processon-ai-skill
ProcessOn 官方作图 Skill，可在 ProcessOn 账号下新建、编辑、查询、导出各类图形文件。覆盖流程图类：流程图、业务流程图、泳道图、BPMN、时序图、UML图、ER图、架构图（系统/软件/云架构）、网络拓扑图、韦恩图、电路图、平面图、图表、UI原型/界面图、路线图、信息图、金字塔图、草图重绘；以及思维导图类：思维导图、脑图、组织结构图、鱼骨图、时间轴、树形图、逻辑图、表格图/树形表格、提纲、知识整理/内容总结。适用于：画流程图、做思维导图、生成图表、可视化流程、把内容整理成图、把图保存到 ProcessOn、修改/查找/导出我的 ProcessOn 文件。
ProcessOn 官方作图 Skill，可在 ProcessOn…
As a process F 33/100 · No process to follow — References files that are not bundled: scripts/envs.json
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 · 2
✓ No critical or high findings
Medium and low: 2
-
medium Dangerous commands
cmd-execpolicy-bypassreferences/auth.md:28Runs PowerShell with execution policy bypassedWindows : powershell -ExecutionPolicy Bypass -File .\scripts\setup\setup.ps1
-
low Dangerous commands
cmd-execpolicy-bypassscripts/setup/setup.ps1:14Runs PowerShell with execution policy bypassed (code comment)# 1) 直接运行： powershell -ExecutionPolicy Bypass -File .\setup.ps1
comment
Files scanned: 30. 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: scripts/envs.json - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 33/100
- 0Tools and files. 1 referenced file(s) missing: scripts/envs.json
- 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. 5 mutating operations with no state check
- 100Steps. 77 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3484 tokens
- low 11 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
- +1No license
- +2Single-language instructions
- +3Description length 291: enough signal without eating the budget
- +4Structure: 21 headings
- +3Step-by-step instructions: 77 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (9 of 9)
- +3All 11 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.