FD airilab
统一调用 AiriLab 图像生成与任务管理能力(MJ 创意渲染 workflowId=0、创意放大 workflowId=16、氛围转换 workflowId=13),并自动处理登录鉴权、项目选择、任务提交、状态轮询与结果回推。用户提到 Midjourney/MJ 文生图、参考图生成、放大超分/4K、天气季节昼夜氛围转换,以及“登录AiriLab、选择/切换项目、查询job状态/结果”等请求时使用。
As a process D 48/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
What is at stake
The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.
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
- Address the high-severity findings: each costs 18 safety points. If one is a false positive, add the rule id to guard.allow in spec.yaml.
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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 · 14
-
high Dangerous commands
cmd-persistencescripts/post-install.sh:98Persistence mechanism (cron / launchd / scheduled task / autorun registry)(crontab -l 2>/dev/null; echo "$cron_line") | crontab -
-
high Dangerous commands
cmd-persistencescripts/setup-autostart.sh:21Persistence mechanism (cron / launchd / scheduled task / autorun registry)EXISTING=$(crontab -l 2>/dev/null | grep -F "start-worker.sh" || true)
-
high Dangerous commands
cmd-persistencescripts/setup-autostart.sh:31Persistence mechanism (cron / launchd / scheduled task / autorun registry)(crontab -l 2>/dev/null | grep -v '^#'; echo "$CRON_ENTRY") | crontab -
Medium and low: 11
-
medium Dangerous commands
cmd-persistencescripts/post-install.sh:95Persistence mechanism (cron / launchd / scheduled task / autorun registry) (string literal in code, not executed)cron_line="@reboot AIRILAB_HOME=\"$AIRILAB_HOME\" \"$SKILL_DIR/scripts/start-worker.sh\" >> \"$AIRILAB_HOME/scheduler/autostart.log\" 2>&1"
code literal -
medium Dangerous commands
cmd-persistencescripts/post-install.sh:96Persistence mechanism (cron / launchd / scheduled task / autorun registry) (string literal in code, not executed)existing="$(crontab -l 2>/dev/null | grep -F "$SKILL_DIR/scripts/start-worker.sh" || true)"
code literal -
medium Dangerous commands
cmd-persistencescripts/post-install.sh:114Persistence mechanism (cron / launchd / scheduled task / autorun registry) (string literal in code, not executed)echo "Autostart: cron @reboot configured"
code literal -
medium Dangerous commands
cmd-persistencescripts/setup-autostart.sh:8Persistence mechanism (cron / launchd / scheduled task / autorun registry) (string literal in code, not executed)CRON_ENTRY="@reboot $SCRIPT_DIR/start-worker.sh"
code literal -
low Dangerous commands
cmd-cron-mentionscripts/post-install.sh:96Mentions editing / listing crontab (string literal in code, not executed)existing="$(crontab -l 2>/dev/null | grep -F "$SKILL_DIR/scripts/start-worker.sh" || true)"
code literal -
low Dangerous commands
cmd-cron-mentionscripts/post-install.sh:98Mentions editing / listing crontab(crontab -l 2>/dev/null; echo "$cron_line") | crontab -
-
low Dangerous commands
cmd-cron-mentionscripts/setup-autostart.sh:21Mentions editing / listing crontabEXISTING=$(crontab -l 2>/dev/null | grep -F "start-worker.sh" || true)
-
low Dangerous commands
cmd-cron-mentionscripts/setup-autostart.sh:28Mentions editing / listing crontab (detector / deny-list definition; string literal in code, not executed)echo " crontab -l | grep -v 'start-worker.sh' | crontab -"
detectorcode literal -
low Dangerous commands
cmd-cron-mentionscripts/setup-autostart.sh:31Mentions editing / listing crontab(crontab -l 2>/dev/null | grep -v '^#'; echo "$CRON_ENTRY") | crontab -
-
low Dangerous commands
cmd-cron-mentionscripts/setup-autostart.sh:38Mentions editing / listing crontabcrontab -l | grep -E "(start-worker|airilab)" || echo " (无)"
-
low Dangerous commands
cmd-background-processscripts/start-worker.sh:39Starts a background / autostarted processnohup python3 "$WORKER_SCRIPT" >> "$LOG_FILE" 2>&1 &
Files scanned: 17. 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 48/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
- 20When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (web, python) that frontmatter does not declare
- 100Steps. 77 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1226 tokens
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
- low 12 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
- -31 of 6 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 202: enough signal without eating the budget
- +4Structure: 23 headings
- +3Step-by-step instructions: 77 items
- +4Has examples (4 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 69.