aevent
AEvent integration. Manage data, records, and automate workflows. Use when the user wants to interact with AEvent data.
58
67%
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/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 relies heavily on the 'AEvent' brand name for differentiation but fails to describe any concrete capabilities or specific use cases. The 'Use when' clause is present but too vague to be truly helpful for skill selection. The description reads more like a generic integration template than a useful guide for choosing this skill.
Suggestions
Replace vague terms like 'manage data, records, and automate workflows' with specific actions such as 'create events, manage attendee registrations, track RSVPs, send invitations'.
Expand trigger terms to include natural phrases users would say, such as 'event registration', 'attendee list', 'event scheduling', or specific AEvent entity names.
Make the 'Use when' clause more specific, e.g., 'Use when the user mentions AEvent, event registrations, attendee tracking, or needs to automate event-related workflows.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'manage data, records, and automate workflows' without listing any 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), with an explicit 'Use when' clause. While the content is vague, the structure is complete. | 3 / 3 |
Trigger Term Quality | It includes 'AEvent' as a product-specific keyword which is useful, and 'data', 'records', 'workflows' are somewhat relevant but generic. It lacks specific trigger terms a user might naturally say, such as event registration, attendee management, or specific AEvent features. | 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 description doesn't clearly carve out a unique niche beyond the product name. | 2 / 3 |
Total | 8 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable integration skill with clear CLI commands and well-structured connection workflows including state-based error handling. Its main weaknesses are some unnecessary introductory fluff (explaining what AEvent is), an incorrect official docs URL pointing to Adobe Analytics, and a vague overview section that adds no value. The workflow clarity is a notable strength with explicit branching logic for connection states.
Suggestions
Remove the introductory paragraph explaining what AEvent is and who uses it — Claude doesn't need this context to execute the integration.
Fix the official docs URL which incorrectly points to Adobe Analytics (adobe.io) instead of AEvent documentation.
Either flesh out the 'AEvent Overview' section with actionable detail about the data model or remove it entirely — 'Event → Attendee, Calendar' is too vague to be useful.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explaining what AEvent is and who uses it is unnecessary context for Claude. The overview section ('Event → Attendee, Calendar') is too vague to be useful. However, the CLI commands and action tables are reasonably efficient. The official docs link points to Adobe Analytics docs, which appears to be an error. | 2 / 3 |
Actionability | The skill provides fully executable, copy-paste-ready CLI commands for every step: installation, authentication, connection setup, action discovery, action execution, and proxy requests. The popular actions table with keys and descriptions is concrete and immediately usable. | 3 / 3 |
Workflow Clarity | The connection workflow is clearly sequenced with explicit state-based branching (READY, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR/SETUP_FAILED), polling instructions with --wait flag, and clear next steps for each state. The headless auth flow includes a feedback loop (login → get code → complete). The overall flow from install → auth → connect → discover → run is well-structured. | 3 / 3 |
Progressive Disclosure | The content is reasonably organized with clear sections, but it's a single monolithic file with no references to supporting documents. The proxy request details and the full popular actions table could potentially be split out. However, for a skill of this size (~150 lines), inline content is acceptable, though the structure could be tighter. | 2 / 3 |
Total | 10 / 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.