1c
1C-Bitrix integration. Manage data, records, and automate workflows. Use when the user wants to interact with 1C-Bitrix data.
48
51%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/1c/SKILL.mdQuality
Discovery
67%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 correctly identifies the 1C-Bitrix domain and includes an explicit 'Use when' clause, which is good. However, the actions described are quite generic ('manage data, records, automate workflows') and could apply to almost any integration platform. Adding more specific capabilities and natural trigger terms would significantly improve skill selection accuracy.
Suggestions
Add specific concrete actions like 'create and update CRM leads, manage deals, sync contacts, handle tasks and calendar events' to replace the vague 'manage data, records'.
Expand trigger terms to include common variations users would say: 'Bitrix24', 'CRM', 'Bitrix API', 'leads', 'deals', 'tasks'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (1C-Bitrix) and some actions ('manage data, records, and automate workflows'), but these actions are fairly generic and not comprehensive — it doesn't specify concrete operations like 'create leads', 'update CRM contacts', 'sync inventory', etc. | 2 / 3 |
Completeness | Clearly answers both 'what' (manage data, records, automate workflows) and 'when' ('Use when the user wants to interact with 1C-Bitrix data'), with an explicit trigger clause present. | 3 / 3 |
Trigger Term Quality | Includes '1C-Bitrix' which is a strong domain-specific keyword, and 'data', 'records', 'workflows' are somewhat relevant but generic. Missing natural variations like 'Bitrix24', 'CRM', 'Bitrix API', 'leads', 'deals', or other terms users would naturally use. | 2 / 3 |
Distinctiveness Conflict Risk | '1C-Bitrix' is a distinct platform name which helps, but 'manage data, records, and automate workflows' is very generic and could overlap with other CRM, ERP, or workflow automation skills. The 'when' clause is also broad enough to potentially conflict. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is a generic Membrane CLI integration template with a thin 1C-Bitrix veneer. It wastes tokens explaining what 1C-Bitrix is and provides no platform-specific action examples or workflows. The CLI commands are concrete but lack validation steps and error handling guidance.
Suggestions
Remove the introductory paragraph explaining what 1C-Bitrix is — Claude already knows this. Replace with a one-line purpose statement.
Replace the vague 'Overview' section (Task, User, Department) with concrete examples of common 1C-Bitrix action IDs and their typical input parameters.
Add validation checkpoints after key steps: verify connection succeeded (`membrane connection list`), verify action output is as expected, and include error recovery guidance for common failures.
Remove or significantly trim the 'Best practices' section — most of it restates what the instructions already convey implicitly.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explains what 1C-Bitrix is ('a content management system...think of it as a regional alternative to WordPress or Drupal') — Claude already knows this. The overview section listing Task/User/Department with no actionable detail wastes tokens. Best practices section restates things already implied by the instructions. | 1 / 3 |
Actionability | Provides concrete CLI commands for installation, login, connection, searching actions, and running actions with parameters. However, the 1C-Bitrix-specific guidance is thin — the overview section ('Task, User, Department — use action names and parameters as needed') is vague and non-actionable. No concrete examples of actual 1C-Bitrix action IDs or typical workflows are shown. | 2 / 3 |
Workflow Clarity | Steps for setup and connection are sequenced clearly (install → login → search connector → connect). However, there are no validation checkpoints — no guidance on verifying the connection succeeded, no error handling for failed action runs, and no feedback loops for common failure modes. | 2 / 3 |
Progressive Disclosure | Content is organized with headers and sections, but it's somewhat monolithic — the proxy request reference table and best practices could be separated or trimmed. There are no references to external bundle files for advanced topics, and the overview section is a stub that doesn't link anywhere useful. | 2 / 3 |
Total | 7 / 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 | |
- Repository
- membranedev/application-skills
- Commit
f484c82
- Reviewed
Table of Contents
Is this your skill?
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.