agile-crm
Agile CRM integration. Manage Persons, Organizations, Deals, Leads, Activities, Notes and more. Use when the user wants to interact with Agile CRM data.
60
70%
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/agile-crm/SKILL.mdQuality
Discovery
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 clearly identifies its niche (Agile CRM) and includes an explicit 'Use when' clause, making it complete and distinctive. However, it relies on the vague verb 'Manage' and the filler phrase 'and more' instead of listing specific concrete actions, and it could benefit from more natural trigger terms users would actually say.
Suggestions
Replace 'Manage' with specific actions like 'Create, update, delete, and search' to improve specificity.
Remove 'and more' and instead list additional concrete capabilities or common user phrases like 'CRM pipeline', 'contact management', 'deal tracking'.
Expand trigger terms in the 'Use when' clause to include variations like 'CRM contacts', 'sales pipeline', 'deal stages', or 'customer records in Agile'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Agile CRM) and lists entity types (Persons, Organizations, Deals, Leads, Activities, Notes), but the actions are vague — 'Manage' and 'and more' don't describe concrete operations like create, update, delete, or search. | 2 / 3 |
Completeness | Answers both 'what' (manage Persons, Organizations, Deals, etc. in Agile CRM) and 'when' ('Use when the user wants to interact with Agile CRM data'), providing an explicit trigger clause. | 3 / 3 |
Trigger Term Quality | Includes 'Agile CRM' as a strong trigger term and entity names like 'Deals', 'Leads', 'Activities' which users might mention. However, it lacks common action-oriented terms users would say like 'create contact', 'update deal', 'add note', or 'CRM pipeline'. | 2 / 3 |
Distinctiveness Conflict Risk | The explicit mention of 'Agile CRM' makes this highly distinctive and unlikely to conflict with other CRM skills (e.g., Salesforce, HubSpot) or generic data management skills. | 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.
The skill provides solid, actionable CLI commands for Agile CRM integration via Membrane, with good coverage of authentication, connection management, action discovery, and proxy requests. Its main weaknesses are some unnecessary introductory content, a lack of validation/confirmation steps for destructive operations, and a monolithic structure that could benefit from splitting reference material into separate files.
Suggestions
Remove the introductory paragraph explaining what Agile CRM is and the bare entity bullet list — Claude already knows this, and the popular actions table provides better context.
Add explicit validation/confirmation guidance for destructive operations (delete, update) — e.g., 'Before deleting, retrieve the record first to confirm it's the correct one' or 'Verify update results by fetching the record after modification'.
Consider moving the popular actions table and proxy request details into separate reference files (e.g., ACTIONS.md, PROXY.md) and linking to them from the main SKILL.md to improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanations (e.g., 'Agile CRM is a customer relationship management platform used by sales and marketing teams' and the overview bullet list of entities without any actionable context). The Membrane CLI setup and connection flow are reasonably efficient but could be tightened. The popular actions table is large but useful as a reference. | 2 / 3 |
Actionability | The skill provides fully executable CLI commands for every step: installation, authentication, connection setup, action discovery, action execution, and proxy requests. Commands are copy-paste ready with clear parameter placeholders and flag descriptions. | 3 / 3 |
Workflow Clarity | The connection setup workflow has a clear sequence with state-based branching (READY, CLIENT_ACTION_REQUIRED, errors), but there are no explicit validation checkpoints for destructive operations like delete actions. The workflow for delete/update operations lacks any confirmation or verification steps, which should cap this at 2. | 2 / 3 |
Progressive Disclosure | The content is reasonably structured with clear sections, but it's somewhat monolithic — the popular actions table, proxy request details, and connection state machine documentation could be split into separate reference files. There are no references to external bundle files for deeper content, and the single-file approach makes it longer than ideal for a SKILL.md overview. | 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 | |
- 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.