BC conflict-coordination
Mechanism conflict detection and coordination for AI assistant systems. Automatically detects crontab conflicts, systemd service conflicts, script overlaps, and log path inconsistencies. Use for maintaining system harmony and preventing internal conflicts.
As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
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
- 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 · 11
✓ No critical or high findings
Medium and low: 11
-
medium Dangerous commands
cmd-persistencescripts/detect-conflicts.sh:230Persistence mechanism (cron / launchd / scheduled task / autorun registry) (detector / deny-list definition)- 新闻推送任务：$(grep -c "daily-news.sh" <(crontab -l 2>/dev/null) || echo 0) 个
detector -
medium Dangerous commands
cmd-persistencescripts/detect-conflicts.sh:231Persistence mechanism (cron / launchd / scheduled task / autorun registry) (detector / deny-list definition)- 健康检查任务：$(grep -c "health-check\|maintenance.sh" <(crontab -l 2>/dev/null) || echo 0) 个
detector -
medium Dangerous commands
cmd-persistencescripts/detect-conflicts.sh:232Persistence mechanism (cron / launchd / scheduled task / autorun registry) (detector / deny-list definition)- Git 推送任务：$(grep -c "git-auto-push.sh" <(crontab -l 2>/dev/null) || echo 0) 个
detector -
medium Dangerous commands
cmd-persistencescripts/detect-conflicts.sh:233Persistence mechanism (cron / launchd / scheduled task / autorun registry) (detector / deny-list definition)- Git 拉取任务：$(grep -c "git pull" <(crontab -l 2>/dev/null) || echo 0) 个
detector -
medium Dangerous commands
cmd-persistencescripts/detect-conflicts.sh:234Persistence mechanism (cron / launchd / scheduled task / autorun registry) (detector / deny-list definition)- 备份任务：$(grep -c "backup.sh" <(crontab -l 2>/dev/null) || echo 0) 个
detector -
low Dangerous commands
cmd-cron-mentionscripts/detect-conflicts.sh:41Mentions editing / listing crontabcrontab -l > "$crontab_file" 2>/dev/null
-
low Dangerous commands
cmd-cron-mentionscripts/detect-conflicts.sh:230Mentions editing / listing crontab (detector / deny-list definition)- 新闻推送任务：$(grep -c "daily-news.sh" <(crontab -l 2>/dev/null) || echo 0) 个
detector -
low Dangerous commands
cmd-cron-mentionscripts/detect-conflicts.sh:231Mentions editing / listing crontab (detector / deny-list definition)- 健康检查任务：$(grep -c "health-check\|maintenance.sh" <(crontab -l 2>/dev/null) || echo 0) 个
detector -
low Dangerous commands
cmd-cron-mentionscripts/detect-conflicts.sh:232Mentions editing / listing crontab (detector / deny-list definition)- Git 推送任务：$(grep -c "git-auto-push.sh" <(crontab -l 2>/dev/null) || echo 0) 个
detector -
low Dangerous commands
cmd-cron-mentionscripts/detect-conflicts.sh:233Mentions editing / listing crontab (detector / deny-list definition)- Git 拉取任务：$(grep -c "git pull" <(crontab -l 2>/dev/null) || echo 0) 个
detector -
low Dangerous commands
cmd-cron-mentionSKILL.md:91Mentions editing / listing crontabcrontab -e
Files scanned: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 51/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
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 100Tools and files. No external tools needed
- 100Steps. 19 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 338 tokens
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
- -223 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 256: enough signal without eating the budget
- +4Structure: 15 headings
- +3Step-by-step instructions: 19 items
- +4Has examples (4 code blocks)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 85.