use-vibe-remote

# Use Avibe Use this skill when the user asks you to configure, repair, explain, or operate a local Avibe installation. Typical requests include: - enable a Slack, Discord, Telegram, Lark/Feishu, or WeChat scope - route one channel or DM user to OpenCode, Claude, or Codex - set a working directory for a channel or DM user - choose a backend model, subagent, or reasoning level - show or hide intermediate message types - configure an outbound proxy (`proxy_url`) for an IM platform that cannot reach its API directly - pair, start, stop, or inspect Avibe Cloud remote Web UI access - create, update, inspect, pause, resume, or remove a managed background watch with `vibe watch` - create, inspect, run, pause, resume, or remove a scheduled task with `vibe task` - run a one-shot Agent job with `vibe agent run`, including async background runs - inspect or cancel concrete Agent Run records with `vibe runs` - check or apply Avibe updates (`vibe check-update`, `vibe upgrade`) - inspect logs, run doctor, check service status, or explain where Avibe stores state - decide whether a requested change belongs in Avibe config or in the host backend's own config Follow this skill as an operations playbook for agents, not as end-user marketing copy. ## Core Rules 1. Prefer the Web UI API for Avibe configuration changes. Do not hand-edit config files for routine work. 2. Read current API state before mutating. Merge the user's requested change into the current payload. 3. Preserve unrelated ...