CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

aevent

AEvent integration. Manage data, records, and automate workflows. Use when the user wants to interact with AEvent data.

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/aevent/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable, built around concrete executable CLI commands with good connection-state handling, and is well organized as a single file. Its main weaknesses are a dangling 'Step 2' reference, missing validation for destructive operations, some filler sections, and an incorrect documentation URL.

Suggestions

Fix the dangling 'skip to Step 2' reference by actually numbering the workflow steps (e.g. Step 1: connect, Step 2: search/run actions).

Add verification guidance before destructive actions (delete-webinar, delete-form, ban-registrant), e.g. run get-webinar first to confirm the ID and confirm with the user before deleting.

Remove the filler 'AEvent Overview' section and trim the marketing-style intro; correct the 'Official docs' URL, which currently points to Adobe Analytics documentation.

DimensionReasoningScore

Conciseness

The body is mostly command-and-table driven and assumes competence, but includes unnecessary material: the marketing-style intro ('It's used by event organizers, marketers, and businesses of all sizes...'), a nearly empty 'AEvent Overview' section, and filler like 'Use action names and parameters as needed.' Not 4 because these padded sections are clearly trimmable.

3 / 5

Actionability

Concrete, copy-paste-ready commands throughout (npm install, membrane login, connection ensure with --wait polling, action list/run, request proxy with a full flag table). Not 5 because there is no worked example of running an action with real input, the action identifier ('Key' vs 'id') is ambiguous, and the 'Official docs' URL points to Adobe Analytics rather than AEvent.

4 / 5

Workflow Clarity

A rough sequence exists (install → authenticate → connect → poll state → search actions → run), with good state-based checkpoints for connections. Not 4 because 'skip to Step 2' references a step that is never defined, and destructive actions (delete-webinar, delete-form, ban-registrant) have no validation/verification steps — the rubric caps workflow clarity at 3 for this.

3 / 5

Progressive Disclosure

A single-file skill with well-organized, clearly headed sections and no nested references. Not 5 because the 20-row 'Popular actions' table is inline API-reference-style content that would fit better in a separate reference file, and the skill exceeds the under-50-lines simple-skill threshold.

4 / 5

Total

14

/

20

Passed

Description

50%Weight 40%Scale 1-5

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 has an explicit 'Use when...' trigger and a distinctive product name, but the capability statement is generic ('manage data, records, and automate workflows') and omits the natural vocabulary of the domain (webinars, registrants, forms, events). It reads like a template description that was never customized to AEvent's actual capabilities.

Suggestions

Replace the generic 'Manage data, records, and automate workflows' with concrete AEvent capabilities, e.g. 'Create and delete webinars, list and ban registrants, manage forms, tags, and media files'.

Add domain trigger terms users would naturally say: webinars, events, registrants, attendees, event registration, forms.

Make the 'when' clause more specific, e.g. 'Use when the user wants to manage AEvent webinars, registrants, or event data.'

DimensionReasoningScore

Specificity

"Manage data, records, and automate workflows" names the domain (AEvent) but the actions are entirely generic, matching the 'names the domain but actions are minimal or generic' anchor. It does not reach 3 because no concrete capability like 'create webinars' or 'list registrants' is stated.

2 / 5

Completeness

Both parts are present: what ("Manage data, records, and automate workflows") and an explicit when ("Use when the user wants to interact with AEvent data"). Not 5 because the 'what' is generic and the 'when' lacks concrete trigger phrases; not 3 because the 'Use when...' clause is explicit.

4 / 5

Trigger Term Quality

The only distinctive keyword is the product name "AEvent"; natural phrases a user would actually say (webinar, registrant, attendee, event management) are all missing. It is not 3 because the keyword set is one product name plus generic terms rather than 'some relevant keywords'.

2 / 5

Distinctiveness Conflict Risk

"AEvent" is a distinctive product name and the trigger is scoped to AEvent data, making overlap with unrelated skills minor. It sits between 3 and 4 since generic terms like "records" and "automate workflows" could pull in data-management or automation skills, so 4 rather than a clear 5 fit.

4 / 5

Total

12

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

membranedev/application-skills

Path

skills/aevent/SKILL.md

Revision

f484c82

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill