← Back to Skills Marketplace
vrtalex

Bitrix24 Skill

by vrtalex · GitHub ↗ · v1.0.0
cross-platform ✓ Security Clean
766
Downloads
3
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install bitrix24-apiskill
Description
Integrate AI agents with Bitrix24 REST API to automate CRM, tasks, chats, event processing, auth selection, and API error troubleshooting.
README (SKILL.md)

Bitrix24 Agent (Lean + Reliable)

Use this skill to deliver correct Bitrix24 integrations with minimal token usage.

Default Mode: Lean

Apply these limits unless the user asks for deep detail:

  • Load at most 2 reference files before first actionable step.
  • Start from references/packs.md.
  • Then open only one target file: references/catalog-\x3Cpack>.md.
  • Open references/chains-\x3Cpack>.md only if user asks for workflow/chain.
  • Open references/bitrix24.md only for auth architecture, limits, events reliability, or unknown errors.

Response format limits:

  • Use concise output (goal + next action + one command).
  • Do not retell documentation.
  • Do not dump large JSON unless explicitly requested.
  • Avoid repeating already provided guidance; return only delta.

Routing Workflow

  1. Determine intent:
  • method call,
  • troubleshooting,
  • architecture decision,
  • event/reliability setup.

Term normalization (product vocabulary):

  • "collabs", "workgroups", "projects", "social network groups" -> collab (and boards for scrum).
  • "Copilot", "CoPilot", "BitrixGPT", "AI prompts" -> platform (ai.*).
  • "open lines", "contact center connectors", "line connectors" -> comms (imopenlines.*, imconnector.*).
  • "feed", "live feed", "news feed" -> collab (log.*).
  • "sites", "landing pages", "landing" -> sites (landing.*).
  • "booking", "calendar", "work time", "time tracking" -> services (booking.*, calendar.*, timeman.*).
  • "orders", "payments", "catalog", "products" -> commerce (sale.*, catalog.*).
  • "consents", "consent", "e-signature", "sign" -> compliance (userconsent.*, sign.*).
  1. Choose auth quickly:
  • one portal/internal: incoming webhook.
  • app/multi-portal/lifecycle features: OAuth.
  1. Select minimal packs:
  • default core.
  • add only required packs: comms, automation, collab, content, boards, commerce, services, platform, sites, compliance, diagnostics.
  1. Execute with guardrails:
  • prefer scripts/bitrix24_client.py and scripts/offline_sync_worker.py,
  • enforce allowlist + --confirm-write / --confirm-destructive,
  • keep writes idempotent when possible.
  1. Escalate to deep reference only on trigger:
  • WRONG_AUTH_TYPE, insufficient_scope, QUERY_LIMIT_EXCEEDED, expired_token,
  • offline event loss concerns,
  • OAuth refresh race or tenant isolation issues.

Quality Guardrails

  • Never expose webhook/OAuth secrets.
  • Scope and permissions must be least-privilege.
  • No nested batch.
  • Online events are not guaranteed delivery; use offline flow for no-loss processing.
  • Prefer REST 3.0 where compatible; fallback to v2 where needed.

Reference Loading Map

  1. references/packs.md for pack and loading strategy.
  2. references/catalog-\x3Cpack>.md for method shortlist.
  3. references/chains-\x3Cpack>.md for implementation chains.
  4. references/bitrix24.md only when deeper protocol detail is required.

Useful search shortcuts:

rg -n "^# Catalog|^# Chains" references/catalog-*.md references/chains-*.md
rg -n "WRONG_AUTH_TYPE|insufficient_scope|QUERY_LIMIT_EXCEEDED|expired_token" references/bitrix24.md
rg -n "offline|event\\.bind|event\\.offline|application_token" references/bitrix24.md

Scripts

  • scripts/bitrix24_client.py: method calls, packs, allowlist, confirmations, audit.
  • scripts/offline_sync_worker.py: offline queue processing with retries and DLQ.
