1crm
1CRM integration. Manage data, records, and automate workflows. Use when the user wants to interact with 1CRM data.
66
58%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/1crm/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 adequately identifies the domain (1CRM) and includes an explicit 'Use when' clause, which is good. However, the capabilities listed are quite generic ('manage data, records, automate workflows') and lack the specific concrete actions that would help Claude confidently select this skill. The trigger terms could be expanded to include more natural user language around CRM tasks.
Suggestions
Replace generic actions with specific concrete capabilities, e.g., 'Create and update contacts, manage deals and opportunities, track sales pipeline, generate reports' instead of 'manage data, records'.
Expand trigger terms to include natural user language like 'CRM', 'contacts', 'leads', 'sales', 'customer records', 'deals', or specific 1CRM module names.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (1CRM) and some actions ('manage data, records, and automate workflows'), but these are fairly generic and not comprehensive — it doesn't list specific concrete actions like 'create contacts', 'update deals', 'generate reports', etc. | 2 / 3 |
Completeness | Clearly answers both 'what' (manage data, records, automate workflows in 1CRM) and 'when' (explicitly states 'Use when the user wants to interact with 1CRM data'), satisfying the explicit trigger guidance requirement. | 3 / 3 |
Trigger Term Quality | Includes '1CRM' as a key trigger term and mentions 'data', 'records', and 'workflows', but misses common variations users might say like 'CRM', 'contacts', 'leads', 'sales pipeline', 'customer management', or specific 1CRM entity names. | 2 / 3 |
Distinctiveness Conflict Risk | The '1CRM' brand name provides some distinctiveness, but 'manage data, records, and automate workflows' is generic enough to overlap with other CRM or data management skills. Terms like 'data' and 'records' could trigger conflicts with many other integrations. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides solid, actionable CLI commands for interacting with 1CRM via Membrane, which is its primary strength. However, it is significantly weakened by the verbose opening explanation of what 1CRM is and the massive, purposeless entity list that wastes tokens without providing any actionable guidance. The workflow could benefit from clearer sequencing and explicit validation steps.
Suggestions
Remove the opening paragraph explaining what 1CRM is and the entire 40+ item entity bullet list — they consume significant tokens without adding actionable value.
Present the end-to-end workflow (install → auth → connect → discover → run) as a clearly numbered sequence with explicit checkpoints, e.g., 'Verify connection succeeded before proceeding to action discovery.'
Add a concrete end-to-end example showing a real task (e.g., creating a contact) from connection to action run with actual input/output JSON.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explains what 1CRM is (something Claude already knows), and the massive bullet list of 40+ entity types adds no actionable value — it's just a list of nouns with no guidance on how to use them. 'Use action names and parameters as needed' is vacuous filler. | 1 / 3 |
Actionability | The skill provides concrete, copy-paste-ready CLI commands for every step: installing the CLI, authenticating, connecting, searching for actions, creating actions, and running actions with JSON input. The commands include specific flags and parameters. | 3 / 3 |
Workflow Clarity | The steps are listed in a logical sequence (install → auth → connect → search → create → run), and the action creation flow includes polling with state checks. However, there are no explicit validation checkpoints or error recovery loops beyond checking the error field, and the overall flow isn't presented as a numbered sequence with clear decision points. | 2 / 3 |
Progressive Disclosure | The content has reasonable section structure with headers, but the 40+ item entity list is inline bloat that adds no value and could be removed entirely. There are no references to separate files for advanced topics. The official docs link is present but not contextualized for specific use cases. | 2 / 3 |
Total | 8 / 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
56d7336
- 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.