SkillFoxx

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

  • 103 ★ on the repository
  • Last commit
  • MIT
SkillOfficialEditors’ pick

Extended access

Why this level

  • Generated code calls a live Bitrix24 portal via a webhook or OAuth
  • Mishandling webhook secrets or OAuth tokens can expose portal access
All reasons and checks
Russian stack

bitrix24/b24phpsdkAuthor:Bitrix24

Install

Services

In your terminal, with SkillFoxx CLI

npx skillfoxx add skills/bitrix24-php-sdk

Detects the agents on your machine, shows the access level and pins the version.

Other ways to install

Access and checks

How we review

Extended accessThe tool runs code or makes network calls and only reads external data.

  • Generated code calls a live Bitrix24 portal via a webhook or OAuth
  • Mishandling webhook secrets or OAuth tokens can expose portal access

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

What it does

The b24phpsdk-developer skill lives inside the SDK repository itself at resources/skills and targets product applications that consume bitrix24/b24phpsdk, not development of the SDK. It lays out a workflow: check the installed version and services via ServiceBuilderFactory first, choose a webhook for a server integration tied to one fixed portal or OAuth for an app installed into different portals, keep secrets only in configuration, catch SDK exceptions at the application boundary, and work with results and pagination through SDK methods rather than the raw response array. Separate reference files cover installation, result handling, and error handling with tests.

Who it is for. For PHP developers building Bitrix24 integrations with the official SDK who want an agent to write code in the project's own style.

Good fit when

  • You are writing PHP code that calls bitrix24/b24phpsdk services
  • You need to correctly initialize access via a webhook or OAuth
  • You want an established practice for SDK exceptions, pagination and batch calls

Not a fit when

  • You are working on the SDK repository itself: issues, releases, generated service wrappers and OpenAPI coverage, for which the repository has a separate b24phpsdk-maintainer skill
  • You need an SDK for a language other than PHP

Example request

Write a service that fetches recent Bitrix24 contacts through b24phpsdk via a webhook and wraps SDK errors

Limitations

The skill must be copied into your project by hand; the README gives no single install command. It requires bitrix24/b24phpsdk already installed via Composer. The library ships two incompatible versions, v1 on the main branch and v3 on the v3 branch with a different REST endpoint format, and the skill does not choose a version for you.

How to disable. Delete the b24phpsdk-developer folder from your project's .claude/skills, or .agents/skills if you used the generic format.

FAQ

How is this different from b24phpsdk-maintainer in the same repository?

b24phpsdk-developer targets code that consumes the SDK in your own app, while b24phpsdk-maintainer is only for working on the SDK repository itself: issues, releases, generated services.

Webhook or OAuth?

The skill recommends a webhook for server integrations tied to a fixed portal, and OAuth only when the application itself owns Bitrix24 installation and token storage.

Discussion

No questions or reviews yet.

All Bitrix24 tools
Russian stack

A skill for administering, diagnosing and developing boxed Bitrix24 and Bitrix Framework, built from official documentation

SkillExtended access1
Russian stack

Four skills for Bitrix24 apps: install and OAuth, a batching REST client, events and iframe placements, CRM business processes and calendar

SkillExtended access

The @bitrix24/b24jssdk skill set

@bitrix24/b24jssdk skills

Official

Seven official Bitrix24 skills for the JS/TS SDK: picking B24Hook, B24Frame or B24OAuth, REST calls, filters, iframe managers and 12 ready mini-apps

SkillExtended access18
Russian stack

A Bitrix24 REST skill split into capability packs with a method allowlist, risk confirmations and an audit log

SkillBroad access26

Bitrix24 REST API skill

bitrix24-rest-api

Russian stack

A Claude Code skill with real-portal-verified Bitrix24 REST API gotchas: auth modes, errors hidden under HTTP 200, retries and rate limits

SkillMinimal access

README in short

The SKILL.md file describes the skill's scope, a seven-step workflow for using the SDK, and a routing table to three reference files: installation and initialization, result and pagination handling, error handling and tests. It separately shows an adapter pattern that keeps domain code independent of SDK services through a product-owned interface.

README badge

Original SKILL.md

---
name: b24phpsdk-developer
description: Use when writing product application code with bitrix24/b24phpsdk, integrating Bitrix24 webhooks or OAuth, choosing SDK service calls, handling SDK results, errors, pagination, batch calls, or tests outside the SDK repository
---

# Bitrix24 PHP SDK Developer

## Scope

Use this skill for product applications that consume `bitrix24/b24phpsdk`.

Do not use it for SDK repository maintenance: GitHub issue triage, release work, changelog policy,
OpenAPI coverage, generated SDK service wrappers, result-item annotation tests, or other SDK
internals. In the SDK repository, those tasks belong to `b24phpsdk-maintainer`.

## Workflow

1. Inspect the installed package version and public API first: read `composer.lock`, run
   `composer show bitrix24/b24phpsdk`, and search `vendor/bitrix24/b24phpsdk/src/Services` before
   writing integration code.
2. Prefer `ServiceBuilderFactory` and public service builders over direct REST calls.
3. Use incoming webhook initialization for server-side integrations that can rely on a fixed portal
   webhook. Use OAuth only when the product owns Bitrix24 app installation, token storage, and token
   refresh.
4. Keep webhook URLs, OAuth tokens, client secrets, and portal domains in environment or application
   configuration. Never inline them in code, docs, test fixtures, or logs.
5. Catch SDK exceptions at the application boundary. Do not scatter low-level SDK error handling
   through domain code.
6. Prefer SDK result objects and accessors such as `getContacts()` over raw response-array indexing.
7. Treat list calls as paginated. Use batch helpers deliberately when reading many records.
8. Test product logic with fakes around your own SDK boundary. Keep live Bitrix24 checks explicit,
   opt-in, and driven by `BITRIX24_WEBHOOK`.

Report a problem