addevent
Addevent integration. Manage data, records, and automate workflows. Use when the user wants to interact with Addevent data.
61
52%
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/addevent/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 is too generic and fails to leverage the specific domain of AddEvent (calendar/event management). The actions described ('manage data, records, automate workflows') are boilerplate that could apply to virtually any integration. The description needs concrete, domain-specific actions and richer trigger terms related to event management.
Suggestions
Replace generic actions with AddEvent-specific capabilities such as 'create calendar events, manage RSVPs, generate add-to-calendar links, track event attendance'.
Expand trigger terms to include natural user language like 'calendar events', 'event scheduling', 'RSVP', 'add to calendar', 'event invitations', or 'event links'.
Improve the 'Use when' clause with specific scenarios, e.g., 'Use when the user wants to create or manage calendar events, generate shareable event links, or track RSVPs through AddEvent.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'manage data, records, and automate workflows' without specifying any concrete actions. It doesn't explain what kind of data, what records, or what workflows — these are generic terms that could apply to almost any integration. | 1 / 3 |
Completeness | It has a weak 'what' (manage data, records, automate workflows) and a 'when' clause ('Use when the user wants to interact with Addevent data'), but the 'when' is essentially just restating the 'what' in different words without providing explicit, useful triggers. | 2 / 3 |
Trigger Term Quality | It includes 'Addevent' as a keyword which is the specific service name users would mention, but lacks natural variations or specific terms users might say like 'calendar events', 'event scheduling', 'RSVP', 'event invitations', or 'add to calendar links'. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'Addevent' provides some distinctiveness since it's a specific service, but the generic terms 'manage data, records, and automate workflows' could easily overlap with dozens of other integration skills. Without specifying event/calendar-related functionality, it risks conflicting with other data management skills. | 2 / 3 |
Total | 7 / 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 commands for integrating with Addevent via Membrane, with clear authentication and action execution workflows. Its main weaknesses are the verbose introductory content, a bulky actions table with no descriptions adding little value, and missing validation/error-recovery steps for destructive operations like deletions.
Suggestions
Remove or drastically shorten the introductory paragraph about what Addevent is — Claude already knows this, and the official docs link suffices.
Either add meaningful descriptions to the popular actions table or remove entries with 'No description' and instead instruct to use `membrane action list --intent` for discovery.
Add explicit validation/confirmation steps before destructive operations (delete actions) — e.g., 'Always confirm with the user before running delete actions' or 'Verify the resource exists with a get action before deleting.'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanation (e.g., 'Addevent is a platform that simplifies event scheduling and ticketing' and the overview of what Addevent is). The popular actions table has 'No description' for every entry, adding bulk without value. However, the CLI commands and workflow steps are reasonably lean. | 2 / 3 |
Actionability | The skill provides concrete, copy-paste-ready CLI commands for every step: installation, authentication, connecting, searching actions, creating actions, and running actions with input parameters. The commands are specific and executable. | 3 / 3 |
Workflow Clarity | The multi-step processes (auth, connect, search, run) are presented in a logical sequence, and the action creation flow includes polling with state checking. However, there are no explicit validation checkpoints or error recovery feedback loops for destructive operations like delete actions, and the overall workflow lacks a clear numbered end-to-end sequence. | 2 / 3 |
Progressive Disclosure | The content is structured with headers and sections, but it's somewhat monolithic — the popular actions table (20 rows, all without descriptions) could be in a separate reference file. The link to official docs is good, but there are no references to supplementary files for advanced usage or detailed 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.