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.
80
76%
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/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 functional for skill selection. However, it relies on the vague verb 'Manage' and the filler phrase 'and more' instead of listing specific concrete actions. Adding specific operations and more natural user trigger terms would strengthen it.
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 entity types to avoid vague filler language.
Add natural trigger terms users might say, such as 'CRM contacts', 'sales pipeline', 'deal tracking', or 'customer records'.
| 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 specify concrete operations like create, update, delete, or search. | 2 / 3 |
Completeness | It answers both 'what' (manage Persons, Organizations, Deals, Leads, Activities, Notes 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', 'Persons' 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 | 'Agile CRM' is a specific product name that creates a clear niche, making it highly unlikely to conflict with other CRM skills (e.g., Salesforce, HubSpot) or generic data management skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with clear workflow sequencing and concrete CLI commands throughout. Its main weaknesses are mild verbosity (introductory explanation, large inline table) and lack of progressive disclosure — the popular actions table and detailed state-handling documentation could be split into referenced files. The workflow clarity is strong with explicit state checks and polling loops.
Suggestions
Remove the introductory paragraph explaining what Agile CRM is — Claude already knows this, and the skill description covers it.
Move the popular actions table to a separate reference file (e.g., ACTIONS.md) and link to it from the main skill to improve progressive disclosure and reduce token usage.
Remove or condense the bare bullet list under 'Agile CRM Overview' — it adds little value without descriptions and the popular actions table already covers the key entities.
| 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...') and the overview bullet list of entity types adds little value without descriptions. The popular actions table is large but arguably useful. Overall mostly efficient but could be tightened. | 2 / 3 |
Actionability | The skill provides concrete, copy-paste-ready CLI commands for every step: installation, authentication, connection management, action discovery, action creation, and action execution. Parameters and flags are clearly specified with examples. | 3 / 3 |
Workflow Clarity | The multi-step workflow is clearly sequenced: install CLI → authenticate → ensure connection → handle connection states (with explicit state machine: BUILDING, READY, CLIENT_ACTION_REQUIRED, errors) → search for actions → run actions. Validation checkpoints and polling/retry loops are explicitly documented for both connections and actions. | 3 / 3 |
Progressive Disclosure | The content is reasonably structured with clear sections, but the popular actions table is quite long and could be referenced externally. The overview bullet list and the detailed connection state handling are all inline, making the document longer than necessary for a SKILL.md overview. No references to external files for detailed content. | 2 / 3 |
Total | 10 / 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
88db8c5
- 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.