Usage Guidance
This skill appears to implement what it claims (Bitrix24 REST integration) and uses only Bitrix-relevant environment variables and local files. Before installing: (1) Review and store Bitrix tokens (OAuth/webhook) in a dedicated secrets store or env scoped to the skill; avoid placing other service credentials in the same environment. (2) Run the scripts against a test portal first (use B24_RUN_INTEGRATION or a sandbox) and enable the two-phase/plan-only mode (B24_REQUIRE_PLAN / --plan-only) to avoid accidental writes. (3) Note the scripts write local state (rate limiter, retry state, DLQ); decide where those files will live and who can read them. (4) If you need a policy-level check, ask the publisher to declare required env vars in the registry metadata (current manifest lists none despite many documented env variables). (5) If you are not comfortable granting access to Bitrix tokens, do not enable this skill or provide only least-privilege tokens scoped to the operations you intend to allow.
Capability Analysis
Type: OpenClaw Skill Name: bitrix24-apiskill Version: 1.0.0 The OpenClaw AgentSkills skill bundle for Bitrix24 is designed with a strong emphasis on security and reliability. It implements numerous guardrails such as method allowlisting, explicit confirmation for write/destructive operations, two-phase execution planning, idempotency, secrets masking, audit logging, and rate limiting. The `scripts/bitrix24_client.py` and `scripts/offline_sync_worker.py` handle API interactions and event processing with robust error handling and security checks (e.g., `secure_compare` for application tokens). Documentation (`SKILL.md`, `README.md`, `references/*.md`) consistently advises on security best practices and least privilege. There is no evidence of intentional harmful behavior, data exfiltration to unauthorized endpoints, or malicious code execution. The `process_event_default` function in `offline_sync_worker.py` is a no-op placeholder, meaning the provided skill itself does not process event payloads in a risky manner.
Capability Assessment
✓ Purpose & Capability
Name/description (Bitrix24 REST integrations) matches the included code, CLI scripts, and many Bitrix-specific reference files. All env vars and files referenced in the README/SKILL.md (webhook code, OAuth tokens, B24_* vars) are directly relevant to Bitrix API integration.
✓ Instruction Scope
SKILL.md limits agent actions to Bitrix references and the included scripts, prescribes allowlists/confirm flags, and explicitly forbids exposing secrets. It does not instruct reading unrelated system files or transmitting data to unrelated external endpoints.
✓ Install Mechanism
There is no install spec (scripts are shipped as files). No network downloads, package installs, or obscure URLs are used by the skill itself. This is lower-risk than an arbitrary remote installer.
ℹ Credentials
The registry metadata lists no required env vars, but README and SKILL.md show many effective environment variables (B24_DOMAIN, B24_AUTH_MODE, B24_ACCESS_TOKEN, B24_CLIENT_SECRET, etc.). Those variables are appropriate for Bitrix integration, but the metadata omission is a mild inconsistency — the skill expects secrets/tokens to be present at runtime.
ℹ Persistence & Privilege
Scripts legitimately read/write local state (rate limiter, retry state, DLQ, plan files) and may create files when running. always:false and no elevated privileges are requested. Persisted files can contain event payloads and retry metadata; users should be aware of on-disk storage location and access controls.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install bitrix24-apiskill
  3. After installation, invoke the skill by name or use /bitrix24-apiskill
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release of bitrix24-agent skill. - Provides a lean, reliable workflow for integrating AI agents with Bitrix24 REST API. - Implements strict limits on file loading and response verbosity for efficiency. - Normalizes Bitrix24 product vocabulary for clear intent detection. - Guides rapid selection of authentication model and minimal required API packs. - Enforces security and reliability guardrails, including secret handling and write confirmation. - Includes scripts for online/offline API interaction and event processing.
Metadata
Slug bitrix24-apiskill
Version 1.0.0
License —
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is Bitrix24 Skill?

Integrate AI agents with Bitrix24 REST API to automate CRM, tasks, chats, event processing, auth selection, and API error troubleshooting. It is an AI Agent Skill for Claude Code / OpenClaw, with 766 downloads so far.

How do I install Bitrix24 Skill?

Run "/install bitrix24-apiskill" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Bitrix24 Skill free?

Yes, Bitrix24 Skill is completely free (open-source). You can download, install and use it at no cost.

Which platforms does Bitrix24 Skill support?

Bitrix24 Skill is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Bitrix24 Skill?

It is built and maintained by vrtalex (@vrtalex); the current version is v1.0.0.

More Skills
self-improving agent
Captures learnings, errors, and corrections to enable continuous improvement. Use when: (1) A command or operation fails unexpectedly, (2) User corrects Clau...
⬇ 463283 · by pskoett
Skill Vetter
Security-first skill vetting for AI agents. Use before installing any skill from ClawdHub, GitHub, or other sources. Checks for red flags, permission scope, and suspicious patterns.
⬇ 259410 · by spclaudehome
Polymarket
Query Polymarket prediction markets. Check odds, find trending markets, search events, track price movements.
⬇ 232503 · by joelchance
Self-Improving + Proactive Agent
Self-reflection + Self-criticism + Self-learning + Self-organizing memory. Agent evaluates its own work, catches mistakes, and improves permanently. Use when...
⬇ 200423 · by ivangdavila
Github
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
⬇ 191115 · by steipete
ontology
Typed knowledge graph for structured agent memory and composable skills. Use when creating/querying entities (Person, Project, Task, Event, Document), linkin...
⬇ 190156 · by oswalpalash

💬 Comments