aevent
AEvent integration. Manage data, records, and automate workflows. Use when the user wants to interact with AEvent data.
Install with Tessl CLI
npx tessl i github:membranedev/application-skills --skill aevent72
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
67%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 integration target (AEvent) and includes an explicit 'Use when' clause, which is good. However, the capabilities listed are vague ('manage data, records, automate workflows') and could apply to almost any integration. The description would benefit from specific AEvent actions and more natural trigger terms users would actually say.
Suggestions
Replace generic actions with specific AEvent capabilities (e.g., 'Create events, manage attendee registrations, track check-ins, export participant lists')
Add natural trigger terms users would say, such as 'event registration', 'attendees', 'event management', 'webinar data', or specific AEvent features
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (AEvent) and mentions some actions ('Manage data, records, and automate workflows'), but these are generic and not comprehensive - doesn't specify what kind of data, what records, or what workflows. | 2 / 3 |
Completeness | Has both 'what' (manage data, records, automate workflows) and explicit 'when' clause ('Use when the user wants to interact with AEvent data'), though both are somewhat generic. | 3 / 3 |
Trigger Term Quality | Includes 'AEvent' and 'AEvent data' as trigger terms, but lacks natural variations users might say (e.g., event management, event registration, attendee data, event automation). | 2 / 3 |
Distinctiveness Conflict Risk | 'AEvent' is a specific platform name which helps distinctiveness, but 'manage data, records, and automate workflows' is generic enough to potentially overlap with other integration or automation skills. | 2 / 3 |
Total | 9 / 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 guidance for AEvent integration with good command examples and a useful actions reference table. However, it includes unnecessary introductory explanation, lacks validation/error handling in workflows, and has an incorrect documentation link. The structure is adequate but could benefit from splitting the actions reference into a separate file.
Suggestions
Remove the introductory paragraph explaining what AEvent is - Claude doesn't need this context
Add validation steps and error handling guidance (e.g., 'If connection fails, check X' or 'Verify connection with membrane connection list')
Fix the incorrect documentation URL (currently points to Adobe Analytics docs)
Move the 'Popular actions' table to a separate ACTIONS.md reference file to improve progressive disclosure
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanation (e.g., 'AEvent is an event management platform that helps users plan...') and the overview section with bullet points adds little value. However, most content is reasonably efficient with clear CLI commands. | 2 / 3 |
Actionability | Provides fully executable CLI commands throughout with specific flags, options, and examples. The action table, proxy request options, and step-by-step connection setup are all copy-paste ready. | 3 / 3 |
Workflow Clarity | Steps are listed for setup and connection, but there are no validation checkpoints or error recovery guidance. The workflow for first-time setup vs. existing connections is clear, but missing feedback loops for failed commands or authentication issues. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but everything is in one file. The popular actions table could be a separate reference file, and there are no links to external detailed documentation despite mentioning 'Official docs' with an incorrect URL (Adobe Analytics docs for AEvent). | 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.