aimtell
Aimtell integration. Manage data, records, and automate workflows. Use when the user wants to interact with Aimtell data.
Install with Tessl CLI
npx tessl i github:membranedev/application-skills --skill aimtell61
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 relies entirely on the product name 'Aimtell' for identification while providing no meaningful information about what the skill actually does. The generic phrases 'manage data, records, and automate workflows' are boilerplate that could apply to virtually any integration, making it impossible for Claude to understand when this skill is appropriate beyond explicit mentions of 'Aimtell'.
Suggestions
Replace generic boilerplate with specific Aimtell capabilities (e.g., 'Create and manage web push notification campaigns, track subscriber analytics, configure automation triggers')
Add natural trigger terms users might say: 'push notifications', 'web notifications', 'subscriber campaigns', 'browser notifications'
Expand the 'Use when' clause with specific scenarios: 'Use when the user wants to send push notifications, manage notification subscribers, or analyze push campaign performance'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'Manage data, records, and automate workflows' without specifying what Aimtell actually does or what concrete actions are available. No specific capabilities are listed. | 1 / 3 |
Completeness | Has a 'Use when' clause but it's circular ('interact with Aimtell data'). The 'what' is generic boilerplate that could apply to any integration. Neither component provides meaningful guidance. | 2 / 3 |
Trigger Term Quality | Includes 'Aimtell' as a trigger term which users would say if they know the product, but lacks natural keywords describing what Aimtell is (web push notifications, subscriber management, campaigns) that users might use instead. | 2 / 3 |
Distinctiveness Conflict Risk | 'Aimtell' as a proper noun provides some distinctiveness, but 'Manage data, records, and automate workflows' is generic boilerplate that could describe dozens of integrations and risks false matches. | 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 Aimtell integration via Membrane, with good coverage of common operations. However, it wastes tokens explaining what Aimtell is, lacks validation/error handling guidance for multi-step workflows, and the popular actions table could be externalized for better progressive disclosure.
Suggestions
Remove the opening paragraph explaining what Aimtell is - Claude already knows this and it wastes tokens
Add validation checkpoints after key operations (e.g., 'Verify connection succeeded by running membrane connection list')
Include error handling guidance for common failure scenarios (auth failures, invalid action IDs, connection issues)
Move the popular actions table to a separate reference file and link to it from the main skill
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explains what Aimtell is (web push notifications, marketers, etc.) which Claude already knows. The overview section and best practices are reasonably efficient, but there's unnecessary context that could be trimmed. | 2 / 3 |
Actionability | Provides fully executable CLI commands throughout - installation, login, connection setup, action discovery, and proxy requests are all copy-paste ready with clear syntax and flag documentation. | 3 / 3 |
Workflow Clarity | Steps are listed sequentially for setup and connection, but there are no validation checkpoints or error recovery guidance. Missing feedback loops for operations like 'membrane connect' or action runs that could fail. | 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 overview section adds little value and the structure could be tighter. | 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.