---
name: Use Vibe Remote
slug: use-vibe-remote
category: Automation
description: Use Vibe Remote guides agents through safe edits to local Vibe Remote config and runtime files. It covers defaults, per-channel overrides, validation, restarts, and when to adjust backend settings instead of Vibe Remote itself.
github: "https://github.com/avibe-bot/avibe/tree/master/docs/plans/use-avibe-skill.md"
language: Python
stars: 494
forks: 76
install: "npx degit https://github.com/avibe-bot/avibe/tree/master/docs/plans ~/.claude/skills/plans"
installs_to: ~/.claude/skills/plans
source_path: docs/plans/use-avibe-skill.md
collection_size: 5
category_size: 1523
collection_url: "https://dirskills.com/collections/avibe-bot/avibe"
added: 2026-08-26T05:12:56.928Z
last_synced: 2026-08-26T05:12:56.928Z
canonical_url: "https://dirskills.com/skills/use-vibe-remote"
---

# Use Vibe Remote

Use Vibe Remote guides agents through safe edits to local Vibe Remote config and runtime files. It covers defaults, per-channel overrides, validation, restarts, and when to adjust backend settings instead of Vibe Remote itself.

**Install:**

```bash
npx degit https://github.com/avibe-bot/avibe/tree/master/docs/plans ~/.claude/skills/plans
```

## README

# Use Vibe Remote Skill Plan

## Background

- We want a reusable skill at `skills/use-avibe/` that teaches agents how to maintain a local Vibe Remote installation.
- The skill should be usable as a default skill for agents that operate inside or alongside Vibe Remote.
- The highest-value use case is translating natural-language requests such as "enable this Slack channel and route it to Codex with GPT-5.4 high reasoning" into safe, accurate config edits.

## Goal

- Document the current Vibe Remote runtime file model and config-editing workflow.
- Cover both global defaults (`config.json`) and per-channel/per-user overrides (`settings.json`).
- Explain operational commands, validation, restart flow, and troubleshooting.
- Explain how host backends such as OpenCode, Claude Code, and Codex should be configured when a requested change belongs to the backend rather than Vibe Remote itself.

## Solution

- Add `skills/use-avibe/SKILL.md` with agent-oriented instructions.
- Keep the skill self-contained: include the runtime path map, config schema overview, precedence rules, backend capability matrix, operational guardrails, and concrete request-to-edit recipes.
- Anchor OpenCode/Codex/Claude backend notes to official docs where practical.
- Call out implementation caveats where the repo schema exposes a field that is not the main runtime source of truth.

## Todo

- [x] Inspect Vibe Remote config/state/runtime source files and existing docs.
- [x] Create a task worktree from `origin/master`.
- [x] Draft this plan document.
- [x] Author `skills/use-avibe/SKILL.md`.
- [x] Validate the skill with `askill validate`.
- [x] Run a reviewer pass and address findings.