Name: addevent
Rating: 52.8 (1 reviews)
Author: membranedev

addevent

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

Quality

58%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/addevent/SKILL.md

Quality

Content

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 functional integration skill with strong actionability and clear workflow sequencing for the connection lifecycle. Its main weaknesses are moderate verbosity (introductory fluff, a large table with empty descriptions) and a monolithic structure that could benefit from splitting detailed reference content into separate files. The Membrane CLI patterns are well-documented with executable commands throughout.

Suggestions

Remove or drastically shorten the introductory paragraph about what Addevent is — Claude already knows this and it wastes tokens.

Either add actual descriptions to the popular actions table entries or remove the table entirely, since 20 rows of 'No description' add bulk without value.

Consider splitting the proxy requests section and detailed CLIENT_ACTION_REQUIRED handling into a separate reference file to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The skill includes some unnecessary explanatory content (e.g., 'Addevent is a platform that simplifies event scheduling and ticketing...') and the popular actions table has 'No description' for every entry, adding bulk without value. The Membrane CLI setup and auth flow sections are reasonably efficient but could be tighter.	2 / 3
Actionability	The skill provides concrete, copy-paste-ready CLI commands for every step: installation, authentication, connection setup, action discovery, action execution, and proxy requests. Flag tables and JSON input examples are specific and executable.	3 / 3
Workflow Clarity	The multi-step connection workflow is clearly sequenced with explicit state checks (READY, BUILDING, CLIENT_ACTION_REQUIRED, errors), polling instructions, and conditional branching. The overall flow from install → auth → connect → discover → run is well-structured with validation checkpoints at each state transition.	3 / 3
Progressive Disclosure	The content is reasonably organized with clear sections, but it's somewhat monolithic for its length. The popular actions table with 20 rows of 'No description' could be trimmed or moved to a reference file. There are no bundle files or external references beyond the API docs URL, and the content could benefit from splitting detailed proxy/auth flows into separate files.	2 / 3
	Total	10 / 12 Passed

Description

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, and automate workflows') are boilerplate phrases that could apply to virtually any integration, providing no meaningful guidance for skill selection. The description needs concrete, domain-specific actions and richer trigger terms.

Suggestions

Replace generic phrases with specific AddEvent capabilities, e.g., 'Create and manage calendar events, generate add-to-calendar links, track RSVPs, and send event invitations.'

Expand trigger terms to include natural user language like 'calendar events', 'event scheduling', 'RSVP tracking', 'add-to-calendar links', or 'event invitations'.

Improve the 'Use when' clause with specific scenarios, e.g., 'Use when the user mentions AddEvent, calendar event creation, RSVP management, or generating shareable event links.'

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 phrases 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 trigger guidance.	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 phrases 'manage data, records, and automate workflows' could easily overlap with dozens of other integration skills. Without specifying event/calendar-related functionality, it's not clearly distinguishable.	2 / 3
	Total	7 / 12 Passed

Validation

90%

Warnings & errors only

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
Path: skills/addevent/SKILL.md
Commit: f484c82

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.