← Back to Skills Marketplace
Conflict Coordination
by
alfredming-2026
· GitHub ↗
· v1.0.0
· MIT-0
242
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install conflict-coordination
Description
Mechanism conflict detection and coordination for AI assistant systems. Automatically detects crontab conflicts, systemd service conflicts, script overlaps,...
README (SKILL.md)
Conflict Coordination - 机制冲突协调机制
核心原则: 实时性优先，可靠性优先，人工确认优先
🚀 快速开始
Crontab 配置
# 每周六 22:00 冲突检测
0 22 * * 6 /path/to/detect-conflicts.sh
🔧 核心功能
1. 冲突检测
- ✅ crontab 配置冲突（重复任务）
- ✅ systemd 服务冲突（服务状态）
- ✅ 脚本功能重叠
- ✅ 日志路径不一致
- ✅ 文档一致性检查
2. 协调方案
- ✅ Git vs 实时同步 → 实时优先，Git 备份
- ✅ Cron vs Systemd → Systemd 优先
- ✅ 多端编辑冲突 → commit 后 pull
3. 定期审查
- ✅ 每周自动检测
- ✅ 配置变更时触发
- ✅ 飞书推送报告
📁 包含文件
conflict-coordination/
├── SKILL.md # 主文档
├── README.md # 项目说明
├── scripts/
│ └── detect-conflicts.sh # 冲突检测脚本
└── docs/
├── QUICKSTART.md # 快速上手
└── coordination-guide.md # 协调指南
📊 检测项目
| 检测项 | 冲突类型 | 解决方案 |
|---|---|---|
| crontab 配置 | 重复任务 | 移除冗余 |
| systemd 服务 | 服务过多 | 合并服务 |
| 脚本功能 | 功能重叠 | 统一脚本 |
| 日志路径 | 路径分散 | 统一目录 |
| 文档一致性 | 文档缺失 | 补充文档 |
💡 使用场景
1. 每周冲突检测
# 手动执行
./detect-conflicts.sh
# 定时执行（每周六 22:00）
0 22 * * 6 ./detect-conflicts.sh
2. 配置变更时检测
# 修改 crontab 后触发
crontab -e
./detect-conflicts.sh
📈 协调原则
- 实时性优先: inotifywait > cron
- 可靠性优先: systemd > nohup
- 可恢复优先: trash > rm
- 人工确认优先: 高风险操作需批准
📝 更新日志
v1.0.0 (2026-03-15)
- ✅ 初始版本发布
- ✅ 冲突检测功能
- ✅ 协调方案文档
- ✅ 定期审查机制
维护者: 虾球 🦐
许可: MIT
Usage Guidance
Before installing or running this skill: 1) Treat it as designed for a specific OpenClaw environment — verify /home/admin/.openclaw/workspace and scripts/task-utils.sh exist and are trustworthy. 2) Inspect and, preferably, modify scripts/detect-conflicts.sh to: make WORKSPACE and messaging target configurable (via env vars), remove or redact any sensitive fields from the report, and avoid hard-coded recipient IDs. 3) Confirm what the 'openclaw message send --channel feishu' command does in your environment and whether the recipient 'user:g68578ee' is internal/trusted; if not, disable the push or change to an approved endpoint. 4) Run the script in a safe test environment (non-production user) to observe exactly what files and data it reads and what it posts. 5) Ask the maintainer for explicit documentation of required runtime dependencies/credentials; if they cannot justify them, do not deploy to sensitive systems.
Capability Analysis
Type: OpenClaw Skill
Name: conflict-coordination
Version: 1.0.0
The skill is designed to detect configuration conflicts in crontab, systemd, and scripts, but it contains a hardcoded Feishu user ID (user:g68578ee) in `scripts/detect-conflicts.sh` to which it exfiltrates system metadata. The script sends reports containing details about the user's scheduled tasks, active services, and file structures to this external ID. While the functionality aligns with the stated purpose of 'coordination and reporting,' the hardcoded destination for sensitive system configuration data is a high-risk behavior.
Capability Assessment
Purpose & Capability
The script implements the stated detection capabilities (crontab, systemd, script overlap, logs, docs). However it assumes a specific OpenClaw runtime layout (/home/admin/.openclaw/workspace), sources task-utils.sh from that workspace, and uses an openclaw CLI call; none of those platform-specific requirements are declared in the skill metadata. That mismatch (undocumented required files/paths/CLI) is disproportionate to the SKILL.md/runtime claim of a simple detection utility.
Instruction Scope
SKILL.md instructs running the included detect-conflicts.sh, which reads the user's crontab, queries systemctl --user, enumerates files under /home/admin/.openclaw/workspace, writes a report into that workspace, and then calls 'openclaw message send' to push the report. Those actions go beyond passive checks: they access local configuration and workspace data and actively send a report to a fixed recipient. The SKILL.md does not warn users about what data will be collected or transmitted, nor provide configuration to change the messaging target or redact sensitive info.
Install Mechanism
No install spec (instruction-only plus a script) — nothing is downloaded or written at install time beyond the included files. This is low-risk from an installation/download perspective.
Credentials
The skill declares no required env vars or config paths but the script depends on several environment-specific artifacts: a fixed WORKSPACE path (/home/admin/.openclaw/workspace), a sourced helper script (task-utils.sh), and an openclaw CLI capable of sending Feishu messages. It also hard-codes a Feishu recipient ('user:g68578ee'). These undeclared dependencies and implicit use of messaging credentials are disproportionate and may leak sensitive system state if the messaging endpoint is external or untrusted.
Persistence & Privilege
always:false and no system-wide configuration changes are requested. The script writes reports into the workspace, which is expected for a monitoring tool. However, because the skill can be invoked autonomously (default) and its runtime triggers include cron/inotify, the combination of autonomous invocation plus the hard-coded message send increases potential blast radius if the messaging integration is misconfigured.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install conflict-coordination - After installation, invoke the skill by name or use
/conflict-coordination - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release of the conflict-coordination skill.
- Provides automatic detection of crontab, systemd service, and script conflicts, as well as log path inconsistencies.
- Includes coordination strategies and guidance for resolving detected conflicts.
- Supports weekly automated checks and triggers on configuration changes.
- Documentation includes setup, quickstart, and coordination guides.
- Designed to help maintain system harmony and prevent internal configuration conflicts.
Metadata
Frequently Asked Questions
What is Conflict Coordination?
Mechanism conflict detection and coordination for AI assistant systems. Automatically detects crontab conflicts, systemd service conflicts, script overlaps,... It is an AI Agent Skill for Claude Code / OpenClaw, with 242 downloads so far.
How do I install Conflict Coordination?
Run "/install conflict-coordination" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Conflict Coordination free?
Yes, Conflict Coordination is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Conflict Coordination support?
Conflict Coordination is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Conflict Coordination?
It is built and maintained by alfredming-2026 (@alfredming-2026); the current version is v1.0.0.
More Skills