46elks
46elks integration. Manage Organizations. Use when the user wants to interact with 46elks data.
Install with Tessl CLI
npx tessl i github:membranedev/application-skills --skill 46elks61
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
40%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 is too vague to effectively guide skill selection. While it correctly identifies the integration (46elks) and includes a 'Use when' clause, it fails to describe what specific capabilities the skill provides beyond the generic 'Manage Organizations'. Users unfamiliar with 46elks wouldn't know this relates to telephony/SMS services.
Suggestions
Add specific concrete actions the skill can perform (e.g., 'Send SMS messages, make phone calls, manage phone numbers, view call logs').
Include natural trigger terms users would say when needing telephony services (e.g., 'SMS', 'text message', 'phone call', 'voice API', 'telephony').
Expand the 'Use when' clause with specific scenarios (e.g., 'Use when the user wants to send SMS, make calls, or manage telephony services through 46elks').
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only mentions 'Manage Organizations' which is vague and abstract. It doesn't list concrete actions like 'create organizations', 'list members', 'update settings', etc. | 1 / 3 |
Completeness | Has a basic 'Use when' clause mentioning '46elks data', but the 'what' is extremely weak ('Manage Organizations') and the 'when' is too vague to provide meaningful guidance on triggers. | 2 / 3 |
Trigger Term Quality | Includes '46elks' as a specific product name which is a good trigger term, but lacks natural variations users might say (e.g., 'SMS', 'phone calls', 'telephony API', 'text messages') and 'organizations' is generic. | 2 / 3 |
Distinctiveness Conflict Risk | '46elks' is a specific product name which helps distinctiveness, but 'Manage Organizations' and 'interact with data' are generic enough to potentially conflict with other CRM or organization management skills. | 2 / 3 |
Total | 7 / 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 CLI commands for 46elks integration via Membrane, with good concrete examples. However, it wastes tokens explaining what 46elks is and lacks validation checkpoints in workflows. The structure could benefit from splitting the action reference into a separate file.
Suggestions
Remove the introductory paragraph explaining what 46elks is - Claude already knows this
Add validation steps after connection creation (e.g., 'Verify connection: membrane connection list --json | grep CONNECTION_ID')
Include error handling guidance for common failures like authentication errors or invalid action IDs
Move the popular actions table to a separate ACTIONS.md reference file to reduce main skill length
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explains what 46elks is, which Claude likely already knows. The overview section listing SMS, Phone Number, Call, etc. adds little value. However, the CLI commands and action tables are appropriately concise. | 2 / 3 |
Actionability | Provides fully executable CLI commands for installation, login, connection setup, searching actions, and running actions. The proxy request section includes concrete flags and examples that are copy-paste ready. | 3 / 3 |
Workflow Clarity | Steps for setup and connection are sequenced, but there are no validation checkpoints or error recovery guidance. Missing feedback loops for verifying connection success or handling failed action runs. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but everything is inline in one file. The popular actions table could be a separate reference file, and there are no links to external detailed documentation within the skill structure. | 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.