New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Use Avibe

by avibe-bot in avibe-bot/avibe

Safely inspect and modify local Avibe configuration, routing, runtime settings, watches, scheduled tasks, Avibe Cloud remote access, and operational state.

MITAuto-check passedProductivity & Automation

Install Use Avibe

skills CLI
$ npx skills add avibe-bot/avibe --skill use-avibe -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install avibe-bot/avibe use-avibe --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/avibe-bot/avibe.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/use-avibe .claude/skills/use-avibe && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
use-avibe
GitHub stars
622
Token cost
~2.5k tokens
SKILL.md length
1,421 words
Files
11 (incl. scripts, references)
Skills in repo
7
Repo updated
First seen
Licence
MIT

At a glance

Safely inspect and modify local Avibe configuration, routing, runtime settings, watches, scheduled tasks, Avibe Cloud remote access, and operational state.

  • Works in 12 steps: Prefer the Web UI API for Avibe… → Read current API state before mutating.… → Preserve unrelated scopes, platforms,… → …
  • Report an Avibe bug
  • SKILL.md covers Core Rules, API First Workflow, Task References and Safety Boundaries, plus 2 more sections
  • Runs Python scripts from its folder

What it does

Use Avibe is an agent skill from avibe-bot/avibe. Safely inspect and modify local Avibe configuration, routing, runtime settings, watches, scheduled tasks, Avibe Cloud remote access, and operational state. Also use it to report an Avibe bug, send product feedback, or file a feature request from the current conversation.

Its SKILL.md is about 2.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 12 other files, including scripts and reference files (for example `references/api-client.md`, `references/backends.md` and `references/feedback.md`).

It sits in Productivity & Automation, covering Scheduled and recurring tasks and Messaging and chat bots. It works with Feishu (Lark), WeChat, Discord and Slack. The repository describes itself as: The local-first Agent OS — your AI partner lives on your own machine. Drive the official Claude Code, Codex & OpenCode from your browser or any chat app. The licence is MIT.

When your agent uses it

  • Report an Avibe bug
  • Send product feedback
  • File a feature request from the current conversation

Example prompts

  • “/use-avibe”

Requirements

  • Python 3

Workflow steps

12 steps, taken from the first numbered list in SKILL.md.

  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 scopes, platforms, users, and secrets.
  4. Treat secrets as opaque. Do not print, invent, rotate, or overwrite tokens unless the user explicitly provides replacements.
  5. Use the smallest viable API call and verify by reading back the API response.
  6. For POST /settings, preserve every existing channel for that platform; the endpoint replaces the platform's channel map.
  7. For POST /api/users, merge each edited user with its current user payload first; missing user fields are not a patch.
  8. 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…
  9. POST /config persists the new payload but does not restart running platform adapters by itself. When the change is platform credentials…
  10. Do not restart the service by default. Use POST /doctor, GET /status, and read-back checks first.
  11. Only start, stop, restart, or reload Avibe when the user explicitly asks or when a change cannot take effect otherwise; explain why before…
  12. If an agent must restart Avibe from an active conversation, use vibe restart --delay-seconds 60 so the current session can receive the…

What it can do on your machine

Read from SKILL.md and the folder at commit b3fc733. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 2 files in scripts/ (Python), which the agent can run.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Use Avibe loads about 2.5k tokens when it runs, and up to ~19k if it reads all its reference files. Until then it costs about 70 tokens; SKILL.md has 1,421 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~70
When it runs · the whole SKILL.md, loaded when a task matches
~2.5k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~19k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from avibe-bot/avibe at commit b3fc733, republished under its MIT licence (© avibe-bot). 1,421 words, ~2,527 tokens.

