bitrix24-vibecode

Install

Clone github.com/lucky-naty/bitrix24-vibecode into ~/.claude/skills/bitrix24-vibecode (for Codex ~/.codex/skills/bitrix24-vibecode) so SKILL.md and references sit at the folder root.

This is third-party code. Review the repository files before installing.

What it does

The skill helps the agent work with the VibeCode Bitrix24 platform without rereading all the docs. It first classifies the task and opens the right section, loading platform facts only when needed. References cover the three key types and when to use each, the difference between VibeCode APIs and native Bitrix24 REST, a step-by-step app deploy with status waits and an error table, iframe placement apps with per-operator identity, business process robots and rate limits. A separate checklist lists predictable mistakes the author ran into in practice.

Who it is for. For developers building Bitrix24 integrations, bots and apps on the VibeCode platform.

Example request

Deploy this app to VibeCode and figure out why it is unreachable after deploy

Limitations

The skill is built from public VibeCode docs and the author's observations, and some error codes and limits are marked as observed rather than documented. The platform changes, so the agent should verify exact parameters against live docs. The skill runs nothing itself, but the tasks it serves require VibeCode keys.

How to disable. Delete the bitrix24-vibecode folder from ~/.claude/skills or ~/.codex/skills.

Security check

• The skill consists only of instructions and references

README in short

The README describes a minimal layout: the repository root is the skill folder, with SKILL.md and six references. It explains which mistakes the skill helps avoid: key choice, API confusion, deploy model, bulk operations. A detailed changelog records platform audit results, new pitfalls and doc-based fixes. It ends with the VibeCode doc sections the skill was built from. MIT license.

SKILL.md

---
name: bitrix24-vibecode
description: Use when working with VibeCode Bitrix24 apps, integrations, bots, or AI Router workflows.
---

# VibeCode Docs

## Overview

Use this skill to route through VibeCode docs quickly, keep platform invariants straight, and avoid re-deriving basics.

## Workflow

1. Identify the task type before reading docs in depth.
2. Load [references/section-routing.md](references/section-routing.md) and open only the most relevant section first.
3. Load [references/universal-knowledge.md](references/universal-knowledge.md) only when the task touches build, deploy, auth, API conventions, scaling, or error handling.
4. Load [references/anti-footguns.md](references/anti-footguns.md) only before implementation or debugging.
5. Confirm endpoint-level details from the live docs only when the answer depends on exact parameter names, current limits, or current behavior.
6. Distinguish VibeCode platform behavior from native Bitrix24 behavior.

## Load Minimally

- For explanation-only questions, start with `section-routing` and stop unless the answer needs platform invariants.
- For implementation or debugging, read `universal-knowledge` before writing code.
- For exact request shapes or current behavior, verify against the live docs instead of relying on memory.

## Task Patterns

### App, Bot, Or Integration Build

Use quick start plus the target domain section. Default flow:

1. Inspect capabilities with `/v1/me`
2. Build against Entity API or another target API
3. Create infrastructure if deployment is needed
4. Deploy and wait for `running` plus `CONNECTED`

### Auth And Access Questions

Open keys/auth first. Decide from the key prefix whether the task is personal (`vibe_api_`), OAuth app (`vibe_app_`), or management (`vibe_live_`). For OAuth app requests, remember that a bearer session token may also be required for user-context calls.

Related