aircall
Aircall integration. Manage Calls, Users, PhoneNumbers. Use when the user wants to interact with Aircall data.
Install with Tessl CLI
npx tessl i github:membranedev/application-skills --skill aircall75
Quality
70%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/aircall/SKILL.mdDiscovery
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 Aircall integration domain and includes an explicit 'Use when' clause, which is good for skill selection. However, it lacks specific concrete actions beyond the generic 'Manage' and could benefit from more natural trigger terms that users might actually say when needing telephony/call management help.
Suggestions
Replace 'Manage' with specific actions like 'Create, list, and transfer calls; add and configure users; assign and manage phone numbers'
Add natural trigger terms users might say: 'phone system', 'call logs', 'VoIP', 'telephony', 'call center'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Aircall) and lists general resource types (Calls, Users, PhoneNumbers), but 'Manage' is vague and doesn't specify concrete actions like 'create calls', 'list users', or 'configure phone numbers'. | 2 / 3 |
Completeness | Explicitly answers both what ('Manage Calls, Users, PhoneNumbers') and when ('Use when the user wants to interact with Aircall data') with a clear trigger clause. | 3 / 3 |
Trigger Term Quality | Includes 'Aircall' as a key trigger term and mentions resource types, but misses natural variations users might say like 'phone system', 'call logs', 'VoIP', or 'telephony'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Aircall' is a specific product name that creates a clear niche, making it unlikely to conflict with other skills unless there are multiple Aircall-related 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 CLI commands for Aircall integration via Membrane, with good coverage of common operations. However, it includes unnecessary introductory content, lacks validation/error handling guidance in workflows, and the extensive actions table could be more efficiently organized. The core technical content is useful but could be tightened.
Suggestions
Remove the introductory paragraph explaining what Aircall is and the sparse 'Aircall Overview' bullet list - Claude already knows this context
Add validation steps after key operations (e.g., 'Verify connection succeeded by running `membrane connection list --json` and confirming the new connection appears')
Add error handling guidance for common failure scenarios like authentication failures or invalid action IDs
Consider moving the full actions table to a separate reference file and keeping only 3-5 most common actions inline
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some unnecessary explanation (e.g., 'Aircall is a cloud-based call center...' which Claude already knows). The overview section with bullet points adds little value, and the best practices section restates obvious points. | 2 / 3 |
Actionability | Provides fully executable CLI commands with clear syntax, including examples for installation, login, connection setup, action discovery, and proxy requests. Commands are copy-paste ready with placeholder values clearly marked. | 3 / 3 |
Workflow Clarity | Steps are listed for setup and connection but lack explicit validation checkpoints. No guidance on verifying successful connection, handling failed authentication, or confirming action execution succeeded. The workflow is sequential but missing error recovery steps. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but the popular actions table is quite long and could be referenced externally. The structure is flat without external file references, though for a skill of this size that's acceptable. Some sections could be better signaled. | 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.