aevent
AEvent integration. Manage data, records, and automate workflows. Use when the user wants to interact with AEvent data.
68
61%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/aevent/SKILL.mdQuality
Discovery
57%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 benefits from having the 'AEvent' product name as a clear identifier and includes an explicit 'Use when' clause, but it is severely lacking in specificity about what concrete actions the skill can perform. The vague terms 'manage data, records, and automate workflows' could apply to virtually any integration skill and don't help Claude understand the skill's actual capabilities.
Suggestions
Replace vague terms like 'manage data, records, and automate workflows' with specific actions such as 'create events, manage attendee registrations, track RSVPs, send event notifications'.
Add natural trigger terms users might say, such as 'event management, attendees, registrations, event scheduling, AEvent API'.
Expand the 'Use when' clause with more specific triggers, e.g., 'Use when the user mentions AEvent, event registrations, attendee management, or needs to automate event-related workflows.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'manage data, records, and automate workflows' without specifying concrete actions. What kind of data? What records? What workflows? These are abstract terms that don't describe specific capabilities. | 1 / 3 |
Completeness | It does answer both 'what' (manage data, records, automate workflows) and 'when' (Use when the user wants to interact with AEvent data). While the 'what' is vague, the structure explicitly addresses both questions with a 'Use when...' clause. | 3 / 3 |
Trigger Term Quality | It includes 'AEvent' as a product-specific keyword and 'data' and 'workflows', but lacks natural variations or specific terms users might say (e.g., event registration, attendees, tickets, event scheduling). The term 'AEvent' itself is a useful trigger but coverage of related natural language terms is thin. | 2 / 3 |
Distinctiveness Conflict Risk | 'AEvent' as a product name provides some distinctiveness, but 'manage data, records, and automate workflows' is extremely generic and could overlap with many other integration or data management skills. The AEvent branding helps but the rest is too broad. | 2 / 3 |
Total | 8 / 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.
The skill provides solid, actionable CLI commands for integrating with AEvent via Membrane, with good coverage of the full workflow from setup to execution. Key weaknesses include unnecessary introductory fluff, a seemingly incorrect documentation link (Adobe Analytics URL for AEvent), and missing validation/confirmation steps for destructive operations like deletions and banning registrants.
Suggestions
Remove the introductory paragraph explaining what AEvent is and the incorrect Adobe Analytics docs link — Claude doesn't need this context and the link appears wrong.
Add confirmation/validation steps for destructive operations (delete-webinar, delete-form, ban-registrant) such as verifying the resource exists before deletion and confirming success after.
Flesh out or remove the sparse 'AEvent Overview' section (Event > Attendee, Calendar) — it's too vague to be useful in its current form.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explaining what AEvent is (event management platform, used by organizers, etc.) is unnecessary context Claude doesn't need. The overview section with just 'Event > Attendee, Calendar' is too vague to be useful. The docs link points to Adobe Analytics, which seems incorrect. However, the CLI commands and workflow sections are reasonably efficient. | 2 / 3 |
Actionability | The skill provides fully executable, copy-paste ready CLI commands for every step: installation, authentication, connecting, searching actions, creating actions, running actions with parameters. The popular actions table gives concrete action keys and descriptions. All commands include proper flags like --json and --connectionId. | 3 / 3 |
Workflow Clarity | The workflow from install → authenticate → connect → search/create → run actions is present and sequenced, but there are validation gaps. The delete operations (delete-webinar, delete-form, delete-media-file, ban-registrant) are listed without any confirmation or validation steps. The action creation polling workflow is well-documented with error states, but destructive operations lack feedback loops. | 2 / 3 |
Progressive Disclosure | The content is structured with clear headers and sections, but it's somewhat monolithic — the popular actions table and all workflow details are inline. The overview section ('Event > Attendee > Calendar') is too sparse to serve as a useful overview. No references to external files for advanced topics or detailed API schemas. | 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 | |
- Repository
- membranedev/application-skills
- Commit
56d7336
- 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.