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.
Install with Tessl CLI
npx tessl i github:membranedev/application-skills --skill agile-crm75
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 adequately identifies the specific CRM platform and includes an explicit 'Use when' clause, which are its main strengths. However, it relies on vague action language ('Manage', 'and more') instead of listing concrete operations, and could benefit from more natural trigger terms users might actually say when working with CRM data.
Suggestions
Replace 'Manage' with specific actions like 'Create, update, search, and delete' to improve specificity
Add natural trigger terms users might say such as 'contacts', 'pipeline', 'sales records', 'customer data', or 'CRM sync'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Agile CRM) and lists entity types (Persons, Organizations, Deals, Leads, Activities, Notes) but uses vague action 'Manage' and 'and more' rather than listing specific concrete actions like 'create', 'update', 'delete', 'search'. | 2 / 3 |
Completeness | Clearly answers both what (manage various CRM entities) and when ('Use when the user wants to interact with Agile CRM data') with an explicit trigger clause. | 3 / 3 |
Trigger Term Quality | Includes 'Agile CRM' as a key trigger term and entity names users might mention, but misses common variations like 'contacts', 'pipeline', 'CRM records', 'sales data', or action-oriented terms users would naturally say. | 2 / 3 |
Distinctiveness Conflict Risk | 'Agile CRM' is a specific product name that creates a clear niche, making it highly unlikely to conflict with other CRM skills or general 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.
This skill provides solid actionable guidance with executable CLI commands and a comprehensive action reference table. However, it includes unnecessary introductory content about what Agile CRM is, lacks validation checkpoints for destructive operations, and could benefit from better progressive disclosure by moving the large action table to a separate reference file.
Suggestions
Remove the introductory paragraph explaining what Agile CRM is - Claude already knows this
Add validation/confirmation guidance for destructive operations (delete actions) to prevent accidental data loss
Move the popular actions table to a separate ACTIONS.md reference file and link to it
Remove or contextualize the bare entity list in the Overview section - it currently provides no actionable value
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanation (e.g., 'Agile CRM is a customer relationship management platform used by sales and marketing teams') that Claude already knows. The overview section listing entity types without context adds little value. However, the CLI commands and action tables are reasonably efficient. | 2 / 3 |
Actionability | Provides fully executable CLI commands with clear syntax, a comprehensive table of action keys, and concrete examples for running actions with JSON parameters. The proxy request section includes specific flags and usage patterns that are copy-paste ready. | 3 / 3 |
Workflow Clarity | Steps for setup and connection are listed but lack validation checkpoints. For destructive operations like delete actions, there's no mention of confirmation or verification steps. The workflow for checking existing connections vs creating new ones could be clearer with explicit decision points. | 2 / 3 |
Progressive Disclosure | Content is reasonably structured with clear sections, but the popular actions table is quite long and could be referenced externally. The overview section listing entity types without explanation adds clutter. No external file references are used despite the content length. | 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 | |
- 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.