AF bitrix24-agent
Design, implement, debug, and harden integrations between AI agents and Bitrix24 REST API (webhooks, OAuth 2.0, scopes, events, batch, limits, and REST 3.0). Use when asked to connect AI assistants/agents to Bitrix24, automate CRM/tasks/chats, process Bitrix24 events, choose an auth model, or resolve Bitrix24 API errors and performance issues.
Design, implement, debug, and harden integrations between AI agents and Bitrix24 REST API (webhooks, OAuth 2.0, scopes, events, batch, limits, and REST 3.0).…
As a process F 51/100 · Will not run — References files that are not bundled: references/catalog-<pack>.md, references/chains-<pack>.md
How to improve
- The text references files that are not there: add them or drop the references.
- 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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Exfiltration
read-dotenvREADME.md:202Reads a .env filecp .env.example .env
-
low Exfiltration
read-dotenvREADME.md:203Reads a .env filesource .env
Files scanned: 31. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: references/catalog-<pack>.md - warning
missing-refreference to a missing file: references/chains-<pack>.md
Process rating: all ten parameters 51/100
- 0Tools and files. 2 referenced file(s) missing: references/catalog-<pack>.md, references/chains-<pack>.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 40Consistency. Frontmatter name (bitrix24-agent) differs from the folder (bitrix24-apiskill)
- 60Result and completion. Output format stated, no completion criterion
- 100Steps. 47 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Execution cost. Instruction body is 877 tokens
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
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
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +1No license
- +2Single-language instructions
- +3Description length 345: enough signal without eating the budget
- +4Structure: 6 headings
- +3Step-by-step instructions: 47 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (2 of 26)
- +3All 2 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 85.