Name: evenium
Rating: 56.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

evenium

Evenium integration. Manage Events, Users, Roles. Use when the user wants to interact with Evenium data.

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

67%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 body is a strong, command-driven integration guide with a well-sequenced connection workflow that includes genuine validation feedback loops. Its main weaknesses are mild verbosity in the overview/editorial passages and placeholder-only examples with a couple of navigation gaps.

Suggestions

Tighten the overview paragraph and remove editorial padding like 'so you can focus on the integration logic rather than auth plumbing' to reclaim tokens.

Add at least one fully-worked end-to-end example with real-looking values (e.g., a concrete connection ID and the 'list-guests' action) instead of only placeholders.

Resolve the dangling 'Step 2' reference by labeling the next section accordingly, and consider moving the entity list and Popular-actions table into a reference file to reduce inline bulk.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and dominated by executable commands, but the platform-overview paragraph, editorial asides ('focus on the integration logic rather than auth plumbing'), and the 35-item entity list add tokens that could be trimmed.	3 / 5
Actionability	Provides many concrete, copy-paste-ready CLI commands plus real action keys and proxy flags; minor gaps remain because every example uses placeholders (CONNECTION_ID, <actionId>) with no fully-worked real example.	4 / 5
Workflow Clarity	The connection flow is a clear state-machine sequence with explicit checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a poll-act-repoll feedback loop; gaps are the unlabeled 'Step 2' reference and missing validation around destructive proxy/action calls.	4 / 5
Progressive Disclosure	Well-organized into clear topical sections with no external references needed for a self-contained CLI skill; minor gaps are the inline entity list and 16-row action table that could live in a reference file, plus a dangling 'Step 2' reference.	4 / 5
	Total	15 / 20 Passed

Description

62%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 is functional and distinct thanks to the named Evenium brand, with an explicit 'Use when' trigger clause covering both what and when. It is held back by a generic action verb ('Manage') and a somewhat abstract trigger phrase that lacks natural user vocabulary.

Suggestions

Replace the generic verb 'Manage' with several concrete actions (e.g., 'Create and manage events, register guests, sync contacts, and pull reports').

Make the trigger phrase more natural and varied: 'Use when the user wants to manage Evenium events, guests, registrations, or contacts.'

Mention a few more representative entities (e.g., guests, registrations, contacts) to broaden trigger coverage beyond Events/Users/Roles.

Dimension	Reasoning	Score
Specificity	Names the Evenium domain and enumerates concrete entities ('Manage Events, Users, Roles'), but the verb 'Manage' is generic and coverage is far from comprehensive given the body lists ~30 entities.	3 / 5
Completeness	Explicitly states both what ('Manage Events, Users, Roles') and when ('Use when the user wants to interact with Evenium data'); the 'when' clause is present but could be more concrete.	4 / 5
Trigger Term Quality	Contains the distinct brand keyword 'Evenium' plus entity terms, but the trigger phrasing 'interact with Evenium data' is generic and misses natural variations a user would actually say.	3 / 5
Distinctiveness Conflict Risk	Evenium is a specific named application, giving a clear niche with minimal conflict risk; the generic 'interact with Evenium data' phrasing is the only thing keeping it from a 5.	4 / 5
	Total	14 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
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/evenium/SKILL.md
Commit: f484c82

Reviewed: 5 days 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.