mcpField
B
bitrix24-tasks

bitrix24-tasks

github.com/bxmaximumDevelopment4784 installsUpdated 2w ago
Repository

About bitrix24-tasks

A server-side task guide for Bitrix24 on-premise developers, covering task reads and writes, members, deadlines, checklists, and access. It emphasizes V2 commands for writes and checking the acting user’s permissions before execution.

Key features

  1. 01Task creation, update, and deletion guidance
  2. 02Task list filtering and pagination
  3. 03Member, deadline, and checklist handling
  4. 04Access rights and event guidance
  5. 05V2 commands and fallback approach

Use cases

  1. 01Create or update tasks in an on-premise portal
  2. 02Query and filter task lists
  3. 03Set task members, deadlines, and tags
  4. 04Check user permissions before write operations

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/bxmaximum/bitrix-framework-skills --skill bitrix24-tasks

After installing, type/bitrix24-tasksin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

rules/
access-events.md
details.md
reading.md
writing.md

Details

From the project README

Bitrix24 tasks (server side)

Scope: Bitrix24 on-premise · Verified: tasks 26.300.100, main 26.800.0

TaskRead
Pick the API layer; create, update, complete, delete; errorsrules/writing.md
One task or lists: filters, sort, paging, datesrules/reading.md
Members, deadlines and time zones, checklists, tags, projects, templates, commentsrules/details.md
Access actions, events and their arguments, REST mappingrules/access-events.md

Invariants

  • Write through the V2 commands (AddTaskCommand, UpdateTaskCommand …; legacy CTaskItem/CTasks end in the same V2 services). Never write TaskTable or member/checklist tables: counters, chat, search, events and recycle bin are skipped.
  • Commands do not check rights. Check TaskAccessService/TaskAccessController for the acting user before run().
  • Pass the acting user id explicitly (userId in configs). Agents and CLI have no $USER; CTasks::Add without USER_ID acts as user 1.
  • Dates in V2 entities are Unix timestamps (deadlineTs). Never pass site-format strings from background code.
  • Keep V2 calls in one /local gateway class: commands take V2\Internal\… entities and configs that may change between releases. The V2 layer is verified in tasks 26.300.100 only; if class_exists(AddTaskCommand::class) is false, use CTaskItem.
  • New task card: comments are messages in the task chat (see rules/details.md, bitrix24-im).

Comments

Markdown supported