Menú
Manage QQ automation targets in openclaw.json as single source of truth for qq-automation-manager.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Use when inspecting or repairing QQ route 与专属 agent 的绑定状态，包括 workspace、角色包是否存在、是否需要补齐默认文件。
Use when a QQ-bound agent needs to understand what QQ channel capabilities exist by domain, without loading all NapCat 接口细节 into prompt.
Use when the owner/main agent needs to manage other QQ route agents: 导入角色、切模板、查看关系状态、修复 agent 资源或自动化配置。
Use when reading or adjusting QQ route 的关系状态，比如好感度、信任度、主动性，以及重置关系状态。
Use when managing QQ route角色卡/人设包: 导入角色卡、切换模板、重置角色、查看当前角色摘要。适用于专属 QQ agent 的角色层管理。
| name | qq-automation-admin |
| description | Manage QQ automation targets in openclaw.json as single source of truth for qq-automation-manager. |
| metadata | {"openclaw":{"emoji":"⏱️","disableModelInvocation":true}} |
Use this skill when user wants to add/update/disable QQ proactive automation targets.
Design rule:
${OPENCLAW_HOME}/openclaw.json.plugins.entries["qq-automation-manager"].config.targets.delivery.*) in targets.openclaw cron add/edit during normal operations.MEDIA: 本地路径），由 QQ 插件按当前会话规则发送。List targets:
python3 ${OPENCLAW_HOME}/workspace/skills/qq-automation-admin/scripts/qq_auto_targets.py list
Create or update target:
python3 ${OPENCLAW_HOME}/workspace/skills/qq-automation-admin/scripts/qq_auto_targets.py upsert \
--id qq-user-123456789-weekday \
--route user:123456789 \
--cron "*/30 9-22 * * 1-5" \
--message "结合最近对话，自然延续当前关系与话题，给出一句有温度但不过界的主动消息。" \
--min-silence 30 \
--active-window 25 \
--random-min 30 \
--random-max 60
Disable target:
python3 ${OPENCLAW_HOME}/workspace/skills/qq-automation-admin/scripts/qq_auto_targets.py disable --id qq-user-123456789-weekday
Remove target:
python3 ${OPENCLAW_HOME}/workspace/skills/qq-automation-admin/scripts/qq_auto_targets.py remove --id qq-user-123456789-weekday
Migrate existing targets to agent-only mode:
python3 ${OPENCLAW_HOME}/workspace/skills/qq-automation-admin/scripts/qq_auto_targets.py migrate-agent-only
Audit targets for non-agent-only fields:
python3 ${OPENCLAW_HOME}/workspace/skills/qq-automation-admin/scripts/qq_auto_targets.py audit
openclaw gateway restart
Internal scheduler verification (agent-only mode):
# 0) Static verification against config + state files
python3 ${OPENCLAW_HOME}/workspace/skills/qq-automation-admin/scripts/qq_auto_targets.py verify --id qq-user-123456789-daylife
# 1) Check manager logs
openclaw logs --follow | rg "qq-automation-manager|internal scheduler|triggered target|strictAgentOnly"
# 2) Check route state files (route may be user:... or user__...)
ls -la ${OPENCLAW_HOME}/workspace/qq_sessions/user__123456789/meta
cat ${OPENCLAW_HOME}/workspace/qq_sessions/user__123456789/meta/automation-latest.json
Verification expectations:
executionMode=agent-onlydelivery field on targetautomation-latest.json and appends automation-state.ndjsontriggered/produced/skipped/sent_by_channel/traceNote: manager uses internal scheduler (cron/every/at) and triggers route agent turns only.