Safely inspect and modify local Avibe configuration, routing, runtime settings, watches, scheduled tasks, Avibe Cloud remote access, and operational state.
SkillScore32Maintained
Automatic
◆DevOps & SRE pack
Last verified 8/21/2026
What it changes
Passed 3 of 8 test cases with the skill, and 2 of 8 without it.
Without skill23%
With skill32%
Checks it passed that the model alone missed
Runs vibe agent run with --session-id sess_abc123.
Obtains CSRF cookie and token from GET /api/csrf-token using a cookie jar.
Uses DELETE /api/users/U5544?platform=slack to reliably revoke DM authorization.
and 2 more in the full report
3 fixed4 passed either way14 still failing1 broke
Pass-rate lift
+9 pp
Tokens
+825%
Agent turns
0%
Response time
-45%
Model gemini-3.6-flashMeasured 8/21/2026v27 of 22 cases passed with skill · 8 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 3
Prompt
Trigger an asynchronous background agent job targeted at session sess_abc123 to review open pull requests using the claude agent. Do not block the current CLI execution.
What was checked, without and with the skill
Checked
Without skill
With skill
Runs vibe agent run with --session-id sess_abc123.
Missed
Passed
Passes --agent claude and omits --sync so the execution runs asynchronously.
Passed
Passed
case-16 · gemini-3.6-flash · 8/21/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md1036 lines2 filesincludes scripts
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
Prefer the Web UI API for Avibe configuration changes. Do not hand-edit config files for routine work.
Read current API state before mutating. Merge the user's requested change into the current payload.
Preserve unrelated scopes, platforms, users, and secrets.
Treat secrets as opaque. Do not print, invent, rotate, or overwrite tokens unless the user explicitly provides replacements.
Use the smallest viable API call and verify by reading back the API response.
For POST /settings, preserve every existing channel for that platform; the endpoint replaces the platform's channel map.
For POST /api/users, merge each edited user with its current user payload first; missing user fields are not a patch.
Make every persistent-state change through the Web UI API or the vibe CLI. Avibe's internal storage is opaque — do not read, query, or hand-edit it.
POST /config persists the new payload but does not restart running platform adapters by itself. When the change is platform credentials, proxy_url, or other transport-level settings, plan an explicit restart afterwards; prefer the delayed CLI form (vibe restart --delay-seconds 60) when triggering it from inside an active conversation. The only credential save that restarts on its own is the WeChat QR-login completion through POST /wechat/qr_login/poll.
Do not restart the service by default. Use POST /doctor, GET /status, and read-back checks first.
Only start, stop, restart, or reload Avibe when the user explicitly asks or when a change cannot take effect otherwise; explain why before doing it.
If an agent must restart Avibe from an active conversation, use vibe restart --delay-seconds 60 so the current session can receive the reply before the restart lands.
Tell the user whether the change is global or scope-specific.