Download SKILL.mdSave it as .claude/skills/use-avibe/SKILL.md (or your agent's skills folder). This skill also uses 10 other files; get the full folder from GitHub.
name
use-avibe
description
Safely inspect and modify local Avibe configuration, routing, runtime settings, watches, scheduled tasks, Avibe Cloud remote access, and operational state. Also use it to report an Avibe bug, send product feedback, or file a feature request from the current conversation.
slug
use-avibe
version
0.8.0

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
  • report an Avibe bug, send product feedback, or file a feature request from the current conversation ("report this to Avibe", "submit a bug", "request a feature")

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 scopes, platforms, users, and secrets.
  4. Treat secrets as opaque. Do not print, invent, rotate, or overwrite tokens unless the user explicitly provides replacements.
  5. Use the smallest viable API call and verify by reading back the API response.
  6. For POST /settings, preserve every existing channel for that platform; the endpoint replaces the platform's channel map.
  7. For POST /api/users, merge each edited user with its current user payload first; missing user fields are not a patch.
  8. 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.
  9. 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.
  10. Do not restart the service by default. Use POST /doctor, GET /status, and read-back checks first.
  11. 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.
  12. 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.
  13. Tell the user whether the change is global or scope-specific.

API First Workflow

Use this order when changing Avibe configuration:

  1. Determine the Web UI base URL.
    • Default is http://127.0.0.1:5123.
    • If the user has a custom UI host or port (from ui.setup_host / ui.setup_port), use that exact origin.
    • When Avibe Cloud remote access is active, the public origin (e.g. https://<slug>.avibe.bot) also speaks the same API and requires OIDC session cookies — prefer the local origin from the host running Avibe.
    • Check liveness with GET /health or GET /status.
  2. Decide whether the request belongs in:
    • POST /config for global defaults, platform credentials, runtime config, agent defaults, UI config, remote-access provider settings, update policy, or global display toggles
    • POST /settings for channel-level routing, working directory, visibility, enablement, and mention policy
    • /api/users and /api/bind-codes for DM user binding and user-scope settings
    • /remote-access/* for Avibe Cloud pairing and tunnel control
    • host backend config instead of Avibe when the request is OpenCode, Claude Code, or Codex native behavior
  3. Fetch the current state from the matching GET endpoint.
  4. Merge the requested change in memory.
  5. Send the mutating request through the Web UI API with CSRF protection.
  6. Read back the changed resource and verify the effective payload.
  7. Run POST /doctor only when the change affects runtime health, platform credentials, or backend availability.
  8. Report the changed scope or global keys and whether a restart was avoided or still required.

Task References

Read only the reference needed for the current task, before composing its calls. Paths below are relative to this Skill directory; scripts remain under scripts/, not under references/.

TaskReference
Send API requests with CSRF, cookies, JSON payloads, or the bundled helperAPI client
Change global defaults, platform credentials, proxies, or discover IM channelsGlobal configuration and platforms
Change channel/DM routing, models, cwd, visibility, mention policy, or bind usersScopes and routing
Pair, inspect, repair, or control the Avibe Cloud tunnelRemote access
Run or delegate Agent work, schedule tasks, manage watches or Session queuesAgent Harness
Choose backend/subagent settings or change native OpenCode, Claude, or Codex configBackends
Inspect runtime paths, logs, or health; restart or upgrade the serviceOperations and troubleshooting
Turn a problem or a wish in this conversation into a bug report, feedback, or feature requestFeedback and feature requests

For multi-step API work, use the bundled scripts/vibe_api.py helper. The API client reference contains its exact invocations and fetch/merge examples.

Show full SKILL.md (517 more words)Show less

Safety Boundaries

Always follow these constraints:

  • never delete unrelated platform scopes
  • never blank out tokens or secrets as part of an unrelated config task
  • never claim a backend feature exists if current Avibe behavior does not support it
  • never read, query, or hand-edit Avibe's internal state storage — go through the Web UI API or vibe CLI
  • never expose bind codes, pairing keys, tunnel tokens, instance secrets, or session secrets unless the user explicitly asks
  • never paste a credentialed proxy_url (user:pass@host) back into chat — mask the credentials portion when echoing the value
  • always say when a requested change actually belongs in OpenCode, Claude Code, or Codex config instead of Avibe
  • never publish anything derived from this conversation until that exact content, destination, and posting identity are authorized — a destination is a host, a repository, and an acting account, never whatever the environment happens to supply; sanitize first, and keep the authorization to one concrete yes rather than a prompt per step; ordinary reads and generic public searches are already covered by the task
  • never splice a generated or user-supplied value into a shell command string; pass it as its own argument

Escalation

Some requests are not local maintenance at all. Switch to the feedback workflow in Feedback and feature requests when:

  • the behavior looks like a real bug rather than a local misconfiguration
  • the user is asking for a feature Avibe does not support yet
  • backend integration behavior appears inconsistent with the documented configuration surface
  • the user simply asks to report something or request a change, with or without prior diagnosis

That reference owns the whole path: gathering facts from this conversation, drafting a short English report, sanitizing it, getting approval, and submitting it to https://github.com/avibe-bot/avibe through an already authorized channel. Do not stop at "open an issue yourself", and do not treat diagnosis, a restart, or a repair as a precondition for filing.

When the user has approved the sanitized content and public consent, use the official route in the feedback reference when commissioning has marked it available. Its packaged scripts/feedback_intake.py helper is distributed inside this existing Skill by the normal wheel skills/ inclusion and built-in snapshot publication path. A development checkout or a deployed receiver alone does not update a client's installed Skill. The helper is bound to the operator's HTTPS Show share and cs-agent-bot posting identity; it creates one UUIDv4, persists the exact payload in its local outbox, and reads the separate public receipt before claiming an Issue URL. resume <request_id> only reads receipts; explicit delivery recovery requires saved POST429 evidence and a fresh minimal404.

If the user wants to contribute back with code, suggest a pull request in that repository.

Response Pattern

When you complete an Avibe maintenance task, report back with:

  1. which API endpoint changed the state
  2. whether the change is global or scope-specific
  3. which keys changed
  4. the read-back or doctor evidence
  5. whether a restart was avoided, deferred, or still required and why

A feedback or feature-request task reports something different: the verified issue URL, or the finished draft plus an explicit statement that it was not submitted.

© avibe-bot, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 10 other files (scripts, references) in skills/use-avibe of avibe-bot/avibe.

  • SKILL.md
  • references/api-client.md
  • references/backends.md
  • references/feedback.md
  • references/global-config.md
  • references/harness.md
  • references/operations.md
  • references/remote-access.md
  • references/scopes-and-routing.md
  • scripts/feedback_intake.py
  • scripts/vibe_api.py

Open the folder on GitHubat commit b3fc733

Compare with similar skills

Use Avibe next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Use Avibe compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Use Avibe this skillavibe-bot/avibe622—~2.5kAutomated safety check: PassMIT
Feedbacknexu-io/nexu3.3k—~660Automated safety check: WarnMIT
Claude To Imop7418/Claude-to-IM-skill2.9k—~3.4kAutomated safety check: NotesMIT
Message Push0xranx/golembot322—~984Automated safety check: PassMIT
Task Manager0xranx/golembot322—~694Automated safety check: PassMIT
Channel Managerclacky-ai/openclacky1.2k—~6.1kAutomated safety check: NotesMIT

Similar skills

  • Feedback

    nexu-io/nexu

    Send feedback to the Nexu team. An agent skill from nexu-io/nexu.

    3.3k GitHub stars~660 tokensUpdated 5 mo ago
    Productivity & AutomationAuto-check: warnings

  • Claude To Im

    op7418/Claude-to-IM-skill

    Bridge THIS Claude Code or Codex session to Telegram, Discord, Feishu/Lark, QQ, or WeChat so the user can chat with Claude from their phone.

    2.9k GitHub stars~3.4k tokensUpdated 6 mo ago
    Productivity & AutomationAuto-check: notes

  • Message Push

    0xranx/golembot

    Send proactive messages to IM groups or individual users via the gateway Send API.

    322 GitHub stars~984 tokensUpdated 12 days ago
    Productivity & AutomationAuto-check passed

  • Task Manager

    0xranx/golembot

    Creates and manages scheduled tasks, cron jobs, recurring reminders, and timers via the Task HTTP API.

    322 GitHub stars~694 tokensUpdated 12 days ago
    Productivity & AutomationAuto-check passed

  • Channel Manager

    clacky-ai/openclacky

    Configure IM platform channels (Feishu, WeCom, Weixin, Discord, Telegram, DingTalk) for openclacky.

    1.2k GitHub stars~6.1k tokensUpdated today
    Productivity & AutomationAuto-check: notes

  • Channel Manager

    open-octo/octo-agent

    Configure IM platform channels (Feishu, Weixin/WeChat, WeCom, DingTalk, Discord, Telegram) for octo.

    125 GitHub stars~6.2k tokensUpdated yesterday
    Productivity & AutomationAuto-check passed

More from avibe-bot/avibe

  • Agent Prompt Audit

    avibe-bot/avibe

    Audit and improve the prompt surface of Avibe Agents across backends (Claude, Codex/GPT, OpenCode) — global and project rules, Agent system prompts, Skills, delegation briefs, and Task and Watch…

    622 GitHub stars~2.9k tokensUpdated today
    Auto-check passed

  • PR Delivery Loop

    avibe-bot/avibe

    Deliver implementation PRs across Avibe, avibe-backend, avibe-docs, avault, and vault-sandbox.

    622 GitHub stars~4.1k tokensUpdated today
    Auto-check passed

  • Background Watch Hook

    avibe-bot/avibe

    Use vibe watch to run a managed Harness waiter that returns to the same conversation later.

    622 GitHub stars~7.7k tokensUpdated today
    Auto-check passed

  • Use Show Pages

    avibe-bot/avibe

    Build, inspect, update, restore, or share Avibe Show Pages for visual explanations, diagrams, reports, or interactive prototypes.

    622 GitHub stars~2.3k tokensUpdated today
    Auto-check passed

  • Use Avibe Harness

    avibe-bot/avibe

    Use Avibe Harness for durable Agent delegation, Sessions, scheduled Tasks, Watches, Runs, queues, and work that must continue beyond the current turn.

    622 GitHub stars~3.7k tokensUpdated today
    Auto-check passed

  • Use Avibe Vault

    avibe-bot/avibe

    Use Avibe Vault for API keys, tokens, passwords, protected credentials, authenticated HTTP requests, or digest signing without exposing secret values to the agent.

    622 GitHub stars~1.1k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Use Avibe

What does Use Avibe do?

Safely inspect and modify local Avibe configuration, routing, runtime settings, watches, scheduled tasks, Avibe Cloud remote access, and operational state. Use Avibe is an agent skill from avibe-bot/avibe. Safely inspect and modify local Avibe configuration, routing, runtime settings, watches, scheduled tasks, Avibe Cloud remote access, and operational state.

When should I use Use Avibe?

Use Avibe fits situations like: report an Avibe bug; send product feedback; file a feature request from the current conversation.

How do I install Use Avibe in Claude Code?

Run `npx skills add avibe-bot/avibe --skill use-avibe -a claude-code`. Or copy the skill folder (skills/use-avibe in avibe-bot/avibe) into .claude/skills/use-avibe in your project. Claude Code loads it when a task matches its description.

How do I install Use Avibe in Codex?

Run `npx skills add avibe-bot/avibe --skill use-avibe -a codex`. Or copy the skill folder (skills/use-avibe in avibe-bot/avibe) into .agents/skills/use-avibe in your project. Codex loads it when a task matches its description.

Can I use Use Avibe in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add avibe-bot/avibe --skill use-avibe -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/use-avibe, .gemini/skills/use-avibe, .github/skills/use-avibe and .opencode/skills/use-avibe in your project.

What does Use Avibe need to run?

Going by SKILL.md and its folder, Use Avibe needs Python for the scripts in its folder. Our summary lists: Python 3.

Does Use Avibe access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Use Avibe safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Use Avibe use?

Use Avibe is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Use Avibe use?

About 2.5k tokens (SKILL.md is roughly 10k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 17k tokens, read only when the agent opens those files.

What are the alternatives to Use Avibe?

Skills that share tags, products or a category with Use Avibe: Feedback (nexu-io/nexu, 3.3k stars), Claude To Im (op7418/Claude-to-IM-skill, 2.9k stars), Message Push (0xranx/golembot, 322 stars) and Task Manager (0xranx/golembot, 322 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Use Avibe?

avibe-bot (a GitHub organization) maintains it in avibe-bot/avibe, which has 622 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 10, 2026.

Source: avibe-bot/avibe on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.