BB bitrix24-rest
Work with Bitrix24 (Битрикс24) via REST API and MCP documentation server. Triggers on: CRM — "сделки", "контакты", "лиды", "воронка", "клиенты", "deals", "contacts", "leads", "pipeline"; Tasks — "задачи", "мои задачи", "просроченные", "создай задачу", "tasks", "overdue", "to-do"; Calendar — "расписание", "встречи", "календарь", "schedule", "meetings", "events"; Chat — "чаты", "сообщения", "уведомления", "написать", "notifications", "messages"; Channels — "каналы", "канал", "объявления", "подписчики", "channels", "announcements", "subscribers"; Open Lines — "открытые линии", "поддержка", "обращения", "клиентские чаты", "операторы", "омниканал", "виджет чата", "open lines", "support", "customer chat", "helpdesk", "operator"; Projects — "проекты", "рабочие группы", "projects", "workgroups"; Time — "рабочее время", "кто на работе", "учёт времени", "timeman", "work status"; Drive — "файлы", "документы", "диск", "files", "documents", "drive"; Structure — "сотрудники", "отделы", "структура", "подчинённые", "departments", "employees", "org structure"; Feed — "лента", "новости", "объявления", "feed", "announcements"; Scenarios — "утренний брифинг", "morning briefing", "еженедельный отчёт", "weekly report", "статус команды", "что у меня сегодня", "итоги дня", "план на день", "воронка продаж", "расскажи про клиента", "подготовь к встрече", "как работает отдел".
As a process B 75/100 · Nearly there — weak spots: inputs and preconditions, running it twice
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- Shorten the description to 1024 characters.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 27. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- error
description-longdescription is 1373 chars, limit 1024 - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
body-longSKILL.md body ≈ 6036 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 75/100
- 30Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 20 mutating operations with no state check
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70Execution cost. Instruction body is 6036 tokens
- 100Steps. 122 steps
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 7 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 12 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 1372: 120–800 characters recommended
- -223 emoji in the instructions: noise for the model
- -31 of 4 scripts are never mentioned in SKILL.md
- +1No license
- +5Description quotes 73 example trigger phrases
- +4Structure: 40 headings
- +3Step-by-step instructions: 122 items
- +3Output format is stated explicitly
- +4Has examples (22 code blocks)
- +4Reference files are cited in the instructions (19 of 19)
- +2Bilingual instructions (RU + EN)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 43.