1C-Bitrix integration. Manage data, records, and automate workflows. Use when the user wants to interact with 1C-Bitrix data.
75
Quality
70%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/1c/SKILL.mdDiscovery
75%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description adequately identifies the 1C-Bitrix platform and includes an explicit 'Use when' clause, making it functional for skill selection. However, the capabilities listed are generic ('manage data, records, automate workflows') and could apply to almost any integration platform. The description would benefit from more specific actions and additional trigger terms.
Suggestions
Add specific concrete actions like 'create leads, manage deals, sync contacts, configure webhooks' to improve specificity
Include common trigger term variations users might say: 'Bitrix24', 'CRM', 'leads', 'deals', 'contacts', 'tasks'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (1C-Bitrix) and mentions some actions ('Manage data, records, and automate workflows'), but these are fairly generic and not comprehensive - doesn't specify what types of data, records, or workflows. | 2 / 3 |
Completeness | Clearly answers both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with 1C-Bitrix data') with an explicit trigger clause. | 3 / 3 |
Trigger Term Quality | Includes '1C-Bitrix' which is the key product name users would mention, but lacks common variations or related terms users might say (e.g., 'Bitrix24', 'CRM', 'leads', 'deals', 'tasks'). | 2 / 3 |
Distinctiveness Conflict Risk | The specific mention of '1C-Bitrix' creates a clear niche that is unlikely to conflict with other skills - this is a distinct platform with a unique name. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides solid, actionable CLI commands for 1C-Bitrix integration via Membrane, with good coverage of common operations. However, it wastes tokens on unnecessary platform explanation, lacks validation/error handling guidance, and the 'Overview' section is cryptic without adding value.
Suggestions
Remove the opening paragraph explaining what 1C-Bitrix is - Claude doesn't need this context
Delete or expand the cryptic 'Overview' section with Task/User/Department bullets - currently it provides no actionable information
Add validation steps after key operations (e.g., 'Verify connection succeeded by running membrane connection list')
Include error handling guidance for common failures like auth timeout or invalid connection IDs
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explaining what 1C-Bitrix is wastes tokens on context Claude doesn't need. The rest is reasonably efficient but could be tightened - the 'Overview' section with bullet points adds little value. | 2 / 3 |
Actionability | Provides fully executable CLI commands throughout with clear syntax examples. Commands are copy-paste ready with proper flags and JSON output options documented. | 3 / 3 |
Workflow Clarity | Steps are listed for setup and connection flows, but lacks validation checkpoints. No guidance on verifying successful connection, handling failed auth, or confirming action execution succeeded. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but the 'Overview' section with Task/User/Department bullets is cryptic and unhelpful. No references to external files for advanced topics despite mentioning official docs. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.