accelo
Accelo integration. Manage Organizations, Leads, Pipelines, Users, Goals, Filters. Use when the user wants to interact with Accelo data.
Install with Tessl CLI
npx tessl i github:membranedev/application-skills --skill accelo69
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.
This description adequately identifies the Accelo integration domain and includes an explicit 'Use when' clause, making it functional for skill selection. However, it relies on the vague verb 'Manage' rather than listing specific actions, and could benefit from additional natural trigger terms that users might say when needing CRM-related functionality.
Suggestions
Replace 'Manage' with specific concrete actions like 'Create, update, query, and delete Organizations, Leads, Pipelines...'
Add natural trigger terms users might say, such as 'CRM', 'sales pipeline', 'customer management', or 'work management platform'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Accelo) and lists entity types (Organizations, Leads, Pipelines, Users, Goals, Filters) but uses vague verb 'Manage' without specifying concrete actions like create, update, delete, or query. | 2 / 3 |
Completeness | Explicitly answers both what ('Manage Organizations, Leads, Pipelines, Users, Goals, Filters') and when ('Use when the user wants to interact with Accelo data') with a clear trigger clause. | 3 / 3 |
Trigger Term Quality | Includes 'Accelo' as a key trigger term and entity names that users might mention, but lacks common variations or action-oriented terms users would naturally say like 'CRM', 'sales pipeline', 'contacts', or 'customer data'. | 2 / 3 |
Distinctiveness Conflict Risk | The specific mention of 'Accelo' as a named platform creates a clear niche that is unlikely to conflict with other CRM or integration skills, as it's tied to a specific product. | 3 / 3 |
Total | 10 / 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 good actionable CLI commands and a useful action reference table, but is severely bloated by an unnecessary 150+ item list of Accelo concepts that adds no value. The workflow lacks validation steps for connection verification and error handling, and the content organization would benefit from moving reference material to separate files.
Suggestions
Remove or drastically reduce the 'Accelo Overview' bullet list - Claude doesn't need a catalog of every possible Accelo object type
Remove the introductory paragraph explaining what Accelo is - this is unnecessary context
Add validation steps after connection creation (e.g., 'Verify connection: membrane connection list --json | grep CONNECTION_ID')
Add error handling guidance for common failure scenarios (auth failures, invalid action IDs, API errors)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The massive bullet-point list of 150+ Accelo concepts (many duplicated) is unnecessary padding that Claude already understands. The introductory paragraph explaining what Accelo is wastes tokens on context Claude doesn't need. | 1 / 3 |
Actionability | Provides fully executable CLI commands with clear syntax, specific flags, and copy-paste ready examples. The action table with keys and descriptions, plus the proxy request options, give concrete guidance. | 3 / 3 |
Workflow Clarity | Steps for setup and connection are listed but lack validation checkpoints. No guidance on verifying successful connection, handling errors, or confirming action results before proceeding. | 2 / 3 |
Progressive Disclosure | Content is somewhat structured with sections, but the enormous inline list of Accelo objects should be in a separate reference file. No external file references for detailed API documentation or examples. | 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 | |
- 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.