aimtell
Aimtell integration. Manage data, records, and automate workflows. Use when the user wants to interact with Aimtell data.
44
45%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/aimtell/SKILL.mdQuality
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 almost entirely on the product name 'Aimtell' for differentiation while providing no specific information about what Aimtell is or what concrete actions the skill enables. The generic phrases 'manage data, records, and automate workflows' are boilerplate that could describe any integration skill, making it unhelpful for Claude to understand when to select this skill over others.
Suggestions
Replace generic phrases with concrete Aimtell-specific actions (e.g., 'manage push notification campaigns, track subscribers, configure website notification settings').
Expand the 'Use when' clause with natural trigger terms users would say, such as 'push notifications, web push, subscriber segments, notification campaigns, Aimtell API'.
Add a brief explanation of what Aimtell is (e.g., 'web push notification platform') so Claude can match user requests even when they don't mention Aimtell by name.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'manage data, records, and automate workflows' without listing any concrete actions specific to Aimtell. These are generic phrases that could apply to virtually any integration. | 1 / 3 |
Completeness | It has a 'Use when' clause ('Use when the user wants to interact with Aimtell data'), but the 'what' is extremely generic and the 'when' is essentially just restating the name without adding meaningful trigger guidance. | 2 / 3 |
Trigger Term Quality | It includes 'Aimtell' as a key trigger term which is specific, but lacks any natural keywords related to what Aimtell actually does (e.g., push notifications, web notifications, subscriber management, campaigns). Users familiar with Aimtell would likely use domain-specific terms. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'Aimtell' provides some distinctiveness since it's a specific product name, but the generic 'manage data, records, and automate workflows' language is identical to what dozens of other integration skills might say, risking overlap. | 2 / 3 |
Total | 7 / 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 actionable, executable CLI commands for interacting with Aimtell through Membrane, which is its primary strength. However, it suffers from significant verbosity — explaining what Aimtell is, including a table of 20 actions all with 'No description', and repeating generic Membrane boilerplate that isn't Aimtell-specific. The workflow covers connection setup well but lacks validation steps for destructive operations.
Suggestions
Remove the introductory paragraph explaining what Aimtell and web push notifications are — Claude already knows this. Start directly with the integration workflow.
Either add meaningful descriptions to the popular actions table or remove entries with 'No description' to reduce token waste.
Add a verification step after destructive operations (e.g., delete-campaign) such as confirming the deletion by listing campaigns afterward.
Extract the generic Membrane CLI setup, authentication, and proxy request documentation into a shared reference file, keeping only Aimtell-specific content in this skill.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explains what Aimtell is and what web push notifications are — concepts Claude already knows. The overview section listing entities adds little value without descriptions. The popular actions table has 'No description' for every entry, wasting tokens. Much of the Membrane CLI setup and connection flow is generic boilerplate not specific to Aimtell. | 1 / 3 |
Actionability | The skill provides fully executable CLI commands for every step: installation, authentication, connection setup, action discovery, action execution, and proxy requests. Commands are copy-paste ready with clear flag descriptions and JSON output options. | 3 / 3 |
Workflow Clarity | The connection flow has a reasonable sequence with state-based branching (READY, CLIENT_ACTION_REQUIRED, errors), but there are no explicit validation checkpoints after running actions or proxy requests. The workflow for destructive operations like delete-campaign lacks any confirmation or verification steps. | 2 / 3 |
Progressive Disclosure | The content is structured with headers and sections, but it's a monolithic file with no references to supporting documents. The lengthy popular actions table and detailed proxy request documentation could be split into separate reference files. No bundle files exist to offload content to. | 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 | |
- 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.