bitrix24-vibecode skill
A skill for building on VibeCode Bitrix24: docs routing, keys and auth, Black Hole deployment and common mistakes
- 2 ★ on the repository
- Last commit
- MIT
Minimal access
Why this level
- The skill consists only of instructions and references
Install
- Works in
- Services
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/bitrix24-vibecodeDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewMinimal accessThe tool runs nothing and makes no network calls.
- The skill consists only of instructions and references
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.
Good fit when
- You need to deploy an app to VibeCode and find out why it is unreachable
- You need to pick the right key type for an integration
- You need a CRM card tab app or a business process robot
Not a fit when
- You work with on-premise Bitrix24 or plain REST without VibeCode
- You need a Bitrix24 integration via an MCP server
Example request
Deploy this app to VibeCode and figure out why it is unreachable after deployLimitations
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.
FAQ
How does it help with deploys?
deploy-playbook gives a linear order: packaging, deploy with waits for running and CONNECTED, redeploy, and a symptom, cause and fix table.
Is there a Codex version?
Yes, the skill is platform-neutral, and there is an optional agents/openai.yaml for Codex.
Discussion
No questions or reviews yet.
Related
All Bitrix24 toolsA skill for administering, diagnosing and developing boxed Bitrix24 and Bitrix Framework, built from official documentation
Bitrix24 app development skill pack
bitrix24-skills-emcsoft
Four skills for Bitrix24 apps: install and OAuth, a batching REST client, events and iframe placements, CRM business processes and calendar
Codex skills for Bitrix development
Bitrix Agent Skills (Core)
Four Codex skills for Bitrix and Bitrix24 development: project audit and architecture, migrating tables to Grid, FTP deploy and incident triage
Bitrix24 REST API skill
bitrix24-rest-api
A Claude Code skill with real-portal-verified Bitrix24 REST API gotchas: auth modes, errors hidden under HTTP 200, retries and rate limits
A Claude Code and Codex skill for 1C-Bitrix and on-premise Bitrix24 development: check the project core first, then answer
Bitrix24 PHP SDK developer skill
Bitrix24 PHP SDK
A skill for Bitrix24's official PHP SDK that teaches an agent to wire up webhooks and OAuth, call SDK services, and handle results, errors and pagination
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.
README badge
Original 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.