accelo
Accelo integration. Manage Organizations, Leads, Pipelines, Users, Goals, Filters. Use when the user wants to interact with Accelo data.
48
51%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/accelo/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 is functional and clearly scoped to the Accelo platform, with an explicit 'Use when' clause that aids skill selection. However, the verb 'Manage' is too generic—it would benefit from specifying concrete CRUD operations. The trigger terms could also be expanded to include synonyms or related concepts users might naturally use.
Suggestions
Replace the vague 'Manage' with specific actions like 'Create, update, list, and delete Organizations, Leads, Pipelines, Users, Goals, and Filters'.
Add natural trigger terms users might say, such as 'CRM', 'sales pipeline', 'contacts', or 'Accelo API' to improve keyword coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (Accelo) and lists specific entity types (Organizations, Leads, Pipelines, Users, Goals, Filters), but 'Manage' is a vague verb—it doesn't specify concrete actions like create, update, delete, list, or search. | 2 / 3 |
Completeness | It answers both 'what' (manage Organizations, Leads, Pipelines, Users, Goals, Filters in Accelo) and 'when' (Use when the user wants to interact with Accelo data), with an explicit 'Use when...' clause. | 3 / 3 |
Trigger Term Quality | It includes 'Accelo' as a strong trigger term and entity names like 'Organizations', 'Leads', 'Pipelines' which users might mention, but it lacks common action-oriented terms users would say like 'create lead', 'update organization', 'CRM', or 'project management'. | 2 / 3 |
Distinctiveness Conflict Risk | Accelo is a specific platform, making this skill clearly distinguishable from other integrations or CRM-related skills. The explicit mention of 'Accelo' creates a distinct trigger unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
27%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is severely bloated by a ~150+ item bullet list of Accelo objects (with many duplicates) that provides no actionable guidance, consuming a huge portion of the token budget for zero value. The Membrane CLI integration instructions are reasonably concrete but lack complete worked examples with real inputs/outputs. The content would benefit enormously from removing the object list, adding end-to-end examples, and splitting reference material into separate files.
Suggestions
Remove or drastically reduce the 'Accelo Overview' bullet list — it's duplicated, non-actionable, and wastes hundreds of tokens. If object types matter, list only the 5-10 most common ones.
Add 1-2 complete end-to-end examples showing a real workflow (e.g., 'List all companies, then get details for one') with actual input JSON and expected output.
Split reference content (popular actions table, proxy request options) into a separate REFERENCE.md file and link to it from the main skill.
Remove the introductory paragraph explaining what Accelo is — Claude can infer this from context, and it wastes tokens on background information.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The massive bullet-point list of ~150+ Accelo 'objects' is egregiously wasteful — most items are duplicated, many are generic concepts (e.g., 'Guideline', 'Standard', 'Framework', 'Simulation'), and the entire list provides zero actionable value. The introductory paragraph explaining what Accelo is also wastes tokens on information Claude already knows or can infer. | 1 / 3 |
Actionability | The CLI commands for authentication, connection, action search, and action execution are concrete and copy-paste ready. However, there are no complete end-to-end examples with real input/output, the popular actions table lacks example invocations with actual input JSON, and the proxy request section has no Accelo-specific path examples. | 2 / 3 |
Workflow Clarity | The connection setup flow is reasonably well-sequenced with state handling (READY, CLIENT_ACTION_REQUIRED, etc.), but there are no explicit validation checkpoints after running actions, no error recovery guidance for failed action runs, and the overall workflow from 'user request' to 'completed task' is not clearly laid out as a numbered sequence. | 2 / 3 |
Progressive Disclosure | The skill is a monolithic wall of text with no bundle files or references to external documents. The enormous object list should be in a separate reference file. There's no separation between quick-start content and detailed reference material, and no navigation structure to help find specific information. | 1 / 3 |
Total | 6 / 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.